There is no feedback about a failed GIT commit at all.
No status bar message, no status window message, no message in Help->Debug Messages and no error dialog.
At least one the above should happen to tell the user that the commit did not happen.
IMO there should be a message in Help->Debug Messages at the very least but also some more visible feedback to the user like an error dialog or at least a status bar message.
The only trace you get is the GIT error output on stderr but I guess most people won't want Geany's stderr regularly :).
--
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/837
Using Geanyctags 1.38 on Ubuntu 20.04.
On first use the 'Project > Generate tags' menu command completes correctly and generates a new .tags file for the project. After that, trying to re-generate the tags (repeat 'Generate tags') fails with the following error in the Messages pane:
```
find -L . -not -path '*/\.*' | ctags --totals --fields=fKsSt --extra=-fq --c-kinds=+p --sort=foldcase --excmd=number -L - -f '/home/user/work/test-project.tags'
ctags: "/home/developer/work/geany-plugins-develop.tags" doesn't look like a tag file; I refuse to overwrite it.
```
Looking inside the .tags file, reveals that the first line of it is blank. Removing the blank line allows the regeneration as expected.
Geany info:
```
geany -V
geany 1.36 (git >= 825acb21) (built on 2020-04-28 with GTK 3.22.30, GLib 2.56.4)
```
--
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/1042
Geany keybindings, like <primary>o to open a file do not seem to work in Vimode's normal mode on macos. As far as I know, <super>o should not overlap with any of Vimode's keybindings, but it seems to interpret it as just "o" as it creates a new line and enters insert mode.
The Geany keybindings do work fine while in insert mode on macos. I have not yet tested visual mode, line visual mode, or replace mode.
Thank you!
--
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/991
Steps to reproduce:
- Enter insert mode.
- Type the letter 'g'.
- Try to exit insert mode.
Expected behavior:
Program exits insert mode.
Actual behavior:
Program stays in insert mode.
--
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/1075
In vi if you, lets say, hit i for insert, then, shift - 3 to add a # sign, you can repeat your last command by hitting period while not in insert mode and it will perform your last command and put a # where your curse is at that moment. Is it possible to get this functionality into this plugin? I never realized how much I rely on it until it wasn't there.
--
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/1011
version 1.37 plugins
abcde;
dt to ; result should be ; not e;
--
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/1052
aaa
bbb
when you yank 2 lines from the top and press p at line bbb it should be.
aaa
bbb
aaa
bbb
but instead it is
aaa
bbbaaa
bbb
It should paste from new line but it didn't
I really like to use geany because is fast, but currently vim mode is very broken even with the latest 1.37.1
I don't like to use the mouse/keyboard since I learned to use vim and is so efficient with the simple editing functions.
A lot of the vim mode is missing. for instance, delete line number doesn't work.
--
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/1060
This code:
# some comment\
some more comment NOT!
... highlights as if the second line was comment, but zsh at least treats it as code.
--
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/2715
I think, when commenting Python code via `Edit` > `Format` > `Comment Line(s)`, after the `#` character would be better to add a space, [as mentioned in PEP8](https://www.python.org/dev/peps/pep-0008/#block-comments), resulting:
<code>
# commented line
</code>
instead of:
<code>
#commented line
</code>
This prevent me to manual adjust (all) the commented line(s).
--
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/1681