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

bug(s): default_mode locked causes input to not work #3998

Open
dougg0k opened this issue Feb 17, 2025 · 1 comment
Open

bug(s): default_mode locked causes input to not work #3998

dougg0k opened this issue Feb 17, 2025 · 1 comment

Comments

@dougg0k
Copy link

dougg0k commented Feb 17, 2025

Issue description

When I set default_mode "locked" in the config.kdl input does not respond when unlocked.

  1. Differently when no default_mode is set in the config. Ctrl + <g> always has the text Lock, regardless if locked or unlocked.
  2. When the default_mode "locked" is set, text always show Unlock in both locked and unlocked mode. In both situations It's probably a small text bug.
  3. When I set default_mode "locked", the background color of the bugged Unlock are in the opposite direciton, it shows when unlocked rather when locked.
  4. As for the main issue, when default_mode are set to "locked", input works when terminal opens, but when you press Ctrl+g to unlock, the input stops working.

Minimal reproduction

  1. Set default_mode "locked" in the config.kdl
  2. Open terminal with zellij
  3. Try typing while unlocked and locked

Other relevant information

❯ zellij --version
zellij 0.41.2
@dougg0k dougg0k changed the title default_mode locked causes input to not work bug(s): default_mode locked causes input to not work Feb 17, 2025
@dougg0k
Copy link
Author

dougg0k commented Feb 17, 2025

Somewhat breaking bug @imsnif

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

No branches or pull requests

1 participant