From: Wesley Schwengle <wesley@opndev.io>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] init.sourcehome: look in ~/.config/zsh for files
Date: Tue, 02 Jan 2024 01:13:17 +0000 [thread overview]
Message-ID: <669abf95-4ebd-4e82-89c0-cc2a222e36f5@opndev.io> (raw)
In-Reply-To: <ZZNN-KQZiS-N88jk@teapot>
On 1/1/24 19:42, earnestly wrote:
> On Mon, Jan 01, 2024 at 10:41:00PM +0000, Wesley Schwengle wrote:
>> That's not an "own standard". Many applications use ~/.config, eg git,
>> google-chrome, i3, signal, vlc, transmission, kitty, yarn, asciinema,
>> and many more.
>
> Hardcoding ~/.config is a custom standard, the applications you list all
> follow XBDS which derives its value from XDG_CONFIG_HOME with a fallback
> on HOME/.config if unset.
>
> The suggest in this thread is to *hardcode* the value of HOME/.config.
That's not how I read the remark, it is stated:
> But wouldn't it be possible to support a minimal subset, e.g. like
> ~/.config, to allow using some XDG features?
So, it asks to let zsh behave as if XDG_CONFIG_HOME isn't set, then
using the default ~/.config
Therefore I don't think this is "a personal or own standard".
Cheers,
Wesley
--
Wesley Schwengle
E: wesley@opndev.io
next prev parent reply other threads:[~2024-01-02 1:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 19:59 Jörg Sommer
2024-01-01 20:06 ` Bart Schaefer
2024-01-01 21:14 ` Jörg Sommer
2024-01-01 22:25 ` earnestly
2024-01-01 22:41 ` Wesley Schwengle
2024-01-01 23:42 ` earnestly
2024-01-02 1:13 ` Wesley Schwengle [this message]
2024-01-01 23:31 ` Bart Schaefer
2024-01-02 7:01 ` Jörg Sommer
2024-01-02 7:58 ` Lawrence Velázquez
2024-01-02 11:18 ` zeurkous
2024-01-02 20:00 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=669abf95-4ebd-4e82-89c0-cc2a222e36f5@opndev.io \
--to=wesley@opndev.io \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).