Live data from Hacker News

Okay, I Like WezTerm

alexplescan.com

231–240 of 281 posts

Re: Okay, I Like WezTerm

#231

Earlier quoted context omitted.

Not out of the box, but I use Hammerspoon to implement a global hotkey to show WezTerm: https://github.com/jaminthorns/environment/blob/a609e81f3f41... I don't have a keybinding to hide, but you could easily achieve that by inspecting the active window with `hs.window.focusedWindow()`/`hs.window.frontmostWindow()` and making the behavior conditional based on the application: https://www.hammerspoon.org/docs/hs.window…

I was unfamiliar with Hammerspoon; to those like me, https://www.hammerspoon.org/

I use it to add window snapping to macos:

https://gist.github.com/spartanatreyu/850788a0441e1c5565668a...

Re: Okay, I Like WezTerm

#233
post #173

I really _want_ to like WezTerm but the font rendering just looks bad compared to Alacritty. I understand that this is a very personal feeling and plenty of people like the WezTerm way better... but not me. The author is not interested in trying to fix this issue, which is totally fine, as they point out font rendering is very subjective, but I'm also not willing to use a terminal that looks worse, even though I like…

I'd probably try a few fonts first just to see if it's an issue with rendering, or if the font itself is problematic since sometimes it's the font's fault itself when it's being used in a different environment. (font internals are a crazy rabbit hole to dive down)

Besides, if you're trying another terminal it's also a great excuse to try other things too!

I'm a fan of tools like these where you compare a series of option pairs (in this case font pairs) in succession until it spits out your most preferred option: https://www.codingfont.com/

Re: Okay, I Like WezTerm

#234
It seems great but it's unusable to me as it does not support any port forwarding and my connections always go through a few jump boxes.

The built in multiplexing is like magic.

Re: Okay, I Like WezTerm

#235

Just tried it. I liked how easy it was to set up colours/fonts etc, using the config file. But I hit a snag. On macOS, it's standard that in any text window, to select everything for copying, you hit Command-a. But Command-a in wezterm just printed an "a" character. What? I spent a while looking in the docs and issues, but couldn't figure out how to Select All. I don't think I should have to justify it, but in case s…

Select all seems a bit risky in a terminal because it could contain way more information than you'd expect.

e.g. I want to `cat` a file to make sure i've got the right one, but I accidentally cat a full 1gb sql backup rather than the tiny 50 line script I was expecting. Sometime later, I try to select all, copy, switch application, paste for some reason but now I'm stuck waiting for 1gb to copy over

Personally I'm a bit more cautious about copying from a terminal.

Either way if that's what you really want to do, you can check the repo to see how other people scripted it into wezterm:

https://github.com/wez/wezterm/discussions/2026

Re: Okay, I Like WezTerm

#236
post #229

Earlier quoted context omitted.

OK so you are not lying, you are just wrong. Now that you have reduced the scope of your personal attack from he doesn't like settings to he doesn't agree with me about one thing, perhaps you should exercise your new found honesty a bit more and link to the issue where he refused to implement bold as bright and gave his reasons, which are perfectly sensible, namely that having that option means that the developers of…

Look: my issue is that the kitty developer clearly thinks of himself as "God's gift to terminals". I pointed at one specific issue that I think is "telling" of an attitude of "I know better than everyone else", but I am not at all relying on that issue. I just went through and started looking at recently closed issues on GitHub. I got through four before I found an example of what I think is the problem, and while th…

Let's discuss the parts you left out in your carefully constructed attempts at character assassination.

1) kitty has a template for issue reporting that the person that reported that issue didn't use, which means it isn't a carefully constructed report.

2) The issue is probably with kkp.el. I don't know about you, but I don't expect maintainers of open source projects to debug all issues in their own projects let alone unrelated ones. Kovid went out of his way to tell the OP exactly how to provide useful debug information. And he did so within a few minutes of the issue being opened.

3) The part you complain about is him saying he has zero interest in debugging kkp.el and emacs. Which is perfectly reasonable, again, why should he have an interest in it. He provided the OP with the means to give him information that he would be interested in debugging instead.

4) He then gets told that the OP would rather use some other terminal rather than provide the debug information he was asked for. Do you have any conception of how rude it is to go to some projects issue tracker and then state you are going to use a competitors product.

5) You tried again to insert an unjustified swipe at Kovid, with "the keyboard protocol he insists everyone get on board with". In reality that keyboard protocol is completely optional, an no one has to use it. The fact that everyone does actually use it, is testament to its being light years ahead of any of the alternatives and represents weeks of hard work on the part of Kovid to finally bring sanity to this corner of the terminal ecosystem. An effort he made for the good of the community. And an effort that has succeeded, since pretty much all modern/maintained terminal software support the protocol as it is clearly superior to the alternatives.

6) You were at best mistaken in making your claim that he doesnt like settings, but given you clearly have an agenda against someone who has done nothing to you other than provide the world free software, I think the default assumption is malice not incompetence on your part.

And yes by all means dont use kitty, I have a strong feeling that Kovid, who has been providing software used by millions of people for decades has reached a point in his life where he recognizes that some users cost way more than others. He is likely very happy that you and people like you give his work a miss.

A position I greatly sympathise with. People that report issues to open source projects need to remember they are asking for help, it behoves them to put in the maximum effort they can to reduce the burden of the free help they are NOT entitled too.

Re: Okay, I Like WezTerm

#237

So many comments from people coming from iTerm. What do you have in your WezTerm config to make it more like iTerm?

As a fellow iterm2 refuge, here's my config:

https://gist.github.com/spartanatreyu/fe6d045c3113f27acaa509...

I added back the familiar option/cmd + arrow key navigation and cmd + click hyperlink behaviour.

There's also some tweaking to make it more similar to iterm's default behaviours (e.g. don't hide the mouse when you start typing).

And finally some personal visual tweaks which you can throw out and replace with your own.

Re: Okay, I Like WezTerm

#238
post #205

In my experience Wez has been shockingly responsive to GitHub issues and usually fixes things (if they’re actually wrong) within a day or two. I’ve only found one or two minor quibbles involving modifier keys over SSH and overall the functionality is basically perfect for my needs. Plus it’s nice and fast. (Former avid Alacritty user but needed better modifier support for remote emacs.)

I didn't have as positive experience. Granted I commented on a closed issue. In any case it was closed as "won't do" and my comment was ignored. I didn't feel like opening a new issue for the same that was already dismissed. https://github.com/wez/wezterm/issues/4706

The way you phrase that makes it sound like you had a negative experience, was that your intention? For all we know he didn't even see it, there's thousands of issues and PRs and it's not like this is his full time job, so missing a message sounds like a pretty expected and neutral interaction to me. There's a reason they used the word "shockingly" to describe his response time, it's because it's amazing that Wez can respond to even a fraction of all the messages as quickly as he does.

Also in case you wanted to bump up the priority of that bug, he does have github sponsors enabled.

Re: Okay, I Like WezTerm

#239
post #228

Recently 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…

While I see nothing particularly egregious about Kitty's maintainer, other than being a bit of a dick, it's not really the job of a maintainer to be your pal. Except, when I started using WezTerm at the start of this year... omg, this guy is absolutely fantastic. I have read scores of his posts and he's struck the perfect tone in every single one. Love this guy, really, he's awesome.

For those of us wishing to see, what links are you referring to ?

Re: Okay, I Like WezTerm

#240

Recently 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.

  > 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 kitty phones home

If you want drama:

tmux:

  - https://github.com/kovidgoyal/kitty/issues/391
Phone Home:

  - https://github.com/kovidgoyal/kitty/pull/3544
  - https://github.com/kovidgoyal/kitty/issues/2481
On a side note: I really don't trust devs who reply to issues and close them. I get wanting to remove the issue from the task list, but just set up an action for stale issues (which has an added advantage of pinging the user who may have just lost the message). Otherwise let the user close because they might have follow-up questions. It's just disrespectful and always a red flag. I know lots of users are dumb (I literally just got an issue on a research project with someone asking how they fine tune our model...), but noobs are wizards in training. You don't have to be nice, but don't be mean either. Plus, you'll just piss off people who could end up helping you. And if you don't want help, I expect your project to decay when you get bored. Definitely not what I want from a terminal
Post reply on HN