UVviewsoft forums

Wiki should clarify expectations for custom snippet panel data. (1) User must create new sub-folder, data/clips (2) Each list lives in a sub-sub-folder, data/clips/mysnipsname (3) mysnipsname appears on the snippets panel drop-down menu (4) Actual snippet file is data/clips/mysnipsname/List.txt Snip...

For anyone else interested, you need a stanza in user.json for files not otherwise matched, with caret in the lexer name as follows: "detect": { "shellcheckrc": "Config-RC ^", "clifmrc": "Config-RC ^", "miller.rc": "Config-RC ^" }...

Cancel stops the whole spellcheck. Ignore All continues the spellcheck while ignoring the specified word anywhere in the document. Simple Ignore continues the spellcheck but only ignores the word once; if it happens again, the same correction prompt will too.

An installer question: why KDL does not show in packages.ini file. All other lexers do, just not KDL. I made an install .zip as follows: $ ls -1 lexer.KDL KDL.cuda-lexmap KDL.lcf default-config.kdl install.inf $ 7z a -tzip ./lexer.KDL.zip ./lexer.KDL The .zip I then opened in Cud to install. What sh...

KDL Specification KDL is a small, pleasant document language with XML-like node semantics ... to be used both as a serialization format and a configuration language, much like JSON, YAML, or XML. all numbers can have underscores to help readability grammar and expected semantics are well-defined an...

Ignore All just needs an in-memory short list of items for a single run. When checking ends, the list disappears. So running spellcheck on the same document stops on the same words again. That's my expectation for Ignore All. There is no ever-growing list. Some spell checkers do add an option beyond...

CudaText 1.232.1.0, linux-x86_64-qt6, fpc 3.2.3 on Wayland Other Cud dialogs work fine. Spellcheck will not allow me to close/cancel. Ignore does not work, either. I must kill the entire Cud process and relaunch. Also, spellcheck lacks a button for "Ignore All" which most spellcheckers have.

DT_RUNPATH in the ELF would be cleaner than a wrapper script. The key here is to use the DT_RUNPATH, which can be embedded into the binary you are creating. You can link it so that it points to the same directory, as you wanted. I run many other wrapper scripts. Finding their execution directory is...

Problem seems gone now. Current version info:

CudaText 1.232.0.4, linux-x86_64-qt6, fpc 3.2.3
Void Linux Qt6 6.10.2_1

All I now see on exit is

If I understand the question, it asks what is wrong requiring users to download and install the Qt Pascal lib to the sys dir. * The user must have admin privs; not likely in multiuser (and/or thin client) corporate settings. * Some Linux distros don't package Qt Pascal libraries. Void only packages ...