zsh itself does not have a default user configuration. So the default ~/.zshrc is actually no ~/.zshrc. But as you tagged the question with oh-my-zsh I would assume that you want to restore the default oh-my-zsh configuration. For this it should be sufficient to copy templates/zshrc.zsh-template from your oh-my-zsh installation path, usually ~/.oh-my-zsh: cp ~/.oh-my-zsh/templates/zshrc.zsh-template … Read more
git config –global color.diff auto git config –global color.status auto
If you’re wondering why this happened: You likely have $EDITOR or $VISUAL set to vi/vim which made zsh default to the vi keymap which doesn’t use ctrl+a for moving the caret. Adding bindkey -e to ~/.zshrc will restore the old behavior (emacs keymap).
It’s actually much simpler than that: lw=(‘plugin1’ ‘plugin2’ ‘plugin3’) for i in $lw; do . ~/Library/Rogall/plugins/$i/lw.prg end done In summary: Assign to foo, not $foo (the shell would try to expand $foo and assign to whatever it expands to; typically not useful) Use the loop variable directly; it contains the array value rather than the … Read more
Regarding M-x eshell: Eshell is not a stand-alone shell; it’s implemented in pure elisp, so can’t be run outside emacs, which is why it’s not one of the standard shells. It doesn’t have its own scripting language like bash/zsh/etc. have; it has elisp, and some command interpretation stuff to make calling elisp a little cleaner. … Read more
To load zsh plugins default format as specified in .zshrc is plugins=(rails git textmate ruby lighthouse). For some reason it was written in this format plugins=(git, lighthouse) separated by comma. Separating just by space and source the .zshrc after saving fixed the issue.
The history n command, where n is a number shows all history since line n. So in your case, history 904 will show the last 100 commands.
For adding a newline after a pattern, you can also say: sed ‘/pattern/{G;}’ filename Quoting GNU sed manual: G Append a newline to the contents of the pattern space, and then append the contents of the hold space to that of the pattern space. EDIT: Incidentally, this happens to be covered in sed one liners: … Read more
When you are at a command line, typing in commands and reading output you are working in a program called a terminal (or console on windows). The terminal is taking your commands and forwarding them to a program, called a shell, who’s job is to actually execute the commands you type in to the terminal … Read more
There is no need to use find. You could try the following: for file in /path/to/directory/**/*(.); do echo $file; done or for file in /path/to/directory/**/*(.); echo $file the ** pattern matches multiple directories recursively. So a/**/b matches any b somewhere below a. It is essentially matches the list find a -name b produces. (.) is … Read more