The following sequence of actions crashes Geany:
1. start debugging a program with the scope plugin
1. wait for a breakpoint
1. in the message window select _"Debug"_ and then select tab _"Locals"_
1. left click in the tabs content area (to prevent #824)
1. the local variables show up, but none of them is selected
1. right click inside the tab to show the context menu, select _"Modify"_
1. Geany crashes
Remark: the crash does not occur if the user first selects a variable to _"Modify"_.
--
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/825
Remember the last 10 commit messages and offer a dropdown in the commit
dialog to choose one of the last commit messages.
One of my use cases is that there was an error on executing `git commit` and so the commit and its message is lost(in this case any feedback of the failed process is missing in the UI but that's another story). With the history, I can restore the message easily.
Another use case is that one might want to repeat the same commit message for multiple commits (i.e. same change in various repositories or whatever).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/836
-- Commit Summary --
* GeanyVC: Add a commit message history
-- File Changes --
M geanyvc/src/geanyvc.c (153)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/836.patchhttps://github.com/geany/geany-plugins/pull/836.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/836
> By the way, I'm a little puzzled by the vte_restart() code - we kill the shell, set pid to 0, but who restarts it? And cannot we get the pid in this case?
Just to resolve this confusion: the restart of the shell was previously done in Geany and so the pid got set properly. But then we removed the start code because of a VTE bug and so pid kept 0 and broke other things :(.
#2116 tries to fix that.
JFYI, it won't help this issue.
--
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/436#issuecomment-478342420
#2116 should fix the original issue (Set path from document broken after VTE restart).
The reason for pid=0 was the removed `vte_start()` call which we removed long time ago because of a VTE bug. But the VTE bug has been fixed also long time ago, so we should explicitly start the shell again and so get a valid pid again and everything else will work again.
--
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/352#issuecomment-478342085
Don't understand why but if a single document is loaded with line breaking set in the saved prefs the `document->line breaking` menu item is not set, and it appears impossible to turn breaking off until another document is loaded probably because the menu item doesn't match the internal value?
--
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/2113
In Windows at least, when a read-only file is opened and certainly when autosave is on (from numbered bookmarks plugin), get an error message on the screen that cannot be sent away except by using program manager to stop Geany. Is this a problem with the numbered bookmarks plugin, or a broader issue.
--
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/2104
I miss this feature a lot from the builds of Geany that are compiled to Gtk3.
I know, it was removed with the Gtk2 -> Gtk3 switch, as the toolkit itself removed it.
I would like it to be there again, with an optional setting to turn it on/off (to reap whatever benefits it has to not have it).
Is it possible to implement it?
--
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/1967