* Do you recognize this zshrc.d naming scheme? @ 2019-01-18 9:13 Robert Spencer 2019-01-18 10:36 ` Magnus Woldrich 2019-01-24 19:12 ` Bart Schaefer 0 siblings, 2 replies; 10+ messages in thread From: Robert Spencer @ 2019-01-18 9:13 UTC (permalink / raw) To: zsh-users [-- Attachment #1: Type: text/plain, Size: 617 bytes --] Hi, 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 50-completions.zsh 55-plugins-oh-my-zsh.zsh 60-prompt-oh-my-zsh.zsh 65-globbing.zsh 70-variables.zsh 80-oh-my-zsh.zsh 85-functions.zsh 92-aliases.zsh 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-18 9:13 Do you recognize this zshrc.d naming scheme? Robert Spencer @ 2019-01-18 10:36 ` Magnus Woldrich 2019-01-18 11:36 ` Robert Spencer 2019-01-24 19:12 ` Bart Schaefer 1 sibling, 1 reply; 10+ messages in thread From: Magnus Woldrich @ 2019-01-18 10:36 UTC (permalink / raw) To: zsh-users >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? ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-18 10:36 ` Magnus Woldrich @ 2019-01-18 11:36 ` Robert Spencer 2019-01-20 15:35 ` René Wilhelm 0 siblings, 1 reply; 10+ messages in thread From: Robert Spencer @ 2019-01-18 11:36 UTC (permalink / raw) To: Magnus Woldrich; +Cc: zsh-users [-- 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? > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-18 11:36 ` Robert Spencer @ 2019-01-20 15:35 ` René Wilhelm 2019-01-21 0:52 ` Nathan.Pope 0 siblings, 1 reply; 10+ messages in thread From: René Wilhelm @ 2019-01-20 15:35 UTC (permalink / raw) To: Robert Spencer; +Cc: Magnus Woldrich, Zsh Users [-- Attachment #1: Type: text/plain, Size: 4779 bytes --] Hello! 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 On Fri, 18 Jan 2019 at 12:36, Robert Spencer <robert@3rock.co.za> 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 <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? > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-20 15:35 ` René Wilhelm @ 2019-01-21 0:52 ` Nathan.Pope 2019-01-23 6:55 ` Robert Spencer 0 siblings, 1 reply; 10+ messages in thread From: Nathan.Pope @ 2019-01-21 0:52 UTC (permalink / raw) To: asdf; +Cc: robert, m, zsh-users Hi, > On 21 Jan 2019, at 02:35, René Wilhelm <asdf@uni-koblenz.de> 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 <robert@3rock.co.za> 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 <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? >>> >> ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-21 0:52 ` Nathan.Pope @ 2019-01-23 6:55 ` Robert Spencer 2019-01-24 18:15 ` Kannan Varadhan 0 siblings, 1 reply; 10+ messages in thread From: Robert Spencer @ 2019-01-23 6:55 UTC (permalink / raw) To: zsh-users [-- Attachment #1: Type: text/plain, Size: 5883 bytes --] I second that request of Nathan's, René. Curious to read through those files. On Mon, 21 Jan 2019, 02:52 <Nathan.Pope@csiro.au wrote: > Hi, > > > On 21 Jan 2019, at 02:35, René Wilhelm <asdf@uni-koblenz.de> 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 <robert@3rock.co.za> 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 <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? > >>> > >> > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-23 6:55 ` Robert Spencer @ 2019-01-24 18:15 ` Kannan Varadhan 0 siblings, 0 replies; 10+ messages in thread From: Kannan Varadhan @ 2019-01-24 18:15 UTC (permalink / raw) To: Robert Spencer, zsh-users 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@3rock.co.za) Reply: Robert Spencer (mailto:robert@3rock.co.za) Date: January 22, 2019 at 10:56:05 PM To: zsh-users@zsh.org (mailto:zsh-users@zsh.org) 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? > > >>> > > >> > > > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-18 9:13 Do you recognize this zshrc.d naming scheme? Robert Spencer 2019-01-18 10:36 ` Magnus Woldrich @ 2019-01-24 19:12 ` Bart Schaefer 2019-02-03 8:58 ` Magnus Woldrich 1 sibling, 1 reply; 10+ messages in thread From: Bart Schaefer @ 2019-01-24 19:12 UTC (permalink / raw) To: Robert Spencer; +Cc: Zsh Users 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. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-01-24 19:12 ` Bart Schaefer @ 2019-02-03 8:58 ` Magnus Woldrich 2019-02-04 7:06 ` Robert Spencer 0 siblings, 1 reply; 10+ messages in thread From: Magnus Woldrich @ 2019-02-03 8:58 UTC (permalink / raw) To: Bart Schaefer; +Cc: Robert Spencer, Zsh Users [-- Attachment #1: Type: text/plain, Size: 97 bytes --] I just stumbled upon this and maybe you can use it as your reference: https://johnnydecimal.com/ ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Do you recognize this zshrc.d naming scheme? 2019-02-03 8:58 ` Magnus Woldrich @ 2019-02-04 7:06 ` Robert Spencer 0 siblings, 0 replies; 10+ messages in thread From: Robert Spencer @ 2019-02-04 7:06 UTC (permalink / raw) To: zsh-users [-- Attachment #1: Type: text/plain, Size: 256 bytes --] Thank you Magnus that is very interesting. I'll definitely be looking further into that. On Sun, 03 Feb 2019, 10:58 Magnus Woldrich <m@japh.se wrote: > I just stumbled upon this and maybe you can use it as your reference: > https://johnnydecimal.com/ > ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2019-02-04 7:06 UTC | newest] Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-01-18 9:13 Do you recognize this zshrc.d naming scheme? 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 2019-02-03 8:58 ` Magnus Woldrich 2019-02-04 7:06 ` Robert Spencer
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).