The current highlighting of dark blue (as opposed to black when not selected) is very difficult for me to see I imagine there's something I can edit, but there's nothing in the documentation and playing with brace_good in filetypescommon didn't appear to achieve much
Using geany 1241
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/885
Steps to reproduce:
1. create a new file using the tree browser
2. give the file a name
3. Try editing the file
4. Try saving.
OS: Windows 10
doing a file->new file via geany works fine.
[original issue](https://github.com/geany/geany/issues/1842)
--
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-plugins/issues/737
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
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
Related to https://github.com/geany/geany/issues/2185 and https://github.com/geany/geany/issues/2180,
I know that _"The colour scheme set for the editor widget where the code is, is again totally independent of any terminals, it's only used to style syntax highlighting of code in the documents notebook"_, but it is creating high-contract and not easy on the eyes.
This is what i get out of the box:
I.e., the editor widget is light-on-dark, while the side bar and the message windows are both dark-on-light. Such high-contract between the windows will make the eyes fatigue easily.
Please consider having a unified colour scheme on all three windows to easy the eyes. Thanks.
--
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/2196
It is nice that the environment variables `LANG` & `LANGUAGE` can be used to override the system locale. But I think it would be even more user friendly to have a configuration option under preferences that would override both system & environment specified language.
It seems there are quite a few users who think there is no locale support or just aren't sure how to change languages. While "I don't have time to read the docs" generally isn't a good excuse, being able to configure the language from within the UI will lead to less confusion, especially for non-Posix system users.
If I get time, I may see if I can add the option myself & create a pull/merge request.
Some related threads:
- #1757
- #2831
- #2619
- #2545 <- I think this one is an especially good reason for a configuration option
- #1910
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3255
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3255(a)github.com>
When using the autocomplete feature in Geany on MacOSX 10.14 Mojave in fullscreen mode, the autocomplete opens in a separate desktop (fullscreen) rather than as a small popup in the editor.
--
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-osx/issues/18
Fixed deprecated gtk3 calls. The PR unfortunately includes an ugly list of all the GTK stockitems as I did not see a different solution.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/865
-- Commit Summary --
* commander: fixed deprecated gtk3 calls
-- File Changes --
M build/commander.m4 (1)
M commander/src/Makefile.am (7)
M commander/src/commander-plugin.c (22)
M utils/src/Makefile.am (3)
A utils/src/gp_gtkcompat.c (222)
M utils/src/gp_gtkcompat.h (5)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/865.patchhttps://github.com/geany/geany-plugins/pull/865.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-plugins/pull/865