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

Config’s default_shell not respected when creating a new tab with a layout #2187

Closed
Zykino opened this issue Feb 24, 2023 · 0 comments · Fixed by #2203
Closed

Config’s default_shell not respected when creating a new tab with a layout #2187

Zykino opened this issue Feb 24, 2023 · 0 comments · Fixed by #2203

Comments

@Zykino
Copy link
Contributor

Zykino commented Feb 24, 2023

Basic information

zellij --version: zellij 0.34.4
uname -av: Linux zykino-pop-os 6.1.11-76060111-generic #202302091138~1675975749~22.04~f771a7f SMP PREEMPT_DYNAMIC Thu F x86_64 x86_64 x86_64 GNU/Linux

Further information

rg shell ~/.config/zellij/config.kdl
17:// Choose the path to the default shell that zellij will use for opening new panes
20:default_shell "fish"

The layout I’m crafting

layout {
        pane size=1 borderless=true {
                plugin location="zellij:compact-bar"
        }
        pane split_direction="vertical" {
                pane edit=""
                pane split_direction="horizontal" {
                        pane command="cargo" {
                                args "test"
                                start_suspended true
                        }
                        pane // <- Default shell here
                        pane command="gitui" {
                                start_suspended true
                        }
                }
        }
}

Open with zellij action new-tab -l ~/.config/zellij/layouts/IDE-rust.kdl.

I expected the configured default_shell (fish) to be opened (like with Ctrl+p or Ctrl+t).
bash opened instead (my user’s sessions default shell). I let it as default since fish’s docs says it should not be set as default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant