Re: Do you recognize this zshrc.d naming scheme?

[Kannan Varadhan <kvaradhan3@xxxxxxxxx>]

While I dont have something this elaborate, I do have a variation that looks as:

~ » ls -a .rc                                               ▸▸▹▹▹▹▹▹▹▹ 10:06:40
./		bin/		dot.vimrc	dot.zshrc	themes/
../		configure*	dot.zlogin	emacs/		zshell/
.emacs-flc/	dot.Xresources	dot.zlogout	fonts/
.git/		dot.emacs	dot.zprofile	openbox/
.gitignore	dot.octaverc	dot.zshenv	shell/

And configure really is:

#! /bin/sh -x

CWD=`pwd`

for i in ./dot.* ; do
    ln $i $HOME/$(echo $i | sed 's/dot//')
done

git clone git://github.com/robbyrussell/oh-my-zsh.git $HOME/.oh-my-zsh

case $(uname) in
Linux)
    ( cd ../.config ; ln -s ../.rc/openbox . )
    (
        cd $HOME ;
        mkdir -p .local/share ;
        cd .local/share ;
        ln -s ../../.rc/themes .
    )
    ( cd $HOME ; ln -s $CWD/fonts .fonts )
    sudo fc-cache -f -v
    ;;
Darwin)
    if [ X$(whoami) = Xroot ] ; then
        FONTSDIR=/Library/Fonts
    else
        FONTSDIR=$HOME/Library/Fonts
    fi
    ln $CWD/fonts/*/*.ttf $FONTSDIR
    ;;
esac

(
    cd $HOME
    if [ ! -d ./bin ] ; then
        mkdir bin
    fi
    ln -s $CWD/bin/* ./bin
)

exit

Basically then, I can get on a new machine, drop ship the .rc
directory, run configure and prep my environment.  the zshell inits
are then:

~ » ls .rc/zshell                                           ▸▸▹▹▹▹▹▹▹▹ 10:08:51
_addpath			_zshrc_60_adobe_fdk
_zlogout_56_fortune		_zshrc_88_utilities
_zlogout_99_delay		_zshrc_99_nethack
_zprofile_52_cisco		addpath
_zshenv_50_cisco		bcharge
_zshrc_20_go			omz.zshrc
_zshrc_30_batteryCharge		set_cdpath
_zshrc_50_fungible		vlc
_zshrc_55_cisco

Been that way for me for a long while now,


Kannan


From: Robert Spencer (mailto:robert@xxxxxxxxxxx)
Reply: Robert Spencer (mailto:robert@xxxxxxxxxxx)
Date: January 22, 2019 at 10:56:05 PM
To: zsh-users@xxxxxxx (mailto:zsh-users@xxxxxxx)
Subject: Re: Do you recognize this zshrc.d naming scheme?

> I second that request of Nathan's, René.
>
> Curious to read through those files.
>
>
> On Mon, 21 Jan 2019, 02:52 >
> > Hi,
> >
> > > On 21 Jan 2019, at 02:35, René Wilhelm wrote:
> > >
> > > This is how my $ZDOTDIR/functions.d/ looks like. Works out really well
> > and
> > > grows since 1999. There is no fixed scheme, rather each file is just a
> > > bucket full of functions and stuff. New things usually end up in
> > > 90-random*.sh. Startup time is still relatively low, at
> > > around 0.14570188522338867 seconds. It is mostly a huge mess, but I feel
> > > very at home in it.
> > >
> > > % wc -l *.sh
> > >
> > > 5 00-defaults.sh
> > > 43 00-quotes.sh
> > > 67 00-utils.sh
> > > 57 10-zsh-completion.sh
> > > 20 10-zsh-contrib.sh
> > > 16 10-zsh-syntax-highlighting.sh
> > > 93 10-zsh.sh
> > > 52 20-archlinux.sh
> > > 62 20-darwin.sh
> > > 104 20-debian.sh
> > > 156 20-gentoo.sh
> > > 5 20-linux.sh
> > > 21 20-osx-iterm.sh
> > > 21 20-osx-launchd.sh
> > > 189 20-osx.sh
> > > 17 30-gpg.sh
> > > 1 30-pass.sh
> > > 6 40-go.sh
> > > 5 40-kotlin.sh
> > > 195 40-node.sh
> > > 24 40-perl.sh
> > > 27 40-python.sh
> > > 3 40-ruby.sh
> > > 9 40-rust.sh
> > > 22 50-admin.sh
> > > 62 50-aliases.sh
> > > 16 50-android.sh
> > > 41 50-api.sh
> > > 2 50-api_keys.sh
> > > 149 50-backup.sh
> > > 64 50-beep.sh
> > > 5 50-beet.sh
> > > 98 50-bidos.sh
> > > 14 50-calc.sh
> > > 8 50-camera.sh
> > > 25 50-chroot.sh
> > > 5 50-clipboard.sh
> > > 17 50-colors.sh
> > > 48 50-copypaste.sh
> > > 74 50-datetime.sh
> > > 16 50-debug-audio.sh
> > > 113 50-dev.sh
> > > 22 50-dev2.sh
> > > 42 50-development.sh
> > > 55 50-dkb.sh
> > > 20 50-dotfiles.sh
> > > 75 50-dslr.sh
> > > 165 50-editor.sh
> > > 18 50-environment.sh
> > > 16 50-evil.sh
> > > 5 50-favs.sh
> > > 71 50-find.sh
> > > 14 50-games.sh
> > > 59 50-glitch.sh
> > > 12 50-global-aliases.sh
> > > 14 50-globalias.sh
> > > 14 50-gtd.sh
> > > 38 50-history.sh
> > > 23 50-homebrew.sh
> > > 9 50-init.sh
> > > 14 50-iptables.sh
> > > 15 50-keyboard.sh
> > > 5 50-local.sh
> > > 43 50-locate.sh
> > > 44 50-mail.sh
> > > 141 50-network.sh
> > > 9 50-notes.sh
> > > 18 50-npm.sh
> > > 3 50-pager.sh
> > > 28 50-pdf.sh
> > > 1 50-pf.sh
> > > 61 50-pi.sh
> > > 13 50-print.sh
> > > 32 50-private.sh
> > > 1 50-react-native.sh
> > > 9 50-redux.sh
> > > 1 50-regexp.sh
> > > 28 50-setup.sh
> > > 236 50-solfeggio.sh
> > > 4 50-string-manipulation.sh
> > > 4 50-string-manipulation2.sh
> > > 13 50-sudo.sh
> > > 29 50-uniko.sh
> > > 24 50-update.sh
> > > 14 50-utils.sh
> > > 8 50-webdev-auth.sh
> > > 118 50-webdev.sh
> > > 11 50-websearch.sh
> > > 112 50-write.sh
> > > 2 50-xorg.sh
> > > 10 50-youtube.sh
> > > 43 70-bookmarks.sh
> > > 11 70-bspwm.sh
> > > 17 70-dmenu.sh
> > > 37 70-docker.sh
> > > 2 70-dtach.sh
> > > 26 70-dwm.sh
> > > 66 70-fzf.sh
> > > 133 70-git.sh
> > > 9 70-imagemagick.sh
> > > 231 70-latex.sh
> > > 171 70-mpd.sh
> > > 11 70-openvpn.sh
> > > 8 70-osascript.sh
> > > 10 70-postgresql.sh
> > > 1 70-ranger.sh
> > > 7 70-reflex.sh
> > > 22 70-selecta.sh
> > > 16 70-sencha.sh
> > > 6 70-sf.sh
> > > 8 70-systemctl.sh
> > > 29 70-tags.sh
> > > 69 70-tmux.sh
> > > 10 70-wu.sh
> > > 1 70-xdg.sh
> > > 10 70-z.sh
> > > 19 80-liveandgov.sh
> > > 27 80-montaigne.sh
> > > 587 90-random0.sh
> > > 81 90-random1.sh
> > > 81 90-random2.sh
> > > 4 90-random3.sh
> > > 6 90-random4.sh
> > > 45 90-random5.sh
> > > 136 90-random6.sh
> > > 17 90-random7.sh
> > > 281 90-random8.sh
> > > 40 90-random9.sh
> > > 7 99-todo.sh
> > > 170 XX-alias.sh
> > > 117 colors.sh
> > > 41 gpg-agent.plugin.sh
> > > 37 spectrum.sh
> > > 6350 total
> > >
> >
> > Some of these look like they could be very useful -
> > do you make any of these public?
> >
> > -Nathan
> >
> > >
> > > On Fri, 18 Jan 2019 at 12:36, Robert Spencer wrote:
> > >
> > >> 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 > > >>
> > >>>> 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?
> > >>>
> > >>
> >
> >