If you choose to give Fedora a try, I recommend Ultramarine, which has more set up from the start, including their “Terrs” repository with more updated packages.

Ah yes you can tell by the post title:

best linux terminal emulator

Oh, is that #4948?

For me: Wezterm. It does pretty much everything. I don’t think Alacritty/Kitty etc. offer anything over it for my usage, and the developer is a pleasure to engage with.

Second place is Konsole – it does a lot, is easy to configure, and obviously integrates nicely with KDE apps.

Honorable mention is Extraterm, which has been working on cool features for a long time, and is now Qt based.

Just note that the comment was inaccurate, in that their weird encryption is indeed open source at least.

mpv+uosc is my jam these days.

No, that’s not used by Zsh.

Glad you have it working. This may also work:

_stfu () {
  shift words
  (( CURRENT-=1 ))
  _normal -P
}
compdef _stfu stfu

FWIW I’ve read an Arch dev complain that folks using any 3rd party installer are not in fact “running Arch” and should not claim to be doing so.

Huh? Is this relevant, or some kind of bot spam?

So far, this isn’t much of anything.

Telegram already closes public channels reported for copyright violations.

Some excerpts from this post:

Compared to other platforms, we do not see the seriousness of Telegram to cooperate.

. . .

In May 2023, progress appeared to be going in the wrong direction. Telegram was reportedly refusing to cooperate with the Ministry of Communications and Digital on the basis it did not wish to participate in any form of politically-related censorship.

. . .

With no obviously public comment from Telegram on the matter, it’s hard to say how the social platform views its end of what appears to be an informal agreement.

Telegram will be acutely aware, however, that whatever it gives, others will demand too. That may ultimately limit Telegram’s response, whatever it may be, whenever it arrives – if it even arrives at all.

The window shade problem is keeping me from Wayland. AFAIU there’s currently no commitment to ever fix it on Wayland, it’s only a maybe.

For anyone interested, it’s being tracked here.

So . . . not relevant to my comment?

By default you can use left and right bracket keys [] to adjust speed, and it should do adjustments to make the pitch sound the same.

To adjust the pitch alone, you can have something like this in your input.conf, customized as you like:

ALT+p af toggle @rb
ALT+UP af-command rb multiply-pitch 1.25
ALT+DOWN af-command rb multiply-pitch 0.8
ALT+LEFT af-command rb set-pitch 1.0

I haven’t looked at this in a long time. If you always need this there’s likely a conf option to always enable the “rubber band” (@rb) filter. And maybe other commands than multiply that would be better.

EDIT: Sorry, I don’t have this quite right. Maybe someone can correct me.

OK, I see some differences between your two screenshots, but what’s the relevance to my comment?

As described at https://docs.kde.org/stable5/en/kwin/kcontrol/windowbehaviour/index.html#titlebar-actions

Shade

Causes the window to be reduced to simply the titlebar.

I don’t know what I should be noticing there. I can’t see any text for the tool buttons along the left edge of the window.

Anyone notice non-obvious Wayland road blocks?

I think the last thing keeping me on X11 is window shade.

I have trouble with both, but more experience with GIMP. I can’t stand all the little tool buttons with no text. I want the name of each tool always visible on its button.

I have the same problem with Inkscape.

It’s more about replacing typed text than using shortcuts, but there’s espanso.