Hi,
I love the Geany search and replace which lets one use regular expressions. I would like to request that it also allows the replacing string to use a case conversion on the selected letters.
Heres an example:
search for `(o|n|r|a)(|mega|_rod)`
replace by `\U1\2` (or similar synthax)
would convert the occurences of omega, n, r, and a_rod to Omega, N, R, and A_rod respectively...
This has been discussed here: http://lists.geany.org/pipermail/users/2012-October/008284.html and is also available in regular expressions: http://www.regular-expressions.info/replacecase.html
Hope someone can get this feature in as Geany is great software !
--
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/1357
@kugel- As you are currently maintainer of this part of geanypy, can you please have a look whether it's still a point?
--
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/270#issuecomment-271581955
The KP_Divide, KP_Add and possibly other keys, at least when together with Ctrl (Primary) modifier, seems to be **unremovable**. If I "remove" the keybinding in Preferences ("Change", press nothing, click "OK"), they remain active. Neither ~/.config/geany/keybindings.conf nor ~/.config/geany/snippets.conf contains "KP_Divide", but pressing Primary+KP_Divide causes a zoom reset ("normal size").
Moreover, it seems that keybindings in **snippets.conf** are "inferior". If I do an explicite binding for Primary+KP_Divide in keybindings.conf then it overrides (removes) the "hardwired" (see above) zoom reset effect. However, when I do the binding in snippets.conf ("[Keybindings]", "comment=<Primary>KP_Divide"), then it does NOT override the "zoom reset": the effect is that *both* action is played. (Side-effect, merged effect.)
My environment is: recent Xubuntu (=Ubuntu with some xfce4).
$ geany -V
geany 1.28 (built on Sep 23 2016 with GTK 2.24.30, GLib 2.49.6)
--
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/1353
For code readability it is common to skip a line every now and then (between functions, variable declarations and so on). May be it is nice to have an option in Line operations to leave those lines.
Easiest way to do this would be to provide a new option which does exactly the same as "Remove empty lines" with the following exception. If there are "n" blank lines together, only delete "n-1" of them.
--
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/498
Currently we have:
* An initial digit marks the whole word as not checked: "1eror" is not underlined
* An ending digit doesn't, and the resulting word is always wrong: "error1" is underlined
I would like the spellchecker to split the words on digits, to have them behave like punctuation (like ".eror" and "error.")
--
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/515
As far as I can find, Geany will only use the line endings specified in "Preferences / Files / Default end of line characters" when it creates new files. Existing files will keep their line endings, unless you check the "Ensure consistent line endings" box, in which case I suppose Geany will find out what type of line ending is in the majority, and use that throughout the file.
What I would like is an option to always, unconditionally, force the default line ending to be applied when saving any file, whether newly created or previously existing.
---
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/984
make it, please
--
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/1355
This PR should remove warnings like
`(geany:7479): Geany-CRITICAL **: sci_get_contents_range: assertion 'start < end' failed`
Backtrace befre:
```
Thread 1 "geany" hit Breakpoint 1, handler_log (domain=0x7ffff7b64da2 "Geany", level=G_LOG_LEVEL_CRITICAL,
msg=0x55555651f800 "sci_get_contents_range: assertion 'start < end' failed", data=0x0) at log.c:121
121 {
(gdb) bt
#0 handler_log (domain=0x7ffff7b64da2 "Geany", level=G_LOG_LEVEL_CRITICAL,
msg=0x55555651f800 "sci_get_contents_range: assertion 'start < end' failed", data=0x0) at log.c:121
#1 0x00007ffff52bd5c4 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff52bd7cf in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff79bf94b in sci_get_contents_range (sci=sci@entry=0x555556373520, start=start@entry=11519, end=<optimized out>)
at sciwrappers.c:990
#4 0x00007fffe5db8da8 in get_current_word (sci=0x555556373520) at automark.c:92
#5 automark (user_data=<optimized out>) at automark.c:117
#6 0x00007ffff52b66aa in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x00007ffff52b6a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x00007ffff52b6d82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007ffff7251cc5 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x00007ffff79ad097 in main_lib (argc=<optimized out>, argv=<optimized out>) at libmain.c:1233
#11 0x00007ffff4cd12b1 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x000055555555478a in _start ()
(gdb) r
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/514
-- Commit Summary --
* Automark: Don't try to get some selection if line is empty
-- File Changes --
M automark/src/automark.c (3)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/514.patchhttps://github.com/geany/geany-plugins/pull/514.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/514