XDG_CONFIG_DIRS an /usr/local/etc/xdg

[Peter White]

On Mon, Sep 20, 2021 at 09:46:22AM -0400, Elsie Hupp wrote:
> > Yes, and then there is XDG which expects exactly that, which
> > then leads to other hacks to soften the isolation of said
> > containers, or the inclusion of files which the go out of
> > sync and out of date compared to what is in the real /etc. If
> > I need hard sandboxing to stop such behaviour, then there is
> > a serious bug in the spec. ;)
> 
> Flatpak generally provides indirect access to system libraries
> through “runtimes”, so in order to provide access to, for
> example, whatever library you’re working on, the library itself
> could be added to the Freedesktop runtime, which would then
> provide properly sandboxed access to that library.

Be that as it may, one should not have to resort to such rather
extreme measures just to get sane behaviour back. And please stop
drumming for Flatpak. ;) It does have its application but not for
this. I mean, come on, more layers of complexity just for this.
Plus all the downsides I do not want to discuss here, since they
are out of scope.


OFF-TOPIC:

> P.S. FYI your email client seems to add hard line breaks to
> soft-wrap text

Yes, that is very much intentional, those are not "soft-wrap" but
real line breaks. You should read up on mailing list
netiquette[1] if this is news to you. Yes, there is an RFC for
that, and please don't go "fixing" my text. ;)

> which renders really strangely on my device.

Then your device/client is broken. Line length is usually limited
to 72 characters on my end (not accounting for quotes) so text is
readable on old-school terminals as well. I have made that 65 for
this message, since I just realized that said RFC recommends it.
Let me know if that's better and I will make this the new
default, but I won't change the automatic line breaks, since that
is what is expected on virtually every mailing list of repute.

> (And I wasn’t sure about the etiquette for quoted email
> history.

The simple answer is always: reduce to the max. ;) The history is
in the thread and you only quote the relevant parts discarding
all the irrelevant stuff. Maybe I should value that more myself.

> I don’t know how much of the peculiarity is just down to how
> mailman works versus how various email clients work, since some
> of these issues other mailing-list platforms handle somewhat
> more gracefully.)

Nothing to do with the platform but everything with the client.
Now, I have stopped nagging people about their line lengths since
I had the "pleasure" of using Thunderbird for mailing list
conversations, which locally suggests line breaks which in fact
are just wrapped lines. Back to good old vim and mutt for me it
is. ;)

[1] http://www.ietf.org/rfc/rfc1855.txt (There might be newer
versions, but that is what a quick search came up with)