Could you please add support for Svelte syntax highlighting. I tried to use HTML markup syntax but it seems to break on some tags like `{# each}` and `{#if}`. Probably because of `{#`.
I've included screenshot and code snippet that may help represent the current situation.
Docs: https://svelte.dev/docs/introduction
```html
<script>
let count = 0;
function increment() {
count += 1;
}
</script>
<button on:click={increment}>
Clicked {count}
{count === 1 ? 'time' : 'times'}
</button>
{#if count > 10}
<p>{count} is greater than 10</p>
{:else if count < 5}
<p>{count} is less than 5</p>
{:else}
<p>{count} is between 5 and 10</p>
{/if}
```
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3562
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3562(a)github.com>
When in overwrite mode, some actions still behave as in insert mode (will cause text to the right of the cursor to move right instead of staying in place and having part of it overwritten). Furthermore, other actions that are "complementary" in insert mode are not in overwrite mode.
For example, I think it would make sense that pressing backspace in overwrite mode would "leave the characters in place" the same way adding text does when in that mode, so rather than simply deleting characters, they would be replaced with spaces.
Something similar would apply to cutting and pasting (which I found already reported in #763 and #716), and deleting selected text.
This behavior would be particularly convenient when editing **tables** that use space padding for alignment (e.g. in LaTeX or reStructuredText), or for ASCII art diagrams (which I often (~~ab~~)use for block diagrams and the like), which are actually the only cases where I've found overwrite mode useful (and quite convenient, in fact). That way I could cut and paste or delete text without having to realign everything afterwards. (In particular, being able to replace a whole segment of text with spaces with a single key press rather than pressing space many times can save a lot of time in this scenario.)
The behavior of the proposed "smart" overwrite mode would be:
- Typing: overwrites text.
- Pressing tab: overwrites with tab/spaces depending on setting, OR: simply moves the cursor forward to the next tab stop without overwriting text.
- Backspace: deletes char at left, places space at right (*: except at end of line); moves cursor left.
- Delete: deletes char at right, places space at left; moves cursor right. (Not too useful since typing space will already do that, but this behavior would mirror insert-mode Delete.)
- Select+backspace: replaces selection with spaces (*); leaves cursor left of selection.
- Select+delete: replaces selection with spaces; leaves cursor *right* of selection.
- Select+cut: same effect as select+backspace.
- Paste (N characters): overwrites N characters.
- Select+paste: same effect as select+backspace followed by paste (overwrite, and if selection was longer than paste buffer, add spaces (*)).
- Ctrl+backspace/delete: word deletion with same behavior as select+backspace/delete.
- Select+typing: equivalent to select+backspace followed by typing (the current behavior is to delete the selected text AND overwrite the following text, which might be done by accident when you're too used to doing that in insert mode).
- _Alternatively, select + typing a character could replace the whole selection with that character rather than space._
- Drag and drop text: equivalent to cut+paste (TBD - maybe making this equivalent to the proposed behavior for cut+paste is not a good idea, since it is a destructive operation, and some may still want to use it e.g. to change the order of words in a sentence).
(Since this behavior would probably be unique to Geany, or at least I haven't seen it before, it should be implemented as an option, possibly disabled by default.)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3559
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3559(a)github.com>
SystemVerilog is almost identical syntax to Verilog. It could be quite easy to support SystemVerilog filetype (.sv) using same rules as Verilog which is already implemented.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3511
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3511(a)github.com>
Just now, while editing a couple of notes, I used Ctrl-Z to recover a recent delete and was surprised that it took action on the main source code I was working on.
Thinking it was a focus issue I tried a few time clicking on the scribble text before actually doing the Ctrl-Z, same result though - the Ctrl-Z acted on the main editor. Then I tried with Ctrl-Y to redo, and that too acted on the main editor. Normal cut/copy/paste actions are local to scribble though.
I submit that, if implementing the Undo and Redo functions in the scribble box is too complicated, at least disabling those functions in the main editor would be wise. After all, the scribble box could be covering the code editor's window.
Geany: 1.38
GTK+ v3.24.34 and GLib v2.74.3
Slackware64 15.0
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3558
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3558(a)github.com>
Like the documentation says, Reflow Lines/Block breaks lines **at** the long line marker if the line breaking is disabled. The problem is that the long line marker marks characters **after** the given column. This means that Reflow Lines/Block should probably reflow at `eprefs->long_line_column + 1`:
https://github.com/geany/geany/blob/b6fe9f17aeae40ab48e73481e618877e65db464…
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2078
Hi,
When opening a file which has tasks, they won't show unless you click the refresh button, I'm not sure if it is default and why?
(1.38 kubuntu 22.04, plasma 5.24)
Kind regards,
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1254
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1254(a)github.com>
Closes #1254.
This is not completely perfect but will do the trick to delay the parsing of tasks in the current document until the main loop has triggered the also delayed colourising of the current document which is necessary for parsing the tasks.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1257
-- Commit Summary --
* Addons: Delay updating of tasks list until document has been colorised
-- File Changes --
M addons/src/ao_tasks.c (45)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1257.patchhttps://github.com/geany/geany-plugins/pull/1257.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1257
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1257(a)github.com>
Without this, cppcheck will throw errors like
```
store/scptreestore.c:1990:37: warning: syntax error [syntaxError]
g_param_spec_boolean("sublevels", P_("Sublevels"),
```
This is probably caused by the P_() macro if GETTEXT_PACKAGE is not set.
Admittedly, this is the easy way to fix or better workaround it. But I guess this is OK. Otherwise, make a better PR :).
The new cppcheck error breaks the night builds on Debian Unstable (https://www.geany.org/download/nightly-builds/).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1264
-- Commit Summary --
* Scope: Define GETTEXT_PACKAGE macro for recent cppcheck versions
-- File Changes --
M scope/src/Makefile.am (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1264.patchhttps://github.com/geany/geany-plugins/pull/1264.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1264
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1264(a)github.com>
The tool to comment/uncomment Lines could be more elegant, adding all the # to the BEGINNING of lines!
And I saw a bug, it failing today, couldn't uncomment had to use REPLACE tool.
Works well to comment, but to uncomment, FAILED.
My suggestion is like this:
Nowadays | Desired
----------------------------------------------------
# code # code
#code # code
#code # code
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3554
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3554(a)github.com>
(Please let me know if I asked the same question ago.)
In Universal Ctags, people can write a parser in C language or .ctags language, which I named optlib.
The code written in optlib is translated into C language with regcomp/regexec calls while building a ctags executable. The optlib is extremely convenient for writing an indexer/parser for a small language.
In the Universal Ctags, I got a pull request for Forth language parser from @farvardin.
Initially, it is written in C. However, the parser was so simple. So we rewrote it in optlib.
After rewriting, we polished the pull request.
It is mostly ready to merge (https://github.com/universal-ctags/ctags/pull/3812).
However, there is one issue. @farvardin wanted to use the parser in Geany.
However, I heard from @farvardin that Geany doesn't support optlib-based parsers.
(https://github.com/universal-ctags/ctags/pull/3812/files#r1322116241)
Is what @farvardin wrote correct? If yes, what should we do?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3557
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3557(a)github.com>