This patch adds basic Prolog support (only scintilla laxer, there's no
ctags parser). I used swi-prolog for the compiler and run commands which
I believe is the most commonly used prolog implementation. I used the
keywords from here:
https://github.com/mxw/vim-prolog/blob/master/syntax/prolog.vim
I only used Prolog at school many years ago but it's an interesting language and I believe Geany should support it (which is why #3086 resonated in my head).
Fixes #3086
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3171
-- Commit Summary --
* Add Prolog filetype support
-- File Changes --
M data/Makefile.am (1)
A data/filedefs/filetypes.prolog (73)
M data/filetype_extensions.conf (1)
M meson.build (1)
M scintilla/Makefile.am (1)
A scintilla/lexilla/lexers/LexVisualProlog.cxx (516)
M scintilla/lexilla/src/Lexilla.cxx (1)
M scintilla/scintilla_changes.patch (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (17)
M src/highlightingmappings.h (35)
-- Patch Links --
https://github.com/geany/geany/pull/3171.patchhttps://github.com/geany/geany/pull/3171.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3171
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3171(a)github.com>
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
Geany's markdown syntax highlighting (without the markdown plugin) is confused, when image link without title is used:
```
```
All the following text is highlighted bold (same as the link itself).
Also the following markdown syntax is ignored - see ```*Obecné*``` is not in italics.
When I fill in some title to image link
```
```
then the highlighting became correct (i.e. only link itself is bold).
Also the following markdown syntax is ok then (*```*Obecné*```* **is** in italics).
The correct behavior is to highlight bold only the link even if its title is empty.
--
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/2798
I'm using the geany 1.32 default installation on ubuntu 18.04 64bit to edit test.md file.
for H1 - H6 headers, the "#" signs are bold, but not the rest of header, i.e. "# Header" only has bold for '#' not for the word 'Header'.
`**bold**` does not show bold, neither does `*italiic*` displays italic.
I can customize them all using filetypes.markdown, except for the H1-H6 headers, the header is not impacted at all as mentioned above, for example:
`header1=0xFFCB4F;0x1E1E1E;true;false` this change will make `#` bold with specified background/front color, but not the header content, i.e. "Header1" in `# Header1` stays non-bold.
At least I would like to have all markdown headers shown as bold inside Geany without the need of any previewer
--
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/2026
I'm not sure how robust our parser is against invalid input or updated ctags file format so better use the upstream version of the official library to parse ctags files so we don't have to worry about this.
In addition, this patch also updates the code to read all the ctags kinds we need in tagmanager.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3049
-- Commit Summary --
* Add ctags 'readtags' library to allow us parse ctags files
* Use the readtags library to parse ctags files
-- File Changes --
M ctags/Makefile.am (2)
A ctags/libreadtags/readtags.c (1310)
A ctags/libreadtags/readtags.h (295)
M src/tagmanager/Makefile.am (1)
M src/tagmanager/tm_source_file.c (174)
-- Patch Links --
https://github.com/geany/geany/pull/3049.patchhttps://github.com/geany/geany/pull/3049.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/3049
Most likely the string doesn't make sense to be transalted
--
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/587