From: Bart Schaefer <schaefer@brasslantern.com>
To: Robert Spencer <robert@3rock.co.za>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Do you recognize this zshrc.d naming scheme?
Date: Thu, 24 Jan 2019 14:12:20 -0500 [thread overview]
Message-ID: <CAH+w=7YH0BRrer2q4nqaLm52v77+=0je31SXAO0kREgmLP8g0A@mail.gmail.com> (raw)
In-Reply-To: <CAPad28_rgz8+0gdRp3+yqRd2-H-u-z3xCbqugocn7zhT_QMvEA@mail.gmail.com>
On Fri, Jan 18, 2019 at 4:14 AM Robert Spencer <robert@3rock.co.za> 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.
next prev parent reply other threads:[~2019-01-24 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 9:13 Robert Spencer
2019-01-18 10:36 ` Magnus Woldrich
2019-01-18 11:36 ` Robert Spencer
2019-01-20 15:35 ` René Wilhelm
2019-01-21 0:52 ` Nathan.Pope
2019-01-23 6:55 ` Robert Spencer
2019-01-24 18:15 ` Kannan Varadhan
2019-01-24 19:12 ` Bart Schaefer [this message]
2019-02-03 8:58 ` Magnus Woldrich
2019-02-04 7:06 ` Robert Spencer
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='CAH+w=7YH0BRrer2q4nqaLm52v77+=0je31SXAO0kREgmLP8g0A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=robert@3rock.co.za \
--cc=zsh-users@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).