Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #77092 > unrolled thread
| Started by | c186282 <c186282@nnada.net> |
|---|---|
| First post | 2025-11-08 02:01 -0500 |
| Last post | 2025-11-09 19:08 +0000 |
| Articles | 20 on this page of 349 — 35 participants |
Back to article view | Back to comp.os.linux.misc
Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-08 02:01 -0500
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 11:31 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 12:15 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 13:32 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 00:08 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:51 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:38 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:35 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-08 12:50 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 12:57 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-08 23:58 -0500
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-09 11:25 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-09 12:48 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 23:29 -0500
Re: Python/C/Pascal ... How To Choose ? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-09 09:18 -0800
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-09 20:13 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:47 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 12:09 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:35 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-10 21:15 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 23:33 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:23 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 01:03 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 10:57 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:36 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-11 20:50 +0100
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 23:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:38 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-12 16:38 -0800
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 04:29 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-13 05:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 01:09 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:42 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:37 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:46 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 05:31 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 06:00 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 02:08 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:55 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:30 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:56 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:54 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:17 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:38 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:20 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:50 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:18 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:54 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:28 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 23:25 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:35 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:49 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:49 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:31 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:33 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-11 21:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:21 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:13 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 05:40 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 01:20 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 23:31 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:39 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-10 19:48 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-10 20:35 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 21:53 +0100
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:37 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 23:51 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:40 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 23:01 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:33 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:27 +0100
Re: Python/C/Pascal ... How To Choose ? Andy Burns <usenet@andyburns.uk> - 2025-11-12 12:44 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 14:17 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:51 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-13 22:38 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:30 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 04:21 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:10 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 02:51 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:08 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:40 +0100
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 16:26 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 19:51 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 19:22 -0500
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-14 17:34 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 19:54 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:37 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 16:09 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-15 02:05 +0000
Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-15 09:59 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-15 17:32 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-15 18:48 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-15 21:38 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-15 22:07 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-15 22:21 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-15 23:14 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 00:29 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-16 00:43 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 00:45 +0000
Re: Recent history of vi Pancho <Pancho.Jones@protonmail.com> - 2025-11-16 09:14 +0000
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-16 15:40 +0000
Re: Recent history of vi Joe Makowiec <makowiec@invalid.invalid> - 2025-11-16 18:38 +0000
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-18 03:55 +0000
Re: Recent history of vi Joe Makowiec <makowiec@invalid.invalid> - 2025-11-19 13:11 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-19 20:12 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:10 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:01 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) rbowman <bowman@montana.com> - 2025-11-16 03:43 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:35 -0500
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-16 15:47 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 05:15 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-16 19:31 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 20:27 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 20:30 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:04 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-17 04:08 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:39 -0500
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:31 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:03 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-17 02:32 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-15 21:51 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 05:11 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 05:13 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-16 12:15 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-16 19:24 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-17 08:24 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-17 19:57 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-18 08:02 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-18 12:09 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:56 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-17 04:01 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-17 08:27 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 10:33 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:49 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:28 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 20:19 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:59 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 21:04 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:19 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 21:23 +0000
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-16 23:13 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 23:18 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-17 00:43 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-21 19:55 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-21 20:27 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-22 03:20 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 05:57 +0000
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-11-16 23:51 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-18 20:04 +0100
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-18 20:29 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-19 08:24 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-21 19:58 +0000
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-11-21 21:14 +0000
ISO 8859-1, ISO 8859-15 and their names (was: Re: Recent history of vi) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-21 23:20 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-11-21 19:10 -0700
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-22 10:23 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-22 17:55 +0100
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-11-22 19:20 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 21:43 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-23 00:23 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-23 02:17 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-23 09:42 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-23 14:59 +0100
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-23 13:09 -0800
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 22:57 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 02:56 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-11-22 20:18 -0700
Re: typing in the mysterious East, Recent history of vi John Levine <johnl@taugh.com> - 2025-11-24 01:45 +0000
Re: typing in the mysterious East, Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-23 18:06 -0800
Re: typing in the mysterious East, Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 02:13 +0000
Re: typing in the mysterious East, Recent history of vi John Levine <johnl@taugh.com> - 2025-11-24 02:23 +0000
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 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 "Carlos E.R." <robin_listas@es.invalid> - 2025-11-22 20:25 +0100
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-27 20:02 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-27 20:16 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-27 21:18 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-12-03 13:38 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-19 02:37 +0100
ISO 8859-1 ("Latin 1") (was: Recent history of vi) Michael Bäuerle <michael.baeuerle@stz-e.de> - 2025-11-19 14:58 +0100
Re: ISO 8859-1 ("Latin 1") (was: Recent history of vi) Eli the Bearded <*@eli.users.panix.com> - 2025-11-20 02:09 +0000
Re: ISO 8859-1 ("Latin 1") Peter Flass <Peter@Iron-Spring.com> - 2025-11-19 20:16 -0700
Re: ISO 8859-1 ("Latin 1") Richard Kettlewell <invalid@invalid.invalid> - 2025-11-20 08:47 +0000
Re: ISO 8859-1 ("Latin 1") The Natural Philosopher <tnp@invalid.invalid> - 2025-11-20 11:10 +0000
Re: ISO 8859-1 ("Latin 1") Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-20 17:57 +0000
Re: ISO 8859-1 ("Latin 1") Ralf Fassel <ralfixx@gmx.de> - 2025-11-21 12:24 +0100
Re: Recent history of vi Eric Pozharski <apple.universe@posteo.net> - 2025-11-19 13:02 +0000
Re: Recent history of vi antispam@fricas.org (Waldek Hebisch) - 2025-11-23 16:25 +0000
Re: Recent history of vi Eric Pozharski <apple.universe@posteo.net> - 2025-11-25 10:26 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-25 20:05 +0000
Re: Recent history of vi c186282 <c186282@nnada.net> - 2025-11-25 23:04 -0500
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 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 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 Anthk NM <anthk@disroot.org> - 2025-11-23 12:48 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-23 17:51 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 20:11 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 20:26 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:44 -0500
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:57 +0000
Re: Recent history of vi antispam@fricas.org (Waldek Hebisch) - 2025-11-15 19:52 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:50 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 18:56 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:24 -0500
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-16 00:43 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 03:20 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-16 16:14 +0000
Re: Recent history of vi scott@slp53.sl.home (Scott Lurndal) - 2025-11-17 19:39 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:24 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 19:41 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:00 -0500
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-13 10:56 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:25 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 04:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 23:40 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:05 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 02:48 -0500
Re: Python/C/Pascal ... How To Choose ? Rich <rich@example.invalid> - 2025-11-16 03:53 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:45 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-14 19:29 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-14 10:22 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-14 10:35 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 15:55 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-15 02:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 15:47 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:36 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:04 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 08:57 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 08:13 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:50 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 21:01 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 22:40 +0100
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 23:14 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 22:21 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 00:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:43 -0500
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 00:35 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-11 01:40 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:48 -0500
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 08:53 +0000
Re: Python/C/Pascal ... How To Choose ? Farley Flud <fsquared@fsquared.linux> - 2025-11-11 11:42 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:25 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:21 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:56 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 08:38 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:43 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:43 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:50 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:11 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:24 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-12 16:22 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 10:59 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 17:14 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:28 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:48 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 11:20 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:31 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:08 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:22 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-10 09:05 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:29 -0500
Re: Python/C/Pascal ... How To Choose ? Farley Flud <fsquared@fsquared.linux> - 2025-11-10 11:56 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 22:23 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-10 22:38 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 00:07 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-13 16:48 +0000
Re: Python/C/Pascal ... How To Choose ? Richard Kettlewell <invalid@invalid.invalid> - 2025-11-10 18:04 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 16:52 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-11 20:06 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 23:09 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 23:31 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:50 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 06:50 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:05 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-15 17:17 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:35 +0100
Re: Python/C/Pascal ... How To Choose ? Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-12 21:09 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:22 -0500
Re: Python/C/Pascal ... How To Choose ? Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-12 21:06 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:30 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:28 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:36 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:46 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 23:22 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 20:16 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 00:08 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 19:58 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 07:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 02:26 -0500
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 08:35 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:29 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:07 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 04:59 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:57 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:19 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-13 20:16 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:17 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 01:54 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:33 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 14:04 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 16:27 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 22:44 +0100
Re: Python/C/Pascal ... How To Choose ? Andy Burns <usenet@andyburns.uk> - 2025-11-14 13:24 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 17:03 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:10 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-11 21:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 00:56 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 13:28 +0100
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-08 12:45 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 14:35 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-08 22:15 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 00:28 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-08 20:29 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-09 01:11 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 02:37 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-09 09:11 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:08 +0000
Page 17 of 18 — ← Prev page 1 … 15 16 [17] 18 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-12 02:26 -0500 |
| Message-ID | <ysWdnU-7PO8Xq4n0nZ2dnZfqn_WdnZ2d@giganews.com> |
| In reply to | #77389 |
On 11/12/25 02:21, vallor wrote:
> At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
>
>> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>>
>>> On 11/10/25 02:46, rbowman wrote:
>>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>>
>>>>> On 11/9/25 14:28, rbowman wrote:
>>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>>
>>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>>> tomorrows forecast next week, or even next month.
>>>>>>
>>>>>> How about in a second or two? The starting point is
>>>>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>>>>>
>>>>> Keep getting "invalid point"
>>>>
>>>> Try
>>>>
>>>> https://api.weather.gov/points/42.934,-90.567
>>>
>>> That works ... but change the coords a bit and it won't. Seems it
>>> only knows a handful of locations.
>>
>> I picked that at random.
>>
>> https://api.weather.gov/points/36.934,-72.567
>> Chincoteague, VA
>>
>> https://api.weather.gov/points/40.934,-94.567
>> Lenox, IA
>>
>> https://api.weather.gov/points/36.934,-84.567
>> Burnside KY
>>
>> https://api.weather.gov/points/58.114,-134.666
>> Juneau, AK
>>
>> https://api.weather.gov/points/38.114,-134.666
>> no data, but it's 886 km off the coast of northern California.
>>
>> https://api.weather.gov/points/19.66,-156.012
>> Kailua, HI
>>
>> You do have to pick points in the US.
>>
>> https://api.weather.gov/points/51.130,-114.218
>> is Calgary AB and no data.
>
> This is pretty slick. I was able to grab the local weather
> forecast. It even includes icons for the weather.
>
> Thank you for posting about it.
All I get are pages of links to links to links ...
And 'icons' are NOT what I'm looking for - I want
comma/tab-delimited tables which automation can
easily get/process.
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-11-12 08:35 +0000 |
| Message-ID | <10f1gs5$18fo7$4@dont-email.me> |
| In reply to | #77390 |
At Wed, 12 Nov 2025 02:26:11 -0500, c186282 <c186282@nnada.net> wrote:
> On 11/12/25 02:21, vallor wrote:
> > At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
> >
> >> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
> >>
> >>> On 11/10/25 02:46, rbowman wrote:
> >>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
> >>>>
> >>>>> On 11/9/25 14:28, rbowman wrote:
> >>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
> >>>>>>
> >>>>>>> Try to predict the weather using Python. You'll be getting
> >>>>>>> tomorrows forecast next week, or even next month.
> >>>>>>
> >>>>>> How about in a second or two? The starting point is
> >>>>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
> >>>>>
> >>>>> Keep getting "invalid point"
> >>>>
> >>>> Try
> >>>>
> >>>> https://api.weather.gov/points/42.934,-90.567
> >>>
> >>> That works ... but change the coords a bit and it won't. Seems it
> >>> only knows a handful of locations.
> >>
> >> I picked that at random.
> >>
> >> https://api.weather.gov/points/36.934,-72.567
> >> Chincoteague, VA
> >>
> >> https://api.weather.gov/points/40.934,-94.567
> >> Lenox, IA
> >>
> >> https://api.weather.gov/points/36.934,-84.567
> >> Burnside KY
> >>
> >> https://api.weather.gov/points/58.114,-134.666
> >> Juneau, AK
> >>
> >> https://api.weather.gov/points/38.114,-134.666
> >> no data, but it's 886 km off the coast of northern California.
> >>
> >> https://api.weather.gov/points/19.66,-156.012
> >> Kailua, HI
> >>
> >> You do have to pick points in the US.
> >>
> >> https://api.weather.gov/points/51.130,-114.218
> >> is Calgary AB and no data.
> >
> > This is pretty slick. I was able to grab the local weather
> > forecast. It even includes icons for the weather.
> >
> > Thank you for posting about it.
>
> All I get are pages of links to links to links ...
>
> And 'icons' are NOT what I'm looking for - I want
> comma/tab-delimited tables which automation can
> easily get/process.
Well, I think JSON is easier to handle in programs, but you can use
jq(1) to create a CSV.
For instance, if you've grabbed the forecast link, try:
jq -r '.properties.periods[] | [.name, .detailedForecast] | @csv' forecast
(By default, wget will save your file as "forecast").
(And thank you for your commentary, without which I wouldn't have
gone and learned more about jq.)
--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G
OS: Linux 6.18.0-rc5 D: Mint 22.2 DE: Xfce 4.18
NVIDIA: 580.105.08 Mem: 258G
"Brain: The apparatus with which we think that we think."
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-12 20:29 +0000 |
| Message-ID | <mnk920Ff6c0U7@mid.individual.net> |
| In reply to | #77391 |
On Wed, 12 Nov 2025 08:35:17 +0000, vallor wrote: > (And thank you for your commentary, without which I wouldn't have gone > and learned more about jq.) Yeah, I didn't know about that one. I wonder if there is something like that to get from GPX to GeoJSON? https://en.wikipedia.org/wiki/GPS_Exchange_Format https://en.wikipedia.org/wiki/GeoJSON My fitness tracker exports gpx files but leaflet prefers GoeJSON: https://leafletjs.com/reference.html#geojson There is a gpx plugin but I didn't have much luck with it. No problem in C using the expat library to parse the XML and then emitting the GeoJSON. Python has a gpxpy module that works well but I only use that to extract data for my amusement, like finding the distance traveled by using the haversine formula for successive points. Python has a handy haversine module too. I coded my own for the C version. That's the drawback of being a programmer; you immediately reach for C, Python, C#, or some other language than neatly packaged tools like jq.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-12 23:07 -0500 |
| Message-ID | <AJGdndS5-KwNxIj0nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #77391 |
On 11/12/25 03:35, vallor wrote:
> At Wed, 12 Nov 2025 02:26:11 -0500, c186282 <c186282@nnada.net> wrote:
>
>> On 11/12/25 02:21, vallor wrote:
>>> At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
>>>
>>>> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>>>>
>>>>> On 11/10/25 02:46, rbowman wrote:
>>>>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>>>>
>>>>>>> On 11/9/25 14:28, rbowman wrote:
>>>>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>>>>
>>>>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>>>>> tomorrows forecast next week, or even next month.
>>>>>>>>
>>>>>>>> How about in a second or two? The starting point is
>>>>>>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>>>>>>>
>>>>>>> Keep getting "invalid point"
>>>>>>
>>>>>> Try
>>>>>>
>>>>>> https://api.weather.gov/points/42.934,-90.567
>>>>>
>>>>> That works ... but change the coords a bit and it won't. Seems it
>>>>> only knows a handful of locations.
>>>>
>>>> I picked that at random.
>>>>
>>>> https://api.weather.gov/points/36.934,-72.567
>>>> Chincoteague, VA
>>>>
>>>> https://api.weather.gov/points/40.934,-94.567
>>>> Lenox, IA
>>>>
>>>> https://api.weather.gov/points/36.934,-84.567
>>>> Burnside KY
>>>>
>>>> https://api.weather.gov/points/58.114,-134.666
>>>> Juneau, AK
>>>>
>>>> https://api.weather.gov/points/38.114,-134.666
>>>> no data, but it's 886 km off the coast of northern California.
>>>>
>>>> https://api.weather.gov/points/19.66,-156.012
>>>> Kailua, HI
>>>>
>>>> You do have to pick points in the US.
>>>>
>>>> https://api.weather.gov/points/51.130,-114.218
>>>> is Calgary AB and no data.
>>>
>>> This is pretty slick. I was able to grab the local weather
>>> forecast. It even includes icons for the weather.
>>>
>>> Thank you for posting about it.
>>
>> All I get are pages of links to links to links ...
>>
>> And 'icons' are NOT what I'm looking for - I want
>> comma/tab-delimited tables which automation can
>> easily get/process.
>
> Well, I think JSON is easier to handle in programs, but you can use
> jq(1) to create a CSV.
>
> For instance, if you've grabbed the forecast link, try:
>
> jq -r '.properties.periods[] | [.name, .detailedForecast] | @csv' forecast
>
> (By default, wget will save your file as "forecast").
>
> (And thank you for your commentary, without which I wouldn't have
> gone and learned more about jq.)
I am privileged to have been your inspiration ! :-)
Alas a LOT of current weather shit isn't even in JSON
format ... it's assembled ad-hoc from hidden files
and tables into JS-created pages. This MAY be just
the 'new guys' at work - or an actual conspiracy to
HIDE the data behind layers and layers so somebody
will have to register/PAY.
SOMETIMES you can get the JS and follow the links.
Sometimes not. Even thus, the links seem to CHANGE
fairly often. Not good for automated stuff.
Anyway, I'm looking for fairly straight-up solutions
that don't require 10,000 lines of code.
Govt-collected weather data - We The People have ALREADY
paid for it. We should be able to GET it without issues.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-13 04:59 +0000 |
| Message-ID | <mnl6tuFjr66U3@mid.individual.net> |
| In reply to | #77442 |
On Wed, 12 Nov 2025 23:07:31 -0500, c186282 wrote: > SOMETIMES you can get the JS and follow the links. > Sometimes not. Even thus, the links seem to CHANGE fairly often. Not > good for automated stuff. Whack-a-mole. For several years I had a Python apt that would scrape comics from the Go Comics site. You can still go there to read them https://www.gocomics.com/realitycheck but it was convenient to pull down the list of the ones I wanted. The app depended on the 'comics' module. It would stop working as gocomics added another hoop. After an upgrade it would start working for a while until yet another change. The current solution is to use Playwright.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-13 00:57 -0500 |
| Message-ID | <MuOcnTBTubHa7oj0nZ2dnZfqnPqdnZ2d@giganews.com> |
| In reply to | #77452 |
On 11/12/25 23:59, rbowman wrote: > On Wed, 12 Nov 2025 23:07:31 -0500, c186282 wrote: > >> SOMETIMES you can get the JS and follow the links. >> Sometimes not. Even thus, the links seem to CHANGE fairly often. Not >> good for automated stuff. > > Whack-a-mole. Yep !!! Even ten years ago I could expect obscure data links to BE there long-term. Now ... not at all. Not sure if it's accidental, intentional, stupidity or something sinister. MAY have to start doing monthly/weekly 'AI' searches just to FIND the raw data I want. Horrible ! And that's just "weather" shit ! > For several years I had a Python apt that would scrape > comics from the Go Comics site. You can still go there to read them > > https://www.gocomics.com/realitycheck > > but it was convenient to pull down the list of the ones I wanted. The app > depended on the 'comics' module. It would stop working as gocomics added > another hoop. After an upgrade it would start working for a while until > yet another change. The current solution is to use Playwright. Typical. Again, intentional, stupidity, sinister ??? What many sites want are active/live humans so they can feed them ADVERTS. Automated data scraping is the opposite of what pays the bills. But 'government' data ... should NOT be that way at all - but increasingly SEEMS so. I really LIKE my automated weather scrapes ... have three different apps - viewed constantly on various PI units - which use that stuff. This includes "Severe Weather Alerts" ... Damned well OUGHT to work ! And re-writing a fine-parser for yet another page ... BIG investment. Had to do near-human 'intuition' code just to get my latest current weather data ... a MESSY MESSY web page that changed subtly at random times. "Likely context" ... then 'similar keywords' ... then shifting back and forth looking for what looks like the right numbers. HELL !!!
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-11-13 10:19 +0000 |
| Message-ID | <10f4bbf$22lg1$1@dont-email.me> |
| In reply to | #77442 |
On 13/11/2025 04:07, c186282 wrote: > Govt-collected weather data - We The People have ALREADY > paid for it. We should be able to GET it without issues. Indeed. And flood and river level data...but all we get is a bunch of numpties with a big map colored red ... 'danger of flooding severe'... Do they think we are idiots? Yes, they do. On all sides of politics. -- "In our post-modern world, climate science is not powerful because it is true: it is true because it is powerful." Lucas Bergkamp
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-11-13 20:16 +0000 |
| Message-ID | <10f5eb9$2crs6$5@dont-email.me> |
| In reply to | #77464 |
On Thu, 13 Nov 2025 10:19:27 +0000, The Natural Philosopher wrote: > On 13/11/2025 04:07, c186282 wrote: >> >> Govt-collected weather data - We The People have ALREADY paid for >> it. We should be able to GET it without issues. > > Indeed. And flood and river level data...but all we get is a bunch > of numpties with a big map colored red ... 'danger of flooding > severe'... Our local Government gives us this <https://maps.hamilton.govt.nz/floodviewer/>.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-13 21:17 -0500 |
| Message-ID | <KX-dnSCOMLGyDIv0nZ2dnZfqn_WdnZ2d@giganews.com> |
| In reply to | #77464 |
On 11/13/25 05:19, The Natural Philosopher wrote: > On 13/11/2025 04:07, c186282 wrote: >> Govt-collected weather data - We The People have ALREADY >> paid for it. We should be able to GET it without issues. > > Indeed. And flood and river level data...but all we get is a bunch of > numpties with a big map colored red ... 'danger of flooding severe'... > > Do they think we are idiots? > > Yes, they do. On all sides of politics. > > Did spend a couple of hours today looking for alternate weather and radar sites. Found few good ones. In the USA, the NOAA and NWS do have 'less complex' pages, a couple that still have radar gif loops. Also found a commercial-ish site that pops up a new .png every five minutes - roll yer own loop with a little daemon. Going thru a number of aviation sites did find a couple of pages easier to parse than the one I've been using - one even has a 24 hour table. The 'main' NWS radar site alas is deep in JS and css and despite looking thru a lot of the code cannot discern where it gets its raw data or even if Joe Average can get there. My weather-show apps (PIs) already have the code to resize, reorient, even re-color, images extracted from GIFs - and the extracts get put into five ordinary .jpg files that then get played in order. So, not TOO evil to switch sources. Just hope it won't be necessary anytime soon. But "24-Hour-Conditions.csv" - those seem to be long gone. The public stuff is all about LOOKS now, pretty pretty pages with a zillion little buttons and drag capability and such.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-14 01:54 +0100 |
| Message-ID | <o7biulx6bn.ln2@Telcontar.valinor> |
| In reply to | #77442 |
On 2025-11-13 05:07, c186282 wrote:
> On 11/12/25 03:35, vallor wrote:
>> At Wed, 12 Nov 2025 02:26:11 -0500, c186282 <c186282@nnada.net> wrote:
>>
>>> On 11/12/25 02:21, vallor wrote:
>>>> At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
>>>>
>>>>> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>>>>>
>>>>>> On 11/10/25 02:46, rbowman wrote:
>>>>>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>>>>>
>>>>>>>> On 11/9/25 14:28, rbowman wrote:
>>>>>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>>>>>
>>>>>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>>>>>> tomorrows forecast next week, or even next month.
>>>>>>>>>
>>>>>>>>> How about in a second or two? The starting point is
>>>>>>>>> url = f"https://api.weather.gov/points/{latitude},
>>>>>>>>> {longitude}"
>>>>>>>>
>>>>>>>> Keep getting "invalid point"
>>>>>>>
>>>>>>> Try
>>>>>>>
>>>>>>> https://api.weather.gov/points/42.934,-90.567
>>>>>>
>>>>>> That works ... but change the coords a bit and it won't.
>>>>>> Seems it
>>>>>> only knows a handful of locations.
>>>>>
>>>>> I picked that at random.
>>>>>
>>>>> https://api.weather.gov/points/36.934,-72.567
>>>>> Chincoteague, VA
>>>>>
>>>>> https://api.weather.gov/points/40.934,-94.567
>>>>> Lenox, IA
>>>>>
>>>>> https://api.weather.gov/points/36.934,-84.567
>>>>> Burnside KY
>>>>>
>>>>> https://api.weather.gov/points/58.114,-134.666
>>>>> Juneau, AK
>>>>>
>>>>> https://api.weather.gov/points/38.114,-134.666
>>>>> no data, but it's 886 km off the coast of northern California.
>>>>>
>>>>> https://api.weather.gov/points/19.66,-156.012
>>>>> Kailua, HI
>>>>>
>>>>> You do have to pick points in the US.
>>>>>
>>>>> https://api.weather.gov/points/51.130,-114.218
>>>>> is Calgary AB and no data.
>>>>
>>>> This is pretty slick. I was able to grab the local weather
>>>> forecast. It even includes icons for the weather.
>>>>
>>>> Thank you for posting about it.
>>>
>>> All I get are pages of links to links to links ...
>>>
>>> And 'icons' are NOT what I'm looking for - I want
>>> comma/tab-delimited tables which automation can
>>> easily get/process.
>>
>> Well, I think JSON is easier to handle in programs, but you can use
>> jq(1) to create a CSV.
>>
>> For instance, if you've grabbed the forecast link, try:
>>
>> jq -r '.properties.periods[] | [.name, .detailedForecast] | @csv'
>> forecast
>>
>> (By default, wget will save your file as "forecast").
>>
>> (And thank you for your commentary, without which I wouldn't have
>> gone and learned more about jq.)
>
> I am privileged to have been your inspiration ! :-)
>
> Alas a LOT of current weather shit isn't even in JSON
> format ... it's assembled ad-hoc from hidden files
> and tables into JS-created pages. This MAY be just
> the 'new guys' at work - or an actual conspiracy to
> HIDE the data behind layers and layers so somebody
> will have to register/PAY.
>
> SOMETIMES you can get the JS and follow the links.
> Sometimes not. Even thus, the links seem to CHANGE
> fairly often. Not good for automated stuff.
>
> Anyway, I'm looking for fairly straight-up solutions
> that don't require 10,000 lines of code.
>
> Govt-collected weather data - We The People have ALREADY
> paid for it. We should be able to GET it without issues.
>
curl v2.wttr.in
gets you some weather info. I have in my machine "metar" from 2006, but
it no longer runs, it was compiled for 32 bits.
Chatgpt suggested these:
wego — nice TUI weather client written in Go
ansiweather — weather in your terminal using ANSI colors
weather-util — classic simple tool (weather command)
curl v2.wttr.in — alternative minimal text version
metar — shows aviation METAR weather reports
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-13 21:33 -0500 |
| Message-ID | <7o2dnTVBfZNmCYv0nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #77504 |
On 11/13/25 19:54, Carlos E.R. wrote:
> On 2025-11-13 05:07, c186282 wrote:
>> On 11/12/25 03:35, vallor wrote:
>>> At Wed, 12 Nov 2025 02:26:11 -0500, c186282 <c186282@nnada.net> wrote:
>>>
>>>> On 11/12/25 02:21, vallor wrote:
>>>>> At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
>>>>>
>>>>>> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>>>>>>
>>>>>>> On 11/10/25 02:46, rbowman wrote:
>>>>>>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>>>>>>
>>>>>>>>> On 11/9/25 14:28, rbowman wrote:
>>>>>>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>>>>>>
>>>>>>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>>>>>>> tomorrows forecast next week, or even next month.
>>>>>>>>>>
>>>>>>>>>> How about in a second or two? The starting point is
>>>>>>>>>> url = f"https://api.weather.gov/points/{latitude},
>>>>>>>>>> {longitude}"
>>>>>>>>>
>>>>>>>>> Keep getting "invalid point"
>>>>>>>>
>>>>>>>> Try
>>>>>>>>
>>>>>>>> https://api.weather.gov/points/42.934,-90.567
>>>>>>>
>>>>>>> That works ... but change the coords a bit and it won't.
>>>>>>> Seems it
>>>>>>> only knows a handful of locations.
>>>>>>
>>>>>> I picked that at random.
>>>>>>
>>>>>> https://api.weather.gov/points/36.934,-72.567
>>>>>> Chincoteague, VA
>>>>>>
>>>>>> https://api.weather.gov/points/40.934,-94.567
>>>>>> Lenox, IA
>>>>>>
>>>>>> https://api.weather.gov/points/36.934,-84.567
>>>>>> Burnside KY
>>>>>>
>>>>>> https://api.weather.gov/points/58.114,-134.666
>>>>>> Juneau, AK
>>>>>>
>>>>>> https://api.weather.gov/points/38.114,-134.666
>>>>>> no data, but it's 886 km off the coast of northern California.
>>>>>>
>>>>>> https://api.weather.gov/points/19.66,-156.012
>>>>>> Kailua, HI
>>>>>>
>>>>>> You do have to pick points in the US.
>>>>>>
>>>>>> https://api.weather.gov/points/51.130,-114.218
>>>>>> is Calgary AB and no data.
>>>>>
>>>>> This is pretty slick. I was able to grab the local weather
>>>>> forecast. It even includes icons for the weather.
>>>>>
>>>>> Thank you for posting about it.
>>>>
>>>> All I get are pages of links to links to links ...
>>>>
>>>> And 'icons' are NOT what I'm looking for - I want
>>>> comma/tab-delimited tables which automation can
>>>> easily get/process.
>>>
>>> Well, I think JSON is easier to handle in programs, but you can use
>>> jq(1) to create a CSV.
>>>
>>> For instance, if you've grabbed the forecast link, try:
>>>
>>> jq -r '.properties.periods[] | [.name, .detailedForecast] | @csv'
>>> forecast
>>>
>>> (By default, wget will save your file as "forecast").
>>>
>>> (And thank you for your commentary, without which I wouldn't have
>>> gone and learned more about jq.)
>>
>> I am privileged to have been your inspiration ! :-)
>>
>> Alas a LOT of current weather shit isn't even in JSON
>> format ... it's assembled ad-hoc from hidden files
>> and tables into JS-created pages. This MAY be just
>> the 'new guys' at work - or an actual conspiracy to
>> HIDE the data behind layers and layers so somebody
>> will have to register/PAY.
>>
>> SOMETIMES you can get the JS and follow the links.
>> Sometimes not. Even thus, the links seem to CHANGE
>> fairly often. Not good for automated stuff.
>>
>> Anyway, I'm looking for fairly straight-up solutions
>> that don't require 10,000 lines of code.
>>
>> Govt-collected weather data - We The People have ALREADY
>> paid for it. We should be able to GET it without issues.
>>
> curl v2.wttr.in
>
> gets you some weather info. I have in my machine "metar" from 2006, but
> it no longer runs, it was compiled for 32 bits.
>
> Chatgpt suggested these:
>
>
>
> wego — nice TUI weather client written in Go
>
> ansiweather — weather in your terminal using ANSI colors
>
> weather-util — classic simple tool (weather command)
>
> curl v2.wttr.in — alternative minimal text version
>
> metar — shows aviation METAR weather reports
Did a lot of searching today and DID find some
alternative sites - GIF loops, PNGs updated every
five minutes, data pages with minimal BS that are
fairly easy to parse. But good old .csv or .tsv
tables ... nope. Long gone.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-14 14:04 +0100 |
| Message-ID | <4vljulxf0c.ln2@Telcontar.valinor> |
| In reply to | #77508 |
Read with line wrap disabled. See below.
On 2025-11-14 03:33, c186282 wrote:
> On 11/13/25 19:54, Carlos E.R. wrote:
>> On 2025-11-13 05:07, c186282 wrote:
>>> Anyway, I'm looking for fairly straight-up solutions
>>> that don't require 10,000 lines of code.
>>>
>>> Govt-collected weather data - We The People have ALREADY
>>> paid for it. We should be able to GET it without issues.
>>>
>> curl v2.wttr.in
>>
>> gets you some weather info. I have in my machine "metar" from 2006,
>> but it no longer runs, it was compiled for 32 bits.
>>
>> Chatgpt suggested these:
>>
>>
>>
>> wego — nice TUI weather client written in Go
>>
>> ansiweather — weather in your terminal using ANSI colors
>>
>> weather-util — classic simple tool (weather command)
>>
>> curl v2.wttr.in — alternative minimal text version
>>
>> metar — shows aviation METAR weather reports
>
> Did a lot of searching today and DID find some
> alternative sites - GIF loops, PNGs updated every
> five minutes, data pages with minimal BS that are
> fairly easy to parse. But good old .csv or .tsv
> tables ... nope. Long gone.
Have a look at https://v2.wttr.in/, the page is simple.
https://github.com/chubin/wttr.in
«wttr.in — the right way to -check- curl the weather!
wttr.in is a console-oriented weather forecast service that supports various information representation methods like terminal-oriented ANSI-sequences for console HTTP clients (curl, httpie, or wget), HTML for web browsers, or PNG for graphical viewers.
Originally started as a small project, a wrapper for wego, intended to demonstrate the power of the console-oriented services, wttr.in became a popular weather reporting service, handling tens of millions¹ of queries daily.
You can see it running here: wttr.in.»
Query your city name:
curl wttr.in/Madrid
cer@Telcontar:~> curl wttr.in/Madrid
Weather report: Madrid
.-. Light drizzle
( ). +13(11) °C
(___(__) ↑ 28 km/h
‘ ‘ ‘ ‘ 10 km
‘ ‘ ‘ ‘ 0.4 mm
┌─────────────┐
┌──────────────────────────────┬───────────────────────┤ Fri 14 Nov ├───────────────────────┬──────────────────────────────┐
│ Morning │ Noon └──────┬──────┘ Evening │ Night │
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│ _`/"".-. Patchy rain ne…│ _`/"".-. Patchy rain ne…│ _`/"".-. Light rain sho…│ _`/"".-. Patchy rain ne…│
│ ,\_( ). +12(10) °C │ ,\_( ). +14(13) °C │ ,\_( ). +13(11) °C │ ,\_( ). +11(8) °C │
│ /(___(__) ↗ 17-23 km/h │ /(___(__) ↑ 23-27 km/h │ /(___(__) ↑ 26-36 km/h │ /(___(__) ↗ 35-50 km/h │
│ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │
│ ‘ ‘ ‘ ‘ 0.0 mm | 84% │ ‘ ‘ ‘ ‘ 0.0 mm | 63% │ ‘ ‘ ‘ ‘ 0.8 mm | 100% │ ‘ ‘ ‘ ‘ 0.1 mm | 100% │
└──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘
┌─────────────┐
┌──────────────────────────────┬───────────────────────┤ Sat 15 Nov ├───────────────────────┬──────────────────────────────┐
│ Morning │ Noon └──────┬──────┘ Evening │ Night │
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│ Overcast │ _`/"".-. Patchy rain ne…│ .-. Moderate rain │ \ / Clear │
│ .--. +11(9) °C │ ,\_( ). +13(11) °C │ ( ). +11(9) °C │ .-. +12(10) °C │
│ .-( ). ↑ 19-26 km/h │ /(___(__) ↑ 19-22 km/h │ (___(__) ← 16-22 km/h │ ― ( ) ― ↗ 19-27 km/h │
│ (___.__)__) 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‚‘‚‘‚‘‚‘ 7 km │ `-’ 10 km │
│ 0.0 mm | 0% │ ‘ ‘ ‘ ‘ 0.1 mm | 100% │ ‚’‚’‚’‚’ 2.5 mm | 100% │ / \ 0.0 mm | 0% │
└──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘
┌─────────────┐
┌──────────────────────────────┬───────────────────────┤ Sun 16 Nov ├───────────────────────┬──────────────────────────────┐
│ Morning │ Noon └──────┬──────┘ Evening │ Night │
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│ Cloudy │ _`/"".-. Patchy rain ne…│ _`/"".-. Patchy rain ne…│ _`/"".-. Patchy rain ne…│
│ .--. +10(8) °C │ ,\_( ). +12(11) °C │ ,\_( ). +11(10) °C │ ,\_( ). 10 °C │
│ .-( ). ↗ 12-16 km/h │ /(___(__) ↗ 13-15 km/h │ /(___(__) ↗ 12-17 km/h │ /(___(__) ↗ 4-7 km/h │
│ (___.__)__) 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │
│ 0.0 mm | 0% │ ‘ ‘ ‘ ‘ 0.0 mm | 74% │ ‘ ‘ ‘ ‘ 0.0 mm | 67% │ ‘ ‘ ‘ ‘ 0.0 mm | 86% │
└──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘
Location: Madrid, Área metropolitana de Madrid y Corredor del Henares, Comunidad de Madrid, España [40.4167047,-3.7035824]
Follow @igor_chubin for wttr.in updates
You can probably look at the source code and find out how they obtain the data.
Or:
«Supported output formats and views
wttr.in currently supports five output formats:
ANSI for the terminal;
Plain-text for the terminal and scripts;
HTML for the browser;
PNG for the graphical viewers;
JSON for scripts and APIs;
Prometheus metrics for scripts and APIs.»
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-14 16:27 -0500 |
| Message-ID | <O8SdndLJcaZZA4r0nZ2dnZfqn_GdnZ2d@giganews.com> |
| In reply to | #77522 |
On 11/14/25 08:04, Carlos E.R. wrote: > > Read with line wrap disabled. See below. > > On 2025-11-14 03:33, c186282 wrote: >> On 11/13/25 19:54, Carlos E.R. wrote: >>> On 2025-11-13 05:07, c186282 wrote: > > >>>> Anyway, I'm looking for fairly straight-up solutions >>>> that don't require 10,000 lines of code. >>>> >>>> Govt-collected weather data - We The People have ALREADY >>>> paid for it. We should be able to GET it without issues. >>>> >>> curl v2.wttr.in >>> >>> gets you some weather info. I have in my machine "metar" from 2006, >>> but it no longer runs, it was compiled for 32 bits. >>> >>> Chatgpt suggested these: >>> >>> >>> >>> wego — nice TUI weather client written in Go >>> >>> ansiweather — weather in your terminal using ANSI colors >>> >>> weather-util — classic simple tool (weather command) >>> >>> curl v2.wttr.in — alternative minimal text version >>> >>> metar — shows aviation METAR weather reports >> >> Did a lot of searching today and DID find some >> alternative sites - GIF loops, PNGs updated every >> five minutes, data pages with minimal BS that are >> fairly easy to parse. But good old .csv or .tsv >> tables ... nope. Long gone. > > Have a look at https://v2.wttr.in/, the page is simple. > > > https://github.com/chubin/wttr.in > > «wttr.in — the right way to -check- curl the weather! > > wttr.in is a console-oriented weather forecast service that supports > various information representation methods like terminal-oriented ANSI- > sequences for console HTTP clients (curl, httpie, or wget), HTML for web > browsers, or PNG for graphical viewers. They'd work fair, IF you can steer it to city near you. Still not .csv alas :-) > Originally started as a small project, a wrapper for wego, intended to > demonstrate the power of the console-oriented services, wttr.in became a > popular weather reporting service, handling tens of millions¹ of queries > daily. > > You can see it running here: wttr.in.» > > > > Query your city name: > > curl wttr.in/Madrid > > cer@Telcontar:~> curl wttr.in/Madrid > Weather report: Madrid > > .-. Light drizzle > ( ). +13(11) °C > (___(__) ↑ 28 km/h > ‘ ‘ ‘ ‘ 10 km > ‘ ‘ ‘ ‘ 0.4 mm > ┌─────────────┐ > ┌──────────────────────────────┬───────────────────────┤ Fri 14 Nov > ├───────────────────────┬──────────────────────────────┐ > │ Morning │ Noon > └──────┬──────┘ Evening │ Night │ > ├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤ > │ _`/"".-. Patchy rain ne…│ _`/"".-. Patchy rain ne…│ > _`/"".-. Light rain sho…│ _`/"".-. Patchy rain ne…│ > │ ,\_( ). +12(10) °C │ ,\_( ). +14(13) °C │ , > \_( ). +13(11) °C │ ,\_( ). +11(8) °C │ > │ /(___(__) ↗ 17-23 km/h │ /(___(__) ↑ 23-27 km/h │ / > (___(__) ↑ 26-36 km/h │ /(___(__) ↗ 35-50 km/h │ > │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ > ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ > │ ‘ ‘ ‘ ‘ 0.0 mm | 84% │ ‘ ‘ ‘ ‘ 0.0 mm | 63% │ ‘ ‘ > ‘ ‘ 0.8 mm | 100% │ ‘ ‘ ‘ ‘ 0.1 mm | 100% │ > └──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘ > ┌─────────────┐ > ┌──────────────────────────────┬───────────────────────┤ Sat 15 Nov > ├───────────────────────┬──────────────────────────────┐ > │ Morning │ Noon > └──────┬──────┘ Evening │ Night │ > ├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤ > │ Overcast │ _`/"".-. Patchy rain ne… > │ .-. Moderate rain │ \ / Clear │ > │ .--. +11(9) °C │ ,\_( ). +13(11) °C │ > ( ). +11(9) °C │ .-. +12(10) °C │ > │ .-( ). ↑ 19-26 km/h │ /(___(__) ↑ 19-22 km/h │ > (___(__) ← 16-22 km/h │ ― ( ) ― ↗ 19-27 km/h │ > │ (___.__)__) 10 km │ ‘ ‘ ‘ ‘ 10 km │ > ‚‘‚‘‚‘‚‘ 7 km │ `-’ 10 km │ > │ 0.0 mm | 0% │ ‘ ‘ ‘ ‘ 0.1 mm | 100% │ > ‚’‚’‚’‚’ 2.5 mm | 100% │ / \ 0.0 mm | 0% │ > └──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘ > ┌─────────────┐ > ┌──────────────────────────────┬───────────────────────┤ Sun 16 Nov > ├───────────────────────┬──────────────────────────────┐ > │ Morning │ Noon > └──────┬──────┘ Evening │ Night │ > ├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤ > │ Cloudy │ _`/"".-. Patchy rain ne…│ > _`/"".-. Patchy rain ne…│ _`/"".-. Patchy rain ne…│ > │ .--. +10(8) °C │ ,\_( ). +12(11) °C │ , > \_( ). +11(10) °C │ ,\_( ). 10 °C │ > │ .-( ). ↗ 12-16 km/h │ /(___(__) ↗ 13-15 km/h │ / > (___(__) ↗ 12-17 km/h │ /(___(__) ↗ 4-7 km/h │ > │ (___.__)__) 10 km │ ‘ ‘ ‘ ‘ 10 km │ ‘ ‘ > ‘ ‘ 10 km │ ‘ ‘ ‘ ‘ 10 km │ > │ 0.0 mm | 0% │ ‘ ‘ ‘ ‘ 0.0 mm | 74% │ ‘ ‘ > ‘ ‘ 0.0 mm | 67% │ ‘ ‘ ‘ ‘ 0.0 mm | 86% │ > └──────────────────────────────┴──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘ > Location: Madrid, Área metropolitana de Madrid y Corredor del Henares, > Comunidad de Madrid, España [40.4167047,-3.7035824] > > Follow @igor_chubin for wttr.in updates > > > You can probably look at the source code and find out how they obtain > the data. Kind of looks like the data comes from his Twitter acct ... there is an encoded link ref probably unique to each city. > Or: > > «Supported output formats and views > > wttr.in currently supports five output formats: > > ANSI for the terminal; > Plain-text for the terminal and scripts; > HTML for the browser; > PNG for the graphical viewers; > JSON for scripts and APIs; > Prometheus metrics for scripts and APIs.» > >
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-14 22:44 +0100 |
| Message-ID | <pfkkulxkn5.ln2@Telcontar.valinor> |
| In reply to | #77554 |
On 2025-11-14 22:27, c186282 wrote: > On 11/14/25 08:04, Carlos E.R. wrote: >> >> Read with line wrap disabled. See below. >> >> On 2025-11-14 03:33, c186282 wrote: >>> On 11/13/25 19:54, Carlos E.R. wrote: >>>> On 2025-11-13 05:07, c186282 wrote: >> >> >>>>> Anyway, I'm looking for fairly straight-up solutions >>>>> that don't require 10,000 lines of code. >>>>> >>>>> Govt-collected weather data - We The People have ALREADY >>>>> paid for it. We should be able to GET it without issues. >>>>> >>>> curl v2.wttr.in >>>> >>>> gets you some weather info. I have in my machine "metar" from 2006, >>>> but it no longer runs, it was compiled for 32 bits. >>>> >>>> Chatgpt suggested these: >>>> >>>> >>>> >>>> wego — nice TUI weather client written in Go >>>> >>>> ansiweather — weather in your terminal using ANSI colors >>>> >>>> weather-util — classic simple tool (weather command) >>>> >>>> curl v2.wttr.in — alternative minimal text version >>>> >>>> metar — shows aviation METAR weather reports >>> >>> Did a lot of searching today and DID find some >>> alternative sites - GIF loops, PNGs updated every >>> five minutes, data pages with minimal BS that are >>> fairly easy to parse. But good old .csv or .tsv >>> tables ... nope. Long gone. >> >> Have a look at https://v2.wttr.in/, the page is simple. >> >> >> https://github.com/chubin/wttr.in >> >> «wttr.in — the right way to -check- curl the weather! >> >> wttr.in is a console-oriented weather forecast service that supports >> various information representation methods like terminal-oriented >> ANSI- sequences for console HTTP clients (curl, httpie, or wget), HTML >> for web browsers, or PNG for graphical viewers. > > > They'd work fair, IF you can steer it to city near you. > Still not .csv alas :-) I can point it to the exact city. 2 Km away. The thing gives latitude and longitude of the site with 7 decimals. I have no idea why, if there is some kind of metering station at that spot. Not that I know. You can make it output in json > > >> Originally started as a small project, a wrapper for wego, intended to >> demonstrate the power of the console-oriented services, wttr.in became >> a popular weather reporting service, handling tens of millions¹ of >> queries daily. >> >> You can see it running here: wttr.in.» >> >> >> >> Query your city name: >> >> curl wttr.in/Madrid >> >> cer@Telcontar:~> curl wttr.in/Madrid >> Weather report: Madrid ...>> Location: Madrid, Área metropolitana de Madrid y Corredor del Henares, >> Comunidad de Madrid, España [40.4167047,-3.7035824] >> >> Follow @igor_chubin for wttr.in updates >> >> >> You can probably look at the source code and find out how they obtain >> the data. > > > Kind of looks like the data comes from his Twitter acct ... there > is an encoded link ref probably unique to each city. > > > >> Or: >> >> «Supported output formats and views >> >> wttr.in currently supports five output formats: >> >> ANSI for the terminal; >> Plain-text for the terminal and scripts; >> HTML for the browser; >> PNG for the graphical viewers; >> JSON for scripts and APIs; >> Prometheus metrics for scripts and APIs.» >> >> > -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-11-14 13:24 +0000 |
| Message-ID | <mnoot8F849tU1@mid.individual.net> |
| In reply to | #77504 |
"Carlos E.R." wrote: > curl v2.wttr.in > > gets you some weather info. Nice, but shame the cloud emoji aren't consistent width
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-14 17:03 -0500 |
| Message-ID | <CiGdnYqUD-7QOor0nZ2dnZfqn_udnZ2d@giganews.com> |
| In reply to | #77525 |
On 11/14/25 08:24, Andy Burns wrote: > "Carlos E.R." wrote: > >> curl v2.wttr.in >> >> gets you some weather info. > > Nice, but shame the cloud emoji aren't consistent width Depends on how you'd want to use it all. Me, I've got a Python app I wrote for use on PI screens (ok, one is a tiny TV set). As such you only want to see the current info - in LARGE type so you can read it across the room. This is why I wanted a .csv derivation, super easy to extract what you want and then add the text to the screen image in large (I like white on dark blue) text. Anyway, as I said somewhere, I did find a few data sites maybe 'better' than what I'm using (and having odd issues with) that are easier to parse out. For this kind of info, "government" sites are likely yer better bet because they don't mess with them much once set-up. The current boss said "We need a weather/radar site !" and so it was done ... just to be forgotten, running in the deep background for years and years. "Commercial" sites always try to look spiff, competition, so they change a lot. What you could parse out yesterday may not work in the least tomorrow. About a year ago the radar GIF I've used suddenly changed - just only to higher-resolution. This meant I had to re-do my resize/position figures but it wasn't TOO bad, just some experimentation. Radar GIFs and other formats, typically you get ten frames ... every 5 minutes. My current has 25 frames - two and a half hours. Use every other frame, makes motion more obvious on a small display. Too many sites now also want one (or ten) JavaScripts allowed in order to deliver anything. Hate 'em ! Nice clean wget !!! (maybe curl ...) Anyway, this evening, I'm gonna write drop-in alts for the radar and weather functions I have, ready Just In Case. Hmm, config-file options ?
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-12 20:10 +0000 |
| Message-ID | <mnk7t2Ff6c0U6@mid.individual.net> |
| In reply to | #77390 |
On Wed, 12 Nov 2025 02:26:11 -0500, c186282 wrote:
> On 11/12/25 02:21, vallor wrote:
>> At 11 Nov 2025 20:16:41 GMT, rbowman <bowman@montana.com> wrote:
>>
>>> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>>>
>>>> On 11/10/25 02:46, rbowman wrote:
>>>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>>>
>>>>>> On 11/9/25 14:28, rbowman wrote:
>>>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>>>
>>>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>>>> tomorrows forecast next week, or even next month.
>>>>>>>
>>>>>>> How about in a second or two? The starting point is
>>>>>>> url =
>>>>>>> f"https://api.weather.gov/points/{latitude},{longitude}"
>>>>>>
>>>>>> Keep getting "invalid point"
>>>>>
>>>>> Try
>>>>>
>>>>> https://api.weather.gov/points/42.934,-90.567
>>>>
>>>> That works ... but change the coords a bit and it won't. Seems it
>>>> only knows a handful of locations.
>>>
>>> I picked that at random.
>>>
>>> https://api.weather.gov/points/36.934,-72.567 Chincoteague, VA
>>>
>>> https://api.weather.gov/points/40.934,-94.567 Lenox, IA
>>>
>>> https://api.weather.gov/points/36.934,-84.567 Burnside KY
>>>
>>> https://api.weather.gov/points/58.114,-134.666 Juneau, AK
>>>
>>> https://api.weather.gov/points/38.114,-134.666 no data, but it's 886
>>> km off the coast of northern California.
>>>
>>> https://api.weather.gov/points/19.66,-156.012 Kailua, HI
>>>
>>> You do have to pick points in the US.
>>>
>>> https://api.weather.gov/points/51.130,-114.218 is Calgary AB and no
>>> data.
>>
>> This is pretty slick. I was able to grab the local weather forecast.
>> It even includes icons for the weather.
>>
>> Thank you for posting about it.
>
> All I get are pages of links to links to links ...
>
> And 'icons' are NOT what I'm looking for - I want comma/tab-delimited
> tables which automation can easily get/process.
It's JSON. If you can't process that you might want to join the 21st
century. That's what you're going to get out of most REST APIs.
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2025-11-11 21:07 +0000 |
| Message-ID | <xANQQ.2055096$ctz9.382312@fx16.iad> |
| In reply to | #77312 |
On 2025-11-11, c186282 <c186282@nnada.net> wrote: > In USA, the most useful sites seem to revolve > around 'aviation weather' and center on certain > airports, typically a 3-letter abbreviation. Four letters now that they've gone to ICAO codes, which in most - but not all - cases are just the IATA code with a K slapped on the front. (Ditto for Canadian location codes, except you prepend a C. The same caveat applies.) -- /~\ 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 | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-12 00:56 -0500 |
| Message-ID | <rdmcndisdIgCvIn0nZ2dnZfqnPYAAAAA@giganews.com> |
| In reply to | #77344 |
On 11/11/25 16:07, Charlie Gibbs wrote:
> On 2025-11-11, c186282 <c186282@nnada.net> wrote:
>
>> In USA, the most useful sites seem to revolve
>> around 'aviation weather' and center on certain
>> airports, typically a 3-letter abbreviation.
>
> Four letters now that they've gone to ICAO codes,
Yea, they've added a leading letter in most cases.
"K"s are typical. Guess there are too many airports
these days - "KATL" for Atlanta GA now.
"Metar" has a lot of desired info, but now it's
gone to the "verify you're human" bullshit so
that's out for automated uses.
US govt data goes deep and wide. SOMEWHERE there's
what you want in a fairly easy format - but FINDING
it is the huge challenge. May be with some totally
obscure little agency or something-district.
Accidentally found weekly tide data from a meter
under a bridge somewhere - VERY accidentally alas.
As said, give me a straight comma/tab delimited
table with the latest info on the top row - or
is that just TOO easy ? Can't have THAT !
> which in most - but not all - cases are just
> the IATA code with a K slapped on the front.
> (Ditto for Canadian location codes, except
> you prepend a C. The same caveat applies.)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-08 13:28 +0100 |
| Message-ID | <sjp3ulxbp7.ln2@Telcontar.valinor> |
| In reply to | #77092 |
On 2025-11-08 08:01, c186282 wrote: > > Note neither 'C' or FP have a straight-up > equiv for 'sleep()'. This is critical to > my app. Turbo had something like it ... but > it was like a legacy lib and not sure to > be as accurate or versatile as Python sleep(). What do you want to do with sleep? FreePascal has sleep() and fpSleep(). -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
Page 17 of 18 — ← Prev page 1 … 15 16 [17] 18 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web