Re: New start up splash screen annoyance...

[tomas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Sep 16, 2007 at 10:15:34PM +0200, Eli Zaretskii wrote:

[...]

> >   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?

On my fastest machine it takes about two seconds. Not all machines I
work with are that fast.

> 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.

You are quite right on that...

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

In some cases it makes sense: when it's my work machine. In others not
so much: a server I log in ocassionally via SSH (where I just decide
spontaneously to view/edit a configuration file). There, all the
preparations to make Emacs the way I'd prefer do not seem worth the
hassle and I just use vim.

(Note that the delay mentioned by me above is not bad because it's too
long -- even a couple of seconds is annoying when they are "in the
middle" of a conceptual action, like "I'd like to edit/view this file").

If you "live" whithin Emacs, you won't see the problem, but coming from
a shell, you will.

> > 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").

I'll give that a try, thanks. It'll at least cover the cases for the
machines I work regularly on.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFG7fy9Bcgs9XrR2kYRAqMOAJ0fQNf41hDz7wdeHWjqZOIHH43X5QCfRv3X
8FTtAv1JTfFl28JbATbp+C8=
=JgLv
-----END PGP SIGNATURE-----