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
I just upgraded geany from 1.36 to 1.38 (Windows 10, version 1909), and the new UI is very bloated and greyscale and borderless. It looks pretty, but its hard to read. It also takes up WAY to much space, far more than it ever did. And its mostly wasted whitespace. On 1.36, its about 29 pixels between each open file on the left (about the height of the font, plus a small margin), on an 1.38, its 38 pixels between. Thats a 30% increase, but the font doesn't scale to justify the bloat. It makes it a lot harder to have a lot of open files, since the entire file pane is wasted whitespace
In addition, theres no border lines between open files, and everything is SUPER greyed out when it loses keyboard focus. Its pretty! But not very functional.
Is there any way to turn this off? I always liked geany as a "poweruser" editor. Functional, lightweight, and to the point
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3063
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3063(a)github.com>
This is a RFC regarding updating to the current version of Scintilla and getting off of the "fork" of the versions 3.x series (LongTerm3 branch).
The longer we wait to update, especially with the splitting off of lexers from Scintilla itself, we're basically just accumulating technical debt. Eventually the kind fellow currently maintaining the LongTerm3 branch will stop.
As far as I know, the main platforms Geany tries to support all have modern enough compilers/C++ standard libraries by now. There may be some older legacy/LTS platforms with users who won't be able to self-update to latest Geany without more effort, but with such limited developer time/interest/contributions for Geany, I don't think it's unreasonable to make some trade-offs like this in order to ensure Geany doesn't bitrot.
I might be willing to have a look at upgrading the code to work with latest Scintilla, but not if people are opposed, hence this RFC.
--
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/2519