You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using wezterm cli split-pane from within a wezterm instance, the resulting split does not retain the working directory of the pane that you ran the command from.
Environment (please complete the following information):
OS: Archlinux GNOME 40 Wayland
Version: this happens on stable build and latest commit on main branch
Keyboard layout: ENG
Configuration
The only relevant option is the use of "CurrentTabDomain" as an argument to the split actions that I have bound with a leader key. When using those, the current working directory is retained.
Expected behavior
I would like the current working directory to be retained, even if behind a config item, without having to pass --cwd to the cli command. The reason being that I utilize this command from my editor, which assigns the command at startup and doesnt expect to pass the working directory (which can be changed during the run of the editor).
The text was updated successfully, but these errors were encountered:
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.
Describe the bug
When using
wezterm cli split-pane
from within a wezterm instance, the resulting split does not retain the working directory of the pane that you ran the command from.Environment (please complete the following information):
Configuration
The only relevant option is the use of "CurrentTabDomain" as an argument to the split actions that I have bound with a leader key. When using those, the current working directory is retained.
Expected behavior
I would like the current working directory to be retained, even if behind a config item, without having to pass
--cwd
to the cli command. The reason being that I utilize this command from my editor, which assigns the command at startup and doesnt expect to pass the working directory (which can be changed during the run of the editor).The text was updated successfully, but these errors were encountered: