emacs-devel
[Top][All Lists]
Advanced

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

Re: minibuffer-exit when emacsclient executes Lisp code


From: Stefan Monnier
Subject: Re: minibuffer-exit when emacsclient executes Lisp code
Date: Thu, 17 May 2007 09:48:42 -0400
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux)

> the first real terminal only on the second run.  One way to reduce
> flickering would be to delay terminal initialization until after .emacs
> is loaded.  Is this what you mean?

I've been using a local hack which does just that.  Funnily enough it
doesn't remove all frame-resizing.  Maybe it's a bug in my hack, of course.

> Wouldn't that make it harder to debug .emacs errors?

Not really, no.  But it did break part of my .emacs which called
`frame-parameter' or something like that.

In any case, w.r.t calling `toplevel' I agree that we should probably not do
that when processing a "-eval" (after all, the user can explicitly add
a call to (toplevel) in the Elisp code passed to the Emacs session).
The only reason why it does do it currently, is because it seemed too much
trouble to try and distinguish this case.  Maybe the recursion-depth check
should be moved elsewhere where it's easier to determine whether -eval was
used or not.


        Stefan




reply via email to

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