121–130 of 331 posts
Does Alacritty still require you to copy terminfo to remote servers in order for backspace to work? I loved Alacritty, but copying terminfo every time gets old pretty quickly.
short-term: Add the terminfo file to your vm provisioning tooling: ansible, terraform, etc long-term: Maintain an alacritty package in your distro of choice so the terminfo is automatically included
Earlier quoted context omitted.
Lots of things alacritty cannot do- 1) If you scale certain fonts using fontconfig, alacritty would ignore that. 2) No emoji colors, no ligatures (and thus no flags), also emoji size has problems ... and not to mention it's one of the slowest (yes! contrary to what they blowhard they response time to keys is very large) terminals out there. List is endless, termite had its place, but there is no doubt that there is s…
> ... and not to mention it's one of the slowest (yes! contrary to what they blowhard they response time to keys is very large) terminals out there. This is intriguing to me. You're not the first I've seen complaining about this, so there must be something to it. But in my case, on a fairly low-end machine, what I type shows up instantaneously[0] on the screen, even when the CPU is busy compiling. I'm running an i5-6…
"Obsoleted" is a word? I've only heard "made obsolete" before, or replaced/discontinued/deprecated.
Earlier quoted context omitted.
Did they ever implement that solution?
It doesn't look like it, I'm sure they would be open to patches to help out there.
Also things like
>adding only hooks for you means that all the other terminals get no benefit.
Makes me quite concerned since these hooks weren't just for termite, as evidenced by tilix showing interest in this patch set.
>Implementing this in VTE would mean ruling out having any flexibility in the terminal using the library. [...] an implementation inside VTE won't satisfy the use case.
I think that the termite developer explained very clearly why the approach suggested by the VTE maintainer wouldn't actually solve the problem they were having, and the maintainer responded with a simple "wontfix" and no more discussion.
This is kind of the thing we're talking about. One project said they needed this, another project said they'd also appreciate this feature, and instead of discussing how to make this work, setting clear requirements and the like, it took 2 years to respond to the first patch submission and then the issue was just randomly closed in the middle of a discussion.
I have no beef with gtk/gnome and the like, but I find it really funny when developers use such colorful language. Still, as a heavy terminal user, I fail to understand what's the big deal with the choice of terminal. I have used only xterm for more than 20 years (with a short stint with gnome-terminal, and I didn't find any relevant difference). It starts instantaneously and doesn't make any fuss while it's running.…
Earlier quoted context omitted.
Electron uses Gtk and Games should use SDL2. They will support CSD, which is work, but it will happen. You could also say that SSD would mean that Mutter needs to do extra work just to satisfy an application designer ego. Btw: I'm a GNOME user who is against SSD.
The issue is that Electron and SDL will fix this 10 years later, old apps will still not work. Same issue with tray icons, GNOME is expecting cross platform apps will use their shirty design OR their users will use only new GNOME apps. >You could also say that SSD would mean that Mutter needs to do extra work just to satisfy an application designer ego Is better that say all the 10 WM implement SSD (maybe as a fallba…
The SSD in GNOME still works for X11 apps. For now the only path for old apps that need SSD is to continue using the X11 backend in Electron and SDL.
For GNOME, SSD was never in the plan with wayland, so this is not breaking compatibility with apps there because it was never supported.
Earlier quoted context omitted.
time agnostic rule #1: people are people
And people form tribes, and tribal allegiance becomes very important to them. In this case, both tribes (GNOME and Wayland) have a vision of the perfect way for software to work. They have each captured enough weak allegiance/users to prove to themselves that they are right. Therefore, the other side is wrong.
I used to use termite, but switched to kitty for ... reasons I can't remember now. Does alacritty support ligatures yet? I've been using kitty because it does, but then I have issues with tmux in kitty ... I know, I want my cake and eat it
I switched from kitty to wezterm. I don't have an official benchmark like the below [1], but low latency is an explicit goal of the project and it seems on par with kitty.
I have no beef with gtk/gnome and the like, but I find it really funny when developers use such colorful language. Still, as a heavy terminal user, I fail to understand what's the big deal with the choice of terminal. I have used only xterm for more than 20 years (with a short stint with gnome-terminal, and I didn't find any relevant difference). It starts instantaneously and doesn't make any fuss while it's running.…