Closed simonmandlik closed 2 months ago
I'm not sure exactly what you're angling for here, but I do want to note that: You have full control over the list of ssh domains via https://wezfurlong.org/wezterm/config/lua/config/ssh_domains.html
You might consider adjusting your config to parse ~/.ssh/known_hosts
or otherwise obtain the relevant list of hosts using logic that makes sense to you and your specific use case.
Thanks for the answer! I have solved it by manually modifying config.ssh_domains
.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I'm using this amazing keymap for attaching SSHMUX domains:
{ mods = "LEADER", key = "a", action = act.ShowLauncherArgs { flags = "FUZZY|DOMAINS" } }
This works amazingly as long as the specific hostname is specified in
~/.ssh_config
. There is one problem with this. Sometimes I modify settings only for the second-level (or the third-level) domain, as there are might be too many possible subdomains.This often happens in HPC clusters. I would have something like
in
~/.ssh_config
, and I would connect likessh node118.cluster.com
orssh node43.cluster.com
. In such cases,wezterm.enumerate_ssh_hosts()
only showscluster.com
.I can think of two ways two solve this without having to use wezterm cli for each connection:
~/.ssh/known_hosts
.