Re: emacs <--> file-browser as coroutines

[Yuri Khan]

On Mon, Jun 27, 2016 at 3:14 PM, Rusi <rustompmody@gmail.com> wrote:
>> The file manager as such is usually not an appropriate method of
>> asking for a file name in response to an Open File command; that calls
>> for a modal dialog.
>
> The question (at least the 2nd part) could well be:
> Why are we stuck on Open File being modal?

No particular reason, just that most other editors already work that way.


> Just strengthens the alternative model I was suggesting:
> - Keep both emacs and file browser open
> - Navigate to files one desires to view/edit in the browser
> - Drag-n-drop into emacs as required
>
> The one thing I miss is an option to ensure that only one browser window opens
> There seems to have been one such in the past but now cant find it

That’s very dependent on the platform and the actual file manager in use.

In practice, it is ensured by not starting the file manager from the
editor. If you arrange for no more than one instance of file manager
opened on startup, and for Emacs to run as a daemon, and for
Emacsclient to be started from the file manager, that will be
sufficient.

The user can then opt to start more instances of the file manager, or
open more Emacs frames, or both, as demanded by his/her workflow.

Also, it might be a good idea to start Emacs with a Dired open at the
user’s home or Documents directory. That’s one more workflow for
opening files in Emacs; one that I personally use the most.