Re: Starting emacs in ediff mode.

["Juanma Barranquero" <lekktu@gmail.com>]

On Jan 28, 2008 5:36 PM, Thierry Volpiatto <thierry.volpiatto@gmail.com> wrote:
> reader@newsguy.com writes:

> What they want to do (i think):
> when you start emacsclient, if no emacs session is found, start an emacs
> session with the server corresponding to the emacsclient you have
> already started (ouf!).

That's it.

What the stock Emacs' emacsclient does today:

 - Try to connect with the Emacs server.
 - If it can connect, great, that's all folks.
 - If it cannot, and there's an alternate editor, start that editor
(it could be Emacs), passing it the file arguments, etc.
 - Otherwise fail.

What would be nice (and Lennart's EmacsW32 emacsclient more or less
does, I think):

 - Try to connect with the Emacs server
 - If it can connect, great, that's all folks
 - If it cannot, start Emacs and wait until Emacs starts the server
 - Retry connecting with Emacs
 - If it can connect, great.
 - If not, start an alternate editor if defined (passing the file args, etc.)
 - Otherwise fail

The difference is that, in the first case, emacsclient starts the
alternate Emacs and then finishes. It does not maintain a connection
with Emacs or waits until the user signals (from inside Emacs) that
he's done with the buffer/file. That is not good when the one calling
emacsclient was not the user, but a process that starts emacsclient to
get a user-edited file (for example, a commit log) and considers that
emacsclient finishing means that the user-edited file is ready to be
used.

             Juanma