[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New start up splash screen annoyance...

From: Eli Zaretskii
Subject: Re: New start up splash screen annoyance...
Date: Sun, 16 Sep 2007 22:15:34 +0200

> Date: Sun, 16 Sep 2007 04:41:09 +0000
> Cc: Mathias Megyei <address@hidden>, address@hidden,
>       address@hidden, address@hidden, address@hidden,
>       address@hidden
> From: address@hidden
> It's rather
>   emacs <filename>
> versus
>   emacs [wait until Emacs is up] C-x C-f <filename>

Why would you need to wait for Emacs to come up on a modern machine?
The only use case I can think of that really causes a long startup is
when you use desktop.el to save and restore the last session.  But in
that case, you probably don't want to specify a file on the command
line anyway, since desktop.el would already visit the files you want.

But if there are use cases that I'm missing, how about using
emacsclient instead, as I suggested?

> The issue becomes somewhat grotesque when calling Emacs from some other
> process, e.g. via the EDITOR shell variable (that's why I have
> EDITOR=vim in my environment).

Now, _that_ is precisely what emacsclient is for.  We even say so in
the manual (see the node "Emacs Server").

reply via email to

[Prev in Thread] Current Thread [Next in Thread]