Currently there are 30+ "programming languages", 20+ "scripting languages", 9 "markup languages" and some "Misc" languages.
The first two categories are so big the menu (Document->Set Filetype->) won't fit on screen (at least with a laptop).
Especially the first should be broken up. This is a call for suggestions of how that should be done.
Otherwise I will make a pull request breaking them up in a reasonable but somewhat arbitary way, rough popularity measure and degree of support. :grin:
--
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/2087
Hi !
on the attached (sorry, I cannot attach PHP file) PHP file, at line 1583,
I have the following code (started before by /*, and finishing after by */) :
` * V...|.......................Jour courant..................................>|<...................................Lendemain.................................................>|`
When I write the "<" character, on this line 1583, Geany closes.
In /var/log/syslog there is :
Mar 30 12:58:29 PRINCIPAL kernel: [ 2151.269486] geany[12005]: segfault at 0 ip 00007f1b1a5cf9de sp 00007ffe7d451aa8 error 4 in libc-2.23.so[7f1b1a531000+1bf000]
Mar 30 13:05:45 PRINCIPAL kernel: [ 2586.680237] geany[13373]: segfault at 0 ip 00007fd0b0b929de sp 00007fffe225d0b8 error 4 in libc-2.23.so[7fd0b0af4000+1bf000]
Mar 30 13:08:16 PRINCIPAL kernel: [ 2737.718143] geany[13586]: segfault at 0 ip 00007fd4ff5ae9de sp 00007ffcc369f738 error 4 in libc-2.23.so[7fd4ff510000+1bf000]
and more ...
On this line 1583, " * V...|.......................Jour courant.....".
I removed the first "<", before the words "Jour courant", just after the first "|" character, and I cannot write it back, because Geany closes each time I trie.
Original was : "V...|**<**.......................Jour courant....."."
If I clic before the second "<" (do not look for the first one, it does not exist anymore), before the word "Lendemain", nothing happen.
If I clic after the second "<" (do not look for the first one, it does not exist anymore), Geany closes.
If I clic after the last ">" Geany does not close.
Let me know if you want my PHP file.
Thank you for looking about it ...
Nils
--
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/1455
Add `ui_notebook_setup()` function which supports notebook tabs already present and any pages added over time. The tab label widget must either support events or be a label, in which case it will be reparented in an event box.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3469
-- Commit Summary --
* Enable mouse wheel tab switching for sidebar and message window
-- File Changes --
M src/notebook.c (34)
M src/ui_utils.c (67)
M src/ui_utils.h (3)
-- Patch Links --
https://github.com/geany/geany/pull/3469.patchhttps://github.com/geany/geany/pull/3469.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3469
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3469(a)github.com>
Since PR #3859 (2d1b3d5), specifically since baaed02, which merges [ctags#3471](universal-ctags/ctags#3471) and [#3473](universal-ctags/ctags#3473) (among others), Geany's tagmanager adds a "module" tag for *instances* of a module (in addition to the "instance" tag for the instance itself, which Geany didn't show in the tree view until #4039).
Example code:
```verilog
module outer_module (input D, output Q);
inner_module inst (D, Q);
endmodule
```
| Before baaed02: | After baaed02: |
|-----------------|----------------|
|  |  |
For an analogy, this is like having the C code `struct inner_struct foo;` tag *both* `inner_struct` and `foo` as struct/variable declarations (but it's *not* defining a struct type, just using it).
This seems to be caused by ctags now creating a *reference tag* whenever it declares an instance, referencing the corresponding module, and Geany erroneously(?) interpreting that reference tag as a normal tag. But I don't know enough about ctags to know what's going on for sure, nor what's the proper way to handle it (other than refraining from creating a reference tag).
Is there a way to fix this? It looks like #3102 might be related to this kind of issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4072
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4072(a)github.com>
Fixes #4072 (re: `my_module inst (d, q);` creating tags for both the instance `inst` and the module `my_module`).
The unit tests have been updated accordingly.
Also includes a minor amendment to #4039 to fix the tag grouping for SystemVerilog so that enum objects are put in the same group as struct/union objects, which makes more sense than putting them in the same group as typedefs (which are types, not objects).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4075
-- Commit Summary --
* Change icon of SystemVerilog struct/enum objects
* tagmanager: Verilog: don't tag module of instances
-- File Changes --
M src/tagmanager/tm_parser.c (7)
M tests/ctags/sysverilog.sv (4)
M tests/ctags/sysverilog.sv.tags (4)
-- Patch Links --
https://github.com/geany/geany/pull/4075.patchhttps://github.com/geany/geany/pull/4075.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4075
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4075(a)github.com>
In https://github.com/geany/geany/pull/4013 I forgot to add a unit test for meson.
However, when I tried to add it now (naming the test file `meson.build`), I got the following in `meson.build.log`:
```
Unknown filetype extension for "/tmp/tmp.XJrc9S8Suo/test.build.tags".
```
The reason is that unlike other filetypes, the Meson configuration in `filetype_extensions.conf` doesn't start with `*.` but instead the whole filename is used:
```
Meson=meson.build;meson.options;meson_options.txt;
```
The unit test runner creates test files starting with `test`, followed by the filetype extension and this doesn't match what's in `filetype_extensions.conf`.
What should we do about it?
A simple (but ugly) way would be to add some `*.meson_unittest` extension to `filetype_extensions.conf` which we would use for the unit test but which wouldn't be used in real life.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4074
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4074(a)github.com>
@techee thanks for the issues cleanup 😃
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/452#issuecomment-2496175990
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/452/2496175990(a)github.com>
Would it be possible to have an option either in the preferences or in the build menu to execute the lint command periodically ?
---
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/1032