Repository navigation
Replies: 4 comments
|
Hey @kasajian - thanks for all the details and your thoughtful write-up. In my experience and opinion, the defaults of any app with a sufficiently large user-base are either:
Over the years I have heard many different opinions and got quite a bit of input regarding how the app should be used and what the defaults should be. I agreed with some (as I do with some of your points), disagreed with others and ultimately learned that the amount of overlap between them is slim. We are all different people and would like our app to work in different ways - especially considering the high level of computer literacy we all have by nature of what Zellij is. As a developer and product designer, the best I can do is offer ways of configuring one's way into/out-of behavior one considers (un)desirable, and make it as easy as possible to do so. So I'd say the only thing you're doing wrong is trying to force the defaults onto your daily-driver workflow. Make it work for you - that's the best advice I can give. |
|
If I go with all the defaults, what's the normal way to solve the problem
of needing to sending Ctrl+G to the app?
…On Mon, Nov 9, 2026, 10:17 PM Aram Drevekenin ***@***.***> wrote:
Hey @kasajian <https://github.com/kasajian> - thanks for all the details
and your thoughtful write-up.
In my experience and opinion, the defaults of any app with a sufficiently
large user-base are either:
1. A compromise between many different workflows and ways of doing
things
2. Dictated by a multi-billion dollar company in a "this is how you
use it, and you're going to like it" fashion
Over the years I have heard many different opinions and got quite a bit of
input regarding how the app should be used and what the defaults should be.
I agreed with some (as I do with some of your points), disagreed with
others and ultimately learned that the amount of overlap between them is
slim. We are all different people and would like our app to work in
different ways - especially considering the high level of computer literacy
we all have by nature of what Zellij is.
As a developer and product designer, the best I can do is offer ways of
configuring one's way into/out-of behavior one considers undesirable, and
make it as easy as possible to do so. So I'd say the only thing you're
doing wrong is trying to force the defaults onto your daily-driver
workflow. Make it work for you - that's the best advice I can give.
—
Reply to this email directly, view it on GitHub
<#5845?email_source=notifications&email_token=AASGHHNEUMW6Z2YI4Q2J2NL5YKXIFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVGEYDMNJYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19510658>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASGHHKAGQG2LI26ORMJXHL5YKXIFAVCNFSNUABIKJSXA33TNF2G64TZHMZDSMRQGE2DEMRZHNCGS43DOVZXG2LPNY5TCMJSGYYTQMRZUF3AE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
With stock defaults you can't keybinds preset="default" primary="Ctrl" secondary="Alt" {
normal {
bind "Ctrl g" { SwitchToMode "locked"; }
...
}
locked {
bind "Ctrl g" { SwitchToMode "normal"; }
}
}( The usual fix is a small override in your config, since binds in keybinds {
normal {
bind "Ctrl g" { Write 7; }
bind "Ctrl Alt g" { SwitchToMode "locked"; }
}
locked {
bind "Ctrl Alt g" { SwitchToMode "normal"; }
}
}
Everything else in the preset stays untouched, and Zellij applies config changes live. The same override can also be done from the settings screen (Keyboard → Key bindings) if you'd rather not touch the file. |
|
Based on your advice, I've decided to go back to stock configuration and only solve this one problem, which I've done by mapping Alt+G to sent Ctrl+G in to the app in Normal mode. I think if I was a heavier user of vim and used it's Alt+* keys, I'd probably be super frustrated with Zellij, but I think I'm good for now. |
Uh oh!
There was an error while loading. Please reload this page.
I'm new to multiplexers -- never used tmux, etc. I set up Zellij and finally got it configured to work the way I want. It's flexible enough to do that. However, as this is a new area for me, I would preferred to stick with the defaults until I became familiar with how the stock system works, and only then make modifications. That way, if I'm deviating from the norm, I can reason about why my particular scenario requires it, whether it's a more unique scenario or just having a less common preference.
But that's not my case. I installed it, and right off the bat, my thought was, wait. This can be the way it's supposed to work. What? So I'd like to describe to you what issues I had IMMEDIATELY and how I addressed them.
First, things that may be less common: I mostly work in Windows, although I am in MacOs, Ubuntu and Termux about 5% of my time.
Issue 1. Right off the bad, I was really surprised about Normal mode. How are people even using this thing if you're not locked mode. So right off the bad, I can no longer use the following keystroke combination: CTRL G, P, T, N, S, O, B, Q, and Alt N, H, L J, K, Left, Right, Down, Up, +, -, [, ], F
My reaction was: "How is it even possible that this is an acceptable tradeoff? So Immediately switched to Unlock mode being the default. This is my FIRST CHANGE.
Issue 2: Out of the box, there's no support for sending Ctrl+G to the app running in the terminal. Zellij traps it. So if I'm a coding agent, and I want to click Ctrl+G (to bring up my paragraph in the default editor) Frustratingly, the most common response on the Internet was "you can map it to another key".
No. I want to send Ctrl+G to the app while I'm in Unlocked mode.
So the SECOND CHANGE I made was for Ctrl+G in Unlocked mode rather, rather than just go back to Lock mode, it now sends ASCII 7 to the app and then switch to Locked mode.
So this solve this one problem. If I'm in a coding agent that takes Ctrl+G to pull up vim, all I do is press Ctrl+G to transition to Unlocked (Normal) mode, then I hit Ctrl+G again to 1) send ASCII 7 to the coding ageit, and 2) exit back to Locked mode.
Issue 3: Now that I've changed the meaning of Ctrl+G in Normal mode, how do I transition to Locked from Normal without sending ASCII 7 to the app. Well, I need another way to do it. THIRD CHANGE: Esc drops you back to Locked mode. Esc or Ctrl+[. Those are usually the same key, but not here. I had to do both.
Issue 4: the whole idea of Zellij is to use it for everything: for tabs and panes. So I made it so that when I created a new session in Termux would create or attach to an existing Zellij called "main". But on Windows, a new Terminal window always created a new Zellij session. I wasn't sure which is better. But I immediately ran into a problem. If I ssh from one computer to another, why doesn't Zellij know there's a nested session. FOURTH CHANGE: ssh by default doesn't send all the env vars. You have to configure it both on the server and client to send the ZELLIJ environment variable across ssh, using "AcceptEnv ZELLIJ". So that solved that.
Issue 5: Every Windows Terminal session would create a new Zellij session. If I want to ssh into another computer and attach to an already running instance there, I would end up with two Zellij nested instances immediately. If I did that again, now I have three. Fortunately, the system I came up with for sending ASCII 7 to the app, also works if "the app" is a nested Zellij session. However, you have to know to do that. So if I'm three deep, I have to hit Ctrl+G three times. Good luck in keeping track of how far deep you are. FIFTH CHANGE: I decided, I am not going to automatically create a zellij session with every terminal session, both in Windows and Termux. So if I am in Termux and what I want to do is ssh into another computer, I open a non-zellij session, ssh in, and then use zellij attach to attach to that running instance. Same with in Windows. But the issue now is, I am not always in Zellij. So now I have to think -- is this a terminal session I might want to attach into from another computer? or is this a session that I am using to ssh into another computer. Never both, although you can, but it's not ideal. I now have an alias for every computer in .ssh/config where computer-z is the convention of ssh'ing into the "main" zellij session on the remote computer. This also required disabling session serialization
Issue 6: It takes a lot more keystrokes than Windows Terminal to simply switch panes. It's no longer Alt array keys. It's Ctrl+G then Ctrl+P (for panes), then arraw. Or if I can remember it's Ctrl+G then Alt arrow. to switch tabs, it's Ctrl+G Ctrl+T arrow keys. It's not a simple Ctrl+Tab. When I look up best practices, I'm told a lot of Zellij power-users avoid Tabs for this reason. They use panes for everything, and if they really want more space for a particular pane, they zoom in and out. I mean, this sounds like a cope. Why do people avoid tabs? And how true is this?
How do people do this with tmux? When I research, I'm told in tmux you have the single ctrl+b key, and don't have any issues with nested session. There was no need to add that support, the way zellij had to introduce the idea of nested sessoin.
Issue 7: typing zellij everywhere just too much. So I had to setup a "z" alias on every platform that was the same as typing out zellij. Now sure why it's not set up by default under Windows.
Issue 8: Too much noise on startup. There's Help and there's Release notes. These had to be turned off by default.
Full config.kdl:
I'm still new to all this. This seems like overengineering on my part, but what's the simpler solution? But a bigger question is, HOW are the defaults usable for anyone? What apps do they use that they don't need these common Ctrl+ and Alt+ keys ?
What am I doing wrong?
All reactions