Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.math > #510006 > unrolled thread
| Started by | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| First post | 2021-01-19 15:21 +0000 |
| Last post | 2021-02-03 09:57 -0600 |
| Articles | 20 on this page of 379 — 25 participants |
Back to article view | Back to sci.math
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-19 15:21 +0000
Re: A "conversation"? Python <python@python.invalid> - 2021-01-19 16:29 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-19 11:20 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-01-19 20:56 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-19 14:04 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-19 23:54 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-20 03:22 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-21 01:18 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-21 03:06 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-22 03:17 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-22 10:10 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-24 02:47 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-24 09:15 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-24 13:25 -0600
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-25 03:16 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-25 05:17 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-25 09:03 -0600
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-26 23:13 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-25 06:43 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-25 09:18 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-01-24 19:46 +0100
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-21 22:26 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-22 08:56 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-20 00:01 +0000
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-19 23:11 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-19 11:13 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-20 00:14 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-20 03:30 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-20 10:14 -0600
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-21 01:50 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-21 03:29 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-22 02:18 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-22 09:21 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-24 02:03 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-24 08:47 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-24 14:08 -0600
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-25 02:35 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-25 05:07 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-25 05:31 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-25 06:57 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-25 22:26 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-26 06:10 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-26 08:08 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-26 22:13 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 08:56 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-27 10:50 -0800
Re: A "conversation"? Patricio Whackmember <patty_whack@mitchmail.net> - 2021-01-27 14:17 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 14:19 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-28 06:05 -0800
Re: A "conversation"? Heywood Jablome <heywood@jablome.net> - 2021-01-28 07:37 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-28 09:24 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-29 12:44 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-30 03:35 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-01-30 08:06 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-30 05:12 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-01-30 08:35 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-30 08:43 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-30 08:45 -0600
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-01-30 21:10 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 02:13 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-31 11:51 -0600
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-02 02:24 +0000
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-01-31 13:42 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-30 05:22 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 02:10 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-01-31 11:26 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 03:22 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-31 05:56 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 06:03 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-31 11:55 -0600
Re: A "conversation"? Rear Admiral Melvin <ram@hotmail.net> - 2021-01-31 11:04 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-31 11:53 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-01-31 20:44 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 14:03 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 00:45 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 00:04 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 09:17 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 01:12 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 10:47 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 03:43 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 12:57 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 04:38 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 13:42 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 07:42 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-01 10:49 -0500
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 16:50 +0100
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-01-31 13:51 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-31 05:53 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 06:20 -0800
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-01-31 13:53 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-02-03 12:38 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-04 09:35 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-04 13:54 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-05 11:47 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-05 21:50 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-05 14:40 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-05 17:53 -0500
Re: A "conversation"? Python <python@python.invalid> - 2021-02-06 10:54 +0100
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-02-07 16:49 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-08 02:35 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-02-08 08:14 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-08 17:58 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-09 08:20 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-09 11:45 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-09 09:03 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-09 18:50 +0100
Re: A "conversation"? Python <python@python.invalid> - 2021-02-09 19:57 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-09 13:11 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-09 22:05 -0800
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-02-09 22:44 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-10 11:58 +0000
Re: A "conversation"? Python <python@python.invalid> - 2021-02-10 13:09 +0100
Re: A "conversation"? Peter <peterxpercival@hotmail.com> - 2021-02-10 16:38 +0000
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-10 13:34 +0000
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-10 06:06 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-10 15:43 +0100
Re: A "conversation"? Peter <peterxpercival@hotmail.com> - 2021-02-10 16:42 +0000
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-10 22:42 +0000
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-10 08:34 -0500
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-10 22:39 +0000
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-10 06:03 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-10 22:41 +0000
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-10 22:19 -0800
Re: A "conversation"? Jim Burns <james.g.burns@att.net> - 2021-02-11 05:40 -0500
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-11 11:54 +0000
Re: A "conversation"? Python <python@python.invalid> - 2021-02-11 13:07 +0100
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-11 16:05 +0000
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-11 12:01 -0500
Re: A "conversation"? Jim Burns <james.g.burns@att.net> - 2021-02-11 11:44 -0500
Re: A "conversation"? Python <python@python.invalid> - 2021-02-11 17:55 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 20:11 -0600
Re: A "conversation"? Jim Burns <james.g.burns@att.net> - 2021-02-11 11:15 -0500
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 07:12 -0600
Re: A "conversation"? Jim Burns <james.g.burns@att.net> - 2021-02-11 11:54 -0500
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 13:54 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-10 12:54 -0600
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-08 09:03 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-09 08:31 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-09 13:14 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 06:36 -0800
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-10 14:46 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 06:58 -0800
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-10 17:10 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-10 13:14 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 06:55 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-11 16:05 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 07:43 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-11 17:04 +0100
Re: A "conversation"? Python <python@python.invalid> - 2021-02-11 17:18 +0100
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-11 15:37 -0500
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-11 15:48 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 14:02 -0800
Re: A "conversation"? Jim Carrubba <jmic4@wlan2iot.co> - 2021-02-11 22:30 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 20:52 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 09:34 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 08:07 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 10:43 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 09:06 -0800
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-11 22:35 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 02:16 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-12 11:22 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 02:57 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-12 12:10 +0100
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-12 14:14 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 14:43 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-12 17:29 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-13 01:20 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-12 12:07 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 14:26 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-12 17:30 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-13 01:21 -0800
Re: A "conversation"? Wade Brewer <wadb@ultnatfs.ca> - 2021-02-13 08:23 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 02:20 -0800
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-12 13:21 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 14:24 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-14 23:42 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-15 09:01 -0800
Re: A "conversation"? Ralf Bader <bader@nefkom.net> - 2021-02-15 19:53 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-16 01:01 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-16 19:22 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 08:23 -0600
Re: A "conversation"? Ralf Bader <bader@nefkom.net> - 2021-02-17 05:30 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-17 04:48 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-17 08:07 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-17 06:13 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-17 09:25 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-17 06:43 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-17 10:42 -0500
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-17 07:34 -0500
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-15 22:23 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-16 01:02 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-16 22:21 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-17 04:58 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-17 06:08 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-17 06:23 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-17 22:33 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-18 02:22 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-18 03:07 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-19 01:26 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-19 02:22 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 05:22 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-21 22:42 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-22 02:27 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-19 05:09 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 05:29 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 08:30 -0600
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-20 10:31 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 23:30 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-21 06:04 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-21 15:07 -0500
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-21 14:51 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-21 21:48 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-21 22:03 -0600
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-22 07:34 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-22 02:45 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-22 03:16 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-20 10:43 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 12:52 -0600
Re: A "conversation"? Ralf Bader <bader@nefkom.net> - 2021-02-20 09:07 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 05:34 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 08:35 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-02-20 15:51 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 09:22 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 23:28 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-21 08:57 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-02-21 17:32 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-20 23:28 -0800
Re: A "conversation"? Alan Mackenzie <acm@muc.de> - 2021-02-21 10:05 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-22 02:19 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-22 03:14 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-02-23 06:20 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-28 22:38 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-01 02:42 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-01 04:10 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-01 05:21 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-01 05:31 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-01 05:41 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-01 22:27 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-02 01:21 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-02 16:04 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-02 22:37 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-04 03:36 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-03-04 13:21 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-04 07:44 -0600
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-03-04 06:56 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-04 09:48 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-03-05 05:46 +0100
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-04 22:02 -0800
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-05 06:00 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-07 22:30 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-08 04:09 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-08 07:37 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-08 10:22 -0600
Re: A "conversation"? Ganzhinterseher <claus.vonnesser@gmail.com> - 2021-03-09 09:48 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-03-09 19:03 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-09 10:33 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-03-09 20:20 +0100
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-11 01:01 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-03-11 10:13 +0100
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-09 22:16 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-11 01:05 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-11 22:18 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-12 03:06 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-12 03:50 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 09:44 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 09:41 -0600
Re: A "conversation"? Brodie Wiser <bdwi@committee.aero> - 2021-03-12 15:52 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 10:06 -0600
Re: A "conversation"? Jim Burns <james.g.burns@att.net> - 2021-03-09 17:07 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-11 01:02 -0800
Re: A "conversation"? * _Joseph W Smith - PhD_ *
The College of Applied Health Science
602 Eeast Green Street
Urbana, IL 61801
joseth@illinois.edu
. <joseth@illinois.edu> - 2021-03-11 11:55 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-03-12 03:11 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-03-12 12:18 +0100
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 09:47 -0600
Re: A "conversation"? Brodie Wiser <bdwi@committee.aero> - 2021-03-12 15:55 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 10:03 -0600
Re: A "conversation"? Brodie Wiser <bdwi@committee.aero> - 2021-03-12 16:14 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 10:38 -0600
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-03-12 09:03 -0800
Re: A "conversation"? Dan Christensen <Dan_Christensen@sympatico.ca> - 2021-03-12 11:41 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 09:33 -0600
Re: A "conversation"? Brodie Wiser <bdwi@committee.aero> - 2021-03-12 16:02 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-12 10:37 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-03-08 22:16 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-03-02 16:00 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-18 22:16 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-19 01:29 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 08:56 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-20 08:18 -0600
Re: A "conversation"? Eddy Scolaro <edsc2@nncasve.cl> - 2021-02-20 19:20 +0000
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-09 14:04 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 06:41 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-10 07:15 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 07:53 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-10 09:22 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-10 13:34 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 07:00 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-11 07:18 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 08:20 -0800
Re: A "conversation"? Gus Gassmann <horand.gassmann@gmail.com> - 2021-02-11 08:31 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 08:48 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 11:19 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-11 13:57 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-11 22:15 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-12 02:28 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-12 04:57 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-11 10:53 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-10 13:33 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-10 13:16 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-05 19:04 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-06 02:03 -0800
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-02-07 16:42 -0800
Re: A "conversation"? "Hoofington P. McSnort" <hoofsnort@plotonium.com> - 2021-01-31 06:57 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-31 22:20 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 00:03 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-01 04:08 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-01 04:32 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-02-01 13:38 +0100
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-01 22:33 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-02 04:34 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-02 05:39 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-02 06:24 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-02 10:18 -0500
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-02 20:40 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-02 22:09 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-03 07:22 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-03 12:05 -0600
Re: A "conversation"? Python <python@python.invalid> - 2021-02-02 14:43 +0100
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-26 22:10 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 08:13 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-01-27 11:55 -0500
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-27 11:20 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 09:29 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 09:33 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-27 15:09 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 14:01 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-29 22:14 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-01-27 22:03 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-26 17:20 +0000
Re: A "conversation"? Eram semper recta <thenewcalculus@gmail.com> - 2021-01-26 10:46 -0800
Re: A "conversation"? Richard Cranium <dickhead@hotmail.net> - 2021-01-26 10:49 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-27 08:24 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-29 00:48 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-29 05:07 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-30 02:06 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-30 03:44 -0800
Re: A "conversation"? Python <python@python.invalid> - 2021-01-30 13:14 +0100
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-01-31 01:47 +0000
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-01-30 21:35 -0600
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-01-30 20:04 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-01-31 03:13 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-02 03:25 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-02 06:10 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-03 03:14 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-03 07:19 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-03 09:56 -0600
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-03 11:13 -0600
Re: A "conversation"? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-02-03 14:18 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-04 01:58 +0000
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-04 09:43 -0800
Re: A "conversation"? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2021-02-05 03:03 +0000
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-03 22:17 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-04 09:31 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-04 22:08 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-05 11:54 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-07 22:41 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-08 02:37 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-08 03:22 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-09 08:19 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-09 12:22 -0600
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 06:32 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-09 22:04 -0800
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-10 06:44 -0800
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-10 22:17 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-08 09:53 -0600
Re: A "conversation"? "zelos...@gmail.com" <zelos.malum@gmail.com> - 2021-02-02 22:09 -0800
Re: A "conversation"? FromTheRafters <erratic@nomail.afraid.org> - 2021-02-03 07:33 -0500
Re: A "conversation"? WM <wolfgang.mueckenheim@hs-augsburg.de> - 2021-02-03 07:21 -0800
Re: A "conversation"? Sergio <invalid@invalid.com> - 2021-02-03 09:57 -0600
Page 12 of 19 — ← Prev page 1 … 10 11 [12] 13 14 … 19 Next page →
| From | Sergio <invalid@invalid.com> |
|---|---|
| Date | 2021-02-20 08:35 -0600 |
| Message-ID | <s0r6n6$29l$1@gioia.aioe.org> |
| In reply to | #512592 |
On 2/20/2021 7:34 AM, WM wrote:
> Ralf Bader schrieb am Samstag, 20. Februar 2021 um 09:07:39 UTC+1:
>> On 02/19/2021 10:26 AM, WM wrote:
>>> Gus Gassmann schrieb am Donnerstag, 18. Februar 2021 um 12:07:22
>>> UTC+1:
>>>> On Thursday, 18 February 2021 at 06:22:52 UTC-4, WM wrote:
>>>>> zelos...@gmail.com schrieb am Donnerstag, 18. Februar 2021 um
>>>>> 07:33:19 UTC+1:
>>>>>>> Then don't pick but use a mathematical proof: E(n+1) = E(n) \
>>>>>>> {n}. This shows: As long as the empty endsegment is not
>>>>>>> reached, the intersection is not empty.
>>>>>> Nope, it only shows no endsegment is empty, the intersection fo
>>>>>> all is still empty because no element exists in all of them.
>>>>> All non-empty endsegments have a non-empty intersection, because
>>>>> every endsegment contains at least one natural number which is in
>>>>> all other endsegments.
>>>>>>> Find non-empty endsegments with empty intersection. Fail.
>>>>>> All fo them, intersection fo ALL of them is empty, hence I have
>>>>>> done it.
>>>>> "All of them" includes the empty endsegment. So the intersection
>>>>> is empty.
>>>> There is no empty end segment.
>>>
>>> Then there is no empty intersection. Note that every endsegment
>>> having an element has an element in common with all other noin empty
>>> endegments. This is easy to prove by inclusion monotony.
>
>> This is obviously wrong.
>
> In fact it is exclusion monotony: Every natnumber that has been lost will never return. This implies that every non-empty endsegment has an element in common with every other non-empty endsegment.
Exclusion monotony Ants
Non-empty Ants
Has been lost will never return Ants
>
>> You are too stupid for mathematics.
>
> Exclusion monotony is mathematics.
but you are not using that here.
>
>>>> By your own definition, every end segment has to contain at least
>>>> one natural number an infinite number of successors.
>>>
>>> That is true for all definable endsegments. All definable endsegments
>>> have infinite intersection:
>>>
>>> ∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} = E(k) /\ |E(k)| = ℵo .
>>>
>>> Definable endsegments cannot have an empty intersection. When you
>>> show that no natnumber remains forever then it is clear that all
>>> natnumbers get lost. The result is an empty endsegment. Note that all
>>> intersections of endsegments are endsegments themselves.
>> Idiotic nonsense.
>
> Why? Is the equation incorrect? Or what is your handicap in understanding mathematics?
The handicap is on your side, where you fail to provide valid proofs, or
correct definitions of things you say.
>
> Regards, WM
>
[toc] | [prev] | [next] | [standalone]
| From | Python <python@python.invalid> |
|---|---|
| Date | 2021-02-20 15:51 +0100 |
| Message-ID | <603121f2$0$27449$426a74cc@news.free.fr> |
| In reply to | #512603 |
Sergio wrote: > Crank Wolfgang Mueckenheim, aka WM wrote: ... >> Exclusion monotony is mathematics. > but you are not using that here. This is business as usual for Pr Wolfgang Mueckenheim, crank from Hochschule Augsburg. Invoking afterwards arguments that wasn't at all involved in his original alleged "proof". This is usually a last resort sophistry when everything else fails. Typically he's doing so with this "inclusion monotony", acting as if it was some kind of theorem (which it is NOT) and not merely a property. I wonder what "exclusion monotony" is even supposed to mean, this is a new one from crank Wolfgang Mueckenheim, from Hochschule Augsburg.
[toc] | [prev] | [next] | [standalone]
| From | Sergio <invalid@invalid.com> |
|---|---|
| Date | 2021-02-20 09:22 -0600 |
| Message-ID | <s0r9gb$19kg$1@gioia.aioe.org> |
| In reply to | #512604 |
On 2/20/2021 8:51 AM, Python wrote: > Sergio wrote: >> Crank Wolfgang Mueckenheim, aka WM wrote: > ... >>> Exclusion monotony is mathematics. >> but you are not using that here. > > This is business as usual for Pr Wolfgang Mueckenheim, crank from > Hochschule Augsburg. Invoking afterwards arguments that wasn't at all > involved in his original alleged "proof". This is usually a last resort > sophistry when everything else fails. > > Typically he's doing so with this "inclusion monotony", acting > as if it was some kind of theorem (which it is NOT) and not > merely a property. > > I wonder what "inclusion monotony" is even supposed to mean, this is a > new one from crank Wolfgang Mueckenheim, from Hochschule Augsburg. > > > this "proves" the existence of two formally Dark Ants Tribes; 1. Inclusion Monotony Tribe of Ants Ants that line up in increasing size (mass or volume) and Absorb Other Ants when the position in the line is found for them which maintains Monotony. 2. Exclusion Monotony Tribe of Ants Ants that line up in pecking order(like chickens) and Exclude Other Ants (by pecking) if the break Line (or sequence) Monotony. Notes: A. never mix the two, all hell will break loose. B. Ants not in either line are called Lineless Ants
[toc] | [prev] | [next] | [standalone]
| From | WM <wolfgang.mueckenheim@hs-augsburg.de> |
|---|---|
| Date | 2021-02-20 23:28 -0800 |
| Message-ID | <4283928a-ed5a-48f6-8c30-73874276281an@googlegroups.com> |
| In reply to | #512604 |
Python schrieb am Samstag, 20. Februar 2021 um 15:51:39 UTC+1: > > I wonder what "exclusion monotony" is even supposed to mean Exclusion monotony means that a sequence of sets loses elements which never return. The sequence of endsegments is a simple example. Of course I am using it: If an endsegment is not empty, then its elements are contained in all its predecessors. Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | Sergio <invalid@invalid.com> |
|---|---|
| Date | 2021-02-21 08:57 -0600 |
| Message-ID | <s0tsc7$fe2$1@gioia.aioe.org> |
| In reply to | #512661 |
On 2/21/2021 1:28 AM, WM wrote: > Python schrieb am Samstag, 20. Februar 2021 um 15:51:39 UTC+1: >> >> I wonder what "exclusion monotony" is even supposed to mean > > Exclusion monotony means that a sequence of sets loses elements which never return. The sequence of endsegments is a simple example. Of course I am using it: If an endsegment is not empty, then its elements are contained in all its predecessors. > > Regards, WM > there is no "monotony" in your definition or use. Fail.
[toc] | [prev] | [next] | [standalone]
| From | Python <python@python.invalid> |
|---|---|
| Date | 2021-02-21 17:32 +0100 |
| Message-ID | <60328b09$0$16168$426a74cc@news.free.fr> |
| In reply to | #512669 |
Sergio wrote: > On 2/21/2021 1:28 AM, WM wrote: >> Python schrieb am Samstag, 20. Februar 2021 um 15:51:39 UTC+1: >>> >>> I wonder what "exclusion monotony" is even supposed to mean >> >> Exclusion monotony means that a sequence of sets loses elements which never return. The sequence of endsegments is a simple example. Of course I am using it: If an endsegment is not empty, then its elements are contained in all its predecessors. >> >> Regards, WM >> > > there is no "monotony" in your definition or use. Fail. Crank Professor Wolfgang Mueckenheim, from Hochschule Augsburg has a very peculiar(*) relationship with definitions, proofs, counter- examples, equivalence (for instance he mysteriously professes that "if and only if" and double implication (equivalence) have a different logical meaning), honesty, integrity, logical deduction, academic freedom, innate racial abilities, women, students, teacher's duty and honest quotation. To say the least. (*) i.e. overwhelmingly weak
[toc] | [prev] | [next] | [standalone]
| From | WM <wolfgang.mueckenheim@hs-augsburg.de> |
|---|---|
| Date | 2021-02-20 23:28 -0800 |
| Message-ID | <b1228696-3f0c-4283-94f1-9206c2ed0ecfn@googlegroups.com> |
| In reply to | #512603 |
Sergio schrieb am Samstag, 20. Februar 2021 um 15:35:28 UTC+1: > On 2/20/2021 7:34 AM, WM wrote: > > Exclusion monotony is mathematics. > but you are not using that here. Exclusion monotony means that a sequence of sets loses elements which never return. The sequence of endsegments is a simple example. Of course I am using it: If an endsegment is not empty, then its elements are contained in all its predecessors. Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | Alan Mackenzie <acm@muc.de> |
|---|---|
| Date | 2021-02-21 10:05 +0000 |
| Message-ID | <s0tb9p$1k08$1@news.muc.de> |
| In reply to | #512660 |
WM <wolfgang.mueckenheim@hs-augsburg.de> wrote: > Sergio schrieb am Samstag, 20. Februar 2021 um 15:35:28 UTC+1: >> On 2/20/2021 7:34 AM, WM wrote: >> > Exclusion monotony is mathematics. >> but you are not using that here. > Exclusion monotony means that a sequence of sets loses elements which > never return. Rubbish. There is no operation "losing" in set theory. Neither is there an operation "returning". And there is no notion of time in set theory, so the use of "never" is wholly wrong. > The sequence of endsegments is a simple example. Of course I am using > it: If an endsegment is not empty, then its elements are contained in > all its predecessors. The last sentence is true, but utterly irrelevant to the fact that the intersection of all endsegments of N is empty. > Regards, WM -- Alan Mackenzie (Nuremberg, Germany).
[toc] | [prev] | [next] | [standalone]
| From | WM <wolfgang.mueckenheim@hs-augsburg.de> |
|---|---|
| Date | 2021-02-22 02:19 -0800 |
| Message-ID | <67e961fc-f410-457e-a0a1-caa8027e59a4n@googlegroups.com> |
| In reply to | #512666 |
Alan Mackenzie schrieb am Sonntag, 21. Februar 2021 um 11:05:54 UTC+1:
> WM <wolfgang.m...@hs-augsburg.de> wrote:
> > Exclusion monotony means that a sequence of sets loses elements which
> > never return.
> Rubbish. There is no operation "losing" in set theory.
Of course there is:
E(n+1) = E(n) \ {n} .
> Neither is there
> an operation "returning".
Of course there is. E U {n} returns n to E.
> And there is no notion of time in set theory,
There is use of indexed sequences, increasing and decreasing.
> so the use of "never" is wholly wrong.
"Never" means "for no index".
"so ist allerdings z eine völlig bestimmte Function der beiden stetigen Variablen x, y und in demselben Intervall (0 1) enthalten. Allein dann giebt es doch unendlich viele echte Brüche, welchen z niemals gleich wird, z. B." (Dedekind)
Die erste Bemerkung auf welche es hierbei ankommt ist, dass wenn P eine von 0 verschiedene abzählbare Menge ist niemals P' P sein kann (Cantor)
Would you like to read more about the use of "never" in mathematics?
> > The sequence of endsegments is a simple example. Of course I am using
> > it: If an endsegment is not empty, then its elements are contained in
> > all its predecessors.
> The last sentence is true, but utterly irrelevant to the fact that the
> intersection of all endsegments of N is empty.
It is utterly relevant to the fact that the intersection of all endsegments is an endsegment and cannot be empty without infinitely many finite predecessors.
E(n+1) = E(n) \ {n} .
Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | "zelos...@gmail.com" <zelos.malum@gmail.com> |
|---|---|
| Date | 2021-02-22 03:14 -0800 |
| Message-ID | <115fde3c-2187-43c6-b7e9-51c4ac0b77ecn@googlegroups.com> |
| In reply to | #512743 |
>Of course there is: That is not losing, again, it is not functions that changes stuff. It doesn't generate a set, it gives you a pre-existing set. >Why can you use more ordinals in ascending sequence (namely infinitely many) than in decreasing sequence (namely finitely many)? Are there decimal notations that can only be used in ascending sequences? For natural numbers we have a well ordering known in the ascending ordering and hence has an initial lowest there. That means it can go on. But due to this the reverse is always finite. Flip the ordering and you have the opposite. If you want both you can use integers, but then eitehr set will not be the entire set. >Mathematics is this: In a mapping however, when you write n --> f(n) then you have to be able to insert every individual n and to calculate its f(n). That however is not possible for crowds. We can do it for all members of the set so this is irrelevant. >That is an offending Cantor: I got no clue what you are writing, but if it is the well-ordering theorem the issue for you is that it requires NON-EMPTY sets, the set you speak of is empty and hence has none smallest.
[toc] | [prev] | [next] | [standalone]
| From | Ganzhinterseher <claus.vonnesser@gmail.com> |
|---|---|
| Date | 2021-02-23 06:20 -0800 |
| Message-ID | <13b9e89b-6d9a-4aa0-8150-f4e214e66255n@googlegroups.com> |
| In reply to | #512747 |
zelos...@gmail.com schrieb am Montag, 22. Februar 2021 um 12:14:29 UTC+1:
> >Mathematics is this: In a mapping however, when you write n --> f(n) then you have to be able to insert every individual n and to calculate its f(n). That however is not possible for crowds.
> We can do it for all members of the set so this is irrelevant.
There remain always aleph_0 members for which you cannot do it, namely those for which
∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} = E(k) /\ |E(k)| = ℵo
the intersection is not empty.
Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | "zelos...@gmail.com" <zelos.malum@gmail.com> |
|---|---|
| Date | 2021-02-28 22:38 -0800 |
| Message-ID | <b42a2288-8749-46fb-bbb1-180ce32dfa8an@googlegroups.com> |
| In reply to | #512830 |
tisdag 23 februari 2021 kl. 15:20:48 UTC+1 skrev Ganzhinterseher:
> zelos...@gmail.com schrieb am Montag, 22. Februar 2021 um 12:14:29 UTC+1:
>
> > >Mathematics is this: In a mapping however, when you write n --> f(n) then you have to be able to insert every individual n and to calculate its f(n). That however is not possible for crowds.
> > We can do it for all members of the set so this is irrelevant.
> There remain always aleph_0 members for which you cannot do it, namely those for which
> ∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} = E(k) /\ |E(k)| = ℵo
> the intersection is not empty.
> Regards, WM
I can do for all of them.
All you show is that any FINITE intersection isn't empty, not that the INFINITE intersection isn't empty.
How hard is this to understand?
[toc] | [prev] | [next] | [standalone]
| From | Ganzhinterseher <claus.vonnesser@gmail.com> |
|---|---|
| Date | 2021-03-01 02:42 -0800 |
| Message-ID | <c319a3a4-105f-4b66-8052-6cb1af568ea7n@googlegroups.com> |
| In reply to | #513162 |
zelos...@gmail.com schrieb am Montag, 1. März 2021 um 07:39:04 UTC+1:
> tisdag 23 februari 2021 kl. 15:20:48 UTC+1 skrev Ganzhinterseher:
> > zelos...@gmail.com schrieb am Montag, 22. Februar 2021 um 12:14:29 UTC+1:
> >
> > > >Mathematics is this: In a mapping however, when you write n --> f(n) then you have to be able to insert every individual n and to calculate its f(n). That however is not possible for crowds.
> > > We can do it for all members of the set so this is irrelevant.
> > There remain always aleph_0 members for which you cannot do it, namely those for which
> > ∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} = E(k) /\ |E(k)| = ℵo
> > the intersection is not empty.
> I can do for all of them.
>
> All you show is that any FINITE intersection isn't empty, not that the INFINITE intersection isn't empty.
Of course. Every definable intersection is finite. But there are infinite intersections. They are not definable. Every definable endsegment
E(k) = (k, k+1, k+2, ...)
is not empty and will not make an incoming infinite set of natural numbers empty.
The set of definitions of the effect of these endsegments
∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} =/= { } (*)
contains every endsegment that is applied in the intersection of definable endsegments
∩_def { E(1), E(2), E(3),... }. (**)
None is missing! The position of any endsegment does not play a role. Every endsegment that is last (*) will not change its effect when being not at last position like in (**). Therefore (**) cannot be empty. But the intersection
∩{ E(1), E(2), E(3),... }
is empty. This is impossible without other endsegments than are defined in (*).
Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | "zelos...@gmail.com" <zelos.malum@gmail.com> |
|---|---|
| Date | 2021-03-01 04:10 -0800 |
| Message-ID | <030f6249-693a-43ad-93a8-643a17ec495dn@googlegroups.com> |
| In reply to | #513173 |
>Of course. Every definable intersection is finite. But there are infinite intersections. They are not definable.
They are, get over it.
>is not empty and will not make an incoming infinite set of natural numbers empty.
But the intersection of all of them IS the empty set.
>∩_def { E(1), E(2), E(3),... }. (**)
∩_def { E(1), E(2), E(3),... }. =∩ {n e |N: E(n)} = {}
>is empty. This is impossible without other endsegments than are defined in (*).
It is empty because for any natural number n, E(n+1) doesn't have the elemnt, ergo no element is in all endsegments, thusly the intersection is empty
[toc] | [prev] | [next] | [standalone]
| From | Ganzhinterseher <claus.vonnesser@gmail.com> |
|---|---|
| Date | 2021-03-01 05:21 -0800 |
| Message-ID | <de52ce3a-1d63-4d36-9793-d47c11eb2203n@googlegroups.com> |
| In reply to | #513176 |
zelos...@gmail.com schrieb am Montag, 1. März 2021 um 13:10:25 UTC+1: > >Of course. Every definable intersection is finite. But there are infinite intersections. They are not definable. > They are, get over it. > >is not empty and will not make an incoming infinite set of natural numbers empty. > But the intersection of all of them IS the empty set. How can that be when their action does not depend on their position? > It is empty because for any natural number n, E(n+1) doesn't have the elemnt, ergo no element is in all endsegments, thusly the intersection is empty If that were right, then we would have a contradiction because the intersetion cannot be empty if the action of an endsegment does not depend on its position. Every endsegment that does not yield an empty intersection when appearing ta last position will not yield an empty intersection when appearing at not last position. Otherwise: Contradiction. Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | "zelos...@gmail.com" <zelos.malum@gmail.com> |
|---|---|
| Date | 2021-03-01 05:31 -0800 |
| Message-ID | <9a1508ff-97f2-4333-b1d1-e64648eb99a3n@googlegroups.com> |
| In reply to | #513179 |
>How can that be when their action does not depend on their position? There is no action, nothing is "changing", you are putting a set in and getting a set out Put in the set of all endsegments and the set that is the intersection is the empty set. >If that were right It is. >then we would have a contradiction because the intersetion cannot be empty if the action of an endsegment does not depend on its position Sets do not have order to them. An ORDERED set has an order and again, NO ACTION IS TAKING PLACE. Intersection is an operation on SETS, not ORDERED SETS. >Every endsegment that does not yield an empty intersection when appearing ta last position will not yield an empty intersection when appearing at not last position. This is you trying to weasle out of the fact that your intersections are finite, the order doesn't matter, and you try to propose for an INFINITE intersection. Stop being a liar.
[toc] | [prev] | [next] | [standalone]
| From | Ganzhinterseher <claus.vonnesser@gmail.com> |
|---|---|
| Date | 2021-03-01 05:41 -0800 |
| Message-ID | <4fe1e895-ec42-4bc3-9959-ecf7932643e1n@googlegroups.com> |
| In reply to | #513182 |
zelos...@gmail.com schrieb am Montag, 1. März 2021 um 14:31:32 UTC+1:
> >How can that be when their action does not depend on their position?
> There is no action, nothing is "changing", you are putting a set in and getting a set out
There is action. |N meeting E(k) in the intersection yields E(k). { } meeting E(k) in the intersection yiels { }.
> Put in the set of all endsegments and the set that is the intersection is the empty set.
Why should all endsegments be required? Because they have an effect. But the definable endsegments have not the effect you need.
>
> >If that were right
>
> It is.
> >then we would have a contradiction because the intersetion cannot be empty if the action of an endsegment does not depend on its position
> Sets do not have order to them.
Correct. Therefore the effet of an endsegment does not change when its position changes.
> An ORDERED set has an order and again, NO ACTION IS TAKING PLACE.
The you could do without endsegments at all.
>
> Intersection is an operation on SETS, not ORDERED SETS.
Therefore it does not matter whether the endegments are applied and checked in
∀k ∈ ℕ: ∩{E(1), E(2), ..., E(k)} =/= { } (*)
or applied in
∩{ E(1), E(2), E(3),... }. (**)
> >Every endsegment that does not yield an empty intersection when appearing ta last position will not yield an empty intersection when appearing at not last position.
> This is you trying to weasle out of the fact that your intersections are finite,
That is required to check the effect of an endsegment.
> the order doesn't matter,
That proves that the intersection of all checked endsegments is not empty.
Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | "zelos...@gmail.com" <zelos.malum@gmail.com> |
|---|---|
| Date | 2021-03-01 22:27 -0800 |
| Message-ID | <a95b1a7f-8800-4a75-a949-20aa9c86c68fn@googlegroups.com> |
| In reply to | #513185 |
>There is action. |N meeting E(k) in the intersection yields E(k). { } meeting E(k) in the intersection yiels { }.
There is no action cause there is no process.
>Why should all endsegments be required? Because they have an effect. But the definable endsegments have not the effect you need.
We can put in any set of endsegments and get a set out, any INFINITE set of endsegments yields the empty set. Including your "definable", whatever that means.
>That proves that the intersection of all checked endsegments is not empty.
Incorrect, as I have pointed out, any FINITE intersection is not empty, but any INFINITE is.
[toc] | [prev] | [next] | [standalone]
| From | Ganzhinterseher <claus.vonnesser@gmail.com> |
|---|---|
| Date | 2021-03-02 01:21 -0800 |
| Message-ID | <43bfd84d-e0df-43db-aaf2-487c702573c7n@googlegroups.com> |
| In reply to | #513246 |
zelos...@gmail.com schrieb am Dienstag, 2. März 2021 um 07:27:22 UTC+1:
> >Why should all endsegments be required? Because they have an effect. But the definable endsegments have not the effect you need.
> We can put in any set of endsegments and get a set out, any INFINITE set of endsegments yields the empty set. Including your "definable", whatever that means.
You are wrong, but obviously not able to learn. Start with the simplest example:
The ability to remove all unit fractions" or {1/1, 1/2, 1/3, ...} from [0, 1] when not individually defining them leaving no unit fraction shows that there are unit fractions which cannot be removed by identifying them.
Regards, WM
[toc] | [prev] | [next] | [standalone]
| From | Sergio <invalid@invalid.com> |
|---|---|
| Date | 2021-03-02 16:04 -0600 |
| Message-ID | <s1mcpq$hc7$1@gioia.aioe.org> |
| In reply to | #513252 |
On 3/2/2021 3:21 AM, Ganzhinterseher wrote:
> zelos...@gmail.com schrieb am Dienstag, 2. März 2021 um 07:27:22 UTC+1:
>
>>> Why should all endsegments be required? Because they have an effect. But the definable endsegments have not the effect you need.
>> We can put in any set of endsegments and get a set out, any INFINITE set of endsegments yields the empty set. Including your "definable", whatever that means.
>
> You are wrong, but obviously not able to learn. Start with the simplest example:
>
> The ability to remove all unit fractions" or {1/1, 1/2, 1/3, ...} from [0, 1] when not individually defining them leaving no unit fraction shows that there are unit fractions which cannot be removed by identifying them.
if "identified", you toss them out, like a cockroach in the spaghetti,
you throw the whole bowl out
>
> Regards, WM
>
>
>
[toc] | [prev] | [next] | [standalone]
Page 12 of 19 — ← Prev page 1 … 10 11 [12] 13 14 … 19 Next page →
Back to top | Article view | sci.math
csiph-web