From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: please conform to the xdg base directory specification
Date: Sat, 17 Aug 2013 10:46:37 +0200 [thread overview]
Message-ID: <CAHYJk3QWBvfT8Q3TpOKDJZaYDmSi8c2NQ8RvJkjr8umz5Y9YPg@mail.gmail.com> (raw)
In-Reply-To: <130816202019.ZM27717@torch.brasslantern.com>
On 17 August 2013 05:20, Bart Schaefer <schaefer@brasslantern.com> wrote:
> This is the second "please conform to XDG" thread in the last few months
> (last time was users/17726). I mention this because ...
>
> On Aug 15, 7:54pm, Peter Stephenson wrote:
> }
> } Adding yet more complexity to the initialisation file logic doesn't seem
> } a great idea, but one thing that could keep everything more or less
> } under control would be to make ZDOTDIR a colon-separated array (and make
> } zdotdir an array).
>
> ... this suggestion, while fine on its own, does not solve the problem of
> bootstrapping the value of ZDOTDIR, so zsh would still not "conform to
> XDG." Unless someone *else* has a good use for a multi-element ZDOTDIR
> path, there's no benefit in going down this road.
>
> Unless of course you're proposing a default of zdotdir=(~/.zsh ~) rather
> than the current default of unset, a change that has its own set of
> potential gotchas.
>
> } We'd need to decide on the rule for multiple directories: use the first
> } found, use the first containing initialisation files, use the first file
> } of each type found by searching through the path...
>
> I'd prefer "use the first found" so that dotfiles could be disabled by
> creating an empty directory. I don't think "first file found of each
> type" is a wise idea, the files in a particular directory are likely to
> be related and not necessarily meant to work with files found elsewhere.
> "First directory containing" would be OK, but means scanning for all the
> files as soon as any of them is needed.
I have my dotfiles in ~/.zsh, but .zshrc linked to ~ so I can edit it
easily (I tend to do that a lot), so parsing both by default would be
bad for me.
--
Mikael Magnusson
next prev parent reply other threads:[~2013-08-17 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 8:33 Thomas Koch
2013-08-13 9:15 ` Frank Terbeck
2013-08-15 18:54 ` Peter Stephenson
2013-08-17 3:20 ` Bart Schaefer
2013-08-17 8:46 ` Mikael Magnusson [this message]
2013-08-24 17:05 ` Peter Stephenson
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=CAHYJk3QWBvfT8Q3TpOKDJZaYDmSi8c2NQ8RvJkjr8umz5Y9YPg@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--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).