Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #77966 > unrolled thread
| Started by | Johnny Billquist <bqt@softjar.se> |
|---|---|
| First post | 2025-11-27 20:10 +0100 |
| Last post | 2025-12-13 08:25 +0000 |
| Articles | 20 on this page of 949 — 49 participants |
Back to article view | Back to comp.os.linux.misc
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: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-27 20:10 +0100
Re: Recent history of vi scott@slp53.sl.home (Scott Lurndal) - 2025-11-27 20:19 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-03 13:44 +0100
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-27 20:44 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-28 07:54 -0500
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-11-28 22:10 +0100
Re: Recent history of vi David Goodwin <david+usenet@zx.net.nz> - 2025-11-29 13:13 +1300
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-29 02:57 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-29 13:35 +0100
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-29 13:45 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-29 15:06 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-29 11:20 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-11-29 12:45 -0700
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-30 10:37 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-30 11:06 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-30 16:20 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-12-01 08:54 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-13 08:22 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-13 11:55 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-12-13 14:44 +0000
Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-13 23:35 +0100
Re: Python rbowman <bowman@montana.com> - 2025-12-14 01:48 +0000
Re: Python drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-14 20:00 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-14 20:43 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-15 02:40 -0500
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:48 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-15 21:43 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:45 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:44 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-15 22:17 +0000
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 23:55 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-19 22:57 +0100
Re: Python c186282 <c186282@nnada.net> - 2025-12-13 23:27 -0500
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-14 11:56 +0000
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-14 23:29 +0000
Re: Python mm0fmf <none@invalid.com> - 2025-12-15 12:57 +0000
Re: Python Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-15 22:57 +0100
Re: Python c186282 <c186282@nnada.net> - 2025-12-15 22:31 -0500
Re: Python Greg Ewing <greg.ewing@canterbury.ac.nz> - 2025-12-16 17:51 +1300
Re: Python rbowman <bowman@montana.com> - 2025-12-16 08:32 +0000
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-16 21:45 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-17 01:54 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-17 03:11 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-17 19:17 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-17 22:10 -0500
Re: Python John Levine <johnl@taugh.com> - 2025-12-18 03:28 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-17 23:02 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-18 06:54 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-18 04:25 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-18 19:22 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-19 01:14 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-18 06:44 +0000
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-18 07:40 -0700
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-18 18:00 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-18 18:28 +0000
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-18 12:52 -0700
Re: Python rbowman <bowman@montana.com> - 2025-12-19 03:53 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-19 00:37 -0500
Re: Python "Michael F. Stemper" <michael.stemper@gmail.com> - 2026-03-04 10:32 -0600
Re: Python ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-03-04 20:01 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2026-03-04 21:29 +0100
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-04 20:37 +0000
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2026-03-04 14:09 -0700
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-04 22:35 +0000
Re: Python Nuno Silva <nunojsilva@invalid.invalid> - 2026-03-04 23:10 +0000
Re: Python c186282 <c186282@nnada.net> - 2026-03-04 20:30 -0500
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2026-03-04 20:13 -0700
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-05 03:49 +0000
Re: Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-03-05 17:42 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2026-03-05 20:02 +0100
Re: Python c186282 <c186282@nnada.net> - 2026-03-05 14:42 -0500
Re: Python Nuno Silva <nunojsilva@invalid.invalid> - 2026-03-06 00:12 +0000
Re: Python Bob Eager <news0009@eager.cx> - 2026-03-06 09:02 +0000
Re: Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-03-05 02:44 +0000
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-05 03:50 +0000
Re: Python Piergiorgio Sartor <piergiorgio.sartor.this.should.not.be.used@nexgo.REMOVETHIS.de> - 2026-03-04 22:14 +0100
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2026-03-04 22:20 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-19 00:29 -0500
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-20 12:38 +0100
Re: Python Dan Espen <dan1espen@gmail.com> - 2025-12-17 16:17 -0500
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-17 22:11 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-17 22:18 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-18 07:07 +0000
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-17 22:13 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-18 00:52 +0000
Re: Python Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-12-18 08:03 +0100
Re: Python rbowman <bowman@montana.com> - 2025-12-18 07:39 +0000
Re: Python scott@slp53.sl.home (Scott Lurndal) - 2025-12-18 15:43 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-18 18:38 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-19 00:56 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-19 08:18 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-19 03:30 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-19 19:38 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-20 04:01 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-21 04:08 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-27 22:36 +0100
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-18 09:55 +0000
Re: Python Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-12-18 11:19 +0100
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-18 12:36 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-14 23:36 -0500
Re: Python candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-12-19 13:30 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-19 19:50 +0000
Re: Python scott@slp53.sl.home (Scott Lurndal) - 2025-12-19 20:03 +0000
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-19 21:00 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-20 04:16 -0500
Re: Python c186282 <c186282@nnada.net> - 2025-12-20 04:15 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-21 04:14 +0000
Re: Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-21 09:06 -0500
Re: Python drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-21 18:31 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-21 21:00 +0000
Re: Python Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-12-22 07:29 +0100
Linux at work in the old days Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-22 07:20 -0500
Re: Linux at work in the old days rbowman <bowman@montana.com> - 2025-12-22 19:18 +0000
Re: Linux at work in the old days c186282 <c186282@nnada.net> - 2025-12-23 01:41 -0500
Re: Linux at work in the old days Peter Flass <Peter@Iron-Spring.com> - 2025-12-23 07:26 -0700
Re: Linux at work in the old days Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-23 20:21 +0000
Re: naughty Python John Levine <johnl@taugh.com> - 2025-12-22 21:26 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-23 00:49 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-23 01:55 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-23 11:21 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-23 06:34 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-23 12:38 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-23 20:28 +0000
Re: naughty Python Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-23 14:21 -0800
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-23 23:55 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-24 05:33 -0500
The power of languages (Re: naughty Python) Lars Poulsen <lars@beagle-ears.com> - 2025-12-24 15:49 +0000
Re: The power of languages (Re: naughty Python) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-24 23:28 +0000
Re: The power of languages (Re: naughty Python) Thomas Prufer <prufer.public@mnet-online.de.invalid> - 2025-12-27 15:29 +0100
Re: The power of languages (Re: naughty Python) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-27 21:21 +0000
Re: The power of languages (Re: naughty Python) rbowman <bowman@montana.com> - 2025-12-27 23:17 +0000
Re: The power of languages (Re: naughty Python) Lars Poulsen <lars@beagle-ears.com> - 2025-12-28 04:09 +0000
Re: The power of languages (Re: naughty Python) Bob Vloon <usenet@bananacorp.nl.invalid> - 2025-12-28 18:00 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-28 22:22 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-28 21:06 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-29 04:04 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-29 01:07 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-29 06:38 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-29 02:31 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-29 17:09 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-29 13:35 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-29 07:33 -0700
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-29 21:59 +0000
Re: naughty Python John Ames <commodorejohn@gmail.com> - 2025-12-29 15:40 -0800
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-30 01:30 +0000
Re: naughty Python John Ames <commodorejohn@gmail.com> - 2025-12-30 08:57 -0800
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 12:51 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 19:00 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-30 19:06 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-30 09:38 +0100
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:11 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-30 07:38 -0700
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 15:04 +0000
Innovation (was Re: naughty Python) Lars Poulsen <lars@beagle-ears.com> - 2025-12-30 21:40 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-30 22:02 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-29 19:23 -0700
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-30 03:53 +0000
OT: incompetence of companies (was: Re: naughty Python) Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-30 10:03 +0000
Re: OT: incompetence of companies The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:12 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 03:14 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:18 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-30 21:49 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 19:47 -0500
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-31 01:01 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-31 03:07 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 23:45 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 07:12 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 23:11 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 07:57 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 09:13 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 19:13 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-31 18:55 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 14:21 -0500
Re: naughty Python Lars Poulsen <lars@beagle-ears.com> - 2025-12-31 22:34 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 22:32 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 22:35 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 22:07 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 12:49 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-01 07:28 -0700
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-01 15:55 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 02:40 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:29 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:18 -0500
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 22:22 +0100
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-03 08:31 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-03 20:12 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 07:56 -0700
Re: naughty Pascal Don_from_AZ <djatechNOSPAM@comcast.net.invalid> - 2026-01-04 09:22 -0700
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-04 21:16 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-04 21:00 +0000
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-04 15:11 +0100
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-05 10:49 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-05 19:57 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-05 20:37 -0700
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 04:10 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-05 23:21 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-06 06:28 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 18:57 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 16:04 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-06 14:22 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 20:47 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-07 02:00 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 22:37 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-07 08:56 -0800
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: naughty Pascal Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2026-01-08 09:57 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-07 08:57 -0800
Re: naughty Pascal Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2026-01-07 09:41 -0800
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-07 10:29 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-07 22:33 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 00:42 -0500
Re: Naughty Advertising (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 07:01 +0000
Re: Naughty Advertising (was Re: naughty Pascal) John Ames <commodorejohn@gmail.com> - 2026-01-08 08:45 -0800
Re: Naughty Advertising (was Re: naughty Pascal) The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 18:23 +0000
Re: Naughty Advertising (was Re: naughty Pascal) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 19:16 +0000
Re: Naughty Advertising (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-08 20:11 -0500
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:27 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 19:16 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 20:23 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 01:48 +0000
Re: naughty Pascal Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2026-01-08 19:32 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 23:36 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 06:44 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-08 18:46 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 22:15 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-08 20:13 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 23:40 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-08 22:23 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 07:04 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-09 07:58 -0800
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 18:47 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:08 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 10:00 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-09 08:06 -0800
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 18:51 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-09 10:54 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:36 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-09 13:24 -0800
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-10 10:27 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-10 07:42 -0700
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-10 19:44 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-10 13:03 -0700
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-10 23:56 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:02 +0000
Re: naughty Pascal Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2026-01-10 15:39 -0800
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:05 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 21:49 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-11 21:19 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-12 07:45 -0700
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 18:35 +0000
Re: naughty Pascal Richard Kettlewell <invalid@invalid.invalid> - 2026-01-12 20:52 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-12 20:58 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 06:03 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-13 12:45 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-12 14:26 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-12 18:17 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 06:26 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-13 09:26 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 05:56 +0000
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-20 14:26 +0100
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-20 13:29 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:01 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-10 18:23 +0000
Re: naughty Pascal Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2026-01-10 15:50 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-10 22:48 -0500
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:19 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:17 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:07 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-11 16:47 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 19:44 +0000
Re: naughty Pascal Dan Espen <dan1espen@gmail.com> - 2026-01-10 12:14 -0500
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-10 09:45 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:32 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-10 20:51 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-10 20:03 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-10 22:31 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 05:39 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-11 01:17 -0500
Re: naughty Pascal Richard Kettlewell <invalid@invalid.invalid> - 2026-01-11 11:00 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:47 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:29 +0000
Re: naughty Pascal Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-11 17:44 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 19:46 +0000
Re: naughty Pascal Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-11 20:23 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 20:30 +0000
Re: naughty Pascal Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-11 21:17 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-11 18:05 -0500
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-11 17:58 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 03:47 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-12 23:41 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-12 22:58 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 05:40 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-13 07:41 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-13 12:38 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 18:00 +0000
Naughty Cat Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-13 14:29 -0500
Re: Naughty Cat rbowman <bowman@montana.com> - 2026-01-14 00:42 +0000
Re: Naughty Cat Peter Flass <Peter@Iron-Spring.com> - 2026-01-14 07:27 -0700
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-13 19:34 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-14 00:49 +0000
Tinned tuna [Was: naughty Pascal] "Carlos E.R." <robin_listas@es.invalid> - 2026-01-20 14:58 +0100
Oil down the drain [Was: naughty Pascal] "Carlos E.R." <robin_listas@es.invalid> - 2026-01-20 14:53 +0100
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 20:57 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-12 11:50 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 18:31 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-11 07:43 -0700
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-11 16:44 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 21:34 +0000
Re: naughty Pascal Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-11 21:38 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-12 08:11 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 18:45 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-12 19:52 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 05:22 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-13 00:37 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 08:18 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-12 13:15 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-12 18:10 -0500
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-12 00:47 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 04:10 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-12 15:44 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 18:52 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-12 20:46 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-12 18:12 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 05:50 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-13 12:41 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 18:17 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-13 22:41 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-14 01:01 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-16 21:40 +0000
Re: naughty Pascal Daniel <me@sc1f1dan.com> - 2026-01-18 12:30 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-18 21:08 -0500
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-19 16:22 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-13 09:23 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-12 08:25 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-12 18:22 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:26 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 21:35 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-12 11:57 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-12 23:41 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-13 06:32 +0000
Re: naughty Pascal Harold Stevens <wookie@aspen.localdomain> - 2026-01-13 04:35 -0600
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-20 15:38 +0100
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-09 09:36 -0800
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 06:58 +0000
Re: naughty Pascal Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2026-01-09 09:19 -0800
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:55 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-07 21:46 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-07 18:48 -0500
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 07:31 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-05 23:18 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 07:42 -0700
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 20:01 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 07:27 -0700
Re: naughty Pascal antispam@fricas.org (Waldek Hebisch) - 2026-01-06 22:32 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 20:53 -0500
Re: naughty Pascal cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 11:51 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-06 08:20 -0800
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 10:15 +0000
Re: naughty Pascal Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 06:33 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-06 19:20 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-06 09:14 -0800
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-05 12:33 -0700
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-05 11:50 -0800
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-05 13:37 -0800
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-06 13:19 +0100
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-06 08:30 -0800
Re: naughty Pascal cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 17:04 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 16:30 -0500
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-07 13:40 +0100
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 07:47 -0700
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 20:08 +0000
Re: naughty Pascal Richard Kettlewell <invalid@invalid.invalid> - 2026-01-07 20:18 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 00:36 -0500
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 07:00 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-08 08:33 -0800
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 20:00 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-08 20:21 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 22:45 +0000
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 23:52 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-09 16:03 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-08 07:51 -0700
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-07 13:38 +0100
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-07 22:03 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 19:21 -0700
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 02:26 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-07 23:20 -0500
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:20 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-08 08:34 -0800
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 20:19 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 01:42 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 09:57 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-08 14:43 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 20:15 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 01:44 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 09:56 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-08 19:28 -0700
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-08 07:47 -0700
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-08 19:52 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 22:45 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 01:35 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 10:02 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-09 08:16 -0700
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 18:46 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:40 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:38 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-09 20:56 -0700
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-10 10:58 +0000
Re: naughty Pascal cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-10 03:12 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-10 19:39 +0000
Re: naughty useless code (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-10 20:52 +0000
Re: naughty useless code (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-11 00:02 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-09 16:04 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 20:54 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 06:36 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-09 08:13 -0700
Re: Naughty PL/I (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-09 18:38 +0000
Re: naughty Pascal Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-10 14:40 +0000
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-10 20:50 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-11 02:00 -0500
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-11 16:55 +0000
Re: Naughty Fortran (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-11 20:24 +0000
Re: Naughty Fortran (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-11 18:00 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-11 21:31 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-08 19:49 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 20:43 -0500
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-10 19:39 +0000
Re: naughty C (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-10 20:47 +0000
Re: naughty C (was Re: naughty Pascal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-01-11 00:27 +0000
Re: naughty C (was Re: naughty Pascal) John Ames <commodorejohn@gmail.com> - 2026-01-10 18:41 -0800
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-10 20:06 -0700
Re: naughty C (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-10 22:44 -0500
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-11 07:40 -0700
Re: naughty C (was Re: naughty Pascal) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-11 03:50 +0000
Re: naughty C (was Re: naughty Pascal) Harold Stevens <wookie@aspen.localdomain> - 2026-01-11 05:55 -0600
Re: naughty C (was Re: naughty Pascal) Pancho <Pancho.Jones@protonmail.com> - 2026-01-11 14:18 +0000
Re: naughty C (was Re: naughty Pascal) Andreas Eder <a_eder_muc@web.de> - 2026-01-11 17:00 +0100
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-11 20:44 +0000
Re: naughty C (was Re: naughty Pascal) The Natural Philosopher <tnp@invalid.invalid> - 2026-01-12 11:49 +0000
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-12 07:52 -0700
Re: naughty C (was Re: naughty Pascal) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-12 17:03 +0000
Re: naughty C (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-12 19:57 +0000
Re: naughty C (was Re: naughty Pascal) scott@slp53.sl.home (Scott Lurndal) - 2026-01-12 20:05 +0000
Re: naughty C (was Re: naughty Pascal) Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-12 20:16 +0000
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-13 05:01 +0000
Re: naughty C (was Re: naughty Pascal) Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-13 06:31 +0000
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-13 08:09 +0000
Re: naughty C (was Re: naughty Pascal) Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-13 14:21 +0000
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-13 17:54 +0000
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-13 04:46 +0000
Re: naughty C (was Re: naughty Pascal) rbowman <bowman@montana.com> - 2026-01-13 04:31 +0000
Re: naughty C (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-12 19:56 +0000
Re: naughty C (was Re: naughty Pascal) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-13 00:24 +0000
Re: naughty C (was Re: naughty Pascal) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-13 00:36 +0000
Re: naughty C (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-12 23:04 -0500
Re: naughty C (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-11 01:52 -0500
Re: naughty C (was Re: naughty Pascal) John Ames <commodorejohn@gmail.com> - 2026-01-10 23:34 -0800
Re: naughty C (was Re: naughty Pascal) c186282 <c186282@nnada.net> - 2026-01-11 02:50 -0500
Re: naughty C (was Re: naughty Pascal) Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-11 14:55 +0000
Re: naughty C (was Re: naughty Pascal) antispam@fricas.org (Waldek Hebisch) - 2026-01-12 02:42 +0000
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-12 07:50 -0700
Re: naughty C (was Re: naughty Pascal) John Ames <commodorejohn@gmail.com> - 2026-01-12 09:14 -0800
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-12 13:12 -0700
Re: naughty C (was Re: naughty Pascal) Harold Stevens <wookie@aspen.localdomain> - 2026-01-12 14:48 -0600
Re: naughty C (was Re: naughty Pascal) Peter Flass <Peter@Iron-Spring.com> - 2026-01-11 07:48 -0700
Re: naughty Pascal antispam@fricas.org (Waldek Hebisch) - 2026-01-11 01:32 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-11 11:21 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-06 19:22 +0000
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-07 13:41 +0100
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:42 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-05 20:33 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-05 22:58 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-05 20:27 -0700
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-05 22:54 -0500
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 07:40 -0700
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 04:09 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 10:10 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 07:46 -0700
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 17:19 +0000
Re: naughty Pascal Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 12:39 -0700
Re: naughty Pascal cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 19:56 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:44 +0000
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 19:57 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 21:53 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-06 19:17 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-06 16:06 -0500
Re: naughty Pascal cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 23:44 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:57 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:56 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-07 22:08 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:21 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 00:41 -0500
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:26 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-08 19:59 +0000
Re: naughty Pascal Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 22:45 +0000
Re: naughty Pascal c186282 <c186282@nnada.net> - 2026-01-08 21:00 -0500
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-08 20:00 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-08 20:09 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 02:02 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 10:05 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-09 16:02 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-09 18:48 +0000
Re: naughty Pascal rbowman <bowman@montana.com> - 2026-01-09 20:27 +0000
Re: naughty Pascal The Natural Philosopher <tnp@invalid.invalid> - 2026-01-10 10:15 +0000
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 15:31 +0000
Re: naughty Pascal Richard Kettlewell <invalid@invalid.invalid> - 2026-01-06 10:39 +0000
Re: naughty Pascal John Ames <commodorejohn@gmail.com> - 2026-01-06 09:25 -0800
Re: naughty Pascal scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 20:35 +0000
Re: naughty Pascal "Carlos E.R." <robin_listas@es.invalid> - 2026-01-06 13:25 +0100
Re: naughty Pascal Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 20:00 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 14:51 -0700
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 21:00 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-01 21:43 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-01 23:54 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-01 20:14 -0700
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 06:03 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:02 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 05:59 +0000
Re: naughty Python ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-01-02 06:01 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 06:58 +0000
Re: naughty Python ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-01-02 17:14 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 14:58 -0500
Re: naughty Python ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2026-01-02 21:11 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 05:37 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:04 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 12:24 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 06:51 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:56 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 10:59 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 12:27 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 06:54 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:57 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 07:10 -0500
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 14:34 +0100
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 14:38 +0100
Re: naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-02 08:49 -0800
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 18:26 +0000
Re: C structure portability, naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:08 -0500
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 20:32 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:08 +0000
Re: C structure portability, naughty Python John Levine <johnl@taugh.com> - 2026-01-03 02:47 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-03 07:03 -0500
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-03 19:43 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 06:42 -0500
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 20:29 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-04 15:14 +0100
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 09:43 -0500
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-04 19:41 +0000
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-04 21:18 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-04 19:04 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 03:55 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 11:29 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:59 -0500
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:55 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 17:43 +0000
Re: Naughty C♯ Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 18:08 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 20:32 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 17:25 -0500
Re: Naughty C♯ Pancho <Pancho.Jones@protonmail.com> - 2026-01-06 07:55 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 06:19 -0500
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-05 08:26 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 18:09 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:16 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 05:57 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 17:48 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 18:09 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:20 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:24 +0000
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:44 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-05 19:31 -0500
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-06 12:16 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 11:12 -0500
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 16:25 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 17:59 +0000
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 19:59 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 21:57 +0000
Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 13:37 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 15:30 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 17:26 +0000
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-06 17:50 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 19:06 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-06 16:24 -0500
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-06 23:10 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 00:22 +0000
Re: Naughty C♯ c186282 <c186282@nnada.net> - 2026-01-06 21:00 -0500
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:24 +0000
Re: Naughty C♯ antispam@fricas.org (Waldek Hebisch) - 2026-01-08 01:00 +0000
Re: Naughty C♯ Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: Naughty C♯ scott@slp53.sl.home (Scott Lurndal) - 2026-01-07 15:27 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:29 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 10:02 +0000
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 11:53 +0000
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 07:34 -0700
Re: Re: Naughty C♯ cross@spitfire.i.gajendra.net (Dan Cross) - 2026-01-07 15:13 +0000
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-07 12:20 -0700
Re: Naughty C♯ John Ames <commodorejohn@gmail.com> - 2026-01-07 11:40 -0800
Re: Naughty C♯ Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:20 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-07 21:36 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 20:09 +0000
Re: Naughty C♯ "Carlos E.R." <robin_listas@es.invalid> - 2026-01-06 13:36 +0100
Re: Naughty C♯ Peter Flass <Peter@Iron-Spring.com> - 2026-01-06 07:55 -0700
Re: Naughty PL/I (was Re: Naughty C♯) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 20:04 +0000
What is wrong with C? (and fond memories of VAX) Lars Poulsen <lars@beagle-ears.com> - 2026-01-06 15:15 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 18:57 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-06 20:10 +0000
Re: What is wrong with C? (and fond memories of VAX) scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 21:59 +0000
Re: What is wrong with C? (and fond memories of VAX) Richard Kettlewell <invalid@invalid.invalid> - 2026-01-06 22:54 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-07 01:40 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: What is wrong with C? (and fond memories of VAX) "Carlos E.R." <robin_listas@es.invalid> - 2026-01-07 13:30 +0100
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-07 22:49 +0000
Re: What is wrong with C? (and fond memories of VAX) c186282 <c186282@nnada.net> - 2026-01-08 00:47 -0500
Re: What is wrong with C? (and fond memories of VAX) The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 11:23 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 19:16 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-08 20:34 +0000
Re: What is wrong with C? (and fond memories of VAX) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 22:45 +0000
Re: What is wrong with C? (and fond memories of VAX) sean@conman.org - 2026-01-09 00:23 +0000
Re: What is wrong with C? (and fond memories of VAX) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-09 04:54 +0000
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-09 07:08 +0000
Re: What is wrong with C? (and fond memories of VAX) scott@slp53.sl.home (Scott Lurndal) - 2026-01-09 16:18 +0000
Re: What is wrong with C? (and fond memories of VAX) "Carlos E.R." <robin_listas@es.invalid> - 2026-01-12 15:44 +0100
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-12 18:57 +0000
Re: What is wrong with C? (and fond memories of VAX) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-12 19:59 +0000
Re: What is wrong with C? (and fond memories of VAX) Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-13 06:13 -0500
Re: What is wrong with C? (and fond memories of VAX) rbowman <bowman@montana.com> - 2026-01-13 18:22 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 17:17 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 18:59 +0000
Re: Naughty C♯ The Natural Philosopher <tnp@invalid.invalid> - 2026-01-05 11:26 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 03:34 +0000
Re: Naughty C♯ Richard Kettlewell <invalid@invalid.invalid> - 2026-01-05 08:24 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-05 19:06 +0000
Re: Naughty C♯ Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 06:50 -0500
Re: Naughty C♯ Pancho <Pancho.Jones@protonmail.com> - 2026-01-06 08:03 +0000
Re: Naughty C♯ rbowman <bowman@montana.com> - 2026-01-06 19:11 +0000
Re: Naughty C♯ Bob Vloon <usenet@bananacorp.nl.invalid> - 2026-01-07 12:01 +0000
Re: Naughty Java (was Re: Naughty C♯) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:18 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-05 03:09 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:31 +0100
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 20:04 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:25 +0100
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 15:47 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:45 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-05 09:20 -0800
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 18:10 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-05 21:45 +0000
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-05 23:28 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 00:14 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 00:23 +0000
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 00:57 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-06 06:24 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-06 08:14 -0800
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-06 18:57 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-06 11:03 -0800
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-07 06:33 +0000
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-07 09:00 -0800
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-07 12:23 -0500
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-08 14:01 +0100
Re: C structure portability, naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-07 20:55 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-06 20:58 +0000
Re: C structure portability, naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-07 09:48 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-07 20:17 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-08 04:57 +0000
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-06 15:29 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-06 06:21 -0500
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-05 18:13 +0000
Re: C structure portability, naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 18:16 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-04 19:48 +0000
Re: C structure portability, naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-05 13:37 +0100
Re: C structure portability, naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-04 21:17 +0000
Re: C structure portability, naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:01 +0000
Re: C structure portability, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 07:07 -0500
Re: C structure portability, naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-05 11:05 -0800
Re: C structure portability, naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-03 18:32 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 19:38 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 21:33 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 15:00 -0700
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:52 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 19:51 -0700
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-03 06:09 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 20:38 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-03 16:58 -0500
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 08:01 -0700
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-04 16:25 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:12 +0000
Re: naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 07:14 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-04 20:25 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 07:59 -0700
Re: naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-04 16:31 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-04 19:41 +0000
Re: naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-04 20:05 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 04:17 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-05 05:57 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-05 19:20 +0000
Re: naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-05 17:35 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-06 06:36 +0000
Re: naughty Python Robert Riches <spamtrap42@jacob21819.net> - 2026-01-06 03:31 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-06 10:20 +0000
Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-06 18:48 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-06 22:02 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-07 00:27 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 02:09 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-07 14:18 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 20:40 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-07 22:23 +0000
Re: Case-dependent file systems Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-10 14:36 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-10 14:53 +0000
Re: Case-dependent file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-10 15:08 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-11 02:00 +0000
Re: Case-dependent file systems Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-11 14:34 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-11 16:14 +0000
Re: Case-dependent file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-11 20:31 +0000
Re: Case-dependent file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-11 21:38 +0000
Re: Case-dependant file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-06 23:09 +0000
Re: Case-dependant file systems "Carlos E.R." <robin_listas@es.invalid> - 2026-01-08 14:17 +0100
Re: Case-dependant file systems The Natural Philosopher <tnp@invalid.invalid> - 2026-01-08 13:36 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:05 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:15 +0000
Re: Case-dependant file systems Richard Kettlewell <invalid@invalid.invalid> - 2026-01-08 14:02 +0000
Re: Case-dependant file systems Lars Poulsen <lars@beagle-ears.com> - 2026-01-08 14:13 +0000
Re: Case-dependant file systems Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-08 22:12 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-06 21:08 +0000
Re: C structures, was naughty Python John Levine <johnl@taugh.com> - 2026-01-02 22:41 +0000
Re: C structures, was naughty Python John Ames <commodorejohn@gmail.com> - 2026-01-02 15:44 -0800
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 02:19 -0500
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 02:08 -0500
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-02 02:18 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 21:57 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 20:07 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 12:17 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 00:06 -0500
Re: language design, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 18:30 +0000
Re: language design, naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:15 -0500
Re: language design, naughty Python John Levine <johnl@taugh.com> - 2026-01-02 20:34 +0000
Re: language design, naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:17 +0000
Re: language design, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-03 07:11 -0500
Re: language design, naughty Python rbowman <bowman@montana.com> - 2026-01-03 19:46 +0000
Re: language design, naughty Python Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-04 06:45 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 03:05 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 23:42 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 07:55 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 09:12 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2025-12-31 19:03 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 14:50 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 12:39 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 09:21 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 15:08 +0000
Re: naughty Python Lars Poulsen <lars@beagle-ears.com> - 2025-12-31 15:38 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-31 20:41 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-01 00:55 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 22:11 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 13:09 +0000
The Egg (was: Re: naughty Python) vallor <vallor@vallor.earth> - 2026-01-02 01:54 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-02 02:18 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:10 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 06:39 -0500
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 07:51 -0700
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:34 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 12:12 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 22:17 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 11:46 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 22:28 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 21:50 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 12:37 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 01:15 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:35 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 20:02 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 12:23 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-31 09:16 -0500
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-01 10:30 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-01 19:00 +0000
Re: naughty Python Richard Kettlewell <invalid@invalid.invalid> - 2026-01-01 19:12 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-01 20:10 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-01 21:37 +0100
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-02 02:18 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 03:23 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-02 04:56 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 06:24 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 06:32 +0000
Re: naughty Python "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-01-02 13:06 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 09:41 -0500
Electronic calculators "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 21:57 +0100
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:36 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 19:57 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 01:07 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-03 08:36 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-03 08:50 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-03 10:54 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-03 07:39 -0700
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-03 14:22 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 20:14 +0000
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-04 07:57 -0700
Re: naughty Python scott@slp53.sl.home (Scott Lurndal) - 2026-01-03 18:34 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-02 21:47 +0100
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:27 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-03 14:24 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-03 14:08 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 20:48 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-01 21:01 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-02 02:53 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 03:24 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-02 05:04 +0000
Re: naughty Python Nuno Silva <nunojsilva@invalid.invalid> - 2026-01-02 13:15 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 02:44 -0500
Re: naughty Python Peter Flass <Peter@Iron-Spring.com> - 2026-01-02 07:43 -0700
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 10:06 -0500
Re: naughty Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-02 17:41 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:04 -0500
Re: naughty Python Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2026-01-03 08:01 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 20:56 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 00:44 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-01 20:05 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-02 15:27 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:21 +0000
Re: naughty Python antispam@fricas.org (Waldek Hebisch) - 2026-01-03 02:12 +0000
Re: naughty Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-03 03:15 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 14:25 -0500
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-01 23:35 -0500
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 06:35 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 11:13 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-02 19:46 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-02 19:58 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 01:03 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-03 08:34 +0000
Re: naughty Python rbowman <bowman@montana.com> - 2026-01-03 20:54 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2026-01-04 15:19 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2026-01-02 15:26 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-31 12:17 +0000
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-29 13:27 +0100
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-29 13:34 +0000
Re: naughty Python John Ames <commodorejohn@gmail.com> - 2025-12-29 09:53 -0800
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-29 21:37 +0100
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-30 02:56 -0500
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-30 18:53 +0000
Re: naughty Python John Levine <johnl@taugh.com> - 2025-12-29 04:43 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-29 01:22 -0500
Re: naughty Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-29 13:34 +0100
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 12:41 +0000
Re: naughty Python Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-24 23:28 +0000
Re: naughty Python c186282 <c186282@nnada.net> - 2025-12-24 21:30 -0500
Intellectuals (Re: naughty Python) Lars Poulsen <lars@beagle-ears.com> - 2025-12-25 22:05 +0000
Re: Intellectuals (Re: naughty Python) c186282 <c186282@nnada.net> - 2025-12-25 22:20 -0500
Re: Intellectuals (Re: naughty Python) The Natural Philosopher <tnp@invalid.invalid> - 2025-12-26 07:02 +0000
Re: Intellectuals (Re: naughty Python) c186282 <c186282@nnada.net> - 2025-12-26 02:16 -0500
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 12:40 +0000
Re: naughty Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 12:32 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-27 22:40 +0100
Re: Python Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-27 23:21 +0000
Re: Python dillinger <dillinger@invalid.not> - 2025-12-28 02:05 +0100
Re: Python Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-27 18:16 -0800
Re: Python dillinger <dillinger@invalid.not> - 2025-12-28 04:59 +0100
Re: Python Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-28 08:32 -0800
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-28 13:48 +0100
Re: Python dillinger <dillinger@invalid.not> - 2025-12-28 14:14 +0100
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-28 14:42 +0100
Re: Python rbowman <bowman@montana.com> - 2025-12-28 17:41 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-28 22:11 +0100
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-28 22:06 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-28 23:30 +0100
Re: Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-12-29 10:47 +0000
Re: Python Bob Eager <news0009@eager.cx> - 2025-12-29 11:11 +0000
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-04 14:15 +0000
Re: Python Niklas Karlsson <nikke.karlsson@gmail.com> - 2026-01-04 16:34 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-28 21:23 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-29 04:15 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-29 01:17 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-29 06:40 +0000
Re: Python Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-28 23:20 -0800
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-29 10:42 +0000
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-29 07:31 -0700
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-29 15:52 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-29 11:12 -0500
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-29 20:48 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-30 02:58 -0500
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-30 10:03 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:06 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-29 17:28 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-29 21:50 +0100
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:06 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-30 01:13 -0500
Re: Python Diego Garcia <dg@linux.rocks> - 2025-12-30 08:08 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 11:14 +0000
Re: Python Farley Flud <fsquared@fsquared.linux> - 2025-12-30 12:43 +0000
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-30 17:34 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-30 15:55 -0500
Re: one time pads, not Python John Levine <johnl@taugh.com> - 2026-01-02 04:55 +0000
Re: one time pads, not Python Richard Kettlewell <invalid@invalid.invalid> - 2026-01-02 09:15 +0000
Re: one time pads, not Python c186282 <c186282@nnada.net> - 2026-01-02 05:45 -0500
Re: one time pads, not Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-02 20:59 +0000
Re: one time pads, not Python Richard Kettlewell <invalid@invalid.invalid> - 2026-01-02 21:17 +0000
Re: one time pads, not Python The Natural Philosopher <tnp@invalid.invalid> - 2026-01-03 08:26 +0000
Re: one time pads, not Python Richard Kettlewell <invalid@invalid.invalid> - 2026-01-03 11:45 +0000
Re: one time pads, not Python rbowman <bowman@montana.com> - 2026-01-03 20:56 +0000
Re: one time pads, not Python c186282 <c186282@nnada.net> - 2026-01-02 05:14 -0500
Re: Python antispam@fricas.org (Waldek Hebisch) - 2025-12-30 18:46 +0000
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-30 19:03 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-30 15:43 -0500
Re: “Quantum” Computing (was Re: Python) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-29 21:56 +0000
Re: “Quantum” Computing (was Re: Python) c186282 <c186282@nnada.net> - 2025-12-30 03:17 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-29 17:15 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-29 02:52 -0500
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-29 13:40 +0000
Re: Python Peter Flass <Peter@Iron-Spring.com> - 2025-12-29 07:29 -0700
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-29 16:27 +0000
Re: Python c186282 <c186282@nnada.net> - 2025-12-20 02:52 -0500
Re: Python rbowman <bowman@montana.com> - 2025-12-21 04:00 +0000
Re: Python candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-12-23 16:00 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-23 20:30 +0000
Re: Python scott@slp53.sl.home (Scott Lurndal) - 2025-12-23 21:14 +0000
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-19 20:57 +0000
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-19 22:09 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-20 05:37 +0000
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-20 10:34 +0000
Re: Python Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-20 11:45 +0000
Re: Python Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-20 13:32 +0000
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-20 16:36 +0000
Re: Python Richard Kettlewell <invalid@invalid.invalid> - 2025-12-20 16:37 +0000
Re: Python "Carlos E.R." <robin_listas@es.invalid> - 2025-12-14 13:16 +0100
Re: Python c186282 <c186282@nnada.net> - 2025-12-15 00:45 -0500
Re: Python The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:55 +0000
Re: Python rbowman <bowman@montana.com> - 2025-12-15 22:39 +0000
Re: Python Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 23:53 +0000
Re: Python (was Re: Recent history of vi) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-14 02:05 +0000
Re: Python (was Re: Recent history of vi) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-12-19 13:30 +0000
Re: Python (was Re: Recent history of vi) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-19 20:58 +0000
Re: Python (was Re: Recent history of vi) rbowman <bowman@montana.com> - 2025-12-20 05:48 +0000
Re: Python (was Re: Recent history of vi) Richard Kettlewell <invalid@invalid.invalid> - 2025-12-20 10:12 +0000
Re: Python (was Re: Recent history of vi) c186282 <c186282@nnada.net> - 2025-12-20 05:25 -0500
Re: Python (was Re: Recent history of vi) rbowman <bowman@montana.com> - 2025-12-21 04:22 +0000
Re: Python (was Re: Recent history of vi) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-20 22:28 +0000
Re: Python (was Re: Recent history of vi) rbowman <bowman@montana.com> - 2025-12-21 04:25 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:39 +0000
Re: Recent history of vi John Bokma <contact@johnbokma.com> - 2025-12-15 19:46 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 23:54 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-30 18:33 +0000
Re: Recent history of vi David Goodwin <david+usenet@zx.net.nz> - 2025-12-01 11:09 +1300
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-13 08:23 +0000
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-30 12:29 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-30 13:23 +0000
Re: Recent history of vi Rich <rich@example.invalid> - 2025-11-30 16:56 +0000
Re: Recent history of vi David Goodwin <david+usenet@zx.net.nz> - 2025-12-01 11:18 +1300
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-01 01:55 +0100
Re: Recent history of vi Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-11-30 13:29 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-13 08:25 +0000
Page 46 of 48 — ← Prev page 1 … 44 45 [46] 47 48 Next page →
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-12-30 19:03 +0000 |
| Subject | Re: Python |
| Message-ID | <10j17mp$20gln$4@dont-email.me> |
| In reply to | #80121 |
On 30/12/2025 18:46, Waldek Hebisch wrote: > In alt.folklore.computers c186282 <c186282@nnada.net> wrote: >> On 12/29/25 12:28, The Natural Philosopher wrote: >>> On 29/12/2025 14:31, Peter Flass wrote: >>>> On 12/29/25 03:42, Richard Kettlewell wrote: >>>>> Bobbie Sellers <bliss-sf4ever@dslextreme.com> writes: >>>>>> On 12/28/25 22:40, rbowman wrote: >>>>>>> On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: >>>>>>>> For most 'office' uses you do NOT need AES-256 encryption for yer >>>>>>>> damned payroll or budget files. Nobody, not even Vlad or Xi, CARES. >>>>>>> We were dealing with NPS sites like Yellowstone and Rocky >>>>>>> Mountain. The Dept. of Interior certainly cares. >>>>>> >>>>>> Any employer who has a payroll has the Social Security numbers >>>>>> of the employees. This certainly deserves the best encryption that >>>>>> can be set up. >>>>>> >>>>>> The encryption schemes are all breakable with enough power >>>>>> brought to bear. >>>>> >>>>> At this point you should take a moment to work out how much ‘enough’ is. >>>>> >>>>> Let’s assume that: >>>>> - you have a circuit design that can do a single AES-128 key >>>>> schedule and decrypt operation in one cycle >>>>> - you can fit a million copies of this design onto one chip >>>>> - you can run the chip at 10GHz >>>>> - you can manufacture a trillion instances of the chip >>>>> (and put enough of a computer around them to do something useful) >>>>> - you can somehow power and cool this unrealistically large >>>>> supercomputer. >>>>> >>>>> This lets you test 10^6 * 10^10 * 10^12 = 10^28 keys per second. There >>>>> are 2^128 possible AES-128 keys so it will take you a little over one >>>>> thousand years to break AES-128. Your SSN will no longer be relevant by >>>>> this point. >>>> >>>> Right now, but people who work with this stuff are worried about what >>>> quantum computers can do with it. >>>> >>>> >>> Enigma codes were also 'unbreakable' >> >> Well ... kinda true. >> >> The Brits did develop early computer tech to >> help them - but the main breakthroughs came >> when NAZI operators screwed up and repeated >> the exact same message using different keys. > > Actually, Enigma was broken by Polish cryptographers (M. Rejewski, > J. Różycki, H. Zygalski). British were relatively late to the game > and received information from Poland. That included internal > connections of the machine and methods to recover keys. > > Polish method were mainly based on the following property: up > to IIRC 1943 German operators were supposed to start from > pre-assigned position (changing with time), choose their > own position, encrypt it using the pre-assigned position, > send it and than change to the new position to encrypt main > message. Imporant part is that operators were instructed to > repeat initial position twice. That is position was encoded > using 3 letters, they doubled this to 6 letter string and > encrypted those letters. This procedure left a lot of > redundancy in the first 6 letters of encrypted message. > Yes. The Poles got a long way into Enigma, but not the whole way. They knew how the machines worked, at least. <snip> > Actually, we are still quite far from ability to brute force > 108.39 bits keys (effective length of Enigma key), and internal > connections of Enigma are worth about 400 bits (and more with > additional rotors). But we know that "know plaintext" attack > can be quite effective at recovering keys. And there are new > statistical approaches, likely to break any cipher designed without > knowledge of such an attack. > Precisely. -- “Progress is precisely that which rules and regulations did not foresee,” – Ludwig von Mises
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-12-30 15:43 -0500 |
| Subject | Re: Python |
| Message-ID | <xfecndbTbJvjpMn0nZ2dnZfqnPqdnZ2d@giganews.com> |
| In reply to | #80121 |
On 12/30/25 13:46, Waldek Hebisch wrote: > In alt.folklore.computers c186282 <c186282@nnada.net> wrote: >> On 12/29/25 12:28, The Natural Philosopher wrote: >>> On 29/12/2025 14:31, Peter Flass wrote: >>>> On 12/29/25 03:42, Richard Kettlewell wrote: >>>>> Bobbie Sellers <bliss-sf4ever@dslextreme.com> writes: >>>>>> On 12/28/25 22:40, rbowman wrote: >>>>>>> On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: >>>>>>>> For most 'office' uses you do NOT need AES-256 encryption for yer >>>>>>>> damned payroll or budget files. Nobody, not even Vlad or Xi, CARES. >>>>>>> We were dealing with NPS sites like Yellowstone and Rocky >>>>>>> Mountain. The Dept. of Interior certainly cares. >>>>>> >>>>>> Any employer who has a payroll has the Social Security numbers >>>>>> of the employees. This certainly deserves the best encryption that >>>>>> can be set up. >>>>>> >>>>>> The encryption schemes are all breakable with enough power >>>>>> brought to bear. >>>>> >>>>> At this point you should take a moment to work out how much ‘enough’ is. >>>>> >>>>> Let’s assume that: >>>>> - you have a circuit design that can do a single AES-128 key >>>>> schedule and decrypt operation in one cycle >>>>> - you can fit a million copies of this design onto one chip >>>>> - you can run the chip at 10GHz >>>>> - you can manufacture a trillion instances of the chip >>>>> (and put enough of a computer around them to do something useful) >>>>> - you can somehow power and cool this unrealistically large >>>>> supercomputer. >>>>> >>>>> This lets you test 10^6 * 10^10 * 10^12 = 10^28 keys per second. There >>>>> are 2^128 possible AES-128 keys so it will take you a little over one >>>>> thousand years to break AES-128. Your SSN will no longer be relevant by >>>>> this point. >>>> >>>> Right now, but people who work with this stuff are worried about what >>>> quantum computers can do with it. >>>> >>>> >>> Enigma codes were also 'unbreakable' >> >> Well ... kinda true. >> >> The Brits did develop early computer tech to >> help them - but the main breakthroughs came >> when NAZI operators screwed up and repeated >> the exact same message using different keys. > > Actually, Enigma was broken by Polish cryptographers (M. Rejewski, > J. Różycki, H. Zygalski). British were relatively late to the game > and received information from Poland. That included internal > connections of the machine and methods to recover keys. The Poles had a top reputation in cryptography back then, maybe even still. > Polish method were mainly based on the following property: up > to IIRC 1943 German operators were supposed to start from > pre-assigned position (changing with time), choose their > own position, encrypt it using the pre-assigned position, > send it and than change to the new position to encrypt main > message. Imporant part is that operators were instructed to > repeat initial position twice. That is position was encoded > using 3 letters, they doubled this to 6 letter string and > encrypted those letters. This procedure left a lot of > redundancy in the first 6 letters of encrypted message. > > Initially Germans changed machine settings rather slowly. > The settings included choice of rotor order, switchboard settings > (IIUC capable of producing arbitrary permutation, but German > did not use its full potential) and pre-assigned position. > French agents managed to steal instruction for operators > and some info about past setting (there is some discrepancy > in various report what exactly they were able to steal). > Polish cryptographers managed to use redundancy that I > mentioned above and collection of intercepted encrypted > German messages to set up system of equations for connections > of first Enigma's rotor (this rotor moved in quite regular > way). Such system of equations alone would not be enough > (Polish cryptographers did not know how to solve it in general), > but Germans made mistakes, like chosing regular patterns of > letters for starting positions. That allowed simplifying the > system of equations. After simplification it would be still > very hard to solve, but French info supplied one variable, > that is switchboard settings. With that info Polish > cryptographers were able to reconstruct connections of the > first rotor. Since Germans were permuting rotors, > each one were first on some dayse, so that actually gave > connections of all rotors. There were some extra things: > non-movable disc sometimes called "reversing disc" whose > connections were determined as part of detemining connections > of the rotors. There were disc passing signals from > switchboard to rotors: to make breaking machine more > difficult this disc should semi-randomly permute signals. > But Polish cryptographers guessed that it may be in > alphabetitic order and it was. Fist rotor were mowing in > very regular way, the other two in less regular way, so > their movement had to be determined. Later Germans > introduces more rotors (each time machine used only 3, > but those 3 could be taken from bigger pool). > > After internal connections of machine were known there was > need to determine current settings, that is switchboard > connections and pre-assigned starting positions. In > a sense main trouble was due to switchboard: with 5 > rotors there were 60 ways to chose 3 that were used, > 17576 ways to choose intial position and factorial 26 > potential setting of the switchboard. In bit terms > the whole key had 108.39 bits of which 88.38 corresponded > to the switchboard. Polish used similar system of > equations as used to break the machine to find > information about rotors. They developed machine called > "cryptological bomb" to go trough all postions and > combination of the rotors to match rotor position with > collected information. Once rotor postions were known > statistiacal method allowed finding switchboard settings > (with effect of rotors defeated switchboard just worked > as a kind of substitution cipher which is easily breakable). Sounds as if the security was just slowly pissed away. Spies, improper methods, mistakes, sheer volume ... combined with the UK 'computer' attacks. Likely the NAZIs thought they'd win the world quickly enough so the machine would still remain secure. > What could be done to make Enigma harder to break? First, > faster changes to settings would make it harder to intercept > enough messaage. Second, initially machines started at the > same position, later Germans modified this so the operator choose > initial "position" (actually offset from preassigned position), > send it in clear and used this position to encrypt the position > used for main body to the massage. This interferd with Polish > method of setting equation system, after that change there > were less information so finding postions were harder. > I mentioned that Germans introduced extra rotors. Two > extra rotors increased number of possible rotor combinations > 10 times, which means more effort to break machine, but that > was relatively mild quantitative difference. Changed > operationg procedure added much more difficulty. Completely > eliminationg redundancy (not doubling info about initial > position) would even more effective (IIUC Germans did something > like this in 1943). > > Looking at machines using similar principle, one probably should > make rotor movement much less regular than it was in Enigma. > In particular in Enigma second and third rotor moved rarely. But > already Enigma was mechanically challenging compared to > earlier attempts at similar machines. > > AFAICS Enigma is weaker than more modern system due to property that > each character of encrypted message depends only on machine settings > and corresponding character in plain text. Moreover, switchboard > is applied "from outside" in a way that leaks information allowing > determining rotor positions independently from switchboard. > >> Enigma was a GOOD scrambler. > > It was reasonably good scrambler. But rotor part had too small > number of positions to resist brute force attack. And > switchboard was much less effective than number of combinations > would suggest. "Brute force" wasn't as brute back then. Yer iPhone could probably tear through it in minutes WHILE you watched a NetFlix. 1940s though ... >> The USA did decode 'Purple', but it was not quite >> as good a code as with Enigma. >> >> These days we can kind of just OVERPOWER 1940s >> ciphers ... but mostly it's just that, overpower, >> not so much in the realm of any General Solution. > > Actually, we are still quite far from abilty to brute force > 108.39 bits keys (effective length of Enigma key), and internal > connections of Enigma are worth about 400 bits (and more with > additional rotors). But we know that "know plaintext" attack > can be quite effective at recovering keys. And there are new > statistical approaches, likely to break any cipher designed without > knowledge of such an attack. Some claim the integrity of a cipher can be fully known via mathematical analysis. In real life though we hear of some clever Jack finding unexpected ways to 'cheat', either breaking or notably weakening the cipher. Mathematical analysis is important for, so to speak, separating the wheat from the chaff. However it's not the FINAL word on a cipher. Some 'AI', trained for the task, might be as clever or much more clever than dear Jack in finding some unrealized flaws. Anyway, AES seems really really good. Camilla and IDEA as well. Awhile back I wrote a backup pgm that would pre-encrypt individual files ... like a server full ... before sending them to cloud storage. AES was fast, 128 a bit faster than 256. Camilla is also fast. Tried using PGP/GPG but the engine had to start up from scratch and that made it useless for the 1-at-a-time approach (ok for large zipped files though). In the end, YOU have to decide what's "secure enough" for your data. If you are a relative nobody then you don't need really hard core encryption. If you manage nuclear missile silos or billions/trillions of dollars then you DO need diamond-hard encryption.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-12-29 21:56 +0000 |
| Subject | Re: “Quantum” Computing (was Re: Python) |
| Message-ID | <10iutf9$1c0aq$1@dont-email.me> |
| In reply to | #80051 |
On Mon, 29 Dec 2025 07:31:06 -0700, Peter Flass wrote: > Right now, but people who work with this stuff are worried about > what quantum computers can do with it. Those kinds of “quantum computers” don’t exist. They can’t even demonstrate a basic number-theoretic operation like factorizing an integer, let alone implementing the fabled Shor’s algorithm. Shor’s algorithm came out about 30 years ago. The progress towards implementing it since then has been ... zero.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-12-30 03:17 -0500 |
| Subject | Re: “Quantum” Computing (was Re: Python) |
| Message-ID | <ANqdnZeG-c5ZF870nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #80079 |
On 12/29/25 16:56, Lawrence D’Oliveiro wrote: > On Mon, 29 Dec 2025 07:31:06 -0700, Peter Flass wrote: > >> Right now, but people who work with this stuff are worried about >> what quantum computers can do with it. > > Those kinds of “quantum computers” don’t exist. They can’t even > demonstrate a basic number-theoretic operation like factorizing an > integer, let alone implementing the fabled Shor’s algorithm. > > Shor’s algorithm came out about 30 years ago. The progress towards > implementing it since then has been ... zero. Hmmm ... put an 'AI' on it. Using quantum to bust encryption is theoretically possible - indeed that is why 'post quantum' encryption methods are being written already. Hey, there's money and power in being able to carve straight through current encryption methods, ergo considerable motivation.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-29 17:15 +0000 |
| Subject | Re: Python |
| Message-ID | <mrfra5F8brlU1@mid.individual.net> |
| In reply to | #80020 |
On Sun, 28 Dec 2025 23:20:46 -0800, Bobbie Sellers wrote: > > On 12/28/25 22:40, rbowman wrote: >> On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: >> >>> For most 'office' uses you do NOT need AES-256 encryption for yer >>> damned payroll or budget files. Nobody, not even Vlad or Xi, >>> CARES. >> >> We were dealing with NPS sites like Yellowstone and Rocky Mountain. The >> Dept. of Interior certainly cares. > > Any employer who has a payroll has the Social Security numbers of the > employees. This certainly deserves the best encryption that can be set > up. > The encryption schemes are all breakable with enough power brought > to bear. > Another reason to worry about AI and vast amounts of computing power > brought to bear on what exactly. 20 years ago I had a background check when Pennsylvania was going to a new CJIN interface and I had to go to a meeting in Harrisburg. Fast forward to a couple of weeks ago and I was notified that one of the PA sites had been hacked and my name and SSN was among the data that had been scraped. At least I got a free year of Experian. Data lives forever and isn't very well secured.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-12-29 02:52 -0500 |
| Subject | Re: Python |
| Message-ID | <cp-dnUeP6vCrrs_0nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #80019 |
On 12/29/25 01:40, rbowman wrote: > On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: > >> For most 'office' uses you do NOT need AES-256 encryption for yer >> damned payroll or budget files. Nobody, not even Vlad or Xi, CARES. > > We were dealing with NPS sites like Yellowstone and Rocky Mountain. The > Dept. of Interior certainly cares. 'Interior' 99.5% doesn't NEED to care. Who gives a fuck what some bubbling hole in Yellowstone is doing ??? Forest replant figures over some old strip mine ??? Sometimes, often ?, "security" gets OVER-sold. There's profit and power in that. Only finance/payroll needs better security. Endless TV commercials in the USA these days about people doing Deed Fraud. Sign up with X, Y or Z and, for a stiff fee, they'll keep watch on yer property records (don't know what THEY do with the info). However, for FREE, my county appraiser will do the SAME THING and mail you if anything important is happening. EZ online form. signed up in five minutes. Now it's the govt's fault if something sneaks in .... which makes it easier to UN-do. Now yer common 'office' ... NOBODY is gonna spend supercomputer time trying to crack yer records. The MAIN use of encryption/obfuscation is internal politics ... hiding what a supervisor says about his underlings or vice versa. THAT can be done in a relatively un-doable obfuscation scheme. And no, most offices maybe have ONE person with significant computer/programming skills, if even THAT these days. Somewhere I noted that my replacement couldn't even code five lines of Python. He was all M$/O365. That's what the new boss wanted ... and it makes all problems Not MY Fault. Somewhere I have an award for innovative computing/tech relevant to to The Industry. That's my coveted reward. Means I *did stuff* other than fill M$ pockets.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-12-29 13:40 +0000 |
| Subject | Re: Python |
| Message-ID | <10iu0d9$1029n$13@dont-email.me> |
| In reply to | #80022 |
On 29/12/2025 07:52, c186282 wrote: > Who gives a fuck what some bubbling hole > in Yellowstone is doing ? People who know that there is a massive magma chamber under it that could erupt into something worse than human history has ever seen? -- A lie can travel halfway around the world while the truth is putting on its shoes.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2025-12-29 07:29 -0700 |
| Subject | Re: Python |
| Message-ID | <10iu37o$11u10$1@dont-email.me> |
| In reply to | #80022 |
On 12/29/25 00:52, c186282 wrote: > On 12/29/25 01:40, rbowman wrote: >> On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: >> >>> For most 'office' uses you do NOT need AES-256 encryption for yer >>> damned payroll or budget files. Nobody, not even Vlad or Xi, CARES. >> >> We were dealing with NPS sites like Yellowstone and Rocky Mountain. The >> Dept. of Interior certainly cares. > > 'Interior' 99.5% doesn't NEED to care. > > Who gives a fuck what some bubbling hole > in Yellowstone is doing ??? Forest replant > figures over some old strip mine ??? The feds mandate encryption, and they probably don't differentiate among agencies.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-12-29 16:27 +0000 |
| Subject | Re: Python |
| Message-ID | <wwvqzsdqmmt.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #80050 |
Peter Flass <Peter@Iron-Spring.com> writes: > On 12/29/25 00:52, c186282 wrote: >> On 12/29/25 01:40, rbowman wrote: >>> On Mon, 29 Dec 2025 01:17:50 -0500, c186282 wrote: >>>> For most 'office' uses you do NOT need AES-256 encryption for yer >>>> damned payroll or budget files. Nobody, not even Vlad or Xi, CARES. >>> >>> We were dealing with NPS sites like Yellowstone and Rocky Mountain. The >>> Dept. of Interior certainly cares. >> 'Interior' 99.5% doesn't NEED to care. >> Who gives a fuck what some bubbling hole >> in Yellowstone is doing ??? Forest replant >> figures over some old strip mine ??? > > The feds mandate encryption, and they probably don't differentiate > among agencies. AIUI the distinction is between National Security Systems (which must use CNSA or suite A) and the rest (which must use FIPS-140). FIPS-140, and other certification targets, are also relied upon outside the US government. Very few organizations have the capability to fully evaluate cryptographic products, and most of those that do have better things to do. So, they use established certifications instead. -- https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-12-20 02:52 -0500 |
| Subject | Re: Python |
| Message-ID | <DYucnUwz0bctyNv0nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #79485 |
On 12/19/25 08:30, candycanearter07 wrote:
> c186282 <c186282@nnada.net> wrote at 04:36 this Monday (GMT):
>> On 12/14/25 06:56, Stéphane CARPENTIER wrote:
>>> Le 14-12-2025, c186282 <c186282@nnada.net> a écrit :
>>>>
>>>> NOT sure why so many people want to trash Python.
>>>
>>> My issues with python are:
>>> - It's using indentations, so when I comment a block of code to see
>>> what happens, it breaks everything and I have to manage the
>>> indentations. I can't just comment/uncomment a block of code as I do
>>> with other programming languages.
>>
>> You CAN do block comments BTW ... use triple-quote at
>> the beginning/end. The double and single quote char
>> work.
>
> Technically, this isn't a comment, but a multi-line string. It just
> happens that Python ignores a string by itself, and multi-line strings
> uses a similar parsing for it.
Maybe ... but WORKS !
>> Indents ... well ... those have been good programming
>> practice since forever. With Python they are also
>> functional, not just 'decorative'. I do pref the 'C'
>> start/end brackets or Pascal Begin/End ... but Python
>> isn't THAT hard to deal with. Typically use just TWO
>> space indents to keep line-lengths shorter. A few
>> editors put in vertical guide lines to help keep
>> Python code right. IDLE is the most common with that,
>> but more elaborate editors like PyCharm can be had.
>> I *think* geany can be set to do that also.
> [snip]
>
>
> The annoyance comes from different editors having different rules on it,
> I think.
Um ... maybe SOMETIMES. Depends on how 'smart' they are
with the particular lang you're using. However one of
THE most common vexations with Python is improperly
indented lines. While I love nano it WON'T help you
there. IDLE is savvy, puts (too fine) guide lines
over the GUI display.
Gotta research 'geany' ... it's a good editor. However
I've forgotten how to do the config file so it will
rec "*.py3" - which I use for everything - as meaning
Python-3. I did it ONCE, but forgot .....
PyCharm ... it's a good IDE ... but SO complex, SO
oriented towards huge multi-author 'projects', that
it's just, well, TOO.
After thinking about it for a year, last night ...
ok night->noon, I wrote a little Python function
for determining when 'dawn' and 'sunset' happen.
I need this for three, maybe more soon, USB
security cams. Two are on a mini-PC box and one
on a PI.
The cams need to shift between 'day' and 'night'
at the correct times - or the image gets too
dark or horribly washed-out.
HAVE been doing this, very crudely, with crontab.
It evokes 'v4l' command scripts at certain times.
But, as implied, the 'times' change through the
year.
Found a page at the US Naval Observatory that had
a table of months/days/sunrise/sunset times. Note
that there is almost NO diff over MANY years. Saved
as text, removed some bullshit from the top, now
EASY to access/parse with Python. Simple math gets
you to the exact right month/day in a step and a few
string slice trix deliver the proper values.
Ah :
https://aa.usno.navy.mil/data/RS_OneYear
Give it a year (irrelevant) and a lat/long
(it will help you there) and you get a
page you can save as 'text'. Rigid space-delim
format for the table, makes it SO easy. Wish
many OTHERS would be so smart/convenient, but
they WON'T anymore, indeed tend to hide data
behind JS ... horrible !!! "Government" is
MOST likely to have simple/sweet tables.
Once you have the table, well, my straight-up
v1.0 code is :
# dissect the table
try:
row=txt[3+int(thisDay)] # get correct row for today
row=row.split(" ") # break up at doublespaces
col=row[thisMonth] # get correct column
col=col.split(" ") # break at spaces
t1=col[0].strip() # get sunrise string
rHR=int(t1[0:2]) # hour
rMN=int(t1[2:4]) # minute
t1=col[1].strip() # get sunset string
sHR=int(t1[0:2]) # hour
sMN=int(t1[2:4]) # minute
except :
rHR=7 ; rMN=7 ; sHR=19 ; sMN=7 # defaults
"thisDay" and "thisMonth" provided by using datetime.now functions
Note my line-by-line commenting. 40 line block comment
at the head of the function explaining things.
Yea, yea ... maybe some of that can be compressed into
single, long, lines ... but WHY ??? Just makes it more
obscure, harder to figure out a year or two from now.
You CAN send the function a specific [month,day] list,
but basically I intend to use it real-time. Returns
a text file with the four values on individual lines
to the current dir AND a list of integers containing
the four values.
Plan ... make a simple daemon ... initiated at
start-up. Sleeps, then does its thing once a minute.
IF within day/night params then run the correct v4l
commands (ARE scripts, but I'm just importing the
text and using os.system() to do 'em).
Result ... at the CORRECT times all through the year
the cams will will be switched from day to night mode.
My cams, best to switch night to day at 15 minutes
before actual sunrise, ok to wait for actual sunset
to switch to night mode. Each mode sets different
brightness/contrast/sharpness/tone figures. The
daemon will check times every minute and do whatever.
Note that because power fails and reboots are possible
we do the v4l commands EVERY minute regardless. Almost
zero CPU load.
Oh, note possible quirk with 'v4l2' ... you MAY have
to set, reverse, then set AGAIN to make it 'take'.
Probably 'depends'. On the PI, once is enough, on
the mini-box, Manjaro, gotta double up.
Anyway, this is how I hack together even 'simple'
stuff AND do the comments so I can "get it"
later on.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-21 04:00 +0000 |
| Subject | Re: Python |
| Message-ID | <mqp9m9Ff5tvU4@mid.individual.net> |
| In reply to | #79549 |
On Sat, 20 Dec 2025 02:52:15 -0500, c186282 wrote: > Gotta research 'geany' ... it's a good editor. However I've forgotten > how to do the config file so it will rec "*.py3" - which I use for > everything - as meaning Python-3. I did it ONCE, but forgot ..... VS Code is good if it doesn't get completely enshitified with AI. So far you can tell it to FOAD. I've got Code-OSS on the Endeavour box but haven't used it enough to discover the pitfalls. It's upstream of VS Code but without the MS secret sauce some of the extensions. For example it has the Python extension but not PyLance. Probably not a big loss and it is sometimes a PITA if I'm using MicroPython. Vim, of course, has Python configurations. There is an option to highlight the whitespace in red (configurable) that I turned off.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-12-23 16:00 +0000 |
| Subject | Re: Python |
| Message-ID | <slrn10klf2f.qml9.candycanearter07@candydeb.host.invalid> |
| In reply to | #79630 |
rbowman <bowman@montana.com> wrote at 04:00 this Sunday (GMT): > On Sat, 20 Dec 2025 02:52:15 -0500, c186282 wrote: > >> Gotta research 'geany' ... it's a good editor. However I've forgotten >> how to do the config file so it will rec "*.py3" - which I use for >> everything - as meaning Python-3. I did it ONCE, but forgot ..... > > VS Code is good if it doesn't get completely enshitified with AI. So far > you can tell it to FOAD. I've got Code-OSS on the Endeavour box but > haven't used it enough to discover the pitfalls. It's upstream of VS Code > but without the MS secret sauce some of the extensions. For example it has > the Python extension but not PyLance. Probably not a big loss and it is > sometimes a PITA if I'm using MicroPython. You can also use VSCodium if you want, but I don't like VSCs UI in general, so I use vim. > Vim, of course, has Python configurations. There is an option to highlight > the whitespace in red (configurable) that I turned off. Do you prefer tabs or spaces? -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-23 20:30 +0000 |
| Subject | Re: Python |
| Message-ID | <mr0cfqFkrd8U3@mid.individual.net> |
| In reply to | #79731 |
On Tue, 23 Dec 2025 16:00:06 -0000 (UTC), candycanearter07 wrote: > Do you prefer tabs or spaces? au BufRead,BufNewFile *.py,*pyw set shiftwidth=4 au BufRead,BufNewFile *.py,*.pyw set expandtab
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2025-12-23 21:14 +0000 |
| Subject | Re: Python |
| Message-ID | <4DD2R.223907$u2q8.208054@fx11.iad> |
| In reply to | #79740 |
rbowman <bowman@montana.com> writes: >On Tue, 23 Dec 2025 16:00:06 -0000 (UTC), candycanearter07 wrote: > >> Do you prefer tabs or spaces? > >au BufRead,BufNewFile *.py,*pyw set shiftwidth=4 >au BufRead,BufNewFile *.py,*.pyw set expandtab /* vim: set sw=4 sts=4 sta TS=8 et: */
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-12-19 20:57 +0000 |
| Subject | Re: Python |
| Message-ID | <6945bc2b$0$11457$426a34cc@news.free.fr> |
| In reply to | #79131 |
Le 15-12-2025, c186282 <c186282@nnada.net> a écrit :
> On 12/14/25 06:56, Stéphane CARPENTIER wrote:
>> Le 14-12-2025, c186282 <c186282@nnada.net> a écrit :
>>>
>>> NOT sure why so many people want to trash Python.
>>
>> My issues with python are:
>> - It's using indentations, so when I comment a block of code to see
>> what happens, it breaks everything and I have to manage the
>> indentations. I can't just comment/uncomment a block of code as I do
>> with other programming languages.
>
> You CAN do block comments BTW ... use triple-quote at
> the beginning/end. The double and single quote char
> work.
It's not my issu. Vim is able to comment blocks of code without issue.
It's python that can't always manage it. Let say I have that part of
code:
if test1:
if test2:
do some stuff
If I comment the second line to see what happens if I remove my test2,
like I would do with any normal language, then with python it just
doesn't work because it breaks the indentation. So, I have to change the
indentation at the same time. And when there are many lines of code, it
can be difficult to see with which if the else is related. It's an
example. I could want to remove a loop to get faster to the point with
only a value and it's the same issue.
> Indents ... well ... those have been good programming
> practice since forever.
I have no issue with indentation. I would find awful a program displayed
on only one line of code or a program with many lines without
indentation.
> With Python they are also
> functional, not just 'decorative'.
And that's where the issue begins. Because sometimes indentation matters
and other times that matter differently, for example in a function call
the parenthesis it's taken care differently.
> but Python
> isn't THAT hard to deal with. Typically use just TWO
> space indents to keep line-lengths shorter. A few
> editors put in vertical guide lines to help keep
> Python code right.
It's not that easy to read a program with many lines
>> - It's sold as an easy programming language. Which is true for
>> discovering it. And once I'm using it in the real life, I
>> discover the hard reality. A lot of things that should just work don't
>> because it's an exception.
>
> Umm ... haven't had many problems myself - and I came
> from COBOL, FORTRAN, Pascal, C .......
Sometimes with libraries I have to parse files or databases, I have to test
"var is None or var == 'None' or var ==''" because it depends on things
I don't understand and it's not my job to spend time on programming. I
have to debug or improve the programs I inherited, but my job is to use
them, not to program them.
--
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-12-19 22:09 +0000 |
| Subject | Re: Python |
| Message-ID | <wwva4zei0nq.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #79518 |
Stéphane CARPENTIER <sc@fiat-linux.fr> writes:
> It's not my issu. Vim is able to comment blocks of code without issue.
> It's python that can't always manage it. Let say I have that part of
> code:
>
> if test1:
> if test2:
> do some stuff
>
> If I comment the second line to see what happens if I remove my test2,
> like I would do with any normal language, then with python it just
> doesn't work because it breaks the indentation.
$ cat t.py
test1=True
test2=False
if test1:
if test2:
print("L6")
if test1:
#if test2:
print("L10")
$ python3 t.py
L10
--
https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-20 05:37 +0000 |
| Subject | Re: Python |
| Message-ID | <mqmr0vF2n74U4@mid.individual.net> |
| In reply to | #79531 |
On Fri, 19 Dec 2025 22:09:45 +0000, Richard Kettlewell wrote:
> Stéphane CARPENTIER <sc@fiat-linux.fr> writes:
>> It's not my issu. Vim is able to comment blocks of code without issue.
>> It's python that can't always manage it. Let say I have that part of
>> code:
>>
>> if test1:
>> if test2:
>> do some stuff
>>
>> If I comment the second line to see what happens if I remove my test2,
>> like I would do with any normal language, then with python it just
>> doesn't work because it breaks the indentation.
>
> $ cat t.py test1=True test2=False
>
> if test1:
> if test2:
> print("L6")
>
> if test1:
> #if test2:
> print("L10")
> $ python3 t.py L10
$ ruff check t.py
All checks passed!
$ ruff format t.py
1 file reformatted
ruff did move the print(("L10") out so you wouldn't want to format the
file. Removing the # from the formatted file without fixing the
indentations gives
$ ruff check t.py
invalid-syntax: Expected an indented block after `if` statement
--> t.py:10:5
|
8 | if test1:
9 | if test2:
10 | print("L10")
| ^^^^^
Stéphane doesn't like Python; I don't like Personal Home Page. We all have
our tastes.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-12-20 10:34 +0000 |
| Subject | Re: Python |
| Message-ID | <69467bb3$0$11432$426a74cc@news.free.fr> |
| In reply to | #79531 |
Le 19-12-2025, Richard Kettlewell <invalid@invalid.invalid> a écrit :
> Stéphane CARPENTIER <sc@fiat-linux.fr> writes:
>> It's not my issu. Vim is able to comment blocks of code without issue.
>> It's python that can't always manage it. Let say I have that part of
>> code:
>>
>> if test1:
>> if test2:
>> do some stuff
>>
>> If I comment the second line to see what happens if I remove my test2,
>> like I would do with any normal language, then with python it just
>> doesn't work because it breaks the indentation.
>
> $ cat t.py
> test1=True
> test2=False
>
> if test1:
> if test2:
> print("L6")
>
> if test1:
> #if test2:
> print("L10")
> $ python3 t.py
> L10
OK, so it works with your example and it doesn't with more nested
loops/if and I don't know when it will work and when it won't. So, it's
exactly my issue with python: that works when expected except when that
doesn't and I don't know why/when.
--
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2025-12-20 11:45 +0000 |
| Subject | Re: Python |
| Message-ID | <10i6285$1u58s$1@dont-email.me> |
| In reply to | #79531 |
On 2025-12-19, Richard Kettlewell wrote:
> Stéphane CARPENTIER <sc@fiat-linux.fr> writes:
>> It's not my issu. Vim is able to comment blocks of code without issue.
>> It's python that can't always manage it. Let say I have that part of
>> code:
>>
>> if test1:
>> if test2:
>> do some stuff
>>
>> If I comment the second line to see what happens if I remove my test2,
>> like I would do with any normal language, then with python it just
>> doesn't work because it breaks the indentation.
>
> $ cat t.py
> test1=True
> test2=False
>
> if test1:
> if test2:
> print("L6")
>
> if test1:
> #if test2:
> print("L10")
> $ python3 t.py
> L10
Doesn't this only work if there are no statements directly under "if
test1:" besides the second conditional?
--
Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-12-20 13:32 +0000 |
| Subject | Re: Python |
| Message-ID | <6946a57f$0$11429$426a74cc@news.free.fr> |
| In reply to | #79568 |
Le 20-12-2025, Nuno Silva <nunojsilva@invalid.invalid> a écrit :
> On 2025-12-19, Richard Kettlewell wrote:
>
>> Stéphane CARPENTIER <sc@fiat-linux.fr> writes:
>>> It's not my issu. Vim is able to comment blocks of code without issue.
>>> It's python that can't always manage it. Let say I have that part of
>>> code:
>>>
>>> if test1:
>>> if test2:
>>> do some stuff
>>>
>>> If I comment the second line to see what happens if I remove my test2,
>>> like I would do with any normal language, then with python it just
>>> doesn't work because it breaks the indentation.
>>
>> $ cat t.py
>> test1=True
>> test2=False
>>
>> if test1:
>> if test2:
>> print("L6")
>>
>> if test1:
>> #if test2:
>> print("L10")
>> $ python3 t.py
>> L10
>
> Doesn't this only work if there are no statements directly under "if
> test1:" besides the second conditional?
I'm happy to see I'm not the only one unable to answer that question for
sure. I really believed my example was a complete minimal example
without checking it when I posted it. And when I saw his answer, I had
to check it. And, yes, I saw: it works. And that's exactly what I'm
saying when I say that real life examples don't work anymore when using
beginners examples. There is a huge gap between the python sold as easy
to understand for beginners and the python that works fine for experts.
And pretending python is good for beginners because it works fine for
experts is just a lie.
I'm not a python expert and I have neither time nor will to become one.
--
Si vous avez du temps à perdre :
https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
Page 46 of 48 — ← Prev page 1 … 44 45 [46] 47 48 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web