OS: Windows 11
Geany Version: 1.38.0
Plugin: Tree Browser
Problem: After I deleted a file from outside the Geany, the list of tree browser not being refreshed even I click refresh.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1194
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1194(a)github.com>
The treebrowser context menu items "Open externally" and "Open Terminal" don't work on Windows 10.
It doesn't lunch any external application.
However, the "Open Externally" function in built-in plugin Filebrowser is working correctly.
--
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/556
The filedef file filetypes.python.in is missing the keywords "match" and "case".
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3263
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3263(a)github.com>
This adds `_`, `case` and `match` to the Python keywords list.
`_` seems not very useful but also won't hurt I guess. It will be highlighted as keyword when used in something like `message = _('Text to be translated')`, while not completely technically correct in this case, it is OK IMO and not worth the efforts to remove this single keyword from the list in the update script.
N.B.: the `scripts/update-python-identifiers.sh` script now requires Python 3.10 which was released about one year ago and the script is only to be executed by developers.
Closes #3263.
Before:
After:
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3277
-- Commit Summary --
* Add soft keywords to Python keyword list
-- File Changes --
M data/filedefs/filetypes.python.in (4)
M scripts/update-python-identifiers.sh (4)
-- Patch Links --
https://github.com/geany/geany/pull/3277.patchhttps://github.com/geany/geany/pull/3277.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3277
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3277(a)github.com>
This is a reworked and extended implementation of sorting based on tag presence in header files discussed (and dropped) from #3185. This implementation uses the header tags from ctags so we know precisely which files are included so we can use not only the tags from the source's header file but also tags from other included files. After this change the ordering sequence looks this way:
- sort local vars first (with highest line number first),
- followed by tags from current file,
- NEW: followed by tags from header,
- NEW: followed by tags from other included files,
- followed by workspace tags,
- followed by global tags
To me, the result seems to improve autocompletion results (it's a bit hard to tell for sure, one can always prepare artificial examples to test where it works better, with the real world it's harder to spot a difference between different orderings unless something is visibly broken).
For reference, I also tried the option to use the includes from the included headers recursively to some depth but the results didn't seem visibly better and were actually slightly worse (by including `<gtk.h>` one got all the GTK symbols which were then fighting with symbols from explicitly included headers that started to appear lower in the list which was often worse).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3269
-- Commit Summary --
* Maintain a hash table of TMSourceFiles inside TMWorkspace
* Process header tags
* Sort autocompletion tags also based on their presence in included files
-- File Changes --
M src/symbols.c (2)
M src/tagmanager/tm_parser.c (4)
M src/tagmanager/tm_parser.h (3)
M src/tagmanager/tm_workspace.c (155)
M src/tagmanager/tm_workspace.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3269.patchhttps://github.com/geany/geany/pull/3269.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3269
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3269(a)github.com>
Please take a look at this issue: https://www.forum.puppylinux.com/viewtopic.php?t=4061 which describes the disappearing message window problem. When this occurs I set message window visible and then fish around at the edge until I find the pane and drag it back to normal. But when this happens to my mentees they find it very difficult to do this as they are beginners and so they form a negative image of Geany as difficult to use. Please could you make it much easier to recover the message window when it has been inadvertently dragged too far to the right to be visible by a beginner?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3329
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3329(a)github.com>
I have geany 1.38 installed from debian repository. I would use it more but there is no horizontal scrollbar for some reason, so it makes some editing slow. Any way to turn that back on? or is it a bug I should file? Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3311
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3311(a)github.com>
When open files are deleted from the filesystem, Geanys behaviour is not very intuitive and somehow contraproductive. It offers to save the file again and does not give me the possibility to close the document.
I suggest to change the dialogue to
"File was not found on the drive. Close the file and discard content?
Yes (Close the tab, do NOT suggest to save it again.)
Yes (Do noting, keep the tab open),
Main use case:
Editing files on a remote server by FTP with Filezilla:
-Several files are stored in a temp folder.
-I can edit them with any editor
-Filezilla tracks changes and lets me update the files after changes
-When I am done, I close Filezilla and the Temp files are deleted by Filezilla.
In that case I want to get rid of the open files quickly and do not want to store them again. Why should I?
Other use case:
editing files that are stored in a cloud and have been deleted in the meantime.
Reference for a better solution:
-Notepad++
--
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/1994