Closed #3869 as resolved.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3869
You are receiving this because you are subscribed to this thread.
Message ID:
Thanks! I wasn't aware of `foo.__doc__`, that's neat.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3869#discussioncomment-9390637
You are receiving this because you are subscribed to this thread.
Message ID:
Version of Geany, what version of GTK?
AFAICT you are operating totally within the GTK open file dialog, it does the
munging of typed input with open directory and Geany can only read the results.
So we can't control that behaviour.
--
Reply to this email directly or view it on GitHub:
https:
@b4n commented on this pull request.
> +static TMParserMapGroup group_LDSCRIPT[] = {
+};
BTW, it's not merely a warning, but I had an error. However, it's a [GCC
extension](https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html)
--
Reply to this email directly or view it on GitHub:
https://git
@techee pushed 1 commit.
acb4678486110d90dd46eb6dea336f5907cafb14 Map freepascal namespaces and add a
unit test for them
--
View it on GitHub:
https://github.com/geany/geany/pull/3859/files/de9ea30900a3c602e89b39666b22029abc9a839a..acb4678486110d90dd46eb6dea336f5907cafb14
You are receiving thi
>>Can do that. Should it be part of this PR or a separate one after this one is
>>merged?
>Whichever you prefer. I'd have said this one given it'll introduce yet another
>set of changes that are probably best diffed from current master, but I don't
>really mind either way in practice, so if it'
@techee commented on this pull request.
> @@ -557,6 +562,7 @@ static TMParserMapEntry map_FREEBASIC[] = {
{'t', tm_tag_struct_t}, // type
{'v', tm_tag_variable_t}, // variable
{'g', tm_tag_externvar_t}, // enum
+ {'n', tm_tag_undef_t}, // namespace
Yes,
@techee commented on this pull request.
> +static TMParserMapGroup group_LDSCRIPT[] = {
+};
I added the dummy one in the latest commit.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3859#discussion_r1597244631
You are receiving this because you are
@techee pushed 2 commits.
0b52e79c93942d115d94a2df6015a1c704fb0ad6 Add dummy TMParserMapGroup for
ldscript to avoid warnings
de9ea30900a3c602e89b39666b22029abc9a839a Map freepascal namespaces and add a
unit test for them
--
View it on GitHub:
https://github.com/geany/geany/pull/3859/files/d5
> Can do that. Should it be part of this PR or a separate one after this one is
> merged?
Whichever you prefer. I'd have said this one given it'll introduce yet another
set of changes that are probably best diffed from current master, but I don't
really mind either way in practice, so if it's
@b4n commented on this pull request.
> @@ -557,6 +562,7 @@ static TMParserMapEntry map_FREEBASIC[] = {
{'t', tm_tag_struct_t}, // type
{'v', tm_tag_variable_t}, // variable
{'g', tm_tag_externvar_t}, // enum
+ {'n', tm_tag_undef_t}, // namespace
No clue
@b4n commented on this pull request.
On tests/ctags/matlab_test.m.tags:
that's a bit sad… I'll see if I can get those fixed upstream (it's easy enough
to patch actually -- yet, I don't have a clue about matlab :grin: )
--
Reply to this email directly or view it on GitHub:
https://github.com/
@b4n commented on this pull request.
> +static TMParserMapGroup group_LDSCRIPT[] = {
+};
This gives me:
```
src/tagmanager/tm_parser.c:1165:44: warning: ISO C forbids empty initializer
braces [-Wpedantic]
1165 | static TMParserMapGroup group_LDSCRIPT[] = {
|
@frlan @b4n @eht16 The major things are "finished" from my perspective. If I
missed something that needs to be done regarding geany-plugins integration,
please let me know.
The word "finished" above means the plugin works but soft-depends on some
things which are not in Geany yet, it's:
* http
As nobody seemed horrified by this, I merged it so we can get CI working again.
If there's any issue with this, we can always fix or revert.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1346#issuecomment-2105222322
You are receiving this beca
Merged #1346 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1346#event-12773739990
You are receiving this because you are subscribed to this thread.
Message ID:
@techee pushed 8 commits.
66e82da94f5b3a718a383f2bee80a7ede3137a50 Make sure menu gets updated whhen
closing the last document
ced8d1717dbc6db861f3824125897774c885d70b Fix semantic token flickering when
LSP server sends incorrect delta value
17b29d78efe1a41309130ab5f2da24265bb86554 Some small
Merged #3759 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3759#event-12773542349
You are receiving this because you are subscribed to this thread.
Message ID:
I don't think there is a way to get two different comment colors without
modifying the lexer code and Geany's styling.
However, the "pythonic" way is using triple-quoted strings (or well, I guess
any string will do, but usually documentation is longer than that) as the first
statement in e.g. a
Hi! I've grown really attached to being able to set different colors for C++
comments (//) and document comments (///), and I'm looking to replicate that
for python code (maybe ## or something). Glancing through LexPython, I don't
see anything about document comments like I do in LexCPP. Is a
On Windows, when I open a file, press Ctrl-L, and enter a relative path using
forward slashes (`/`) instead of Windows's official backslash path separator
(`\`), Geany doesn't understand that and produces a confusing error message.
Specifically, if I go to `C:\Users\cousteau\` and enter `AAA/BBB
@eht16 @b4n This is squashed and ready to go.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3759#issuecomment-2104724781
You are receiving this because you are subscribed to this thread.
Message ID:
> Do we need to adjust anything for the Meson build system?
No, this is in data/meson.build:
`install_subdir('filedefs', install_dir: cdata.get('GEANY_DATA_DIR'),
exclude_files: 'filetypes.python.in')`
I think this is done now.
--
Reply to this email directly or view it on GitHub:
https:/
@andy5995 pushed 1 commit.
63474cc70c093122c09c2c1706d63065d4f1305a Add Dockerfile filedef
--
View it on GitHub:
https://github.com/geany/geany/pull/3757/files/f684daf36e9b31a91fdd115b4026f8de35412188..63474cc70c093122c09c2c1706d63065d4f1305a
You are receiving this because you are subscribed to
@andy5995 pushed 1 commit.
f684daf36e9b31a91fdd115b4026f8de35412188 Update
data/filedefs/filetypes.Dockerfile.conf
--
View it on GitHub:
https://github.com/geany/geany/pull/3757/files/b21ed0baba253cb40c6a2e239c1812c833c16a66..f684daf36e9b31a91fdd115b4026f8de35412188
You are receiving this beca
@b4n Thanks for having a look at the javascript parser.
> we should probabmy use a newer snapshot (some parser changes, e.g. related to
> class vs. object vs. variable are gonna lead to additional test result
> changes, which are admittedly better in the newer version, and I'm not sure
> it's w
BTW:
> Sync our ctags to the latest tag version (p6.1.20240421.0)
Tags `p*` are NOT releases, but probably pre-versions, or even nightly
snapshots. Releases are `v*`.
It's probably fine, but noteworthy :slightly_smiling_face:
--
Reply to this email directly or view it on GitHub:
https://gith
Regarding JS:
> The only unexpected thing is the behavior of the javascript parser - this is
> from the javascript commit message:
>
> There are lots of differences because of
>
> [universal-ctags/ctags@6d85089](https://github.com/universal-ctags/ctags/commit/6d85089456ed215ce6b6a673744ae42ccc5
28 matches
Mail list logo
