Andrzej Matuch wrote this copyrighted missive and expects royalties:
On Thu, 09 May 2024 04:34:14 +0000, rbowman wrote:
On Wed, 8 May 2024 19:39:09 -0400, DFS wrote:
Here's what I posted to cola Apr 2019, when running Solus Linux with
the Budgie desktop.
https://en.wikipedia.org/wiki/Budgie_(desktop_environment)
Could you possibly find a more obscure/fucked up distro?
For what it's worth, I appreciate that DFS is looking for minuscule
problems in Linux and pointing them out. You can't make anything better if >> you're not going to be honest about its flaws. Unfortunately, even after
he points out the flaws and submits bug reports, the developers don't seem >> to do anything to fix it.
That's a project problem, not a platform problem.
Microsoft itself seems to treat issue reports in a similar manner to bad projects. So often in a Microsoft help forum, you'll get non-answers or no answers, with user's getting plaintive about the lack of help.
Other companies act the same, all too often.
I wouldn't ding small open-source team for being slow in responding to bugs, as
they may have other more important things on their plate.
I will note one responsive project: Meson, on GitHub. Meson was using a file called "meson_options.txt" to hold default values for project options. I wrote
up an issue about it (as had others earlier, apparently), and I noted that the "txt" extension is too generic, and that I edited my /etc/DIR_COLORS file so that I could grok a directory listing faster. And in version 1.1 IIRC, voila, there was meson.options to supplement meson.build.
On Thu, 9 May 2024 11:47:23 -0400, Chris Ahlstrom <OFeem1987@teleworm.us> wrote in <v1ir6d$o14n$1@dont-email.me>:[snip]
I wouldn't ding small open-source team for being slow in responding to bugs, as
they may have other more important things on their plate.
I will note one responsive project: Meson, on GitHub. Meson was using a file >> called "meson_options.txt" to hold default values for project options. I wrote
up an issue about it (as had others earlier, apparently), and I noted that >> the "txt" extension is too generic, and that I edited my /etc/DIR_COLORS file
so that I could grok a directory listing faster. And in version 1.1 IIRC,
voila, there was meson.options to supplement meson.build.
I posted an issue for gmime yesterday, and ended up in a dialogue
with the lead developer.
Pan users will note that I was bird-dogging a problem that has plagued
pan since they moved to gmime for handling headers -- currently,
Newsgroups: lines don't wrap properly, and get MIME-encoded
if they are too long. News servers choke on that. (My C is too rusty
to fix it easily, but I can see where the fix should go.)
vallor <vallor@cultnix.org> wrote at 23:42 this Thursday (GMT):
On Thu, 9 May 2024 11:47:23 -0400, Chris Ahlstrom[snip]
<OFeem1987@teleworm.us>
wrote in <v1ir6d$o14n$1@dont-email.me>:
I wouldn't ding small open-source team for being slow in responding to
bugs, as they may have other more important things on their plate.
I will note one responsive project: Meson, on GitHub. Meson was using
a file called "meson_options.txt" to hold default values for project
options. I wrote up an issue about it (as had others earlier,
apparently), and I noted that the "txt" extension is too generic, and
that I edited my /etc/DIR_COLORS file so that I could grok a directory
listing faster. And in version 1.1 IIRC, voila, there was
meson.options to supplement meson.build.
I posted an issue for gmime yesterday, and ended up in a dialogue with
the lead developer.
Pan users will note that I was bird-dogging a problem that has plagued
pan since they moved to gmime for handling headers -- currently,
Newsgroups: lines don't wrap properly, and get MIME-encoded if they are
too long. News servers choke on that. (My C is too rusty to fix it
easily, but I can see where the fix should go.)
That explains why I see random MIME messages..
On Thu, 9 May 2024 11:47:23 -0400, Chris Ahlstrom
<OFeem1987@teleworm.us>
wrote in <v1ir6d$o14n$1@dont-email.me>:
Andrzej Matuch wrote this copyrighted missive and expects royalties:
On Thu, 09 May 2024 04:34:14 +0000, rbowman wrote:
On Wed, 8 May 2024 19:39:09 -0400, DFS wrote:
Here's what I posted to cola Apr 2019, when running Solus Linux with >>>>> the Budgie desktop.
https://en.wikipedia.org/wiki/Budgie_(desktop_environment)
Could you possibly find a more obscure/fucked up distro?
For what it's worth, I appreciate that DFS is looking for minuscule
problems in Linux and pointing them out. You can't make anything
better if you're not going to be honest about its flaws.
Unfortunately, even after he points out the flaws and submits bug
reports, the developers don't seem to do anything to fix it.
That's a project problem, not a platform problem.
Microsoft itself seems to treat issue reports in a similar manner to
bad projects. So often in a Microsoft help forum, you'll get
non-answers or no answers, with user's getting plaintive about the lack
of help.
Other companies act the same, all too often.
I wouldn't ding small open-source team for being slow in responding to
bugs, as they may have other more important things on their plate.
I will note one responsive project: Meson, on GitHub. Meson was using a
file called "meson_options.txt" to hold default values for project
options. I wrote up an issue about it (as had others earlier,
apparently), and I noted that the "txt" extension is too generic, and
that I edited my /etc/DIR_COLORS file so that I could grok a directory
listing faster. And in version 1.1 IIRC, voila, there was meson.options
to supplement meson.build.
I posted an issue for gmime yesterday, and ended up in a dialogue with
the lead developer.
Pan users will note that I was bird-dogging a problem that has plagued
pan since they moved to gmime for handling headers -- currently,
Newsgroups: lines don't wrap properly, and get MIME-encoded if they are
too long. News servers choke on that. (My C is too rusty to fix it
easily, but I can see where the fix should go.)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 304 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 34:31:48 |
| Calls: | 6,821 |
| Calls today: | 1 |
| Files: | 12,335 |
| Messages: | 5,407,131 |