Prepend commands in run_cmd with a space to prevent them to be stored in the history #109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
First of all, thanks for this tools, it's awesome!
However I have a small issue with the history, in the function
__go_to_window_or_session_path
, it callsrun_cmd "cd \"$target_path\""
andrun_cmd "clear"
, which get added to my history. I find this a bit annoying since I didn't typed those commands myself. I would appreciate if it would be possible to disable this behavior.An idea to fix that issue is to prepend those commands with a
<space>
character. If the user has set the variableHISTCONTROL=ignorespace
orHISTCONTROL=ignoreboth
, the command will be ignored from the history.In the case some users would want to keep those commands in their history, we could add an environment variable
TMUXIFIER_KEEP_HISTORY
, but I'm not sure that anybody would want that ?