Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Do you recognize this zshrc.d naming scheme?
- X-seq: zsh-users 23845
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Robert Spencer <robert@xxxxxxxxxxx>
- Subject: Re: Do you recognize this zshrc.d naming scheme?
- Date: Thu, 24 Jan 2019 14:12:20 -0500
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qV90EeAQxW9gEzIXjRD/JVCQjt5syDrRJl/cuhc8fFY=; b=dRY4QyeIhDwlUAy3lFSDCa8jG3vu3yaelJh5Fbk3KTUh53unuPDBzbl6wqzJcKOe/D sbF9CAZpbu2RoYA92Cp6dZpof/QlMEw3MxZN/y7Kyv7v4QP85lytXzHNBRL+nPg3Wvl2 4DPo/tEIIluaJn+eBqheBjWtVFsY8+VWJRABDCjHRlMtjj5BciFqAZkE7RGzh5yL5zBl OGCEJ8k3DC1yoM9QQsgAkergcYargTSvZ57FJE24uF+c7bYgFPgXT61JeL9blRZtxDrA BoPyg32bx32FXLcKffmGBeWkx4cPLV+asn3i4+bnTnZQg3/n2PGJvgc1m7hWDP9HKPxf UsSQ==
- In-reply-to: <CAPad28_rgz8+0gdRp3+yqRd2-H-u-z3xCbqugocn7zhT_QMvEA@mail.gmail.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- List-unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAPad28_rgz8+0gdRp3+yqRd2-H-u-z3xCbqugocn7zhT_QMvEA@mail.gmail.com>
On Fri, Jan 18, 2019 at 4:14 AM Robert Spencer <robert@xxxxxxxxxxx> wrote:
>
> I've started working on an in-house project (awit-zsh-superawesome) that
> uses it, regrettably my boss can't remember where he got it from.
>
> I'd like to find the upstream source, so I can document the naming scheme.
> Unfortunately so far I've had no luck finding references online.
I've been traveling/busy so have only peripherally paying attention to
this thread ... but so far I've only seen people describing their own
similar setups. I strongly suspect that's because there is no
"upstream source" for this; this sort of file naming is a common idiom
in unix/linux used for forcing an ordering on configuration files that
are read from a directory, without having to name the individual files
in some sort of control script.
So this particular ordering was probably invented by the original
author of your in-house project.
A typical extension of this would be to add another tag in each file
name so that they could be divided into files read for all shells /
interactive shells / login shells.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author