I have a some questions about a few things:
1. I could not figure out what the following properties are for:
marker_line
marker_search
marker_mark
call_tips
white_space
string_eol
scalar
label
decorator
extra
entity
2. The "version" property says "incremented automatically, do not change manually" should I just leave it at 1225?
3. How do I make the "#include" part of a preprocessor command a different color than "<stdio.h>"
4. what is the difference between:
number, number_1, and number_2
keyword, keyword_1, keyword_2, keyword_3, and keyword_4
identifier, identifier_1, identifier_2, identifier_3, and identifier_4
string, string_1, string_2, string_3, and string_4
5. How do I get rid of the vertical line through the middle of the editor (shown in [this picture](https://i.imgur.com/oPNI8G8.png))?
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-themes/pull/21
-- Commit Summary --
* added atom-one-dark theme
-- File Changes --
M AUTHORS (5)
A colorschemes/atom-one-dark.conf (116)
A screenshots/atom-one-dark.png (0)
-- Patch Links --
https://github.com/geany/geany-themes/pull/21.patchhttps://github.com/geany/geany-themes/pull/21.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-themes/pull/21
I am editing C programs with about 2,000 LOC. There seems to be an intermittent past corruption error. It may happen on "Find and Replace" or "Copy" (Ctrl-C) and then "Paste" (Ctrl-V) elsewhere.
The corrupting text seems to be randomly sprayed in a few places. I find out it happened when I attempt to recompile my code and gcc complains. The corrupting text can land in comments, blank lines, in varaible names, you name it.
So now, if I am pasting anything, I save the file, end Geany, and bring it back up.
I am running on a Raspberry Pi 3B+, Raspbian OS. The only package I believe I downloaded is gcc. The Geany version is "Gorgon", (built on or after 2018-04-16). I am not aware of having any Geany plugins.
The editor is great and works 95% of the time. I just keep hitting the corruption errors if I stay in it too long.
Any help is appreciated.
--
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/2753
I love Geany and use it all the time, but I was a little disappointed to find that CSS extension languages - such as Sass, SCSS and Less - do not have syntax highlighting
The userbase for these is probably small enough that new syntax highlighting rules specific to these languages would not be worthwhile, but to me it would make sense for the '.less' and '.scss' filename extensions to be recognised as CSS files (the same as '.css'); these languages are supersets of vanilla CSS (so the new features they add would still not receive highlighting, but most of the usual syntax highlighting one might expect would work)
Sass syntax is slightly different (uses indentation rather than braces a-la-Python) but still not a million miles from normal CSS.
--
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/2767
geany 1.37.1 (built on 2021-01-05 with GTK 3.24.24, GLib 2.66.4) on Manjaro Linux
I am unable to use execute(F5), I get the message:
`06:38:20: Cannot execute build command "xterm -e "/bin/sh /tmp/geany_run_script_Z4MN20.sh"": No such file or directory. Check the Terminal setting in Preferences`
the terminal is not set to xterm, in the preferences I have:
`/usr/bin/gnome-terminal -e /bin/zsh %c`
I've tried other terminals as well.
The Compile and Build options do work
also xterm does not seem to be installed by default on Manjaro, and is not installed on my system.
--
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/2803
It might be cool to make [the GP website](https://plugins.geany.org) into a section/page on the new site or at least use the same backend/css framework/etc. Maybe `plugins.geany.org` could just re-direct to a new `/plugins` route/page on the new site?
I'm not sure whether that's a lot of work or not.
--
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/www.geany.org/issues/14
I love the ability to theme the edit area and I prefer a darker theme.
The problem is that the theme does not apply to the side bar which to my mind is a bit inconsistent. Especially when there is a strong light / dark contrast.
I am sure there are users that would prefer it to stay the way it is but for myself at least I would optionally like the relevant portions of the theme to apply to the side bar.
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/1344
resolves #434
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2584
-- Commit Summary --
* Create julia lexer, no ctags
-- File Changes --
M data/Makefile.am (1)
M data/filedefs/filetypes.common (4)
A data/filedefs/filetypes.julia (62)
M scintilla/Makefile.am (1)
M scintilla/include/SciLexer.h (14)
M scintilla/include/Scintilla.iface (16)
A scintilla/lexers/LexJulia.cxx (536)
M scintilla/src/Catalogue.cxx (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (10)
M src/highlightingmappings.h (32)
-- Patch Links --
https://github.com/geany/geany/pull/2584.patchhttps://github.com/geany/geany/pull/2584.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/2584
When editing a document in (soft) Line wrapping mode (the document line that is longer than the screen width is spread over multiple display lines while keeping the same line number), the End key takes you to the end of the document line. This is understandable, but it keeps being unexpected while editing in the middle of a document line...
My proposal is just to change the defaults:
End = "go to the end of the display line", Alt-End = "go to the end of the document line", Home = "go to the beginning of the display line", and Alt-Home = "go to the beginning of the document line"
When not in Line Wrapping mode, it still works the same, but when in Line Wrapping mode, it's more intuitive.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/949
)?](http://picture](https://i.imgur.com/oPNI8G8.png))?){kind=link}