GNOME Bugzilla – Bug 598057
Manage folder open at command line
Last modified: 2020-11-24 09:59:35 UTC
When gedit is called from command line with a directory as parameter gedit should just starts normally and open that directory as filebrowser root, without display the message "%s is a directory" . in most cases users know about that.
I have to agree, I'd like to use "gedit ." in a shell to jump to that folder in gedit. To concretise, this could be used for handling multiple projects with distinct sets of files, if you really apply "open that folder" meaning to that command: - open a new gedit window - filebrowser visible in that window by default - filebrowser root of that window = fixed to that folder (no way to navigate up) - window title / alt+tab switcher text shows the name of that folder
*** Bug 628914 has been marked as a duplicate of this bug. ***
Filebrowser should just go from being an optional plugin to a feature and then gedit . or gedit /path/to/some/dir Should open the file browser pane and set the root equal to the directory from the command line.
Came here to file this exact RFE. I use this extensively to open a project directory in Sublime Text but with all the enhancements to GEdit, I find myself using it more. This is probably the thing I miss most as I attempt to edit projects as whole units vs just files. `gedit .` is my common use case.
Mass-closing of all gedit bugzilla tickets. Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.