You are not logged in.
I was thinking that when I install kate via `sudo pacman -S kate`, there is both kate and kwrite.
I wonder why there are 2 editors and I deleted kate, as I only need basic editing, kwrite is enough.
But then I found that kwrite was deleted too.
https://archlinux.org/packages/extra/x86_64/kate/
Then I know that there is only kate package, no kwrite.
https://kate-editor.org/post/2022/2022- … te-kwrite/
As this website says, kwrite and kate will remain 2 applications.
I think it is not proper to throw away the kwrite package and install both of them, that's not Simplicity.
For people who just need kwrite, kate is a redundant package that cannot be uninstalled.
Last edited by Firestar (2022-08-24 12:21:39)
Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams, because that is a universal interface.
Offline
kate used to be a split package that build both kate & kwrite .
You could take the latest version of the kate PKGBUILD before the change and adjust that to only build kwrite .
use a new pkgname (f.e. kwrite-nokate) and pacman will not replace it with kate .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
kate and kwrite are both just wrappers around katepart - I doubt that it would make anything simpler or significantly leaner to split them.
Especially not since they both inevitably drag half of KDE onto your system.
Also nobody "needs" either, there're leaner (shameless plug) alternatives ![]()
Offline
As I understand it kwrite and kate now have a shared code base, whereas kwrite previously used a more significant chunk of distinct code. So kwrite is now explicitly created as kate with stuff stripped out. I assume this explains the change in packaging policy. (I still have separate packages because I've not got the updates yet.)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
You could also just NoExtract= the kate.desktop file/binary in /usr/bin which "logically" leads to this same end result.
Offline
I tried the suggestion from Seth, as I was anyways planning to continue moving away from K utilities (e.g., replaced Okular with Atril)
Sadly, the sqriptor editor misses some things I use in kwrite, most importantly the block editing mode (partial line vertical selection).
I also stumbled into a bug: when trying to toggle comments on a multiple-line selection, only the first one is affected.
It seems that I still need kwrite for programming/simple text editing until I can spend more time finding a replacement.
Notepadqq looked promising, but does not do the block editing mode either.
Following Lone_Wolf's suggestion, I was able to compose a kwrite-only PKGBUILD based on the old 22.04.3 version.
Just for the record, I wiped out the following before building: kactivities okular knewstuff libksysguard kdevelop okteta konsole kuserfeedback kdoctools.
I did not have plasma-framework to begin with, it built successfully without it.
The result is OK with me, considering that I still use Krusader on XFCE - many of the dependencies do not exist solely for the sake of the text editor.
At least, I was able to exclude what gives me the "bloat feel" (kactivities, knewstuff, kuserfeedback).
Offline
Sadly, the sqriptor editor misses some things I use in kwrite, most importantly the block editing mode
Nope. The feature is kinda hidden in scite and there's no toggle, but the "Help" menu has an explicit entry because of that ;-)
Edit, ftr.:
I only found out about that when going through the scite shortcuts for an entirely different reason and the help points that out because you'll find this by random chance or never.
Last edited by seth (2022-10-23 11:16:32)
Offline
Thanks for pointing that out!
I tried it out. Deleting a vertically-selected chunk of text works fine, but inserting (either pasting or typing) does not.
The vertical selection is lost, and the action is applied only to the last of the selected rows.
Perhaps this comes from the fact that the mode is transient (no toggling).
Very interesting editor all the same, I will keep it in mind.
Offline
The scintilla blockposting behavior is even more peculiar (should maybe extend the help, I had to look that up as well)
You can block post but only block copies.
Ie. if you cut/copy text w/ a block selection, you can then insert it as block.
If you copy a text in normal selection, it gets pasted in normal mode.
Offline