I managed to add a hotkey for the sidebar, and it's very nice being able to quickly toggle that one. Would be really nice to have the message-window the same. That way i would get to focus on the text file itself.
Thank you for the great IDE!
--
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/2511
Uses the Geany "key-press" signal, allowing access to all keys, including bound ones.
Fixes a bug that prevent the use of bound keys without modifiers.
Prevents playback during recording.
Displays recording indicator on the status bar.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/980
-- Commit Summary --
* Connect to Geany "key-press" signal
* Prevent playback during recording
* Add recording indicator to status bar
* Fix bug: allow bound keys without modifiers
-- File Changes --
M keyrecord/src/keyrecord.c (72)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/980.patchhttps://github.com/geany/geany-plugins/pull/980.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/980
This might be a little nuisance, but its still an issue. Dragging the window doesn't work. Using geany 1.36 on Arch Linux LXQT/Openbox
--
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/2510
O:show on symbol list
X:just like never exist
auto getName(int id)->::std::string; // O
auto getName(int id)->std::string; // X
auto getName(int)->::std::string; // O
auto getName(int)->std::string; // X
auto getName(uint32_t id)->std::string; // X
auto getName(uint32_t)->std::string; // O
Use global namespace could cover this bug for now.
--
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/2509
Thanks for Geany.
I use Geany 1.29 with pleasure. After upgrading my Linux distribution Geany is upgraded to version 1.33. The appearance has changed. Now working with Geany has become tiresome. The text in the not active tabs is light gray on a bit lighter gray and also the theme, syntax highligting, has changed to something more fatiguing colors. Maybe this works for young people with good eyes. If ones eyes are a bit less than that it is not nice, tiresome and timecosuming.
I would like to have a Geany with the look and feel of version 1.29 back or an easy the option to switch back to it.
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/2496
I using [geany-on-rails filetype](https://github.com/dejw/geany-on-rails/blob/master/geany/filedefs… (without [styling], I also updated the filetype_extensions.conf) with Geany 1.36 on Debian Testing, but the highlighting does not work with **.html.erb** files.
Perhaps one configuration line is missing somewhere? (I say that because there is no problem with .html.php and .php files)
example.html.erb: **ko**
example.rb: ok
--
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/2507
Geany-INFO: 11:12:09.088: Geany 1.34.1, en_US.UTF-8
Geany-INFO: 11:12:09.088: GTK 3.22.30, GLib 2.56.3
OS: Linux(Ubuntu 18.10)
Filetype: Fortran
For Fortran modules the first function/subroutine contained in the module is not displayed in the Symbols list.
--
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/2115
As far as trying the input directly with u-ctags, it captures all expected tags.
--
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/349#issuecomment-629691440
# Description
If you add some macros into a type definition (ex. struct, enum, etc), the last token before the opening brace of the definition seems to be taken as the type name. I guess this is a bug in old `c.c` ctags parser.
# Example
```c
#define BLEH
struct foo BLEH { int _; };
```
Here, `BLEH` gets highlighted as the type name instead of `foo`.
# Use case
Using macros for things like GNU C's `__attribute__` extension.
# Version
I don't think version matters at all, but I'm using a fairly recent 1.32 build.
--
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/1654