From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14540 invoked by alias); 17 Aug 2013 08:46:57 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31658 Received: (qmail 25609 invoked from network); 17 Aug 2013 08:46:43 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.223.181 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mQdDgV8MAN8HytyOUR0ppq/018fsvh4f9bh4dsDRwjw=; b=FHWI8ThNmToy17UIQNasEBVCBOfm35/UvXNnr7Ep+1ekZ9A+9AL/3On+quCw/ThFRf W0yQBzxwlB68jfBVTzcPTVyzlFo0yWf3pCx/VIvnWw65N4NMQX7XnqLcomJsiFRnOv8n eGuoA4CtM0K8QGwD6KGHARqZpOO2mX7Yd5AurrCGO4j4PHMC0D59rYxRlk6acJN7zw74 oIUouGTjlUswqs+FXShpitn4DzVi0AaIcKNJEE4xKLH6JI4WBL558rpw63ltqNpk3cW6 ZfpcwE0YoB1TpE80j3e0BhQztfIp5oQQu+XPVp4MB8iPisKWD2PC/sEAlnWC0RlnJNWd apXQ== MIME-Version: 1.0 X-Received: by 10.50.127.145 with SMTP id ng17mr820273igb.6.1376729197626; Sat, 17 Aug 2013 01:46:37 -0700 (PDT) In-Reply-To: <130816202019.ZM27717@torch.brasslantern.com> References: <201308131033.54673.thomas@koch.ro> <87siyehrxy.fsf@ft.bewatermyfriend.org> <20130815195447.3ab675b0@pws-pc.ntlworld.com> <130816202019.ZM27717@torch.brasslantern.com> Date: Sat, 17 Aug 2013 10:46:37 +0200 Message-ID: Subject: Re: please conform to the xdg base directory specification From: Mikael Magnusson To: Bart Schaefer Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On 17 August 2013 05:20, Bart Schaefer 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