Delete trailing spaces on saving a file? Fine, #KDEKate. But don't delete trailing spaces when I use a #NoBreakSpace.

I write text in the editor and then paste it in sites, and two of the sites I do that on have been updated to delete blank lines. The only way to preserve them is to put a #HardSpace on the line that's supposed to be blank.

If I unthinkingly hit Ctrl+S to save the file after I've methodically inserted a bunch of non-breaking spaces, they vanish. That's annoying.

I really wish you were better, #Kate. Please give me the abilities I had in The Semware Editor on Windows. Abilities you lack, least annoying of the Linux text editors I've tried.

#kdeKate supports git, projects and language servers. Apart from telemetry doesn't seem so different from #vscode ...

#programming

Installed more apps and such in the fresh #LinuxMint. (I swap M.2 SSDs and do a clean install with each release.) Had to do "sudo apt install libxcb-cursor0" before installing #Calibre. Don't recall if I had to do that last time; added it to my lengthy setup notes.

Also had to install nfs-utils via command line to talk to my NAS in NFS mode and not just Samba. NFS is faster, even if it does have the occasional permission error when overwriting a file. But that's the only two times I had to use the #commandline. (Well, okay, I did a "sudo nemo" to install my eXtra Typographical Characters file, and make the folders for NFS.)

One annoying change is to Virtual Magnifying Glass. Used to be that I got the magnification window when I clicked the VMG icon. Now I get a menu and have to click the first option or hit 'S' to Show. I then get the mag window, but the menu doesn't close. (Well, it does close first usage in a session; it doesn't close in subsequent use.) No hotkey to get the viewer without going through the menu. I'll have to look into other screen magnifiers.

On how emojis are displayed in #KDEKate, since it's the same font, maybe the issue is a new emoji pack, or rules on how some are displayed in different places?

Got up early to pick up new #eyeglasses, so decided to install new #LinuxMint. The actual OS is fine, but of course various programs in the Software Manager are changed.

For example, #KDEKate jumped from 21.12.3 to 23.8.5, and while colors can be set for the text editing area, menu bar and status bar don't seem to do #DarkMode any more, not even via Zoom Text toggle, which forced it in the version I used previously.

And though I'm using the same Deja Vu Sans Mono v2.37 font as before, it appears differently. Pics show the same line of icons in the old and new Kate versions. While the line of hearts is mostly the same (the gray heart no longer appears smaller), the colors of the circles are mostly gone, and that of the squares are entirely gone. Other characters appear different, as well. Weird.

Also I frequently open up Kate to just like, jot notes down and then realized as far as a GUI text editor goes it appears to have everything I need? No more, no less? Plus a very nicely done UI?

I think I'm gonna give it a bigger shot tomorrow (it has VI mode which weeeeeeeee)

#KDE #kdeKate #Kate

Una más de #KDE #Kate.
https://milangaelectronica.com.ar/posts/133-hugo-y-kate-ii-config-general/
#kdekate

@greenpete
At the level I use the operating systems, #LinuxMint and #LMDE are functionally identical. Things no doubt differ at a deep level, but the deepest thing I do is paste the update command for #Calibre into the terminal.

Programs in the Software Managers have different versions, however. I use #CopyQ #ClipboardManager and #KDEKate #TextEditor. Linux Mint has CopyQ 6.0.1 and Kate 21.12.3, while LMDE has 6.4.0 and 22.12.3. Both have little annoyances in LMDE.

Well, there’ll be more settings that I forgot to change in the next day or two, but the basic setup works. #Gigolo, #InputRemapper, #CopyQ, #VMG, #KDEKate, #DoubleCommander, and #Vivaldi all installed and configured. Weird new quirk in Kate text editor, where the last display line on screen sometimes gets the bottom part of a line of text that scrolled by stuck to it. And the white line I use as a highlight doesn’t override or fix it, though flipping to another tab and back does. (And I can’t do a screenshot, because that redraws the screen and fixes it.) Same version of Kate.

@saluki     I’ve never had any trouble using #DoubleCommander in #AppImage form. I use it as my daily #FileManager. It’s always open on #workspace two. I’ve tried the same with my #TextEditor, #KDEKate (my always-open #desktop one app), since the AppImage version is newer than the #LinuxMint repo version, but that didn’t work out.

The repository version of the editor has a chrome quirk. I run apps in #DarkMode, but repo Kate starts with one tab dark, but other tabs (as well as menu bar and status bar) light. I found that defining system hotkeys for “increase text size” and “decrease text size” and then doing an inc with Alt+Super+] (and dec with Alt+Super+[) fixes everything to uniform dark mode.

The AppImage version handles chrome well, but spellcheck doesn’t work. In #Flatpak Kate, chrome and spellcheck work, but sessions don’t. So I go with the version where everything works, with a nudge.

#softwareNitpick #KDEKate

Guys... don't make "cut" the first option in the menu. It's not even alphabetical; "copy" should come first, then "cut". "Copy" is harmless and should be the default accidental-action.

That way I won't be forever accidentally deleting bits of code (and sometimes not noticing until later, when I have no memory of where I pasted it... if I actually got around to pasting it... and it's long gone from the undo buffer).