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

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

Re: New symptom and code


From: David Vanderschel
Subject: Re: New symptom and code
Date: Thu, 08 Jul 2004 02:05:38 GMT

"David Kastrup" <address@hidden> wrote in message
news:address@hidden
> "David Vanderschel" <address@hidden> writes:

> > Well, when I try that, what I see in the echo area is

> >   "First line^JSecond line^JThird line"

> > which is not acceptable.

> You are confusing the output of the message command with its return
> value.  Obviously, if you use M-x eval-expression RET, then the last
> thing that gets displayed is the evaled expression.

Nonsense.  I was not doing it with M-x eval-expression
in the first place.  I was writing the function call
in a buffer and executing it with eval-last-sexp.
What I see in the echo area is all that I care about,
and it is not coming out as I wish - no matter how
I manage to invoke message.


"Kevin Rodgers" <address@hidden> wrote in message
news:address@hidden
> That's what happens for me in Emacs 19.34.  But in Emacs 21.3 it behaves
> as desired.

Ahhh!  So my 20.7.3 is probably obsolete in this
manner also.  However, I do not want to force users of
my program to upgrade their emacs, so this revelation
about improvement in 21.3 does not really help either.



Since what I am doing is logically a pop-up, I decided
the easiest solution would be to just create a new,
temporary frame for it.  Then I have complete control,
and I do not get surprised by the subtleties of
minibuffers or the echo area.

Though I have given up on both the echo area and the
minibuffer approaches, I would still like to
understand my strange symptoms with the minibuffer if
only on principle.  I was really hoping that someone
could point me to some clarifying documentation which
had escaped my attention.

Regards,
  David V.




reply via email to

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