This is a fairly basic filetype, with only highlighting (using an upstream Scintilla lexer), but it works quite well AFAICT. See https://lists.geany.org/pipermail/devel/2019-November/010506.html
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2399
-- Commit Summary --
* Add Smalltalk filetype
-- File Changes --
M data/Makefile.am (1)
A data/filedefs/filetypes.smalltalk (56)
M data/filetype_extensions.conf (1)
M scintilla/Makefile.am (1)
A scintilla/lexers/LexSmalltalk.cxx (324)
M scintilla/scintilla_changes.patch (4)
M scintilla/src/Catalogue.cxx (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (2)
M src/highlightingmappings.h (29)
-- Patch Links --
https://github.com/geany/geany/pull/2399.patchhttps://github.com/geany/geany/pull/2399.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/2399
When a find operation fails to find a match, the find dialog's text entry field sets the background color of selected text to dark red. This is fine if the Gtk theme happens to use a light color for selected text, but for other themes, it makes the text nearly unreadable.
If Geany is going to set a background color here, it should set a foreground color as well, in order to avoid this problem.
--
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/2332
I guess this is a GTK issue because I also see other applications with this behaviour, but I don't know where I can put this request.
I copy the full location of a file on my system in the clipboard and want to open it in geany. But at the open dialog there is no possibility where I can put in the fullname of my file.
May this is for "normal" user useful, but as an editor for programers this should be able.
My System: Debian 10 (XFCE4), geany 1.33 (kompiliert am 2018-04-16 mit GTK 3.22.29, GLib 2.56.1)
--
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/2612
I've developed hundreds of bash scripts with Geany, and have always been able to click Execute and they run properly.
Many of these scripts make use of the $0 variable - that is - the path the script was run with.
So if I'm editing `/home/pi/myfolder/myscript.sh`, then $0 is `/home/pi/myfolder/myscript.sh`.
Well just yesterday that behavior changed. Now $0 is `./myscript.sh` - not with the full path anymore.
Using Geany, I tried executing multiple scripts that worked fine the day before, but all of them failed now because the scripts were no longer being run from their full path.
Running the scripts from a terminal, using their full paths, still works fine.
I don't remember changing any Geany settings, but is there a setting somewhere with which I can change its Execute behavior back to how it was?
--
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/2611
This adds a combo-box to the find-in-files dialog which lets the user choose which kind of regular expressions shall be used: extended, basic or perl.
The pre-selected value is 'extended' so users which do not want to change the reg-exp mode used, do not need to change anything. If a user only toggles the checkbox to enable/disable regular expressions then anything works as it used to.
Also see #443.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1809
-- Commit Summary --
* find-in-files: choose reg-exp mode (extended/basic/perl)
-- File Changes --
M src/search.c (44)
-- Patch Links --
https://github.com/geany/geany/pull/1809.patchhttps://github.com/geany/geany/pull/1809.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/1809
Closing as it is unlikely this will happen unless someone will write a Scintilla lexer for reStructuredText.
--
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/300#issuecomment-703253246