> and by having a "you don't really need it" policy for things like panes, which you can just do with tmux. They do panes, they don't have tabs. Although it lo

> and by having a "you don't really need it" policy for things like panes, which you can just do with tmux. They do panes, they don't have tabs. Although it looks like github user nrabulinski created a PoC[0]. Not having tabs is what made helix unusable for me, it just messes with my workflow too much. And you are wrong about using tmux for this. It does not work with helix because it doesn't follow a client-server model, two instances do not share information between each other (someone please correct me if I'm wrong) If you are using kakoune, you can actually use tmux (or any tiling window manager like i3wm) to recreate proper tabs since it does have a client-server model. Multiple kakoune instances can kakoune processes can share information. It's actually the most flexible system for windowing in my opinion. It allows you to do things like |kak|firefox|kak| with both kak instances sharing information. [0] https://github.com/helix-editor/helix/issues/2295#issuecomment-1499559184 https://github.com/helix-editor/helix/issues/2295#issuecomme...