![]() † This is tmux-mediated inheritance, not the parent–child inheritance that is the usual mechanism for passing along the cwd. According to the CHANGES file, it looks like this has been the case since tmux 0.6 (at least for new-window). when done through the tmux binary, instead of via a binding or at a tmux- : prompt). There should be no need to use cd command like that in the shell-command argument given to either tmux new-session or tmux new-window.Ī new window will “inherit” † the current working directory when using new-session and new-window from the command line (i.e. rsync, SSH-based Git access, etc.) since these programs expect a “clean” connection without such debugging noise present. Note: These debug additions need to be temporary since they will cause problems if you ever use a program that makes automated logins (e.g. The errors may not actually be in your startup file itself, but in a script that it runs.Once you know which file is being processed when the errors occur, add more debug outputs around each “major block” or line to narrow down the responsible section/line.If the errors happen before that file, then the problem may be in /etc/profile. ![]() ![]() If not, instrument your other startup files. bashrc to see if the error occurs during your. If you find the -vx output too verbose, you could try “printf debugging” (manually adding debug statements to your startup files until you can narrow down exactly which lines are causing the errors): The shell errors are probably due to some problem in your startup files (or something they run).Īs shellter commented, temporarily including the command set -vx early in your startup sequence is a good way to find out where the errors are occurring.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |