Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #77961 > unrolled thread
| Started by | Johnny Billquist <bqt@softjar.se> |
|---|---|
| First post | 2025-11-27 19:55 +0100 |
| Last post | 2025-12-08 18:40 +0000 |
| Articles | 20 on this page of 234 — 30 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 19:55 +0100
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-11-28 22:08 +0100
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-03 13:37 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-03 13:56 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-03 13:58 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-03 15:40 +0100
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-03 07:39 -0700
Re: Recent history of vi Andreas Eder <a_eder_muc@web.de> - 2025-12-06 16:46 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-13 08:28 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-15 10:38 +0100
Re: Recent history of vi antispam@fricas.org (Waldek Hebisch) - 2025-12-16 02:20 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-16 02:52 +0000
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-16 11:53 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-12-16 17:42 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-17 10:39 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-16 23:34 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-17 01:49 +0000
Re: Recent history of vi Diego Garcia <dg@linux.rocks> - 2025-12-03 14:40 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-12-04 07:00 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-05 20:52 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-05 15:57 -0700
Re: Recent history of vi candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-12-08 18:40 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-13 11:42 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-12-13 11:40 +0000
Re: Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-13 15:58 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-06 12:22 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-06 19:51 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-06 15:13 -0700
Re: polyglot programming, Recent history of vi John Levine <johnl@taugh.com> - 2025-12-06 22:28 +0000
Re: polyglot programming, Recent history of vi rbowman <bowman@montana.com> - 2025-12-07 01:39 +0000
Re: polyglot programming, Recent history of vi Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-07 06:19 +0000
Re: polyglot programming, Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-06 22:50 -0800
Re: polyglot programming, Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-07 10:52 +0000
Re: polyglot programming, Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-22 12:02 +0000
Re: polyglot programming, Recent history of vi rbowman <bowman@montana.com> - 2025-12-07 18:34 +0000
Re: polyglot programming, Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-16 00:02 +0000
Re: polyglot programming, Recent history of vi rbowman <bowman@montana.com> - 2025-12-16 01:41 +0000
Re: polyglot programming, Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-16 07:39 -0700
Re: polyglot programming, Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 15:57 +0000
Re: polyglot programming, Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-17 07:13 +0000
Re: polyglot programming, Recent history of vi Andy Walker <anw@cuboid.co.uk> - 2025-12-07 16:58 +0000
Re: polyglot programming, Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-16 00:00 +0000
Re: Recent history of vi Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-07 00:35 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-07 19:48 +0100
Re: Recent history of vi Lars Poulsen <lars@beagle-ears.com> - 2025-12-07 00:38 +0000
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-07 01:31 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-07 11:18 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-07 18:52 +0000
Re: more polyglot programming, was Recent history of vi John Levine <johnl@taugh.com> - 2025-12-07 19:39 +0000
Re: more polyglot programming, was Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-07 20:27 +0000
Re: more polyglot programming, was Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-07 14:31 -0700
Re: more polyglot programming, was Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 01:46 +0000
Re: more polyglot programming, was Recent history of vi Rich <rich@example.invalid> - 2025-12-08 05:53 +0000
Re: more polyglot programming, was Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-07 22:25 -0800
Re: more polyglot programming, was Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 08:34 +0000
Re: more polyglot programming, was Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:48 +0000
Re: more polyglot programming, was Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 23:43 +0000
Re: more polyglot programming, was Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 23:56 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-07 16:31 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-07 18:49 +0000
Re: Recent history of vi scott@slp53.sl.home (Scott Lurndal) - 2025-12-07 19:12 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-07 19:44 +0000
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-07 12:14 -0800
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-07 20:26 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 03:05 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:46 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-08 16:39 +0100
Re: Recent history of vi Rich Alderson <news@alderson.users.panix.com> - 2025-12-08 16:07 -0500
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-10 13:15 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 13:43 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-11 02:54 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-11 08:55 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 00:41 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-07 14:30 -0700
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 03:12 +0000
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-07 11:52 -0800
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-07 20:23 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-07 22:54 +0100
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-07 14:25 -0800
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:25 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-08 16:26 +0100
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-08 12:15 -0700
Re: Recent history of vi Rich Alderson <news@alderson.users.panix.com> - 2025-12-08 16:13 -0500
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-10 13:19 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-09 00:08 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 23:58 +0000
Greek origins of Christian scriptures [was Re: Recent history of vi] Rich Alderson <news@alderson.users.panix.com> - 2025-12-07 18:17 -0500
Re: Recent history of vi Rich <rich@example.invalid> - 2025-12-08 01:35 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:34 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-08 14:23 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-09 01:10 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-12-09 04:25 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-12-09 04:47 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-10 15:16 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 16:59 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-11 02:55 +0000
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-10 19:34 -0800
Re: Recent history of vi drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-12 16:13 +0000
Re: Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-13 15:51 +0000
Re: Recent history of vi Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-14 04:57 +0000
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-13 21:21 -0800
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-20 00:21 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-20 05:52 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 02:38 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:21 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-12-08 07:38 -0700
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-12-12 06:59 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-12 07:35 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-08 16:35 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-10 13:54 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-10 13:41 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-10 23:07 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-11 08:52 +0000
Re: Recent history of vi John Levine <johnl@taugh.com> - 2025-12-11 20:54 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-11 20:57 +0000
Re: linguistic hegemony, was Recent history of vi John Levine <johnl@taugh.com> - 2025-12-12 02:01 +0000
Re: linguistic hegemony, was Recent history of vi rbowman <bowman@montana.com> - 2025-12-12 02:27 +0000
Re: linguistic hegemony, was Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-12 03:28 +0100
Re: linguistic hegemony, was Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-11 21:43 -0800
Re: linguistic hegemony, was Recent history of vi rbowman <bowman@montana.com> - 2025-12-12 07:25 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-12 09:57 +0100
EU (was: Re: Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-12 09:53 +0000
Re: EU (was: Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-12 11:51 +0100
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:54 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-12 19:26 +0000
Re: EU Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-13 12:01 +0100
Re: EU Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-20 00:23 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:34 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-15 20:59 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 21:34 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-15 23:24 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-16 05:54 +0000
Re: EU Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-16 12:47 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-16 19:57 +0000
Re: EU "Carlos E.R." <robin_listas@es.invalid> - 2025-12-17 13:27 +0100
Re: EU c186282 <c186282@nnada.net> - 2025-12-17 22:05 -0500
Re: EU Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-17 07:34 -0500
Re: EU Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-16 12:42 -0500
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-16 18:14 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-16 19:55 +0000
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-16 20:05 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-16 20:30 +0000
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-16 23:15 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-17 01:49 +0000
Re: EU Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-12-17 07:32 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-17 18:53 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-16 05:54 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-16 08:06 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:33 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-16 20:02 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-17 01:09 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-17 01:18 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-17 03:03 -0500
Re: EU "Carlos E.R." <robin_listas@es.invalid> - 2025-12-18 23:26 +0100
Re: EU c186282 <c186282@nnada.net> - 2025-12-19 02:29 -0500
Re: EU "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-18 17:28 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-19 00:32 -0500
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-19 10:47 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-19 19:30 +0000
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-19 20:01 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-19 22:03 +0000
Re: EU John Ames <commodorejohn@gmail.com> - 2025-12-19 14:08 -0800
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-19 22:33 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-20 05:12 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-20 20:45 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-21 03:41 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-22 01:00 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-22 07:06 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-22 02:21 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-22 19:06 +0000
Re: EU Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-22 14:41 -0800
Re: EU c186282 <c186282@nnada.net> - 2025-12-23 01:59 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-23 19:47 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-23 21:18 +0000
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-23 22:38 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-23 23:32 +0000
Re: EU "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-24 10:24 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-24 12:36 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-23 23:27 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-23 23:40 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-24 07:02 +0000
Re: EU "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-24 10:32 +0000
Re: EU Lars Poulsen <lars@beagle-ears.com> - 2025-12-24 15:04 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-24 23:28 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-23 01:21 -0500
Re: EU scott@slp53.sl.home (Scott Lurndal) - 2025-12-22 16:38 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-22 17:33 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-20 01:20 -0500
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-20 10:39 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-21 03:10 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-21 14:29 -0500
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-21 20:09 +0000
Re: EU rbowman <bowman@montana.com> - 2025-12-21 20:52 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-22 00:59 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-21 03:07 +0000
Re: EU c186282 <c186282@nnada.net> - 2025-12-17 00:04 -0500
Re: EU rbowman <bowman@montana.com> - 2025-12-17 07:43 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:30 +0000
Re: EU Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-12-16 05:54 +0000
Re: EU The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:25 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:53 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-12 20:27 +0100
Yes,{, Prime} Minister (was: Re: Recent history of vi) Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-12 23:27 +0000
Re: Recent history of vi "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-12-13 15:55 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-15 18:38 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-15 22:40 +0000
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-12-15 15:44 -0800
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-16 01:59 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:22 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:18 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-16 20:45 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-17 10:14 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-16 10:02 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-16 20:13 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-17 13:59 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-17 07:06 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-10 23:06 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-11 19:38 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-12-08 02:03 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:41 +0000
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-12-12 07:09 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-12 11:49 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-07 20:14 +0000
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-12-07 22:56 +0100
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-12-08 08:18 +0000
Re: Unicode (was Re: Recent history of vi) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-15 00:32 +0000
Re: Unicode (was Re: Recent history of vi) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-12-14 23:32 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-15 10:52 +0100
Re: Unicode, not Recent history of vi John Levine <johnl@taugh.com> - 2025-12-05 01:59 +0000
Re: Unicode, not Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-12-05 10:14 +0000
Re: Unicode, not Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-12-05 10:35 +0000
Re: Unicode, not Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-12-05 12:05 +0100
Re: Unicode, not Recent history of vi Andreas Eder <a_eder_muc@web.de> - 2025-12-06 16:41 +0100
Re: Unicode, not Recent history of vi candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-12-08 18:40 +0000
Page 2 of 12 — ← Prev page 1 [2] 3 4 … 12 Next page →
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2025-12-05 15:57 -0700 |
| Message-ID | <10gvo0v$1s112$1@dont-email.me> |
| In reply to | #78330 |
On 12/5/25 13:52, Stéphane CARPENTIER wrote: [snip] > > Agreed. I see only one issue clearly limited to UTF-8. In most of the actual > writing systems the characters are displayed from left to right, others > from right to left and, to my knowledge only old scripts, in > boustrophedon. I wonder, is there any way to do this now without a lot of work? Are the right-to-left charachers different from the left-to-right? > > Of course, the rendering isn't considered by the encoding. It's the > purpose of the font. I choose fonts which doesn't make me think about > the character written. The 0 and O doesn't have to be similar. Like 1 > and l and I can be easily differentiated. If it's not the case on your > computer and if that matters, change the font, not the encoding. > I usually spend a lot of time settling on fonts for an editor. Right now I'm using "IBM Plex Mono", but I've tried a bunch.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-12-08 18:40 +0000 |
| Message-ID | <slrn10je6j9.1sivk.candycanearter07@candydeb.host.invalid> |
| In reply to | #78332 |
Peter Flass <Peter@Iron-Spring.com> wrote at 22:57 this Friday (GMT): > On 12/5/25 13:52, Stéphane CARPENTIER wrote: > [snip] >> >> Agreed. I see only one issue clearly limited to UTF-8. In most of the actual >> writing systems the characters are displayed from left to right, others >> from right to left and, to my knowledge only old scripts, in >> boustrophedon. > > I wonder, is there any way to do this now without a lot of work? Are the > right-to-left charachers different from the left-to-right? >> >> Of course, the rendering isn't considered by the encoding. It's the >> purpose of the font. I choose fonts which doesn't make me think about >> the character written. The 0 and O doesn't have to be similar. Like 1 >> and l and I can be easily differentiated. If it's not the case on your >> computer and if that matters, change the font, not the encoding. Generally, thats considered an accesibility issue I think. > I usually spend a lot of time settling on fonts for an editor. Right now > I'm using "IBM Plex Mono", but I've tried a bunch. Same, I'm currently using "Monocraft" -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-12-13 11:42 +0000 |
| Message-ID | <693d512e$0$28072$426a74cc@news.free.fr> |
| In reply to | #78510 |
Le 08-12-2025, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> a écrit : > Peter Flass <Peter@Iron-Spring.com> wrote at 22:57 this Friday (GMT): >> On 12/5/25 13:52, Stéphane CARPENTIER wrote: >> [snip] >>> >>> Agreed. I see only one issue clearly limited to UTF-8. In most of the actual >>> writing systems the characters are displayed from left to right, others >>> from right to left and, to my knowledge only old scripts, in >>> boustrophedon. >> >> I wonder, is there any way to do this now without a lot of work? Are the >> right-to-left charachers different from the left-to-right? >>> >>> Of course, the rendering isn't considered by the encoding. It's the >>> purpose of the font. I choose fonts which doesn't make me think about >>> the character written. The 0 and O doesn't have to be similar. Like 1 >>> and l and I can be easily differentiated. If it's not the case on your >>> computer and if that matters, change the font, not the encoding. > > Generally, thats considered an accesibility issue I think. It depends on the purpose. If you are reading a novel, it's not. If you are reading a password, it is. Between those two use cases, it depends. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-12-13 11:40 +0000 |
| Message-ID | <693d50af$0$28072$426a74cc@news.free.fr> |
| In reply to | #78332 |
Le 05-12-2025, Peter Flass <Peter@Iron-Spring.com> a écrit : > On 12/5/25 13:52, Stéphane CARPENTIER wrote: > [snip] >> >> Agreed. I see only one issue clearly limited to UTF-8. In most of the actual >> writing systems the characters are displayed from left to right, others >> from right to left and, to my knowledge only old scripts, in >> boustrophedon. > > I wonder, is there any way to do this now without a lot of work? Are the > right-to-left charachers different from the left-to-right? I believe that characters form rigth-to-left are different than those from left-to-right because if it wasn't the case it would be cumbersome to write by hand. But I see no difficulties. The same way as the same Arabic letter is written differently if it's in the beginning, in the end or in the middle of a word. As the same time as you have a character to tell you it's the end of the line or the end of the file, you have a character to switch the order of the reading. So everything is ready to use, maybe the old boustrophedon scripts are already encoded, I have no clue. But I see no issue for taking care of it. >> Of course, the rendering isn't considered by the encoding. It's the >> purpose of the font. I choose fonts which doesn't make me think about >> the character written. The 0 and O doesn't have to be similar. Like 1 >> and l and I can be easily differentiated. If it's not the case on your >> computer and if that matters, change the font, not the encoding. > > I usually spend a lot of time settling on fonts for an editor. Right now > I'm using "IBM Plex Mono", but I've tried a bunch. That I can understand. When I was young, I was looking for nice looking fonts. Now, I'm looking for easy to distinguish characters fonts. I'm stuck with source code pro which is fine for me. But I could switch to another font, I'll would look for 0 O I l 1 to see if I have to discard it directly or not. When reading plain text English or French it's not very important, when reading programs, it can be. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | "Kerr-Mudd, John" <admin@127.0.0.1> |
|---|---|
| Date | 2025-12-13 15:58 +0000 |
| Message-ID | <20251213155807.ee72508720492c2e3587bd12@127.0.0.1> |
| In reply to | #78984 |
On 13 Dec 2025 11:40:31 GMT Stéphane CARPENTIER <sc@fiat-linux.fr> wrote: > Le 05-12-2025, Peter Flass <Peter@Iron-Spring.com> a écrit : > > On 12/5/25 13:52, Stéphane CARPENTIER wrote: > > [snip] > >> > >> Agreed. I see only one issue clearly limited to UTF-8. In most of the actual > >> writing systems the characters are displayed from left to right, others > >> from right to left and, to my knowledge only old scripts, in > >> boustrophedon. > > > > I wonder, is there any way to do this now without a lot of work? Are the > > right-to-left charachers different from the left-to-right? > > I believe that characters form rigth-to-left are different than those > from left-to-right because if it wasn't the case it would be cumbersome > to write by hand. But I see no difficulties. The same way as the same > Arabic letter is written differently if it's in the beginning, in the > end or in the middle of a word. As the same time as you have a character > to tell you it's the end of the line or the end of the file, you have a > character to switch the order of the reading. So everything is ready to > use, maybe the old boustrophedon scripts are already encoded, I have no > clue. But I see no issue for taking care of it. > > >> Of course, the rendering isn't considered by the encoding. It's the > >> purpose of the font. I choose fonts which doesn't make me think about > >> the character written. The 0 and O doesn't have to be similar. Like 1 > >> and l and I can be easily differentiated. If it's not the case on your > >> computer and if that matters, change the font, not the encoding. > > > > I usually spend a lot of time settling on fonts for an editor. Right now > > I'm using "IBM Plex Mono", but I've tried a bunch. > > That I can understand. When I was young, I was looking for nice looking > fonts. Now, I'm looking for easy to distinguish characters fonts. I'm > stuck with source code pro which is fine for me. But I could switch to > another font, I'll would look for 0 O I l 1 to see if I have to discard > it directly or not. When reading plain text English or French it's not > very important, when reading programs, it can be. > With my current level of eyesight I find a cursive? capital 'L' difficult to distinguish from 'I.'. Oh, the joy of fonts. -- Bah, and indeed Humbug.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-12-06 12:22 +0000 |
| Message-ID | <10h175s$2b64m$19@dont-email.me> |
| In reply to | #78330 |
On 05/12/2025 20:52, Stéphane CARPENTIER wrote: >> I would say the problem Unicode is trying to solve, albeit with some >> inconsistency, is the communication of all written languages in a >> standardized system of encoding. > Yes. And it wasn't a small thing to solve considering the way too limited > ASCII was everywhere. I think this is the best summary. In the end nearly everybody's first or second language is now [some form of] English, and I bet Chinese programmers don't type their C code in ideograms. Whilst English is possible the worst standard to adopt, it is a de facto standard. -- "I am inclined to tell the truth and dislike people who lie consistently. This makes me unfit for the company of people of a Left persuasion, and all women"
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-06 19:51 +0000 |
| Message-ID | <mpjfqaFo7f6U3@mid.individual.net> |
| In reply to | #78357 |
On Sat, 6 Dec 2025 12:22:19 +0000, The Natural Philosopher wrote: > I think this is the best summary. In the end nearly everybody's first or > second language is now [some form of] English, and I bet Chinese > programmers don't type their C code in ideograms. I've seen C written in languages other than English. To clarify, the C key words are the same, if, else, int, #include, and so forth but variable and function names, comments and everything else are in Spanish, German, and so forth. It's difficult to read.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2025-12-06 15:13 -0700 |
| Message-ID | <10h29pm$30833$1@dont-email.me> |
| In reply to | #78372 |
On 12/6/25 12:51, rbowman wrote: > On Sat, 6 Dec 2025 12:22:19 +0000, The Natural Philosopher wrote: > >> I think this is the best summary. In the end nearly everybody's first or >> second language is now [some form of] English, and I bet Chinese >> programmers don't type their C code in ideograms. > > I've seen C written in languages other than English. To clarify, the C key > words are the same, if, else, int, #include, and so forth but variable and > function names, comments and everything else are in Spanish, German, and > so forth. It's difficult to read. > I've seen the same with PL/I. I understand there was once an ALGOL compiler where they used French keywords. Debut-Fin, etc.
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@taugh.com> |
|---|---|
| Date | 2025-12-06 22:28 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10h2am5$2lt7$1@gal.iecc.com> |
| In reply to | #78375 |
According to Peter Flass <Peter@Iron-Spring.com>: >> I've seen C written in languages other than English. To clarify, the C key >> words are the same, if, else, int, #include, and so forth but variable and >> function names, comments and everything else are in Spanish, German, and >> so forth. It's difficult to read. > >I've seen the same with PL/I. I understand there was once an ALGOL >compiler where they used French keywords. Debut-Fin, etc. Algol60 had a reference language which had boldface keywords, and every implmentation made its own decision about how to translate that into the local character set. (Yes, this made portable programming a lot harder.) So while it was typical to turn the begin keyword into something like 'BEGIN' it was just as valid to turn it into 'DEBUT'. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-07 01:39 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <mpk47aF8qt0U1@mid.individual.net> |
| In reply to | #78376 |
On Sat, 6 Dec 2025 22:28:21 -0000 (UTC), John Levine wrote: > According to Peter Flass <Peter@Iron-Spring.com>: >>> I've seen C written in languages other than English. To clarify, the C >>> key words are the same, if, else, int, #include, and so forth but >>> variable and function names, comments and everything else are in >>> Spanish, German, and so forth. It's difficult to read. >> >>I've seen the same with PL/I. I understand there was once an ALGOL >>compiler where they used French keywords. Debut-Fin, etc. > > Algol60 had a reference language which had boldface keywords, and every > implmentation made its own decision about how to translate that into the > local character set. (Yes, this made portable programming a lot > harder.) So while it was typical to turn the begin keyword into > something like 'BEGIN' it was just as valid to turn it into 'DEBUT'. you could have real fun with Forth.
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2025-12-07 06:19 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <q%8ZQ.82856$Bfr.58031@fx17.iad> |
| In reply to | #78383 |
On 2025-12-07, rbowman <bowman@montana.com> wrote: > On Sat, 6 Dec 2025 22:28:21 -0000 (UTC), John Levine wrote: > >> According to Peter Flass <Peter@Iron-Spring.com>: >> >>>> I've seen C written in languages other than English. To clarify, the C >>>> key words are the same, if, else, int, #include, and so forth but >>>> variable and function names, comments and everything else are in >>>> Spanish, German, and so forth. It's difficult to read. >>> >>> I've seen the same with PL/I. I understand there was once an ALGOL >>> compiler where they used French keywords. Debut-Fin, etc. >> >> Algol60 had a reference language which had boldface keywords, and every >> implmentation made its own decision about how to translate that into the >> local character set. (Yes, this made portable programming a lot >> harder.) So while it was typical to turn the begin keyword into >> something like 'BEGIN' it was just as valid to turn it into 'DEBUT'. > > you could have real fun with Forth. I did. I still have a copy of Leo Brodie's _Starting Forth_. I got it running on my CP/M box and fiddled with it for a while. I never got any real-world application going, but I did manage to write a Sieve of Eratosthenes. Forth love if honk then -- /~\ Charlie Gibbs | Growth for the sake of \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology X I'm really at ac.dekanfrus | of the cancer cell. / \ if you read it the right way. | -- Edward Abbey
[toc] | [prev] | [next] | [standalone]
| From | Bobbie Sellers <bliss-sf4ever@dslextreme.com> |
|---|---|
| Date | 2025-12-06 22:50 -0800 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10h384c$39fv9$1@dont-email.me> |
| In reply to | #78388 |
On 12/6/25 22:19, Charlie Gibbs wrote:
> On 2025-12-07, rbowman <bowman@montana.com> wrote:
>
>> On Sat, 6 Dec 2025 22:28:21 -0000 (UTC), John Levine wrote:
>>
>>> According to Peter Flass <Peter@Iron-Spring.com>:
>>>
>>>>> I've seen C written in languages other than English. To clarify, the C
>>>>> key words are the same, if, else, int, #include, and so forth but
>>>>> variable and function names, comments and everything else are in
>>>>> Spanish, German, and so forth. It's difficult to read.
>>>>
>>>> I've seen the same with PL/I. I understand there was once an ALGOL
>>>> compiler where they used French keywords. Debut-Fin, etc.
>>>
>>> Algol60 had a reference language which had boldface keywords, and every
>>> implmentation made its own decision about how to translate that into the
>>> local character set. (Yes, this made portable programming a lot
>>> harder.) So while it was typical to turn the begin keyword into
>>> something like 'BEGIN' it was just as valid to turn it into 'DEBUT'.
>>
>> you could have real fun with Forth.
>
> I did. I still have a copy of Leo Brodie's _Starting Forth_.
> I got it running on my CP/M box and fiddled with it for a while.
> I never got any real-world application going, but I did manage
> to write a Sieve of Eratosthenes.
>
> Forth love if honk then
>
On the Amiga I used a shareware text processor called Textra.
Forth written it it was and very handy for editing Startup Scripts.
It did tricks I have not seen in Linux text processors and did them
somewhat more reliably than bookmarks in KWrite or Kate. Both
are excellent but aimed toward programmers more than simple
ASCII. I believe we had a menu-based "insert file" and know
we could select vertical columns of text and that was using the
mouse.
bliss-Dell Precision 7730-PCLOS 2025.10-Linux 6.12.60-pclos1- KDE
Plasma 6.5.3
[toc] | [prev] | [next] | [standalone]
| From | "Kerr-Mudd, John" <admin@127.0.0.1> |
|---|---|
| Date | 2025-12-07 10:52 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <20251207105256.2296b03bbd3725b0d4c12fc4@127.0.0.1> |
| In reply to | #78390 |
On Sat, 6 Dec 2025 22:50:50 -0800 Bobbie Sellers <bliss-sf4ever@dslextreme.com> wrote: > > > On 12/6/25 22:19, Charlie Gibbs wrote: > > On 2025-12-07, rbowman <bowman@montana.com> wrote: > > > >> On Sat, 6 Dec 2025 22:28:21 -0000 (UTC), John Levine wrote: > >> > >>> According to Peter Flass <Peter@Iron-Spring.com>: > >>> > >>>>> I've seen C written in languages other than English. To clarify, the C > >>>>> key words are the same, if, else, int, #include, and so forth but > >>>>> variable and function names, comments and everything else are in > >>>>> Spanish, German, and so forth. It's difficult to read. > >>>> > >>>> I've seen the same with PL/I. I understand there was once an ALGOL > >>>> compiler where they used French keywords. Debut-Fin, etc. > >>> > >>> Algol60 had a reference language which had boldface keywords, and every > >>> implmentation made its own decision about how to translate that into the > >>> local character set. (Yes, this made portable programming a lot > >>> harder.) So while it was typical to turn the begin keyword into > >>> something like 'BEGIN' it was just as valid to turn it into 'DEBUT'. > >> > >> you could have real fun with Forth. > > > > I did. I still have a copy of Leo Brodie's _Starting Forth_. > > I got it running on my CP/M box and fiddled with it for a while. > > I never got any real-world application going, but I did manage > > to write a Sieve of Eratosthenes. > > > > Forth love if honk then > > > > On the Amiga I used a shareware text processor called Textra. > Forth written it it was and very handy for editing Startup Scripts. > It did tricks I have not seen in Linux text processors and did them > somewhat more reliably than bookmarks in KWrite or Kate. Both > are excellent but aimed toward programmers more than simple > ASCII. I believe we had a menu-based "insert file" and know > we could select vertical columns of text and that was using the > mouse. > > bliss-Dell Precision 7730-PCLOS 2025.10-Linux 6.12.60-pclos1- KDE > Plasma 6.5.3 > xposted to clf, for more possible nostalgia. -- Bah, and indeed Humbug.
[toc] | [prev] | [next] | [standalone]
| From | "Kerr-Mudd, John" <admin@127.0.0.1> |
|---|---|
| Date | 2025-12-22 12:02 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <20251222120252.5c4895facadde6ffce8d0962@127.0.0.1> |
| In reply to | #78391 |
On Sun, 7 Dec 2025 10:52:56 +0000 "Kerr-Mudd, John" <admin@127.0.0.1> wrote: > On Sat, 6 Dec 2025 22:50:50 -0800 > Bobbie Sellers <bliss-sf4ever@dslextreme.com> wrote: > > > > > > > On 12/6/25 22:19, Charlie Gibbs wrote: > > > On 2025-12-07, rbowman <bowman@montana.com> wrote: > > > > > >> On Sat, 6 Dec 2025 22:28:21 -0000 (UTC), John Levine wrote: > > >> > > >>> According to Peter Flass <Peter@Iron-Spring.com>: > > >>> > > >>>>> I've seen C written in languages other than English. To clarify, the C > > >>>>> key words are the same, if, else, int, #include, and so forth but > > >>>>> variable and function names, comments and everything else are in > > >>>>> Spanish, German, and so forth. It's difficult to read. > > >>>> > > >>>> I've seen the same with PL/I. I understand there was once an ALGOL > > >>>> compiler where they used French keywords. Debut-Fin, etc. > > >>> > > >>> Algol60 had a reference language which had boldface keywords, and every > > >>> implmentation made its own decision about how to translate that into the > > >>> local character set. (Yes, this made portable programming a lot > > >>> harder.) So while it was typical to turn the begin keyword into > > >>> something like 'BEGIN' it was just as valid to turn it into 'DEBUT'. > > >> > > >> you could have real fun with Forth. > > > > > > I did. I still have a copy of Leo Brodie's _Starting Forth_. > > > I got it running on my CP/M box and fiddled with it for a while. > > > I never got any real-world application going, but I did manage > > > to write a Sieve of Eratosthenes. > > > > > > Forth love if honk then > > > > > > > On the Amiga I used a shareware text processor called Textra. > > Forth written it it was and very handy for editing Startup Scripts. > > It did tricks I have not seen in Linux text processors and did them > > somewhat more reliably than bookmarks in KWrite or Kate. Both > > are excellent but aimed toward programmers more than simple > > ASCII. I believe we had a menu-based "insert file" and know > > we could select vertical columns of text and that was using the > > mouse. > > > > bliss-Dell Precision 7730-PCLOS 2025.10-Linux 6.12.60-pclos1- KDE > > Plasma 6.5.3 > > > > xposted to clf, for more possible nostalgia. > <tumbleweed> Ah well. -- Bah, and indeed, Humbug
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-07 18:34 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <mplvmdFi256U2@mid.individual.net> |
| In reply to | #78388 |
On Sun, 07 Dec 2025 06:19:02 GMT, Charlie Gibbs wrote: > I did. I still have a copy of Leo Brodie's _Starting Forth_. > I got it running on my CP/M box and fiddled with it for a while. > I never got any real-world application going, but I did manage to write > a Sieve of Eratosthenes. > > Forth love if honk then I had two paying jobs that used Forth. The second was for a test rig for aircraft fuel and management systems. The company paid my way to the Forth conference in Rochester, NY. The most interesting part was Charlie Moore, who is a bit strange. He had a handheld keyboard for one handed typing that was sort of like learning chords on a guitar. They were recruiting Forth programmers for a airport baggage handling system -- in Riyadh. Good money but I passed. 'Threaded Interpretive Languages: Their Design and Implementation' by R. G. Loeliger was interesting and walked through a design for a Forth like language. https://archive.org/details/ R.G.LoeligerThreadedInterpretiveLanguagesTheirDesignAndImplementationByteBooks1981 if you need something to do this winter. iir there was an amazingly small kernel in Z80 assembler and you bootstrapped your way from there. The best description I've heard is 'Forth -- the language where the programmer is the preprocessor.'
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-12-16 00:02 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10hq7je$29cri$7@dont-email.me> |
| In reply to | #78388 |
On Sun, 07 Dec 2025 06:19:02 GMT, Charlie Gibbs wrote: > I still have a copy of Leo Brodie's _Starting Forth_. I got it > running on my CP/M box and fiddled with it for a while. I never got > any real-world application going, but I did manage to write a Sieve > of Eratosthenes. One time, I was looking for Forth-related projects on GitHub. I found lots of Forth implementations, but hardly anybody was using it to write actual applications. My feeling is, while both Forth and PostScript, as stack-based languages, belong in a museum these days, PostScript still has some interesting ideas worth resurrecting (homoiconicity, for one). Forth does not.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-12-16 01:41 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <mqbrlsF7nnkU1@mid.individual.net> |
| In reply to | #79245 |
On Tue, 16 Dec 2025 00:02:54 -0000 (UTC), Lawrence D’Oliveiro wrote: > On Sun, 07 Dec 2025 06:19:02 GMT, Charlie Gibbs wrote: > >> I still have a copy of Leo Brodie's _Starting Forth_. I got it running >> on my CP/M box and fiddled with it for a while. I never got any >> real-world application going, but I did manage to write a Sieve of >> Eratosthenes. > > One time, I was looking for Forth-related projects on GitHub. I found > lots of Forth implementations, but hardly anybody was using it to write > actual applications. https://www.forth.com/resources/forth-apps/ You can create domain specific, almost natural language interfaces with Forth. https://www.hackster.io/news/mecrisp-stellaris-port-brings-the-forth- programming-language-to-the-raspberry-pi-pico-rp2040-4c8e7077ae64 The video isn't very inspiring but it does open possibilities. It was always too idiosyncratic to take the world by storm but it does have its place.
[toc] | [prev] | [next] | [standalone]
| From | Peter Flass <Peter@Iron-Spring.com> |
|---|---|
| Date | 2025-12-16 07:39 -0700 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10hrquj$2ptll$1@dont-email.me> |
| In reply to | #79248 |
On 12/15/25 18:41, rbowman wrote: > On Tue, 16 Dec 2025 00:02:54 -0000 (UTC), Lawrence D’Oliveiro wrote: > >> On Sun, 07 Dec 2025 06:19:02 GMT, Charlie Gibbs wrote: >> >>> I still have a copy of Leo Brodie's _Starting Forth_. I got it running >>> on my CP/M box and fiddled with it for a while. I never got any >>> real-world application going, but I did manage to write a Sieve of >>> Eratosthenes. >> >> One time, I was looking for Forth-related projects on GitHub. I found >> lots of Forth implementations, but hardly anybody was using it to write >> actual applications. > > https://www.forth.com/resources/forth-apps/ > > You can create domain specific, almost natural language interfaces with > Forth. > > https://www.hackster.io/news/mecrisp-stellaris-port-brings-the-forth- > programming-language-to-the-raspberry-pi-pico-rp2040-4c8e7077ae64 > > The video isn't very inspiring but it does open possibilities. It was > always too idiosyncratic to take the world by storm but it does have its > place. I was interested in Forth in the early days because it seemed like a solution for systems with very limited resources. The interpreter is (I believe) quite small, and your application can be built up from just the words you need with no added cruft. That was the attraction of C for me back then, too. Unfortunately C gave up the idea of being a small language and has ballooned and become less clear and readable.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-12-16 15:57 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10hrvhm$2ripd$1@dont-email.me> |
| In reply to | #79294 |
On 16/12/2025 14:39, Peter Flass wrote: > > > I was interested in Forth in the early days because it seemed like a > solution for systems with very limited resources. The interpreter is (I > believe) quite small, and your application can be built up from just the > words you need with no added cruft. Yes, that is so. probably a K or so for the basic words that cabt be written in DForth itself That was the attraction of C for me > back then, too. Unfortunately C gave up the idea of being a small > language and has ballooned and become less clear and readable. C is as compact as it ever was. But advanced hardware and graphics means big fat libraries. -- "It is an established fact to 97% confidence limits that left wing conspirators see right wing conspiracies everywhere"
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-12-17 07:13 +0000 |
| Subject | Re: polyglot programming, Recent history of vi |
| Message-ID | <10htl7k$3af0f$4@dont-email.me> |
| In reply to | #79294 |
On Tue, 16 Dec 2025 07:39:15 -0700, Peter Flass wrote: > I was interested in Forth in the early days because it seemed like a > solution for systems with very limited resources. The interpreter is (I > believe) quite small, and your application can be built up from just the > words you need with no added cruft. That was the attraction of C for me > back then, too. Unfortunately C gave up the idea of being a small > language and has ballooned and become less clear and readable. Nevertheless, it is still feasible to cross-compile C code from a machine with more resources available, to one with much less.
[toc] | [prev] | [next] | [standalone]
Page 2 of 12 — ← Prev page 1 [2] 3 4 … 12 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web