Hello,
I was looking forward to change the entire windows to dark, but the theme only changed the color of the editor.
Is it possible to set the whole programm to dark on windows?
Regards
Andi
--
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/2225
There is enough room to show everything in the picture but some of it is clipped of to the left.
> Windows 7.
> Geany 2.0.
> "Pryce"
> (bygget Oct 19 2023 eller efter)
> Med afviklingsbibliotekerne GTK+ v3.24.39 og GLib v2.78.0
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3630
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3630(a)github.com>
The language is based on Go. I created `filetypes.Foo.conf` and set `Foo=*.foo;` in `filetype_extensions.conf`. Foo is indeed appeared on `Set Filetype` but syntax highlighting for the language Foo is simply not work. When you opened a file name with extension `.foo`, it's treated as `None` and even if you manually set the language to be `Foo` via `Set Filetype`, there is absolutely no syntax highlighting. Strangely enough, if I set the language to `Go` via `Set Filetype` then I have syntax highlighting. If I edit `filetype_extensions.conf` to add `.foo` to the list of extensions of `Go` source file, then `.foo` files will be treated as `Go` and have syntax highlighting, too. Of course, this syntax highlighting is for Go and the keywords specific to the language `Foo` is not highlighted. I have read and followed the FAQ so I want to know what exactly did I do wrong or if I should make a bug report.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3663
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3663(a)github.com>
With Geany, there has never been a clear recent files button like in other text editors. On previous versions, everything is put on `geany.conf`, and one has to manually edit this file to delete the recent files list. Now on Geany 2.0, the recent files are no longer stored in `geany.conf`, and I can't find where they are stored either. Like in all previous versions, deleting `recently-used.xbel` has no effect.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3662
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3662(a)github.com>
Hello, I followed the FAQ guideline **How to change the GTK theme?** on Windows 10.
To make it work on my machine, I had to change the location of file `settings.ini` from `c:\Users/<YOUR_USERNAME>\AppData\Local\gtk-3.0\` to `c:\Users/<YOUR_USERNAME>\AppData\Roaming\gtk-3.0\` . I would assume that this change is also required to Windows 11.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3529#discussioncomment-7400178
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3529/comments/7400178(a)github.com>
I think we should switch to using dedicated lexers where these lexers are available in Lexilla. This allows better highlighting, where for instance for JSON we can color the keys differently from the values and also provide optional comment support.
The exact highlighting mapping is open for discussion - I used keys in dicts to be colored like keys in conf files but it can be changed to something different.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3647
-- Commit Summary --
* Convert JSON to builtin filetype and use Scintilla JSON lexer for it
-- File Changes --
M data/Makefile.am (2)
D data/filedefs/filetypes.JSON.conf (17)
A data/filedefs/filetypes.json (59)
M data/filetype_extensions.conf (2)
M meson.build (1)
M scintilla/Makefile.am (1)
A scintilla/lexilla/lexers/LexJSON.cxx (506)
M scintilla/lexilla/src/Lexilla.cxx (1)
M scintilla/scintilla_changes.patch (1)
M src/editor.c (5)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (14)
M src/highlightingmappings.h (27)
-- Patch Links --
https://github.com/geany/geany/pull/3647.patchhttps://github.com/geany/geany/pull/3647.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3647
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3647(a)github.com>
CSS nesting is becoming native these days. no more SCSS/Less/SASS files needed.
unfortunately the text color is broken when you do nesting with geany.
is it possible to get this issue fixed?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3523
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3523(a)github.com>
GCC 8 introduced `-Wsizeof-pointer-div` which is enabled by `-Wall` and
warns for sizeof divisions that look like they would compute the size
of a static array but are called on something on which this doesn't
work (e.g. a pointer as LHS). This is quite reasonable and useful, but
it fails to detect the case where the computation is guarded against
being called on problematic values, like our HL_N_ENTRIES() macro that
accepts NULLs but won't use the sizeof computation result then.
Work around this by implementing HL_N_ENTRIES() macro in a way that
cannot trigger such a warning yet yield the same result.
Example warning:
```
../../src/highlighting.c: In function ‘highlighting_init_styles’:
/usr/include/glib-2.0/glib/gmacros.h:351:42: warning: division ‘sizeof (HLKeyword * {aka struct <anonymous> *}) / sizeof (HLKeyword {aka struct <anonymous>})’ does not compute the number of array elements [-Wsizeof-pointer-div]
#define G_N_ELEMENTS(arr) (sizeof (arr) / sizeof ((arr)[0]))
^
../../src/highlightingmappings.h:74:48: note: in expansion of macro ‘G_N_ELEMENTS’
#define HL_N_ENTRIES(array) ((array != NULL) ? G_N_ELEMENTS(array) : 0)
^~~~~~~~~~~~
../../src/highlighting.c:966:5: note: in expansion of macro ‘HL_N_ENTRIES’
HL_N_ENTRIES(highlighting_keywords_##LANG_NAME)); \
^~~~~~~~~~~~
../../src/highlighting.c:1011:3: note: in expansion of macro ‘init_styleset_case’
init_styleset_case(CONF);
^~~~~~~~~~~~~~~~~~
```
---
Another solution could be reporting a bug to GCC for it to detect our use case and avoid the warning then, but that might or might not be much meaningful, and won't fix the issue on currently affected GCC versions anyway.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2398
-- Commit Summary --
* Rewrite HL_N_ENTRIES macro to avoid a GCC8 false positive warning
-- File Changes --
M src/highlightingmappings.h (12)
-- Patch Links --
https://github.com/geany/geany/pull/2398.patchhttps://github.com/geany/geany/pull/2398.diff
--
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/pull/2398