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
This is a general tracking issue for what should be improved in the user facing documentation.
A problem is that some information is not documented at all or only at some places, because we provide multiple documentation locations:
man page
online docs
zellij --help
statusbar tips
Ideally, most / all information is available everywhere (as long as it is reasonable) because we can't expect users to check multiple places. Also, I guess most users don't expect another documentation location if they find one place.
Layout file: show how to run commands and drop into an interactive shell afterwards Run multiple commands in layouts #1099
to really get an interactive shell with some commands pre-executed, it is better to use a startup script file or doing it inline in the layout config: run: command: {cmd: bash, args: ["-c", "exec bash --init-file <(echo \"set -m; source .bashrc; cd <somewhere>; vim -S\") -i"]}
I don't want to open new issue, so will put my observation here: the old documentation contains the description of modes: https://zellij.dev/old-documentation/keybindings-modes but the new one have only list of them: https://zellij.dev/documentation/keybindings-modes
Is there a reason for that or it was just not-ported yet?
This is a general tracking issue for what should be improved in the user facing documentation.
A problem is that some information is not documented at all or only at some places, because we provide multiple documentation locations:
zellij --help
Ideally, most / all information is available everywhere (as long as it is reasonable) because we can't expect users to check multiple places. Also, I guess most users don't expect another documentation location if they find one place.
Checklist of small documention issues I noticed:
to really get an interactive shell with some commands pre-executed, it is better to use a startup script file or doing it inline in the layout config:
run: command: {cmd: bash, args: ["-c", "exec bash --init-file <(echo \"set -m; source .bashrc; cd <somewhere>; vim -S\") -i"]}
Related issues:
The text was updated successfully, but these errors were encountered: