Rules for the “compost waste” doesn’t apply for making the compost that you use as a fertilizer. Maybe that’s why we call it “wet”. It’s basically anything that is biodegradable. But not everything that is biodegradable is ok for fertilizing…
Nice, this may be the path to kill AI made for money and not for helping people
Great! Anyway, still far from what you can get with tmux or kitty with just a line in the config…
The thing is that the qdbus command only works from inside the terminal, because it needs to know the correct konsole instance. Anyway, I moved to alacritty because the konsole support for ANSI codes is terrible…
Qdbus command:
qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION runCommand "!!"
Remember, it’s Microsoft… it can’t be normal
I guess there are many benefits if subprocesses (usually written in C) are replaced with functions (usually wrapping C code). That way, you could run an entire OS scripts via Python, with sensible performance improvements.
BUT
Does this tool replace shell commands with python functions? Or does it just call many times subprocesses.run()?
How often do you use images inside a terminal?
Why having a Gpu-accelarated terminal? The computational power used by the graphical rendering of a terminal is minimal…
How often do you use the image display within a terminal?
Kitty is not “minimal” at all, it’s full of superfluous features… I used it for many years and I loved it, but I wouldn’t say it’s “minimal”
What are the benefits if Gpu-accelarated terminals? From my understanding, that’s a really negligible difference.
Once upon a time, I loved Xfce Terminal. It use light and complete for the use-case I had. Then I wanted something that looked nicer with vin. So I started looking for an alternative.
I used alacrity for a long time (4 years). Then, I found kitty provided some nice stuffs that simplified the workflow for remote servers thanks to special ssh commands and session tabs. I used kitty for about 2-3 years. One thing I missed was that it’s hard to integrate with other software because it implementa all it’s crazy “kitty protocols” and pretend to use them even if they’re compleynon-standard.
Recently, some misterious bug appeared and made it impossible to use. I switched to wezterm. I liked it could be configured in Lua, so it feels more coherent with my neovim configs. I just missed the mappings for switching terminal and send “!!<enter>” (i.e. execute last command). The special commands for copying custom configs on any ssh server was also missing, but it’s easy to make a script for that. I haven’t experienced too much with integrating it with other tools, but I suspect it’s not better than kitty in this.
I gave a chance to konsole last week. I just asked myself why we (neovim users) all look for Gpu-accelarated stuffs. The improvement in performance is negligible actually. However, konsole is super-well integrated in the OS, with a scratch terminal (yakuake), file managers (dolphin, konqueror), text editors (Kate), and even simple browsers (konqueror). It provides all the features of wezterm. I still lack a key map for sending “!!<enter>” to a specific terminal, though. But I think the integration it offers is superior to that niche feature (that can be paired within neovim, btw).
Whenever you delete something, nvim copies it in a register. Which register it puts in depends on the command. Honestly, I’ve always been confused from all these registers for two reasons:
So, I just use my OS clipboard (KDE Plasma has a clipboard manager built-in) and osc52 plugin (but support for osc52 will is built-in in nightly). If you really want to use registers, you could try to copy all of them into only one and use that.
Probably the second is the reason