-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac doesn't show the history on the top panel #2
Comments
What version of bash are you using? The log pane only seems to function with bash 4.2.0 and later (also does not work with bash 3.2.57). In earlier versions, the history is held up until you quit from spack install bash
spack load bash
bash --version
path/to/swc-shell-split-window.sh Maybe README.md can be updated to mention >= bash-4.2 as a dependency in addition to tmux. |
FYI I ran in to this issue, but was able to install a newer bash with macports (or homebrew) and now things seem to be working. |
Encountered this right now and fixed with installing new bash with homebrew - thanks for reporting this and for the tips how to fix! |
One point: on my MacBook Pro I had a job getting it to work at first, as my default shell was i.e. do this:
but not this:
That is, any comments you put in the middle of a multi-line shell script command should have a backtick at the start and finish of the line (the backtick is the syntax for command substitution - kudos to @giordano for telling me this!) |
I'm also having the issue that the history is not shown in the top panel, on my mac.
|
@liz-is I used it in teaching in May on my mac, but in default shell (zsh). Does it work on your machine this way? |
Seems that on mac the script doesn't write to the /tmp/log-file. Problem may be on line 48
"HISTFILE='${LOG_FILE}' HISTCONTROL=ignorespace PROMPT_COMMAND='history -a' bash --norc; kill '${LOG_PID}'"
with the-a
flag, which is different for mac. When I remove the flag the history is writing to the file. However the history then appears in theSHELL_PANE
not theLOG_PANE
.The text was updated successfully, but these errors were encountered: