Skip to content
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

Document how to change mux SSH_AUTH_SOCK #6283

Open
phromo opened this issue Oct 16, 2024 · 1 comment
Open

Document how to change mux SSH_AUTH_SOCK #6283

phromo opened this issue Oct 16, 2024 · 1 comment
Labels
docs Primarily or only affects documentation

Comments

@phromo
Copy link

phromo commented Oct 16, 2024

What page or section of the docs have an issue?
https://wezfurlong.org/wezterm/config/lua/config/mux_enable_ssh_agent.html

Describe the issue

Background:
I typically set SSH_AUTH_SOCK from my fish shell (which wezterm starts), my basic profile env holds an inappropriate value. When wezterm starts it seems to read SSH_AUTH_SOCK from the env and use that for the mux servers (as listed by wezterm cli list-clients).

Desired change:
Since in my case, what wezterm has picked up is wrong, I would like to have clearer documentation on how to change it. I can list it yes, but how to change it?

Additional notes
The doc says this: "The auth sock will point to a symbolic link that will in turn be pointed to the authentication socket associated with the most recently active multiplexer client."

Maybe that statement is intended to tell me what I should do? However, I cannot convert that statement into what I should do :/

@phromo phromo added the docs Primarily or only affects documentation label Oct 16, 2024
@phromo
Copy link
Author

phromo commented Oct 16, 2024

It could be that the only solution is to ensure my env has a correct value for SSH_AUTH_SOCK before wezterm starts. If so, maybe add that explicitly to the docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Primarily or only affects documentation
Projects
None yet
Development

No branches or pull requests

1 participant