Note that "local" variables seem to be local for the given file and not local within a certain function so mapping them to `tm_tag_local_var_t` isn't appropriate.
At the moment autocompletion doesn't work - this is caused by
https://github.com/universal-ctags/ctags/pull/3697
which I add to this PR if it gets merged upstream.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3460
-- Commit Summary --
* autoit: use local/global variable tags
-- File Changes --
M src/tagmanager/tm_parser.c (5)
M tests/ctags/simple.au3.tags (6)
-- Patch Links --
https://github.com/geany/geany/pull/3460.patchhttps://github.com/geany/geany/pull/3460.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3460
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3460(a)github.com>
It would be great to have the ability to create multiple carets, select multiple pieces, or progressively clone a selection of a word to the next identical match creating multiple selections, not necessarily square, and then be able to type, delete, replace, etc. using the multiple carets until Esc is hit, pasting into all carets with Ctrl-V, and so on.
Here's an animated demonstration of these features: https://www.sublimetext.com/
This is Sublime Text's killer feature, and this would put Geany closer to one of the most reputed, feature rich commercial multiplatform editors, while still being free software. I believe there's support for this in Scintilla, at least to some extent.
This supersets #850.
---
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/1141
Geany's markdown syntax highlighting (without the markdown plugin) is confused, when code block is indented.
All the text after code block end is blue and ignores *all following* markdown syntax highlighting .
When code block is *not* indented, everything is ok.
--
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/2797
I get `Error opening file /<path>/index.html: No such file or directory`
<path> is the path to the directory that contains the markdown file I'm trying to load.
If I open the plugin preferences and change the template to "template.html" I get a different error:
```[general] template=/home/ventsyvelev/.config/geany/plugins/markdown/markdown.conf [view] position=0 font_name=Serif code_font_name=Mono font_point_size=12 code_font_point_size=12 bg_color=#ffffff fg_color=#000000```
Geany 1.38
Ubuntu 22
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1247
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1247(a)github.com>
I'm using Geany 1.30.1 on Windows 7.
After happily editing a file over some time, suddenly Geany refuses to save it with this error message:
I know that Windows sometimes grabs a lock on a file when I'm just looking at it with another tool, but I am pretty sure that the only way I'm operating on this file since the last bootup of my machine, is by editing it in Geany. Still, for the safe side, I run the [Handle](https://technet.microsoft.com/en-us/sysinternals/bb896653) utility to see whether someone has a handle to either the file or the directory where the file is in - nothing. I also used Geany's "File/Properties" to check, whether maybe the file secretly became readonly; this is also not the case. Finally I turned on the gio_unsafe_save_backup and tried again, but same result. Note that it is a local file, so there can't be network issues involved either.
Then I tried "save as" with "rename", to store it under a new name in the same directory. This was refused with the same error message. I could see that the file got renamed, but still had the old content. This is weird: If the cause would be a directory lock, the rename should ALSO have failed.
Needless to say that it is not a disk space problem either.
I resolved the problem temporarily by using the following strategy:
1. Using "Save as" to save it to a completely different directory.
2. Copying the file back (on the command line)
3. Closing the Buffer in Geany
4. Reopening it
I then checked with my remaining open files in Geany. Modifying the buffer and saving, caused the same error with two of the files, while it worked fine with two others. One of the two where the error occured too, belonged to a different directory, while all the others - including those which could be saved - belonged to the same directory as the file where the problem occured initially.
I don't see yet in what respect the two files which did not have the problem, differed significantly from the two files where the problem occured.
Closing Geany, starting it, and I can continue editing like normal, but my feeling is that it will be only a question of time until the problem occurs again. Is there anything I can do to help the Geany developers to nail down the cause of this strange problem?
--
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/1500
Since distros are now not defining `python` and python 2 is dead, should be changed to `python3`, see also discussion on #2223
--
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/2615