From: "David Vanderschel" <DJV4@Austin.RR.com>
Subject: Re: New symptom and code
Date: Wed, 07 Jul 2004 01:16:16 GMT [thread overview]
Message-ID: <A9IGc.18551$T72.10721@fe2.texas.rr.com> (raw)
In-Reply-To: 40EAEC5D.8040603@yahoo.com
"Kevin Rodgers" <ihs_4664@yahoo.com> wrote in message
news:40EAEC5D.8040603@yahoo.com...
> David Vanderschel wrote:
> > I should have mentioned that I am using the minibuffer primarily so
> > that I can get a temporary multi-line display. Otherwise, I could
> > have used message. I am not letting the user edit in the minibuffer.
> > I am just showing him some data. The single character he types is
> > treated by my program as a command, which then modifies the display.
> I don't understand. What's wrong with
> (message "First line\nSecond line\nThird line")
Well, when I try that, what I see in the echo area is
"First line^JSecond line^JThird line"
which is not acceptable. Interestingly, what appears
in emacs' *Messages* buffer does have real newlines.
Is there some setting which affects whether or not
newline characters cause the echo area to grow?
message was actually my first choice, but I have not
been able to see how to make the echo area grow.
Regards,
David V.
next prev parent reply other threads:[~2004-07-07 1:16 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 [this message]
2004-07-07 1:24 ` David Kastrup
2004-07-07 16:04 ` Kevin Rodgers
2004-07-08 2:05 ` David Vanderschel
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='A9IGc.18551$T72.10721@fe2.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).