I have selected an executable from a subdir of `E:\Projects` and when pressing the run button it says "The system cannot find the file specified", which is odd since the the "Setup Program" dialog allowed me to select the file using the file dialog, so I know the file exists Perhaps it's just a misleading error message?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/337
When linewrap is in effect the height of the overlay is not adjusted if the old line is too long.
Overlay when line wrap is activated.
Overlay when line wrap is off.
---
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/425
This simplifies translations by being less redundant.
Note: label variable is not freed because `keybindings_set_item()` currently assumes static strings but for plugins, so we need not free the label right away. It's not a real problem though, as this string
is required during the whole process' lifetime, so it'd use just as much memory anyway.
Closes #953.
---
I'm not certain this is a great way to fix, but it works. Opinions welcome.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1058
-- Commit Summary --
* Use a format string instead of repeating almost the same string 9 times
-- File Changes --
M src/keybindings.c (39)
-- Patch Links --
https://github.com/geany/geany/pull/1058.patchhttps://github.com/geany/geany/pull/1058.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/1058
Add `parfor` to the list of keywords to be highlighted in Matlab script sources. `parfor` is a Matlab keyword that can be used in place of `for` to achieve parallel processing.
Although `parfor` is technically a function, its use is syntactically equivalent to traditional `for`, and therefore it should be treated the same in terms of syntax highlighting.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1021
-- Commit Summary --
* Add parfor to Matlab keyword list
-- File Changes --
M data/filedefs/filetypes.matlab (2)
-- Patch Links --
https://github.com/geany/geany/pull/1021.patchhttps://github.com/geany/geany/pull/1021.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/1021
Based on the discussion here https://github.com/geany/geany/issues/921 I tried what is still missing to support opening remote files without gvfs-fuse. As I suspected, there wasn't much missing - mostly some g_file_test() calls which didn't work remotely, file name validation which didn't allow URIs, getting filenames instead of URIs from file dialogs etc.
What works after these patches:
* opening links like https://developer.gnome.org/gio/stable/GFile.html both from command-line and file open dialog
* browsing remote locations in file browser
* opening/saving ftp/ssh/etc. locations when mounted - I guess they need to be mounted to work - even gedit needs them mounted (it would probably be possible to use g_file_mount_enclosing_volume () to pop up dialog to make user mount them, not sure if we want it or not)
* opening/saving remote projects
What doesn't work:
* TM parsing - the only reason here's the g_stat() in tm_source_file_init(), after commenting it out it works but TM at the moment doesn't know about Geany's file operation method used so it's not possible to implement this properly (I plan moving the TM - without ctags - into src making it effectively part of Geany after which it will have access to Geany's definitions)
* File->Properties - I simply have been lazy to implement it
* of course things like find in files, build commands etc. which we cannot run remotely
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/963
-- Commit Summary --
* Add wrappers around g_file_test() and use them everywhere
* Update utils_get_path_from_uri() to return URI when using GIO
* Fix warning in utils_tidy_path()
* Use g_file_new_for_uri() when needed
* Preserve URIs in tm_get_real_path()
* Merge implementations of write_data_to_disk() and utils_write_file()
* Use gtk_file_chooser_get_uris() in file opening/saving dialogs
* Add GIO version of document_rename_file()
* Add GIO implementation to utils_get_file_list_full()
* Add file reading utils function
* Load project config files using the new utility function
* Allow opening projects using URI
-- File Changes --
M plugins/export.c (2)
M plugins/filebrowser.c (6)
M plugins/htmlchars.c (2)
M plugins/saveactions.c (6)
M src/build.c (4)
M src/callbacks.c (8)
M src/dialogs.c (8)
M src/document.c (131)
M src/editor.c (2)
M src/highlighting.c (6)
M src/keybindings.c (4)
M src/keyfile.c (4)
M src/libmain.c (24)
M src/msgwindow.c (6)
M src/plugins.c (2)
M src/project.c (57)
M src/symbols.c (2)
M src/templates.c (2)
M src/ui_utils.c (6)
M src/utils.c (322)
M src/utils.h (16)
M src/vte.c (2)
M src/win32.c (4)
M tagmanager/src/tm_source_file.c (16)
-- Patch Links --
https://github.com/geany/geany/pull/963.patchhttps://github.com/geany/geany/pull/963.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/963
The plugin seems to not collapse the directory containing the active document, but it collapses others in the tree view when reloading. It would be cool if it kept all directories that are expanded before the reload, expanded after, provided they still exist.
---
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/415
I have configured some build commands for my project:
In Commander, I can invoke independent commands (such as “Run tests”) and execute commands (such as “Run on test input”), but not filetype-specific commands (such as “Pylint”). It seems like Commander just doesn’t see their labels:
---
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/462
As far as I can find, Geany will only use the line endings specified in "Preferences / Files / Default end of line characters" when it creates new files. Existing files will keep their line endings, unless you check the "Ensure consistent line endings" box, in which case I suppose Geany will find out what type of line ending is in the majority, and use that throughout the file.
What I would like is an option to always, unconditionally, force the default line ending to be applied when saving any file, whether newly created or previously existing.
---
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/984