[Top][All Lists]

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

Re: minibuffer-exit when emacsclient executes Lisp code

From: Lennart Borgman (gmail)
Subject: Re: minibuffer-exit when emacsclient executes Lisp code
Date: Wed, 16 May 2007 13:49:18 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070326 Thunderbird/ Mnenhy/

David Kastrup wrote:

--eval '(find-file "xxxx")

Yes, but I thought this could just be referred to the --eval case. But in the long run I agree that it is a problem and that a solution along the lines you describe below should be better.

I just wanted to give a quick and non-dangerous solution for now.

I think we should probably try to address this in connection with
another issue: a suitable way for opening a tty: open a frame only
once it is "needed".  One problem we currently have is that it is not
really pleasing to specify Emacs frame geometries, colors, toolbar or
menubar presence by using .emacs and/or customize: that way, the
initial frame will first get mapped wrongly, then flicker into

So one would want to have a delayed mapping, basically happening when
sit-for is called.

If this point is never reached, we don't need a mapping at all.  In a
similar vein, if emacsclient never reaches a point where it would be
interested in looking at tty input, maybe it is not worth mapping a
frame (and stealing the minibuffer).  Of course, the question when to
call "top-level" remains.

reply via email to

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