I've just upgraded from Fedora 23 to 24. Geany (version 1.27) now hangs in the find box (with a blue ring around it) after one or two successful finds. The rest of the app seems to work ok, but I am then unable to type into the find box. Solution is to close down Geany and re-start. Works then for a while. Seems to be rwalted to the "incremental" search aspect of the Find function - if I leave the typing and then return to it in a second or so it hangs, but if I type the whole string in straight away it seems to work. Perhaps a short timeout?
---
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/1101
The original Issue is somewhat invalidated now that document messages are shown in a non-modal infobar. If the focus is setup correctly, it should be a matter of tabbing to a document and pressing Enter (or the mnemonic, or <kbd>Ctrl</kbd> + <kbd>R</kbd>).
Perhaps it would be more appropriate to add a "Reload All" command instead?
---
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/301#issuecomment-232824470
Hmm, that doesn't look as trivial as I hoped for. Here are some observations:
- The best position would probably be right below the "Disk check timeout" option, probably named "Automatic reload".
- That GUI element is defined in `data/geany.glade:4596`, so for a new property, this file would need to be touched. `HACKING` seems to recommend Glade 3.8.5, so I'll go with that.
- The correlation to internal keys seems to be done in `src/keyfile.c:222`, so for a new property, this file would need to be touched.
- When a file is deemed reload-necessary, `monitor_reload_file` in `src/document.c:3606` seems to be called to trigger the notification. So for the new property, this function would need to be touched.
- Apparently, this uses the "new 'simple' prefs", as `src/prefs.c` puts it, so this file would need no changes.
Does this so far sound like a good idea? I'm new to the project, so I'd like to hear feedback whether a PR changing these places would have hopes of being accepted.
---
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/301#issuecomment-232816067
@BenWiederhake it doesn't appear that anyone has needed or wanted it enough to make a pull request.
---
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/301#issuecomment-232801430
Git checkout also causes this for many files, at least for the branches I work with.
---
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/301#issuecomment-232795409
Is there any activity on this? I was about to create a new issue for this when I saw this 1 year old thread.
Use case: git rebase touches many files that I would like to be reloaded automatically.)
---
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/301#issuecomment-232794131
Some time ago I posted an e-mail into the Geany-users mailing list asking for a keybinding for deleting from the begining of the line to the current position. I got some good answers and suggestions, and, some months later, here I come with the implementation ready to be used.
I've tested it and it looks fine.
Anything else, just let me know. I didn't touch any of the translation files, should I?
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1134
-- Commit Summary --
* Added keybinding for Delete from line start to current position
-- File Changes --
M doc/geany.txt (3)
M src/keybindings.c (6)
M src/keybindings.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/1134.patchhttps://github.com/geany/geany/pull/1134.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/1134
1. Do something (Find in Files) to populate the list of messages or compiler errors.
2. Jump to the first message/error. Let’s say it refers to `foo.c`:123.
3. Edit `foo.c` in such a way that you add 3 more lines at that point. In other words, text that used to be on lines 124+ is now on lines 127+, respectively.
4. Jump to the next message/error. Let’s say it refers to `foo.c`:345.
5. I want Geany to take me to `foo.c`:348, because the text that the message refers to is now on line 348. Instead, Geany takes me nonchalantly to `foo.c`:345.
A similar but different thing happens with the navqueue. The navqueue stores Scintilla positions, which, too, start referring to different text as the document is edited. (Please let me know if you want me to file this as a separate issue.)
Things that are maintained by Scintilla itself, such as bookmarks and indicators (squiggly underlines), do not suffer from this problem. Perhaps Geany could tap into that somehow?
Otherwise, I guess Geany could do some bookkeeping where it handles `SCN_MODIFIED` and then transparently rewrite line numbers in `msgwin_goto_messages_file_line()`. Sadly, I am not up to this task. But please let me know if there is any other way I can help, as currently this is by far the biggest problem I have with Geany.
---
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/1136