From: "David Vanderschel" <DJV4@Austin.RR.com>
Subject: Re: New symptom and code
Date: Thu, 08 Jul 2004 02:05:38 GMT [thread overview]
Message-ID: <SZ1Hc.19195$mY2.10638@fe1.texas.rr.com> (raw)
In-Reply-To: 40EC1F05.6060008@yahoo.com
"David Kastrup" <dak@gnu.org> wrote in message
news:x5oemsfw3n.fsf@lola.goethe.zz...
> "David Vanderschel" <DJV4@Austin.RR.com> 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" <ihs_4664@yahoo.com> wrote in message
news:40EC1F05.6060008@yahoo.com...
> 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.
next prev parent reply other threads:[~2004-07-08 2:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 9:53 Minibuffer wipeout: "Auto-saving... done" David Vanderschel
2004-07-06 10:37 ` New symptom and code David Vanderschel
2004-07-06 18:15 ` Kevin Rodgers
2004-07-07 1:16 ` David Vanderschel
2004-07-07 1:24 ` David Kastrup
2004-07-07 16:04 ` Kevin Rodgers
2004-07-08 2:05 ` David Vanderschel [this message]
2004-07-06 10:42 ` David Vanderschel
2004-07-10 17:17 ` Kai Grossjohann
2004-07-06 18:13 ` Minibuffer wipeout: "Auto-saving... done" Kevin Rodgers
2004-07-08 2:26 ` David Vanderschel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='SZ1Hc.19195$mY2.10638@fe1.texas.rr.com' \
--to=djv4@austin.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).