After a recent update, kate seems to exec a copy of itself, presumably with some parameter which prevents an endless recursion, and then exits. Presumably this was intended to help users who run kate with a command in a command window and don't want the command window blocked until the kate window is closed. However this breaks things like git commit and sudoedit, since these wait for kate to exit and then check to see if the file was changed. Now that the original kate process exits immediately, the file hasn't changed. How can I stop kate from exec'ing itself? The only way that I can think of is to move the real /usr/bin/kate to something like /usr/bin/realkate, and create a tiny shell script at /usr/bin/kate which does something like /usr/bin/realkate -b $*, but this will get overwritten on the next upgrade. I tried alias kate='kate -b' in my .bashrc, but this only works if I run kate from the command line, not when git commit or sudoedit runs it. Possibly this could be fixed in katerc, but there doesn't seem to be any documentation for that.

I would like to insert the current date into an open Kate text document while editing it by using a shortcut key combination. I see several such options for Atom, but I don't find anything for Kate.

Notepad++ has the nice feature of keeping the entire session between opening and closing the program, even with files not yet saved anywhere. How can I enable the same functionality for Kate?

So I'm toying around with scad files. When I open them on Kate I get this error: [10:55:26  LSP Client Warning] Failed to find server binary: openscad-lsp Please check your PATH for the binary See also https://github.com/Leathong/openscad-LSP for installation or details I got to the github link, and there I see that to install `openscad-lsp I need to have cargo installed. I install this, with build-essential as well and I try to install openscad-lsp` and I get the long output below that to me reads like "there was a problem" and doesn't give any concrete information (as in, there is no specific package that failed to be installed). My knowledge about rust (which I understand is the programming/scripting language) is 0, so I'm left helpless here. Any of you has an idea how I can fix this? yotam@poorThing:~$ cargo install openscad-lsp Updating crates.io index Downloaded openscad-lsp v1.3.1 Downloaded 1 crate (60.3 KB) in 1.37s Installing openscad-lsp v1.3.1 Updating crates.io index Locking 101 packages to latest compatible versions Adding bitflags v1.3.2 (latest: v2.9.1) Adding getrandom v0.2.16 (latest: v0.3.3) Adding lsp-types v0.94.1 (latest: v0.97.0) Adding wasi v0.11.0+wasi-snapshot-preview1 (latest: v0.14.2+wasi-0.2.4) Adding windows-targets v0.52.6 (latest: v0.53.0) Adding windows_aarch64_gnullvm v0.52.6 (latest: v0.53.0) Adding windows_aarch64_msvc v0.52.6 (latest: v0.53.0) Adding windows_i686_gnu v0.52.6 (latest: v0.53.0) Adding windows_i686_gnullvm v0.52.6 (latest: v0.53.0) Adding windows_i686_msvc v0.52.6 (latest: v0.53.0) Adding windows_x86_64_gnu v0.52.6 (latest: v0.53.0) Adding windows_x86_64_gnullvm v0.52.6 (latest: v0.53.0) Adding windows_x86_64_msvc v0.52.6 (latest: v0.53.0) Downloaded anstyle-query v1.1.2 Downloaded tree-sitter-language v0.1.5 Downloaded equivalent v1.0.2 Downloaded zerofrom v0.1.6 Downloaded stable_deref_trait v1.2.0 Downloaded strsim v0.11.1 Downloaded bitflags v1.3.2 Downloaded anstyle v1.0.10 Downloaded anstyle-parse v0.2.6 Downloaded dirs v6.0.0 Downloaded zerofrom-derive v0.1.6 Downloaded clap_lex v0.7.4 Downloaded dirs-sys v0.5.0 Downloaded serde_repr v0.1.20 Downloaded form_urlencoded v1.2.1 Downloaded shlex v1.3.0 Downloaded colorchoice v1.0.3 Downloaded zerovec-derive v0.11.1 Downloaded idna_adapter v1.2.1 Downloaded streaming-iterator v0.1.9 Downloaded utf8parse v0.2.2 Downloaded potential_utf v0.1.2 Downloaded lazy_static v1.5.0 Downloaded itoa v1.0.15 Downloaded option-ext v0.2.0 Downloaded percent-encoding v2.3.1 Downloaded linked-hash-map v0.5.6 Downloaded heck v0.5.0 Downloaded lsp-server v0.7.8 Downloaded yoke-derive v0.8.0 Downloaded utf8_iter v1.0.4 Downloaded is_terminal_polyfill v1.70.1 Downloaded synstructure v0.13.2 Downloaded anstream v0.6.18 Downloaded quote v1.0.40 Downloaded yoke v0.8.0 Downloaded displaydoc v0.2.5 Downloaded shellexpand v3.1.1 Downloaded tree-sitter-openscad-ng v0.6.0 Downloaded litemap v0.8.0 Downloaded writeable v0.6.1 Downloaded tinystr v0.8.1 Downloaded directories v6.0.0 Downloaded smallvec v1.15.0 Downloaded crossbeam-utils v0.8.21 Downloaded clap_derive v4.5.32 Downloaded log v0.4.27 Downloaded icu_normalizer v2.0.0 Downloaded unicode-ident v1.0.18 Downloaded serde_derive v1.0.219 Downloaded ryu v1.0.20 Downloaded proc-macro2 v1.0.95 Downloaded clap v4.5.38 Downloaded url v2.5.4 Downloaded icu_properties v2.0.1 Downloaded memchr v2.7.4 Downloaded zerotrie v0.2.2 Downloaded indexmap v2.9.0 Downloaded zerovec v0.11.2 Downloaded idna v1.0.3 Downloaded hashbrown v0.15.3 Downloaded tree-sitter v0.25.4 Downloaded aho-corasick v1.1.3 Downloaded serde_json v1.0.140 Downloaded icu_properties_data v2.0.1 Downloaded clap_builder v4.5.38 Downloaded syn v2.0.101 Downloaded regex v1.11.1 Downloaded regex-syntax v0.8.5 Downloaded crossbeam-channel v0.5.15 Downloaded icu_locale_core v2.0.0 Downloaded icu_collections v2.0.0 Downloaded serde v1.0.219 Downloaded cc v1.2.24 Downloaded lsp-types v0.94.1 Downloaded icu_provider v2.0.0 Downloaded icu_normalizer_data v2.0.0 Downloaded regex-automata v0.4.9 Downloaded tree-sitter-traversal2 v0.2.1 Downloaded libc v0.2.172 Downloaded 80 crates (5.8 MB) in 1.56s error: failed to compile openscad-lsp v1.3.1, intermediate artifacts can be found at /tmp/cargo-install9QolOI. To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path. Caused by: rustc 1.80.1 is not supported by the following packages: icu_collections@2.0.0 requires rustc 1.82 icu_locale_core@2.0.0 requires rustc 1.82 icu_normalizer@2.0.0 requires rustc 1.82 icu_normalizer_data@2.0.0 requires rustc 1.82 icu_normalizer_data@2.0.0 requires rustc 1.82 icu_normalizer_data@2.0.0 requires rustc 1.82 icu_properties@2.0.1 requires rustc 1.82 icu_properties_data@2.0.1 requires rustc 1.82 icu_properties_data@2.0.1 requires rustc 1.82 icu_properties_data@2.0.1 requires rustc 1.82 icu_provider@2.0.0 requires rustc 1.82 idna_adapter@1.2.1 requires rustc 1.82 litemap@0.8.0 requires rustc 1.82 potential_utf@0.1.2 requires rustc 1.81 tinystr@0.8.1 requires rustc 1.81 writeable@0.6.1 requires rustc 1.81 yoke@0.8.0 requires rustc 1.81 zerofrom@0.1.6 requires rustc 1.81 zerotrie@0.2.2 requires rustc 1.82 zerovec@0.11.2 requires rustc 1.82 Try re-running cargo install with --locked yotam@poorThing:~$ cargo install --locked openscad-lsp

I misclicked when correcting a spelling error when using Kate and added the misspelled word to my dictionary, how do I go about removing it?

I use Kate for coding and note-taking. Sometimes it crashes - often when I've got a lot open. Unsaved 'real' documents (eg, ones backed by files, that have been saved at some point) usually have a backup/autosave type recovery file, that more-or-less works. Unfortunately, I've gotten in the habit of using untitled buffers (eg, pressing Ctrln in Kate) to store temporary notes. Kate just crashed and I lost half a dozen of these. Does Kate store backups for 'new' files anywhere? I checked, ~/.kde/share/apps/kate/ and didn't see anything obvious ...

kate-editor 3.8.5
KDE 4.8.5
Ubuntu 12.04 (Don't remember if Kubuntu or Ubuntu + KDE, in case that makes a difference)

Is it possible to show a Table of Content (TOC) in Kate for text documents such as txt files or files without filetype? Maybe it's possible with some setting that I haven't found or with some plugin (maybe there's a plugin for it that isn't available in the options you can select under Settings->Configure Kate). If so, please describe how one can enable a TOC. It would be useful to organize notes, todos and other texts into separate sections. Clicking on a section in the TOC would make you jump to it. The text has the syntax "Normal" (this should work with default settings when simply opening a txt file and *not* require you to select the Markdown syntax for example). For example, if you then write "####This is is a header" somewhere in the txt document, it would display just like all the other text in the file (no color-highlighting or necessarily headers that have a larger font-size) but still make this show up as a section in the TOC which is shown in the panel on the left beneath (not instead) the "Documents" tab if you have that view open there. I created **an issue requesting this feature here ** but haven't received a reply yet and it may already be possible with some plugin/option/separate tool/Kate-fork/workaround. I have Kate v20.12.2 in Debian11/KDE.

The problem: Edit many files in one single kate process. 1) FILE_LIST is a variable which contains a list of path FILE_LIST="$MAIN_PATH1 $MAIN_PATH2 ... $MAIN_PATH3" 2) DST_DIR is the destination folder in /tmp for the symlink of the files to edit. 3) A for - loop feed a find request 4) The find request uses xargs to build the link files; one uses print0/-0 because some filename contains space for A_DIR in $LIST_PATH ; do find "$A_DIR" -type f ! -name "*.*~" ! -path "*000_ERRORS*" ! -path "*KEEP*" -print0 | xargs -0 -I@ bash -c " ln -s \"@\" \"$DST_DIR/${@##*/}\"" done 5) Up to here everything is alright. All symlinks are in one folder. 6) Then another finds request feed kate at once. find "$WORK_PATH" -type l -print0 | xargs -0 -I{} xdg-su -c "kate {} " That does not work as expected. Files are only accessible one by one. That is not the goal. But in another terminal if I run manually second find request command : find /tmp/000_PGM_001 -type l -print0 | xargs -L 1 -0 -I{} bash -c "kate '{}'" I may obtain all the files in the same instance. I may manually repeat the command until I get all the files in one kate install.

When running Kate snippets, I do not know how to use the date variable in a snippet. When I am trying to create a personal snippet where the current date can be inserted such as #### Snippet #A-1

Kate snippets returns

instead of the following desired output #A-2 below. #### Snippet A-2

Screenshots " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">

Kate requires omnisharp to be added to the PATH. I'm not sure which configuration file needs to be modified to include omnisharp in Kate's PATH. Only when I start Kate through a console which contains omnisharp in its PATH it works. However, I don't think it's a good solution to simply call exec bash with a PATH export on the .desktop file, it looks like a botched job. It's the LSP Client, more specifically, the one complaining. Is there an rc file for the LSP Client, perhaps? I'm completely lost.

I am writing Python scripts and using a shebang line to specify the location of the Python interpreter in my system.: #!/usr/bin/env python So, in principle, my system should be able to run the script correctly, using the right interpreter. This should also be true for other scripting languages, such as shell scripts, provided that I give the right path to the interpreter in the shebang line. What I do now to run it is to open a terminal, and type: python /path/to/my/script.py but I am looking for a more efficient way. So, my question is: is there a command, within Kate, which allows me to run the current file as a script? I am trying the command "Run Current Document", under the "Tools" menu, I get a message asking if I really want to run it, but then nothing happens.

How can I switch the text direction in kate and kwrite editors? I have English & Persian layouts and want to read the Persian text as right to left but I can't seem to be able to switch the text direction.

**Is there a plugin/xml file or any way to extend the capability of Kate to highlight Markdown?** I am really comfortable with Kate (using version 15.12.3) and I use it to write logs. For plain-text readibility I use Markdown, since it is a Markup language that (in my opinion) doesn't need compilation to look pretty. However, Markdown-syntax-highlighting helps! Luckily, Kate supports some basic syntax highlighting, like highlighting headers (when using #), italic (using * or _), indents, inline code (using backticks) and lists (using - or 1. / 2. / ...). However, some interesting features are missing, e.g. like bold text (using ** or __) highlighting headers in underline style: h1: my header ============= h2: my sub header ----------------- and most importantly for me the syntax highlighting *without indent*, using backticks: a syntax block in markdown can be started with indents (4 spaces): code() but also with 3 backticks:

code()
    highlight.me{}

only in the backtick syntax we can use a notation that some tools convert to language specific highlighting

public class HelloWorld {
       public static void main(String[] args) {
         System.out.println("Hello, World");
       }
    }

Since I use this in plain-text markdown to write code that I can copy and paste without indents, I'd love if Kate would be able to recognize this as code. So are there syntax highlighting extensions for enhanced Markdown support in Markdown?

Goal: If I have two c files, A and B, and I don't plan to compile B into an object file, but rather include it directly in A, can clangd (or any other LSP service that works with Kate) show me only the errors in B that arise from compiling A directly? In other words, A is the "entry file" for compilation errors in B. Please bare with the me on the snubbing of standard include practices. Simplest example: Let's say this is main.c: #include #include "test.c" int main() { test(); return 0; } and test.c is: void test() { printf("Hello world!\n"); } If I were to compile test.c into an object file, I would get the following errors: > clang -c test.c -o test test.c:2:5: warning: implicitly declaring library function 'printf' with type 'int (const char *, ...)' [-Wimplicit-function-declaration] printf("Hello world!\n"); ^ test.c:2:5: note: include the header or explicitly provide a declaration for 'printf' Kate's LSP Server will of course pick up on this and highlight "printf" in test.c for fixing. Now, let's say I have no plan to compile test.c separately. I only want to run: clang main.c Which will include test.c AFTER stdio is included in main.c, and thus compile without errors. Therefore the printf warning the LSP server shows me - while good for demonstrating test.c's compile-ability in isolation - will be irrelevant to how I ultimately compile the program. In this scenario, can I tell the LSP server to ONLY compile main.c (treat main.c as the "entry point" of compilation), and then have kate only highlight the errors in test.c that would arise from compiling main.c? In the concrete example, this would lead to NO errors being highlighted in test.c. I might also be snubbing the definition of "entry point", since it usually refers to runtime entry point, not certain compilation choices, but if there's a name for what I'm asking for, I'm not sure what it is.

Entering arbitrary Unicode characters according to their code point is simple e.g. in Gedit (press Ctrl+Shift+u, enter the (hex) code point, press enter). One can even use the terminal. For example, executing echo -e '\u2603' produces a snowman, ☃. Here 2603 is, again, the code point in hex. KDE's Kate, however, currently (as of Version 19.12.3) does not seem to have similar functionality. True, one can use Gedit or the terminal to produce the symbol, which can then be copied and pasted into Kate. But this is awkward. At the same time, Kate does support plugins and scripts. Unfortunately, I have not been able to find any tutorials for how to write them (except [this one](https://kate-editor.org/2004/01/06/writing-a-kate-plugin/) , from 2004, which is so terse that it hardly qualifies as a tutorial, and anyway is probably obsolete). It would be nice if the plugin were to implement the same functionality as Gedit, since its method of entering Unicode characters seems to be a pretty standard way to do it. But it doesn't have to be done that way. Maybe the Kate plugin (or Kate script?) could work like this: upon pressing a keyboard shortcut, a standard KDE pop-up dialog appears, prompting you to enter the Unicode hex code. Once the code is entered, we press 'enter', and the corresponding Unicode character is inserted at the current location of the cursor in Kate. No doubt there are other methods of entering that would make sense. The key is that the Unicode character must be entered at the current location of the cursor. Is something like this possible to do in Kate using plugins (or scripts)? How difficult might it be to write the appropriate plugin (or script)? How would one go about writing and installing such a plugin?

I am running Kubuntu 20.04 with Kate editor pre-installed through Discover software center. Recently I've noticed, that the version of Kate I have is not the latest version available. Latest available version of Kate editor in Discover software center is version **19.12.3** The latest available version on kate-editor.org is kate-**22.12.2** Tried running

apt update && apt upgrade

This did not upgrade my Kate to the newest version, and I think I know, why:

apt info kate

Returns "Version: 4:**19.12.3**-0ubuntu1" (the same outdated version I already have installed) I suspect that this may be connected to the fact I am using an LTS version of Kubuntu, but I am not sure about that. My question is: can I upgrade Kate editor to the latest available version using

or

-get

? This feels like a trivial task, but I can't wrap my head around it

In Kate editor I have been using meld to compare files and find differences. I was happily using the contextual menu that you get when you have two files open and you right-click on the tab of the non active document, as explained in this answer . However, after moving to the Flatpak version of Kate, this doesn't work anymore... I still have meld installed, and the "compare with active document" menu appears, when I right-click on the tab. However, I get a message: "The selected program can not be started. Maybe is not installed". I guess this has to do with the "sandboxing" of Flatpak. I have messed with some of the settings for Kate in "Flatseal" (the sandboxing manager for Flatpak), in particular granting to Kate access to all system resources, but I can't get meld back. Maybe I need to export an environment variable? but which one?

On my system, one click of the scroll wheel on the mouse moves 3 lines. Kate seems to be scrolling based on 3 *file*-lines. Whereas something like Notepad++ in Windows scrolls 3 *visible*-lines (which might end up only being half of a single file-line, for example). This means that for really long lines with word wrap enabled, scrolling can be very jarring and not smooth, as half the screen could go by in one tick of the wheel. Can Kate be configured to scroll by visible lines instead of file lines? Or is this actually a system setting somewhere, unrelated to Kate?

I'm working with CSV files, and I'm using vim because of the rainbow CSV plugin that makes the editing easier: http://www.vim.org/scripts/script.php?script_id=4598 But I prefer using Kate, and as I did not find anything on the Internet like it. I'm trying to do a syntax highlight myself, but I'm not familiar with the file format and do not know if it is possible to do something similar to rainbow CSV on Kate. I was trying to do an itemData for each word position, but it did not work as I expected.

I want each word to have a different colour. Text example: word0,word1,word2,word3,word4,...,wordN If anyone could help me, I would appreciate it.

I'm running Standard Debian Wheezy with KDE 4.8.4 and Kate 3.8.4.

The Kate text editor's syntax highlighting files are located in:

/usr/share/kde4/apps/katepart/syntax

If I run

kde4-config --prefix

this gives

/usr

and $KDEDIR is empty. This results in that only XML files in the upper direcory are used for highlighting.

In several other forums, I saw that it should work to create a folder "syntax" in

~/.kde/share/apps/katepart/ If I put syntax-highlighting files there on my system, they appear to be ignored. How can someone change/set the directory for the syntax-highlighting files used by *Kate* to an arbitrary directory?