Upvote! I tried Mac Terminal, iTerm2, Kitty, Warp, etc etc, and settled with WezTerm. Easy to configure, fast, looks nice. I created a theme for it too: https://tiniri.vlad.studio/
Okay, I Like WezTerm
261–270 of 281 posts
Re: Okay, I Like WezTerm
#262Earlier quoted context omitted.
X?
X11, the "old" [0] Linux graphics server. --- [0] "old" because there's a new kid in town: wayland.
How long can we call something that’s at least 15 years old “the new kid”?
Re: Okay, I Like WezTerm
#263Earlier quoted context omitted.
> the exact same types of comments from the maintainer. Kovid really bugs me and is a reason I turned away from kitty too. I saw his character when looking up tmux issues. He's brash like Linus, but at least while Linus is calling you an idiot he'll tell you a better way to solve your problem. Kovid seems to think tmux is really about splitting panes and peoples' main draw to it isn't about persistence... Oh, and kit…
This one is the straw that broke the camels back for me: https://github.com/kovidgoyal/kitty/issues/4965 "Are you sure you want to close this window", meant to only trigger in interactive scenarios like ssh or htop, triggered on the regular shell sometimes. Not even consistently
> It breaks nothing.
OOFFF yeah, that is out of touch.Reminds me of something Linus said
> The gcc people have a BAD attitude. When the meaning of "inline" changed (from a "inline this" to "hey, it's a hint"), the gcc people never EVER said "sorry". They effectively said "screw you".
> Comparing it to the kernel is ludicrous. We care about user-space interfaces to an insane degree. We go to extreme lengths to maintain even badly designed or unintentional interfaces. Breaking user programs simply isn't acceptable. We're _not_ like the gcc developers. We know that people use old binaries for years and years, and that making a new release doesn't mean that you can just throw that out. You can trust us.
Which I think is an important lesson here. About how when you build tools, people build around you and what they have to work with. But I'm surprised this attitude is not more common, because I don't know a single person who is unfazed when changes happen that break their programs/workflow. It's reasonable for someone to be upset. And not a single person is ever like "no worries, I'll go read the commits first, no need for documentation." (Don't get me started on "my code is so clear it doesn't need documentation" people...).I think one big issue with all this is that costs are outsourced either to time or someone who isn't you, and this naively makes people believe that there is no cost (and sometimes fight to reject claims of cost. There is always a cost. There's a cost to everything). I wonder how much time and money would be saved if we recognized this. I just don't know how to motivate solving this, as it's non-obvious.
https://yarchive.net/comp/linux/gcc_vs_kernel_stability.html
Re: Okay, I Like WezTerm
#264Earlier quoted context omitted.
It's not tmux specific, i have had the same issue and for me, it was a showstopper.
I’ve yet to try WezTerm myself, but this single issue would make me switch back to Alacritty. I did some searching and it looks like the issue might be fixed in latest nightly. See https://github.com/wez/wezterm/pull/5396
Re: Okay, I Like WezTerm
#265Re: Okay, I Like WezTerm
#266I originally installed WezTerm because I switched from Kubuntu to Ubuntu and wanted some of the features of Konsole (infinite scrollback, searching the scrollback) without actually installing Konsole (I know you can install it under Gnome too, but it just felt... wrong). And yes, it instantly grew on me, although (as I can see from this article) I have barely scratched the surface of its configurability. My only comp…
Re: Okay, I Like WezTerm
#267I've been using wezterm for around a year, and sponsoring Wez on github, and it's been a fantastic terminal and he's a great developer. One of the things I love most about it, which the article mentions it is not going into, is the quick copy and other copy modes. I use them All. The. Time. C-S-Space and type the letters that appear next to the item you want to copy. One big use case I have is: mosh+tmux-like functio…
One really cool feature of the quick copy mode is that if you do the uppercase version of the letters it will automatically paste the value back into the terminal prompt.
Re: Okay, I Like WezTerm
#268Recently switched to WezTerm and I'm very happy. Was using kitty before that – loved the set up and simplicity coming from iTerm2. WezTerm is leaps and bounds better in terms of what comes out-of-the-box. My terminal config is short enough to sit all in one screen on my editor. After that, the terminal just... gets out of the way and I don't need to think about it. But the straw that broke my back with using kitty wa…
> e.g. IIRC his answer to "How do I set up tmux with kitty?" was something like "Don't, tmux is dumb" and closing it. Eventually I gave up. Heh, I switched from Kitty to Wezterm due to the exact same types of comments from the maintainer. It's his project of course, and he's a great programmer, but some humility wouldn't hurt.
Re: Okay, I Like WezTerm
#269Earlier quoted context omitted.
Is it better in typing latency though?
..you have noticable latency when you type? I'm genuinely sorry, that would infuriate me. Personally I don't notice any typing latency in wezterm. I have p10k as a zsh theme and not really any 'plugins' beyond git for the terminal and use neovim+ also pretty much just got and CoC for an editor. I don't notice any latency when typing and, while not instant, still sub 200ms startup latency.
iTerm2 was shockingly bad, for instance, at 44ms vs 6ms for Apple's default Terminal.app. That right there is a deal-killer as far as I am concerned.
Re: Okay, I Like WezTerm
#270Am I a rare one being happy with Terminal.app?