zsh-users
 help / color / mirror / code / Atom feed
From: Robert Spencer <robert@3rock.co.za>
To: Magnus Woldrich <m@japh.se>
Cc: zsh-users@zsh.org
Subject: Re: Do you recognize this zshrc.d naming scheme?
Date: Fri, 18 Jan 2019 13:36:49 +0200	[thread overview]
Message-ID: <CAPad28_OWvVmu_W73cxSg-SyLho8ycuTSV6gV0sO7GW+2DC8Yg@mail.gmail.com> (raw)
In-Reply-To: <20190118103631.3sthpno7x44fdgtc@japh.se>

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

Apologies for the top posting I'm on my phone and it tends to mangle
anything else.

The overall concept makes sense, not the execution in this case.

I'm struggling to guess what the original plan was with the naming scheme
sections.

10 makes sense, local variables.
20 what did this used to be?
30 history, but is 35 really related?
40 term settings? But 42 is aliases, that I would have expected in the 90's.
50 completion, but then what is 55 doing there.
60 prompt, but I'm not sure that 65 belongs here.
70 variables
80 oh-my-zsh, but then why doesn't 85-functions have its own section?
90 what did this section used to be? Misc? 92 is aliases, which again, I
would expect to have its own section. Although it makes sense that it's
last.

I'm hoping if I can find the upstream source it will all make sense.

What naming scheme do you use?


On Fri, 18 Jan 2019, 12:36 Magnus Woldrich <m@japh.se wrote:

> >As it says in the subject line, do you recognize this zshrc.d naming
> scheme?
>
> >10-locals.zsh
> >30-history-oh-my-zsh.zsh
> >32-history.zsh
> >35-long-running.zsh
> >40-term.zsh
> >42-dircolors.zsh
>
> I use something similar but isn't it just common sense so that we can
> iterate
> the files and load them in the correct order?
>

  reply	other threads:[~2019-01-18 11:37 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 [this message]
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
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=CAPad28_OWvVmu_W73cxSg-SyLho8ycuTSV6gV0sO7GW+2DC8Yg@mail.gmail.com \
    --to=robert@3rock.co.za \
    --cc=m@japh.se \
    --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).