I suggest trying this one for Zsh, over the more common one: https://github.com/zdharma-continuum/fast-syntax-highlighting

As someone else said, setting less’ jump value is helpful.

Another tool I use, mostly for the zshall manpage, is https://github.com/kristopolous/mansnip

Thanks, yes, I use nox and github actions for automated environments and testing in my own projects, and tox instead of nox when it’s someone else’s project. But for ad hoc, local and interactive multiple environments, I don’t.

If it didn’t bring something more to the table, besides speed, no one would care

I’m literally saying its speed in certain operations makes an appreciable difference in my workflows, especially when operating on tens of venvs at a time. I don’t know why you want to fight me on my own experience.

I’m not telling anyone who doesn’t want to use uv to do so. Someone asked about motivation, and I shared mine.

The convention

That’s one convention. I don’t like it, I prefer to keep my venvs elsewhere. One reason is that it makes it simpler to maintain multiple venvs for a single project, using a different Python version for each, if I ever want to. It shouldn’t matter to anyone else, as it’s my environment, not some aspect of the shared repo. If I ever needed it there for some reason, I could always ln -s $VIRTUAL_ENV .venv.

Learn pyenv

I have used pyenv. It’s fine. These days I use mise instead, which I prefer. But neither of them dictate how I create and store venvs.

Shell scripts within Python packages is depreciated

I don’t understand if what you’re referencing relates to my comment.

I have a pip-tools wrapper thing that now optionally uses uv instead. Aside from doing the pip-tools things faster, the main advantage I’ve found, and what really motivated me to support and recommend uv with it, is that uv creates new venvs MUCH faster than python’s venv module, which is really annoyingly slow for that operation.

I use my own Zsh project (zpy) to manage venvs stored like ~/.local/share/venvs/HASH-OF-PROJECT-PATH/venv, so use zpy’s vpy function to launch a script with its associated Python executable ad-hoc, or add a full path shebang to the script with zpy’s vpyshebang function.

vpy and vpyshebang in the docs

If anyone else is a Zsh fan and has any questions, I’m more than happy to answer or demo.

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.

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.

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

Ok next time I won’t use your computer.

I’ll just second the suggestion that KDE Plasma is worth a try, as it’s very adaptable once you know what you want. You don’t need to install any addons for the functionality you describe, just open the Shortcuts settings, KWin category, and have at it.

Ooh I haven’t seen this one. Anyone have a comment on this vs the KleverNotes project? I think that’s the name.

The Power and Battery widget now responds to middle-clicks and scrolls: middle-click will block or re-enable automatic sleep and screen locking, and scrolling will change the active power profile

Scrolling on the battery applet is how I adjust my brightness. Is that no longer a thing?

Have you checked the system settings page that includes compositor stuff?

I just grabbed it. The dash cam features might possibly be useful on a bike (?). But I tried and tried and couldn’t find the magic zoom level for it to show me the name of the street I’m on, got frustrated, and uninstalled.

I’m not off Google Maps either, but the closest to replacing it for me is Organic Maps, FWIW.