Snazzy underline in README screenshot
akinsho opened this issue · comments
Hi @megalithic 😄,
I stumbled across a comment by you on the kitty terminals discussions where you posted a similar screenshot to the one you have in your README, and I've been wondering how you got the underline between what I'm guessing is your kitty tab bar and the rest of the content. Hope the line I'm referring to is clear, otherwise I can do a diagram.
I'm not willing to do any custom python for it, noticed your bar is creating using a custom script personally cba to dig into something that isn't just an option right now but was just curious how you were doing it.
Hey there @akinsho!
So, of the two screenshots from that post, the first one is just kitty (no tmux), and the second one is kitty with tmux (where tmux is "owning" the rendering of the pane border).
For reference, I'm thinking this is what you're referring to: kovidgoyal/kitty#4447 (comment)
If that is the case, you'll still need tmux :(
I've not been able to replicate all of my needs from tmux into kitty.. yet (so I'm still using tmux as the primary terminal window manager within kitty). I rely too heavily on tmux sessions for the different projects at work, and personal.
Let me know if that helps!
Thanks for all of your amazing work/efforts. It's Christmas for me anytime I discover something new in your nightly dots.
Ah, thanks for the quick reply, that makes sense I scoured kitty's docs and couldn't find a setting for something like that, would be nice but definitely not going to bother the kitty maintainer for that 😅. Was more just curious what it was.
Yeah, tbh been trying to avoid tmux because it tends to lag behind features like terminal hyperlinks or support for images in the terminal. Kitty on its own definitely isn't as good for session management solutions, though. That's definitely become a pain.
@akinsho what has your current strategy been for flipping between projects in kitty (aka "sessions"). do you just use a single kitty window with tabs for each "project" and let neovim manage additional things within the kitty tab (like running services, etc; for that project)? i really want to be able to at least just treat a kitty window as a session with individual "session" files (like startup_session) and load/unload those, i think the thing we'll never get is the ability to save a session's state in time (it's not a true multiplexer after all).
thoughts, etc? i realize koval is not very into wanting sessions/multiplexing with kitty (wezterm has something similar, but is incredibly slower than kitty, in my recent trialling of wezterm).
EDIT: i've remembered https://zellij.dev/documentation/layouts.html#session; i'm going to see what i can do with this.
Hey @megalithic so tbh I don't love the current solution I use, kitty's lack of sessions or use of startup files is not an ideal mechanism since you have to manually update the startup files and the state dump logic is kind of buggy, so you can't really persist and reload state properly. I use auto-session which can load vim sessions based on the directory you're in, so I open kitty in the correct directory in a session file and launch nvim and autosession reloads the vim session. It's not perfect, but sort of ok.
I saw zellij, but I'm wary of adding something new that adds another layer like tmux but happens to do things differently still e.g. it uses sixel for image support not kitty's image protocol so plugins like hologram.nvim which I'm keen to use at some point won't work. I've also read some issues about performance with nvim in zellij so not tried it yet.
Just got a bit curious to actually try it and immediately hit some of the sort of issues that made me give up on tmux like the fact undercurl was a nightmare to set up or some colouring issues like the underline highlights I use seem not to work properly in nvim. Basically, this sort of faff keeps me away from solutions like tmux and zellij for now
🤦 yeah; i'm trying wezterm which has multiplexing, but, it's objectively "slower" than kitty.
i really just need to be able to have term-level splits/tabs for long running processes, versus using :term and friends (toggleterm.nvim.. thanks for that!, and et al); and be able to flip to them per session/project/workspace/whatever-nomenclature.
The search continues.