Shell – zsh, modularity,multiple .zsh files and oh-the-zsh

debianshellzsh

I use/enjoy zsh and have used oh-my-zsh in couple. While it's all nice and cool, I do get irritated that I have to constantly update the oh-my-zsh script every 15 days/month .

Now I have put zsh as a prompt on another machine. Now the good thing about my oh-my-zsh is that instead of putting everything in .zshrc which when you install .zsh does, it does it in multiple directories with .zsh extension.

While I do not want to go that whole hog, is there a way I can put multiple *.zsh files under say ~/.zsh/ and strive to have a similar working environment.

Can this work or am I missing something ?

Running zsh on debian 64-bit.

Update – There are only two files which can be in my zsh installation –

think-debian% pwd
/home/shirish

think-debian% ls .z
.zcompdump  .zshrc

Any ideas ?

Best Answer

You can set your Zsh dotfiles directory with the ZDOTDIR environment variable; just add it to your ~/.zshenv:

ZDOTDIR="${ZDOTDIR:-$HOME/.zsh}"

Then, source any files in that directory that are named *.zsh from your ~/.zsh/zshrc:

if [[ -d "$ZDOTDIR" ]]; then
  for file in "$ZDOTDIR"/*.zsh; do
    source "$file"
  done
fi

For bonus points, uninstall Oh-My-Zsh and enjoy Zsh as it was intended, a powerful and flexible alternative to Bash, not a bloated ratmangle...

Related Solutions

Shell – hook-like system for shell

Things that may help you:

The preexec hook function is called before every command line is executed (not before every command).

preexec() echo will execute: $1

precmd before each prompt.

precmd() echo executed: $history[$[HISTCMD-1]]

You can extend a function like this:

functions[git]='
  (){ '$functions[git]'; } "$@"; local myret=$?
  do-extra-stuff
  return $myret'

Or:

functions[git-old]=$functions[git]
git() {
  git-old "$@"
  local myret=$?
  do-extra-stuff || return $myret
}

The DEBUG trap is executed after each command:

trap 'echo $ZSH_DEBUG_CMD returned with $?' DEBUG

You can redefine the accept-line widget (mapped to Enter) to do stuff in there:

accept-line() {
  zle -R "going to run: $BUFFER"
  sleep 1
  zle .$WIDGET
}

zle -N accept-line

Shell – cleaning output of a script so it’s descending, gives package names and cleanly exists

Starting with

for source in $(dpkg-query --show -f '${source:Package}\n' | sort -u); do bts select source:${source} tag:patch; done

sorting the output involves another use of sort, to sort the overall output numerically in reverse order:

for source in $(dpkg-query --show -f '${source:Package}\n' | sort -u); do bts select source:${source} tag:patch; done \
| sort -n -r

To display the (source) package name along with the bug number, the simplest option is to add ${source} (the source package) in the right place, processing bts's output each time it's run:

for source in $(dpkg-query --show -f '${source:Package}\n' | sort -u)
do bts select source:${source} tag:patch | sed "s/^/${source} /g"
done

This outputs lines of the form

linux 845422

so we need to change the final sort to sort on the second field:

for source in $(dpkg-query --show -f '${source:Package}\n' | sort -u)
do bts select source:${source} tag:patch | sed "s/^/${source} /g"
done | sort -k2,2n -r

On a single line that's

for source in $(dpkg-query --show -f '${source:Package}\n' | sort -u); do bts select source:${source} tag:patch | sed "s/^/${source} /g"; done | sort -k2,2n -r

Best Answer

Related Solutions

Shell – hook-like system for shell

Shell – cleaning output of a script so it’s descending, gives package names and cleanly exists

Related Question