Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #680832 > unrolled thread
| Started by | CrudeSausage <crude@sausa.ge> |
|---|---|
| First post | 2024-12-19 20:03 -0500 |
| Last post | 2024-12-25 16:19 -0500 |
| Articles | 20 on this page of 255 — 29 participants |
Back to article view | Back to comp.os.linux.advocacy
The problem with not owning the software CrudeSausage <crude@sausa.ge> - 2024-12-19 20:03 -0500
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-21 16:52 +0800
Re: The problem with not owning the software CrudeSausage <crude@sausa.ge> - 2024-12-21 07:26 -0500
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-23 23:15 +0800
Re: The problem with not owning the software ant@zimage.comANT (Ant) - 2024-12-23 23:24 +0000
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-25 11:48 +0800
Re: The problem with not owning the software ant@zimage.comANT (Ant) - 2024-12-25 06:54 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-25 20:39 +0000
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-27 22:23 +0800
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-28 07:04 +0000
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-28 16:53 +0800
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-28 19:34 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-28 15:07 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-28 15:12 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-28 17:11 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-28 17:17 -0500
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 13:16 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 14:24 -0500
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 15:39 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 16:06 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 17:10 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 17:39 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 18:58 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 19:10 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 19:21 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-29 22:55 +0000
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 18:02 -0500
Re: The problem with not owning the software sticks <wolverine01@charter.net> - 2024-12-29 18:35 -0600
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 19:51 -0500
Re: The problem with not owning the software sticks <wolverine01@charter.net> - 2024-12-29 20:00 -0600
Re: The problem with not owning the software knuttle <keith_nuttle@yahoo.com> - 2024-12-29 22:34 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-30 03:48 +0000
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 19:55 -0500
Re: The problem with not owning the software sticks <wolverine01@charter.net> - 2024-12-29 20:15 -0600
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-29 21:49 -0500
Re: The problem with not owning the software Jack Sovalot <hee-cawkforme@jack.sovalot> - 2024-12-30 04:06 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 08:31 -0500
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2024-12-30 19:12 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 00:53 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 21:06 -0500
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2024-12-31 11:01 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 19:00 +0000
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 19:52 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-01 01:46 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 20:52 -0500
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-01 17:02 -0500
Re: The problem with not owning the software sticks <wolverine01@charter.net> - 2025-01-18 11:54 -0600
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 18:46 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-30 04:51 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 09:34 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 00:53 +0000
Re: The problem with not owning the software Mark Lloyd <not.email@all.invalid> - 2024-12-29 19:42 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 21:09 +0000
Re: The problem with not owning the software Mark Lloyd <not.email@all.invalid> - 2024-12-29 19:44 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 21:05 +0000
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-29 23:14 +0100
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-30 03:57 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-30 08:25 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-30 08:24 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 10:09 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 00:32 +0000
Re: The problem with not owning the software ant@zimage.comANT (Ant) - 2024-12-29 01:43 +0000
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2024-12-28 20:52 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 07:05 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 06:58 +0000
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-29 21:17 +0100
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2024-12-29 20:41 +0000
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-29 23:31 +0100
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2024-12-30 10:56 +0000
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-31 03:24 +0100
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2024-12-31 13:50 +0000
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2024-12-31 13:18 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-31 19:14 +0000
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-01 07:44 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-02 00:22 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-02 12:09 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-02 19:36 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 02:09 +0000
Re: The problem with not owning the software Farley Flud <fflud@gnu.rocks> - 2024-12-31 19:25 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 11:46 -0500
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-31 20:27 +0100
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 21:16 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-29 22:57 +0000
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 18:50 -0500
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-30 02:30 +0100
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-30 04:55 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-30 07:05 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-30 08:24 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 01:00 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-31 16:15 +0000
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2024-12-29 16:39 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 21:00 +0000
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 19:08 -0500
Re: The problem with not owning the software Char Jackson <none@none.invalid> - 2024-12-29 22:30 -0600
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-30 07:00 +0000
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-30 12:53 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-30 04:52 +0000
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-30 13:01 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 00:56 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-30 08:25 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 00:57 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-01 16:45 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-01 19:31 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-01 14:50 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-01 22:03 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-02 00:41 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-02 00:33 +0000
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-02 00:15 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-02 05:33 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-02 12:09 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-02 22:03 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 02:32 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-04 04:50 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 08:52 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 00:42 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 01:05 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:59 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-04 10:01 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 10:29 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-04 10:38 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 11:45 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-04 12:00 -0500
Re: The problem with not owning the software Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-04 18:01 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 13:59 -0500
Re: The problem with not owning the software Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-04 20:45 +0000
The Desktop Environment (was: Re: The problem with not owning the software) vallor <vallor@cultnix.org> - 2025-01-05 03:05 +0000
Re: The Desktop Environment (was: Re: The problem with not owning the software) pothead <pothead@snakebite.com> - 2025-01-05 17:28 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-04 20:25 +0000
Re: The problem with not owning the software vallor <vallor@cultnix.org> - 2025-01-04 15:58 +0000
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-04 11:23 -0500
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2025-01-04 21:13 +0000
Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-04 21:50 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 00:39 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 00:59 +0000
Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-05 01:52 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 03:04 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 16:07 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-06 00:22 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-06 08:23 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-06 22:47 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-07 00:12 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-07 02:10 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-07 02:31 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-07 14:12 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-08 02:26 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-08 13:28 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-08 21:28 +0000
[OT] Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-05 01:50 +0000
Re: [OT] Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 03:01 +0000
Re: [OT] Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-05 03:25 +0000
Re: [OT] Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 06:47 +0000
Re: [OT] Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-05 08:20 -0500
Re: [OT] Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-08 12:21 -0500
Re: [OT] Re: The problem with not owning the software CrudeSausage <crude@sausa.ge> - 2025-01-08 14:10 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-04 21:18 -0500
[OT] Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-05 02:34 +0000
Re: [OT] Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-04 22:08 -0500
Re: [OT] Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2025-01-04 22:34 -0500
Re: [OT] Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-05 07:19 -0500
Re: [OT] Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2025-01-05 10:39 -0500
Re: [OT] Re: The problem with not owning the software snipeco.2@gmail.com (Sn!pe) - 2025-01-05 03:39 +0000
Re: [OT] Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-05 08:13 -0500
Re: [OT] Re: The problem with not owning the software chrisv <chrisv@nospam.invalid> - 2025-01-05 08:52 -0600
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 16:32 +0000
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-04 20:53 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-28 21:26 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 06:38 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 07:17 -0500
Re: The problem with not owning the software Graham J <nobody@nowhere.co.uk> - 2024-12-29 13:19 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 08:48 -0500
Re: The problem with not owning the software chrisv <chrisv@nospam.invalid> - 2024-12-29 08:02 -0600
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 09:08 -0500
Re: The problem with not owning the software Mark Lloyd <not.email@all.invalid> - 2024-12-29 19:32 +0000
Re: The problem with not owning the software Mark Lloyd <not.email@all.invalid> - 2024-12-29 19:46 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-29 20:56 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-29 17:03 -0500
Re: The problem with not owning the software Physfitfreak <physfitfreak@gmail.com> - 2024-12-31 23:32 -0600
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-05 11:05 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-05 13:29 -0500
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2025-01-05 13:53 -0500
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-05 15:08 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-06 10:17 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2025-01-06 10:28 -0500
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-06 11:26 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-06 12:34 -0500
Re: The problem with not owning the software Joel <joelcrump@gmail.com> - 2025-01-06 12:40 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-06 14:23 -0500
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-06 16:27 -0500
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2024-12-29 13:21 -0500
Re: The problem with not owning the software Ken Blake <Ken@invalid.news.com> - 2024-12-29 07:41 -0700
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-30 19:05 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 20:50 -0500
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-02 12:09 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-02 22:05 +0000
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-03 09:09 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-03 20:33 +0000
Re: The problem with not owning the software pothead <pothead@snakebite.com> - 2025-01-03 21:00 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-03 23:28 +0000
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-04 21:17 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:57 +0000
Re: The problem with not owning the software -hh <recscuba_google@huntzinger.com> - 2025-01-04 22:25 -0500
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 02:19 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-04 04:49 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 01:10 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:52 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-05 15:55 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-06 00:20 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-06 08:11 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-06 16:16 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-06 22:46 +0000
Re: The problem with not owning the software Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-11 11:36 +0000
Re: The problem with not owning the software Physfitfreak <physfitfreak@gmail.com> - 2024-12-31 23:20 -0600
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-30 18:58 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 00:59 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-31 02:18 -0500
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-31 08:41 -0500
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2024-12-31 13:08 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-31 13:54 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-31 19:26 +0000
Re: The problem with not owning the software Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-01 07:43 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 10:32 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 00:37 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2025-01-04 19:43 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:47 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-12-31 18:58 +0000
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2024-12-31 19:25 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-31 19:32 -0500
Re: The problem with not owning the software rbowman <bowman@montana.com> - 2025-01-01 01:43 +0000
Re: The problem with not owning the software "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2024-12-25 11:53 +0800
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2024-12-30 08:24 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-30 10:08 -0500
Re: The problem with not owning the software "Carlos E.R." <robin_listas@es.invalid> - 2024-12-31 20:32 +0100
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-31 21:34 -0500
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-01 16:47 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-01 19:29 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-02 12:09 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-02 21:59 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-02 18:01 -0500
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2025-01-03 11:26 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2025-01-03 08:55 -0500
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2025-01-03 14:33 +0000
Re: The problem with not owning the software Paul <nospam@needed.invalid> - 2025-01-04 19:32 -0500
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:46 +0000
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2025-01-05 15:46 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-06 00:17 +0000
Re: The problem with not owning the software Frank Slootweg <this@ddress.is.invalid> - 2025-01-06 14:57 +0000
Re: The problem with not owning the software Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-05 02:47 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 02:14 +0000
Re: The problem with not owning the software Chris <ithinkiam@gmail.com> - 2025-01-04 02:09 +0000
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-30 19:02 -0500
Re: The problem with not owning the software Stéphane CARPENTIER <sc@fiat-linux.fr> - 2024-12-31 10:10 +0000
Re: The problem with not owning the software Andrzej Matuch <andrzej@matu.ch> - 2024-12-31 08:50 -0500
Re: The problem with not owning the software DFS <guhnoo-basher@linux.advocaca> - 2024-12-31 12:09 -0500
Re: The problem with not owning the software Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-04 10:31 +0000
Re: The problem with not owning the software bad sector <forgetski@_INVALID.net> - 2024-12-25 16:19 -0500
Page 5 of 13 — ← Prev page 1 … 3 4 [5] 6 7 … 13 Next page →
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-12-31 20:27 +0100 |
| Message-ID | <o5td4lx9h4.ln2@Telcontar.valinor> |
| In reply to | #681875 |
On 2024-12-31 14:50, Frank Slootweg wrote: > Carlos E.R. <robin_listas@es.invalid> wrote: >> On 2024-12-30 11:56, Frank Slootweg wrote: >>> Carlos E.R. <robin_listas@es.invalid> wrote: >>>> On 2024-12-29 21:41, Frank Slootweg wrote: >>>>> Carlos E.R. <robin_listas@es.invalid> wrote: >>>>> [...] >>>>> >>>>>> Amazing that none of you has mentioned latex. >>>>> >>>>> This isn't that kind of group! >>>> >>>> Latex is software :-P >>> >>> Obviously, but as you used all lowercase, it screamed for a pun. And >>> of course, it's 'LaTeX'. >>> >>> <https://en.wikipedia.org/wiki/LaTeX> >> >> Well, I do not talk LaTeX, so I do not know. >> >> I do know, though, that I do have a command named "latex" in my computer. >> >> cer@Telcontar:~> latex --version >> pdfTeX 3.141592653-2.6-1.40.22 (TeX Live 2021/TeX Live for SUSE Linux) >> kpathsea version 6.3.3 >> Copyright 2021 Han The Thanh (pdfTeX) et al. >> There is NO warranty. Redistribution of this software is >> covered by the terms of both the pdfTeX copyright and >> the Lesser GNU General Public License. >> For more information about these matters, see the file >> named COPYING and the pdfTeX source. >> Primary author of pdfTeX: Han The Thanh (pdfTeX) et al. >> Compiled with libpng 1.6.34; using libpng 1.6.34 >> Compiled with zlib 1.2.11; using zlib 1.2.13 >> Compiled with xpdf version 4.03 >> cer@Telcontar:~> > > Yes, I know you use Linux, so I indeed assumed that lowercase 'latex' > is a command on Linux. > > I've never used LaTeX either, but from the Wikipedia ppage, I > understand that LaTeX is the markup/formatting language and that > <something>TeX<something> is the software/program which processes that > language. That understanding id confirmed by the fact that your > 'latex --version' output mentions '<something>TeX<something>', but not > 'LaTeX'. > > Bottom line: Two guys talking about something they don't know anything > about! :-) :-D I think I have generated output from Latex documents, but just following a recipe. And I like LyX. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2024-12-29 21:16 +0000 |
| Message-ID | <ltdsi3F7nkqU9@mid.individual.net> |
| In reply to | #681623 |
On Sun, 29 Dec 2024 21:17:16 +0100, Carlos E.R. wrote: > On 2024-12-29 07:58, rbowman wrote: >> On Sun, 29 Dec 2024 01:43:11 +0000, Ant wrote: >> >>> What do you use to edit/create documents and spreadsheets with others? >> >> I don't. Anything I create is done with Vim. For external use we have >> tech writers that make it pretty. My attempts to edit RFPs with >> LibreOffice don't work well, so I either use Vim and reference the >> sections or print relevant pages and use a pen. > > Amazing that none of you has mentioned latex. You can edit documents > with vi. The only things I know about latex are gloves and paint. It goes back to never needing to make documents look pretty. I do know a little about nenscript from a programming aspect. We used a modified version to allow for headers, footers, and font selection for printed reports and I had to tweak the code.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-12-29 22:57 +0000 |
| Message-ID | <vksk47$17k9s$2@dont-email.me> |
| In reply to | #681623 |
On Sun, 29 Dec 2024 21:17:16 +0100, Carlos E.R. wrote: > Amazing that none of you has mentioned latex. The few times I tried to get started with TEX or LATEX, I kept getting baffled by screeds of mysterious error/warning messages. Then I tried writing man pages with groff and some standard macros. Now I can get nice typeset-quality PDF output from the same source, and I can actually understand what I’m doing.
[toc] | [prev] | [next] | [standalone]
| From | -hh <recscuba_google@huntzinger.com> |
|---|---|
| Date | 2024-12-29 18:50 -0500 |
| Message-ID | <vksn8i$12a03$9@dont-email.me> |
| In reply to | #681623 |
On 12/29/24 3:17 PM, Carlos E.R. wrote: > On 2024-12-29 07:58, rbowman wrote: >> On Sun, 29 Dec 2024 01:43:11 +0000, Ant wrote: >> >>> What do you use to edit/create documents and spreadsheets with others? >> >> I don't. Anything I create is done with Vim. For external use we have >> tech >> writers that make it pretty. My attempts to edit RFPs with LibreOffice >> don't work well, so I either use Vim and reference the sections or print >> relevant pages and use a pen. > > Amazing that none of you has mentioned latex. You can edit documents > with vi. Good point. I have friends who used to use latex quite a bit for large documents with interesting formatting needs. There also was Encapsulated Postscript (EPS) too...I don't know much more about it, other than MS dropped support of it after Word 5. -hh
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-12-30 02:30 +0100 |
| Message-ID | <6m994lxoms.ln2@Telcontar.valinor> |
| In reply to | #681656 |
On 2024-12-30 00:50, -hh wrote: > On 12/29/24 3:17 PM, Carlos E.R. wrote: >> On 2024-12-29 07:58, rbowman wrote: >>> On Sun, 29 Dec 2024 01:43:11 +0000, Ant wrote: >>> >>>> What do you use to edit/create documents and spreadsheets with others? >>> >>> I don't. Anything I create is done with Vim. For external use we have >>> tech >>> writers that make it pretty. My attempts to edit RFPs with LibreOffice >>> don't work well, so I either use Vim and reference the sections or print >>> relevant pages and use a pen. >> >> Amazing that none of you has mentioned latex. You can edit documents >> with vi. > > Good point. I have friends who used to use latex quite a bit for large > documents with interesting formatting needs. > > There also was Encapsulated Postscript (EPS) too...I don't know much > more about it, other than MS dropped support of it after Word 5. Me, I am aware of Latex, but I prefer LyX myself. I have seen an engineer produce production ready math papers and complex formulas using Latex in Windows. Some process going from the Latex file to the PDF output, marking the same word on both sides. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-12-30 04:55 +0000 |
| Message-ID | <vkt93o$1fes1$4@dont-email.me> |
| In reply to | #681656 |
On Sun, 29 Dec 2024 18:50:42 -0500, -hh wrote: > There also was Encapsulated Postscript (EPS) too... PostScript was a big deal, back in the day when desktop/workstation machines had more primitive graphics stacks. EPS was a way of embedding such graphics in a form that they could be sent to a printer that understood PostScript, from a machine which did not. Think of PDF as being the PostScript graphics model without the actual PostScript programming language.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2024-12-30 07:05 +0000 |
| Message-ID | <ltev1nFdi94U2@mid.individual.net> |
| In reply to | #681697 |
On Mon, 30 Dec 2024 04:55:20 -0000 (UTC), Lawrence D'Oliveiro wrote: > PostScript was a big deal, back in the day when desktop/workstation > machines had more primitive graphics stacks. EPS was a way of embedding > such graphics in a form that they could be sent to a printer that > understood PostScript, from a machine which did not. And then there is Ghostscript... One of our applications that prints reports sniffs at the document to determine if it's PS, then checks the configuration of the printer to see if it can handle PS. If not, it spawns Ghostscript to massage it into something the printer can handle. Great fun.
[toc] | [prev] | [next] | [standalone]
| From | Chris <ithinkiam@gmail.com> |
|---|---|
| Date | 2024-12-30 08:24 +0000 |
| Message-ID | <vktlcq$1i26p$5@dont-email.me> |
| In reply to | #681623 |
Carlos E.R. <robin_listas@es.invalid> wrote: > On 2024-12-29 07:58, rbowman wrote: >> On Sun, 29 Dec 2024 01:43:11 +0000, Ant wrote: >> >>> What do you use to edit/create documents and spreadsheets with others? >> >> I don't. Anything I create is done with Vim. For external use we have tech >> writers that make it pretty. My attempts to edit RFPs with LibreOffice >> don't work well, so I either use Vim and reference the sections or print >> relevant pages and use a pen. > > Amazing that none of you has mentioned latex. You can edit documents > with vi. Writing direct latex is quite a learning curve. I prefer markdown for simple documents which can be converted to pdf or docx as needed with pandoc. Markdown is also great for embedding interpretable code which can be evaluated when knitted or compiled. Perfect for writing data reports as part of a workflow.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-12-31 01:00 +0000 |
| Message-ID | <vkvfnp$1sirn$6@dont-email.me> |
| In reply to | #681703 |
On Mon, 30 Dec 2024 08:24:58 -0000 (UTC), Chris wrote: > Markdown is also great for embedding interpretable code which can be > evaluated when knitted or compiled. Perfect for writing data reports as > part of a workflow. Do you use Jupyter notebooks as a delivery medium? Think of it as an interactive report, including both live code and narrative description. And the code can produce rich output directly into the notebook, too.
[toc] | [prev] | [next] | [standalone]
| From | Chris <ithinkiam@gmail.com> |
|---|---|
| Date | 2024-12-31 16:15 +0000 |
| Message-ID | <vl15bc$2acb7$1@dont-email.me> |
| In reply to | #681813 |
Lawrence D'Oliveiro <ldo@nz.invalid> wrote: > On Mon, 30 Dec 2024 08:24:58 -0000 (UTC), Chris wrote: > >> Markdown is also great for embedding interpretable code which can be >> evaluated when knitted or compiled. Perfect for writing data reports as >> part of a workflow. > > Do you use Jupyter notebooks as a delivery medium? Think of it as an > interactive report, including both live code and narrative description. > And the code can produce rich output directly into the notebook, too. Typically, I use Rstudio.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2024-12-29 16:39 +0000 |
| Message-ID | <vks1gq.ufk.1@ID-201911.user.individual.net> |
| In reply to | #681544 |
Ant <ant@zimage.comant> wrote: [...] > In alt.comp.os.windows-11 rbowman <bowman@montana.com> wrote: > > On Sat, 28 Dec 2024 15:07:39 -0500, Andrzej Matuch wrote: > > > > Yeah, it sometimes pains me that it is brought up as often as it is as > > > some sort of must-have piece of software. It suggests that people don't > > > do much other than open up Word and Excel. > > > I'm the minority report. I have never used Office. I have no need for it > > in my personal life and the company never installed it on the programming > > machines. If we get RFPs or other documents in docx or xlsx we use > > LibreOffice. For me, that's a read-only thing since my attempts to edit > > anything were disasters. > > What do you use to edit/create documents and spreadsheets with others? [...] > I'm surprised you don't do any documents. I have been using word > processors since I was in elementary with Apple 2's AppleWorks. Like rbowman, I used/used vi/vim for my documents. Have been using it, ever since it became available (to me). First on Unix/UNIX and later - mainly privately - also on DOS and Windows. I currently have some 3500 of such documents. And FTR, I'm using vim to compose this very article! :-) In a past working life, I shortly used nroff when vi couldn't yet format/reformat text (or I didn't know about it or didn't know how to do it). On a temporary assignment, I had to use WordPerfect, because the organization which hired me was more (only?) interested in how research/ investigation/etc. reports looked, than in their content/substance. Luckily after a few months, I managed to escape. And of course I still get the occasional .doc[x] attachment from someone who only *needs* a note-taking program, but only *has* (or knows how to use) Word. Luckily my current Windows 11 seems to grok such files, at least I didn't have to install LibreOffice since I got it, over two years ago. Knock on wood. [...]
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2024-12-29 21:00 +0000 |
| Message-ID | <ltdrjlF7nkqU6@mid.individual.net> |
| In reply to | #681600 |
On 29 Dec 2024 16:39:41 GMT, Frank Slootweg wrote: > And of course I still get the occasional .doc[x] attachment from > someone who only *needs* a note-taking program, but only *has* (or knows > how to use) Word. Luckily my current Windows 11 seems to grok such > files, at least I didn't have to install LibreOffice since I got it, > over two years ago. Knock on wood. That's my annoyance with Excel. Any xls document I've ever gotten was a freeform notepad with handy rows. I can't recall ever getting a xls where there were any manipulations on the cells. When all you know how to use is a hammer...
[toc] | [prev] | [next] | [standalone]
| From | -hh <recscuba_google@huntzinger.com> |
|---|---|
| Date | 2024-12-29 19:08 -0500 |
| Message-ID | <vkso91$12a03$10@dont-email.me> |
| In reply to | #681630 |
On 12/29/24 4:00 PM, rbowman wrote: > On 29 Dec 2024 16:39:41 GMT, Frank Slootweg wrote: > >> And of course I still get the occasional .doc[x] attachment from >> someone who only *needs* a note-taking program, but only *has* (or knows >> how to use) Word. Luckily my current Windows 11 seems to grok such >> files, at least I didn't have to install LibreOffice since I got it, >> over two years ago. Knock on wood. > > That's my annoyance with Excel. Any xls document I've ever gotten was a > freeform notepad with handy rows. I can't recall ever getting a xls where > there were any manipulations on the cells. When all you know how to use is > a hammer... That's a very common 'organizer' use case. I have some analytically based Excel stuff; it can get involved to build in certain types of logic (like "last entry" instead of "MAX"). Ditto for cell formatting which doesn't break from "divide by [no data]". I don't know how many cells it is, but a couple are over 1MB in size, including one with 21 tabs plus links to pull in data from other spreadsheets. I have a colleague who's done some amazing stuff in Excel using Visual Basic Script (VBS); the PC I had at the time would fail just trying to load the files; his beefy machine he had would take literally hours to crunch through a set. A quick search shows that I still have an older copy: it takes up 14.34GB on disk. Youch. -hh
[toc] | [prev] | [next] | [standalone]
| From | Char Jackson <none@none.invalid> |
|---|---|
| Date | 2024-12-29 22:30 -0600 |
| Message-ID | <2d84nj977vqsg5ar71obv8m0tfhj1cejse@4ax.com> |
| In reply to | #681660 |
On Sun, 29 Dec 2024 19:08:00 -0500, -hh <recscuba_google@huntzinger.com> wrote: >I have a colleague who's done some amazing stuff in Excel using Visual >Basic Script (VBS); the PC I had at the time would fail just trying to >load the files; his beefy machine he had would take literally hours to >crunch through a set. A quick search shows that I still have an older >copy: it takes up 14.34GB on disk. Youch. I assume you meant to say VBA, Visual Basic for Applications, which is built into each of the major MS Office applications?
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2024-12-30 07:00 +0000 |
| Message-ID | <lteuokFdi94U1@mid.individual.net> |
| In reply to | #681694 |
On Sun, 29 Dec 2024 22:30:53 -0600, Char Jackson wrote: > On Sun, 29 Dec 2024 19:08:00 -0500, -hh <recscuba_google@huntzinger.com> > wrote: > >>I have a colleague who's done some amazing stuff in Excel using Visual >>Basic Script (VBS); the PC I had at the time would fail just trying to >>load the files; his beefy machine he had would take literally hours to >>crunch through a set. A quick search shows that I still have an older >>copy: it takes up 14.34GB on disk. Youch. > > I assume you meant to say VBA, Visual Basic for Applications, which is > built into each of the major MS Office applications? Possibly, but there was a VBScript. https://en.wikipedia.org/wiki/VBScript I used JScript which was similar to JavaScript but Microsoft didn't want to butt heads with Sun. They had been down that road with Visual J++. You could use either with Windows Script Host. https://en.wikipedia.org/wiki/Windows_Script_Host and make COM calls against the applications that supported it. For example I used it in conjunction with EagleView (now Pictometry). Given the latitude and longitude of an incident I could create a URL referencing the EagleView server, instantiate a connection to IE, and call the NavigateTo() function with the URL. The relevant page would come up in IE. It was a long way around the barn but it was easier than trying to incorporate COM into an existing application. That was a very simple use but you could make calls to any functionality exposed as COM. That whole technology goes back to OLE and DDE. https://en.wikipedia.org/wiki/Object_Linking_and_Embedding Very powerful but as it was designed to work with VisualBasic the data structures were the wierd Basic things like BSTRs.
[toc] | [prev] | [next] | [standalone]
| From | -hh <recscuba_google@huntzinger.com> |
|---|---|
| Date | 2024-12-30 12:53 -0500 |
| Message-ID | <vkumlu$1mknq$1@dont-email.me> |
| In reply to | #681698 |
On 12/30/24 2:00 AM, rbowman wrote: > On Sun, 29 Dec 2024 22:30:53 -0600, Char Jackson wrote: > >> On Sun, 29 Dec 2024 19:08:00 -0500, -hh <recscuba_google@huntzinger.com> >> wrote: >> >>> I have a colleague who's done some amazing stuff in Excel using Visual >>> Basic Script (VBS); the PC I had at the time would fail just trying to >>> load the files; his beefy machine he had would take literally hours to >>> crunch through a set. A quick search shows that I still have an older >>> copy: it takes up 14.34GB on disk. Youch. >> >> I assume you meant to say VBA, Visual Basic for Applications, which is >> built into each of the major MS Office applications? > > Possibly, but there was a VBScript. > > https://en.wikipedia.org/wiki/VBScript To be honest, I don't know ... I'd have to go ask which one ... although knowing this person, I'd not be surprised if they used both. At the time, this spreadsheet model was a "sanity" distraction while worrying through his son's cancer treatments; in one summer he used it to make $80K by day-trades on the Stock Market .. it helped to pay down the medical bills. I laughed when he commiserated that the biggest shortcoming the model had was that it was predicting up to two (2) days in advance, which made it tricky to use. -hh
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-12-30 04:52 +0000 |
| Message-ID | <vkt8va$1fes1$3@dont-email.me> |
| In reply to | #681660 |
On Sun, 29 Dec 2024 19:08:00 -0500, -hh wrote: > I have a colleague who's done some amazing stuff in Excel using Visual > Basic Script (VBS); the PC I had at the time would fail just trying to > load the files; his beefy machine he had would take literally hours to > crunch through a set. A quick search shows that I still have an older > copy: it takes up 14.34GB on disk. Youch. How much data was involved, really? I suspect a more sensible app would deal with the same data much more efficiently and easily.
[toc] | [prev] | [next] | [standalone]
| From | -hh <recscuba_google@huntzinger.com> |
|---|---|
| Date | 2024-12-30 13:01 -0500 |
| Message-ID | <vkun59$1mknq$3@dont-email.me> |
| In reply to | #681696 |
On 12/29/24 11:52 PM, Lawrence D'Oliveiro wrote:
> On Sun, 29 Dec 2024 19:08:00 -0500, -hh wrote:
>
>> I have a colleague who's done some amazing stuff in Excel using Visual
>> Basic Script (VBS); the PC I had at the time would fail just trying to
>> load the files; his beefy machine he had would take literally hours to
>> crunch through a set. A quick search shows that I still have an older
>> copy: it takes up 14.34GB on disk. Youch.
>
> How much data was involved, really? I suspect a more sensible app would
> deal with the same data much more efficiently and easily.
There was a pretty modest chunk of data ... maybe just 1000 unique data
points?
What made it large & computationally intensive was that the dataset was
routed iteratively through a ~dozen different "Monte Carlo" statistical
exercises and filters to identify & glean signal from noise.
He has expressed that he should rewrite it in {some flavor of C}, but
there were reasons why it originated in Excel: it was a personal
spin-off from the original application which was a work project, and
that (smaller) model ended up going through a M&S for ~10 million design
permutations.
-hh
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-12-31 00:56 +0000 |
| Message-ID | <vkvffu$1sirn$3@dont-email.me> |
| In reply to | #681754 |
On Mon, 30 Dec 2024 13:01:13 -0500, -hh wrote: > On 12/29/24 11:52 PM, Lawrence D'Oliveiro wrote: > >> How much data was involved, really? I suspect a more sensible app would >> deal with the same data much more efficiently and easily. > > There was a pretty modest chunk of data ... maybe just 1000 unique data > points? > > What made it large & computationally intensive was that the dataset was > routed iteratively through a ~dozen different "Monte Carlo" statistical > exercises and filters to identify & glean signal from noise. I’m sure something could be whipped up in Python with NumPy/Pandas/ Matplotlib etc that would go through the same operations much more quickly and efficiently. Microsoft is even offering access to these Python toolkits to Excel users now -- at a cost. You know -- charging for something that the users could bypass Microsoft and access for free, only they’re too dumb to realize it.
[toc] | [prev] | [next] | [standalone]
| From | Chris <ithinkiam@gmail.com> |
|---|---|
| Date | 2024-12-30 08:25 +0000 |
| Message-ID | <vktlct$1i26p$9@dont-email.me> |
| In reply to | #681660 |
-hh <recscuba_google@huntzinger.com> wrote: > On 12/29/24 4:00 PM, rbowman wrote: >> On 29 Dec 2024 16:39:41 GMT, Frank Slootweg wrote: >> >>> And of course I still get the occasional .doc[x] attachment from >>> someone who only *needs* a note-taking program, but only *has* (or knows >>> how to use) Word. Luckily my current Windows 11 seems to grok such >>> files, at least I didn't have to install LibreOffice since I got it, >>> over two years ago. Knock on wood. >> >> That's my annoyance with Excel. Any xls document I've ever gotten was a >> freeform notepad with handy rows. I can't recall ever getting a xls where >> there were any manipulations on the cells. When all you know how to use is >> a hammer... > > That's a very common 'organizer' use case. > > I have some analytically based Excel stuff; it can get involved to build > in certain types of logic (like "last entry" instead of "MAX"). Ditto > for cell formatting which doesn't break from "divide by [no data]". I > don't know how many cells it is, but a couple are over 1MB in size, > including one with 21 tabs plus links to pull in data from other > spreadsheets. > > I have a colleague who's done some amazing stuff in Excel using Visual > Basic Script (VBS); the PC I had at the time would fail just trying to > load the files; his beefy machine he had would take literally hours to > crunch through a set. A quick search shows that I still have an older > copy: it takes up 14.34GB on disk. Youch. Sounds horribly inefficient and virtually impossible to debug. I'd bet a decent python script would do it in minutes, with a tiny footprint and be reliable.
[toc] | [prev] | [next] | [standalone]
Page 5 of 13 — ← Prev page 1 … 3 4 [5] 6 7 … 13 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web