From: "Roland Winkler" <Roland.Winkler@physik.uni-erlangen.de>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: RE: messages override minibuffer input
Date: Mon, 24 Sep 2007 03:28:24 +0200 [thread overview]
Message-ID: <18167.4792.543242.737218@tfkp07.physik.uni-erlangen.de> (raw)
In-Reply-To: <BNELLINCGFJLDJIKDGACMEAHCDAA.drew.adams@oracle.com>
On Sun Sep 23 2007 Drew Adams wrote:
> > If we put such messages at the end, that may cause the minibuffer
> > to grow by a line. Would you find that disturbing?
> >
> > If not, perhaps the thing to do is to put the message below the
> > current input, always growing the minibuffer. Or put the message
> > above the minibuffer contents. What would you think of that?
>
> Please don't do that. In general, let's try to keep echo-area messages to
> one line. If they happen to be so long that they wrap, so be it. So I'd
> request that we append without a newline.
Maybe I misunderstand something here. I thought that the question
was about messages placed at the end of a minibuffer line. So if the
minibuffer takes already 70 display columns and the message requires
another 70 columns I don't know how the message could fit into a
standard window with 80 display columns unless the message is
wrapped. In such a (standard?) case it would seem more natural to me
to put the message completely into a new line. (But I do agree that
this might be a matter of personal preference.) If, on the other
hand, the last line displayed in the minibuffer takes only 30
columns and the message is a short "Mismatched parentheses" then it
would be sufficient to display the message at the end of that line.
Roland
next prev parent reply other threads:[~2007-09-24 1:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 4:23 messages override minibuffer input Roland Winkler
2007-09-08 14:48 ` Stefan Monnier
2007-09-10 21:41 ` Davis Herring
2007-09-11 20:30 ` Richard Stallman
2007-09-12 22:32 ` Davis Herring
2007-09-13 3:23 ` Luc Teirlinck
2007-09-13 4:23 ` Davis Herring
2007-09-14 7:05 ` Richard Stallman
2007-09-12 9:25 ` Johannes Weiner
2007-09-12 10:24 ` Johannes Weiner
2007-09-12 16:25 ` Davis Herring
2007-09-12 16:28 ` Davis Herring
[not found] ` <E1IUCJ9-0000VV-9H@fencepost.gnu.org>
2007-09-16 3:23 ` Roland Winkler
2007-09-17 0:20 ` Richard Stallman
2007-09-17 14:49 ` Roland Winkler
2007-09-17 22:24 ` Richard Stallman
2007-09-22 15:18 ` Roland Winkler
2007-09-23 9:07 ` Richard Stallman
2007-09-23 15:08 ` Roland Winkler
2007-09-23 21:54 ` Richard Stallman
2007-09-23 23:33 ` Roland Winkler
2007-09-24 18:19 ` Richard Stallman
2007-09-25 1:06 ` Roland Winkler
2007-09-24 0:24 ` Drew Adams
2007-09-24 1:28 ` Roland Winkler [this message]
2007-09-24 2:02 ` Drew Adams
2007-09-24 3:20 ` Roland Winkler
2007-09-24 10:36 ` Robert J. Chassell
2007-09-24 15:08 ` Drew Adams
2007-09-24 16:11 ` Robert J. Chassell
2007-09-24 16:53 ` Drew Adams
2007-09-24 10:43 ` Johannes Weiner
2007-09-24 11:12 ` David Kastrup
2007-09-24 13:19 ` Johannes Weiner
2007-09-24 14:48 ` Roland Winkler
2007-09-25 10:44 ` Richard Stallman
2007-09-24 15:13 ` Drew Adams
2007-09-25 10:43 ` Richard Stallman
2007-09-17 22:31 ` Davis Herring
2007-09-18 0:53 ` Stefan Monnier
2007-09-23 21:55 ` Richard Stallman
2007-09-24 8:30 ` Stefan Monnier
2007-09-24 17:16 ` Davis Herring
2007-09-24 17:24 ` Drew Adams
2007-09-25 10:44 ` Richard Stallman
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=18167.4792.543242.737218@tfkp07.physik.uni-erlangen.de \
--to=roland.winkler@physik.uni-erlangen.de \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).