Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey,
I recently had several cases where my
SSH_TTYenvironment variable was unset in my emacs even thoughtmux show-environment SSH_TTYwas correctly pointing to/dev/pts/0. This breaksclipetty-cutand thus alsointerprogram-cut-function. I wonder if we should be usingclipetty--get-tmux-ssh-ttyinstead of(getenv "SSH_TTY" (selected-frame))when tmux is available?Here's what I saw when debugging this:
I'm not sure if my suggested solution is the "correct" solution in general but I'm opening this in case someone else faces similar issues and to potentially discuss if there's a better fix to this. I guess the first question is why is my
SSH_TTYunset under emacs even thoughtmux show-environment SSH_TTYis set and correct. Is this a common thing to happen or is there something weird in my setup?