bug-gnu-emacs
[Top][All Lists]
Advanced

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

Re: more than one-line minibuffer needed for eval-last-sexp output


From: Dan Jacobson
Subject: Re: more than one-line minibuffer needed for eval-last-sexp output
Date: 22 Jan 2001 09:42:26 +0800
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7

>>>>> "Eli" == Eli Zaretskii <address@hidden> writes:

Eli> [Still using a fake address, despite the many requests not to, do
Eli> you?  What would it take to get you to respect those requests, I
Eli> wonder?]

[A cherry pie with no dairy products.  Actually I see that in other
newsgroups many noted figures do indeed use bogus addresses, so if I
wanted to be a noted figure... OK, I suppose I must push up the date
when I will learn the 'procmail' thingy by a few months... but not yet
:-) . I am too busy finding the rest of the blemishes in "emacs
classic".]

Eli> On 20 Jan 2001, Dan Jacobson wrote:

>> OK, go to the *scratch* buffer, or most buffers actually.  Type:
>> auto-mode-alist ^X^E to do a eval-last-sexp on this rather long
>> valued variable, or your favorite other long valued variable.
>> 
>> Notice that the minibuffer doesn't crack open to give you the
>> several lines needed to display the value.

Eli> This is solved in the next version 21.1 which is now in pretest.

>> anyways obviously something should be done in order to usefully see
>> the output.

Eli> You can press C-j (or LFD, if your keyboard has that key), then
Eli> the result is inserted into *scratch*, where the one-line
Eli> limitation doesn't exist.

But just like I said last message
Dan> Sure one can hit ^U^X^E but that's not the point.
and ^J=^U^X^E here, ok never mind, glad to hear it's fixed.
-- 
http://www.geocities.com/jidanni Tel886-4-25854780 e-mail:restore .com. 積丹尼



reply via email to

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