linux - How to debug Shell command after customization -
I spent some time optimizing my configuration this way. Actually I can simulate all my dotfiles (.zshrc, .vimrc, ...) with the GIT repository, then I changed many things.
I'm on Mac OS X and my configuration works very well. However, when I use the same dotfile on Linux (Ubuntu), I find some difference. Most of them are minor differences but it is very annoying.
I use ZSH and PRIZO
when I get the message CD
20:17 ~ ❯ CD project script: invalid option - 'g' usage: script [option] [file] option: -a, - add input- c, --command & Lt; Command & gt; Run commands instead of interactive shell-R, - Hair Process -F return withdrawal code - Run flush after every flash drive - Even using force output file, when it is a link -q, shutdown -t, - -timing [= & lt; File & gt;] stderr (or FILE) output time data-V, - version output version information and exit -h, --help Display this help and exit
<I am posting here that someone knows how to debug this kind of error. The error message is not very clear and I do not know what else to look at.
Any thoughts?
Most of my configuration comes from the configurations of many others. / P>
Normally, you can type zsh
parameter -x
For debugging, it executes any line of shell code before running by this shell. This helps in where your configuration works.
In this case you get an error message from script
because it has no choice 'G'
list of all available options Extra (compare and compare script-G
). Command line tools are often quite different between different Unix derivatives, including the number and meaning of the command line option. man script
Compare between your platform.
as nickname for nocorrect cd
, check nocorrect
looks the most probable offender For, run unalias cd
If the problem is fixed, then type nocorrect
and go from there.
If the problem persists in looking for your configuration for your add-zsh-hook chpwd SOMETHING
Comments
Post a Comment