I use the "Find in files" dialog extensively in my everyday work *because* it is a very elegant interface to `grep` but nevertheless integrates so well with Geany. However, sometimes I am not interested in the contents of files but merely there names. In these situations I would love to have a similar interface to POSIX `find` that simply takes find arguments and presents any found paths similarly to the "Find in files" dialog (i.e. clickable to open the respective file). Please consider this as a feature request - I won't try to implement it (partially due to the outcome of my "reload all" PR #54 :P)
--
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/1178
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
Always load the builtin color scheme before the user's one in case the latter lacks some named colors, so it uses the default.
This helps us adding new named styles without requiring each and every theme to be updated.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1186
-- Commit Summary --
* Always load the default builtin color scheme as fallback
-- File Changes --
M src/highlighting.c (43)
-- Patch Links --
https://github.com/geany/geany/pull/1186.patchhttps://github.com/geany/geany/pull/1186.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/1186
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:
![geany-build-menu](https://cloud.githubusercontent.com/assets/300211/16819835/e3c17a26-4956-11e6-924a-0cdedeeaf905.png)
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:
![geany-commander-build](https://cloud.githubusercontent.com/assets/300211/16819891/2b0ae35e-4957-11e6-9cbc-57381962c8cb.png)
---
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
Here are some changes to lineoperations; adding selection support.
If a selection is made in the file, the line operation will be applied to the lines within the selection, rather than the whole file.
Like usual, I'm open to hear any suggestions/improvements.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/378
-- Commit Summary --
* lineoperations: combined similar code
* lineoperations: added selection support
* lineoperations: removed unnecessary parameters
* lineoperations: added selection to documentation
* lineoperations: added some ui changes
* lineoperations: minor formatting
-- File Changes --
M lineoperations/ChangeLog (6)
M lineoperations/README (14)
M lineoperations/src/linefunctions.c (340)
M lineoperations/src/linefunctions.h (28)
M lineoperations/src/lineoperations.c (237)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/378.patchhttps://github.com/geany/geany-plugins/pull/378.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/378