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.
CLI flow: run command, print output below
TUI flow: navigate and interact with a layout that updates in place
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.
For anyone else wondering:
Navidrome is an open source web-based music collection server and streamer. It gives you freedom to listen to your music collection from any browser or mobile device. It’s like your personal Spotify!
Congrats on all the labor you saved.
If you think folks here are uniquely unreasonable you could try lemmy.world/c/selfhosted .
On the off chance that you truly don’t understand:
The nice thing to do would be to accept the feedback and add a short description. It’s confusing to others why you are staunchly opposed to performing that small courtesy, and instead jump to never posting here again.
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?
Well FWIW CodeWars has plenty of Factor katas, and I try to gather related resources at https://programming.dev/c/concatenative
I’m trying to keep up with the Perl Weekly Challenges, but with Factor, and am posting some Factor solutions to Exercism’s 48in24 series.
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 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.