Please tell me if there is some way I can make the line marker (the cross) on line number 1, shown below,
larger as it is very difficult to find visually.
--
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/1733
As a python teacher I recommend Geany to newcomers a lot. It's always a pain to explain to them that first you need to change the execute command. The official python installer no longer adds itself to the path variable by default, therefore on a default python install the command "python" does not work. Instead for several years now the python installer also installs the "python launcher" named "py.exe". Users are expected to use the command "py" in the command prompt instead of "python". The python launcher adds support for shebangs to windows, making it easier to control python versions.
I propose that you change the default execute command for python files from `python "%f"` to `py "%f"` in order to make Geany on Windows work with python out of the box.
A potential downside is people that install python from Anaconda or similar packages, which do not install the python launcher and therefore still require modifying PATH and using the "python" command. However I feel that a user adept enough to adjust the PATH variable can probably also figure out how to change the execute command.
--
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/2211
Some Gtk themes define a dark foreground color for selected text, so when we
set the background to dark red, it becomes difficult to read. We must therefore
set a foreground color that will remain legible against our background.
Fixes #2332
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2333
-- Commit Summary --
* Define text color when setting dark background
-- File Changes --
M data/geany.css (1)
M data/geany.gtkrc (1)
-- Patch Links --
https://github.com/geany/geany/pull/2333.patchhttps://github.com/geany/geany/pull/2333.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/2333
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
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
As pointed out in #1218, currently the Windows nightly builds are not really compabitle with the release installers (line end character detection, strange warnings about image loading, maybe more).
Currently, the nightly builds are created with a very old toolchain (gcc 3.x) and probably outdated GTK stack.
Ideally, we use https://github.com/geany/geany/blob/master/scripts/cross-build-mingw.sh also for the nightly builds with newer Mingw toolchain and maybe even use NSIS to create full installers.
--
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/1241
I'm on 1.34.1 . Win10
When double clicked on any geany associated file (let's say txt), or when other tools "push" some files to external editor (mine is geany) every time a new instance pops-up. It started to behave like this Today without any errors or warnings. Important is that when double click on text file it used to open in 1/10 of blink of an eye. Now it takes about 2 seconds to open. I've tried to re-install already.
I've run it with verbose, but there is not enough to debug for me
procexp of two running geanys
_Originally posted by @volcik in https://github.com/geany/geany/issues/641#issuecomment-469643957_
I have also done the same with all plugins disabled
--
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/2101
Line wrap breaks at word boundaries (word wrap). Straight line wrapping - breaking at a column - would be better for long lines of cryptic code.
When long lines end with series of tabs followed by text intended to align at column, calculation of column varies by number of characters preceding the wrap.
To replicate, type a long line of text that wraps a couple of words onto the (wrap)
following line<tab><tab><tab><tab>Aligned Text
Insert characters into the first line (before the wrap) and watch "Aligned Text" shift a character at a time.
Expected behavior is "Aligned Text" should only shift a tab at a time, as the second line increases length. The number of characters on the first line, before the wrap, shouldn't make any difference.
Xubuntu 17.10 with latest Geany from repository (1.29).
--
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/1495
markdown is getting even more common these days it would be nice that geany can make itself a first class markdown editor. The "urgent" feature I would request:
1. When adding a list, a return key should automatically make next line read for the list, now I have to type each list line with "* my line", the "* " part should be automatically added.
2. select a few lines and change them to a list easily together
3. when type headlines they should be bold as what **bold** already does
4. select some text then use keybinding to make it bold or italic, e.g. Ctrl+B(bold), ctrl+I(italic) , or just type `**` , `*` it can auto be added to both ends of the selected text, now I can only do this with quote sign \`
with above features, geany will become one of the best markdown editor, that alone is enough for its wider usage
--
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/2070