From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org, Dan Nicolaescu <dann@ics.uci.edu>,
Geoff Gole <geoffgole@gmail.com>, Miles Bader <miles@gnu.org>
Subject: Re: Annoying paren match messages in minibuffer
Date: Tue, 13 Jan 2009 10:33:03 -0800 (PST) [thread overview]
Message-ID: <200901131833.n0DIX33W010995@mothra.ics.uci.edu> (raw)
In-Reply-To: <jwv8wpfnjur.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 13 Jan 2009 13:27:18 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> >> I think all messages should be. I've used experimental code to do that
> >> in the past, and it was _really_ nice. No stupid awkward pauses and
> >> annoyance like the current method, everything just seemed *right*.
> > How about allowing the minibuffer to have a header line, and display
> > messages in the header line? This limits the messages to be one line
> > long, but it's probably easier to read, and it shouldn't be too much of
> > a distraction. Just my 2 cents.
>
> In my setup (where I use a seperate minibuffer-only frame), this would
> work OK, maybe, but in general eating up one more line of text
> is undesirable.
I didn't mean for the extra header line to always be present, just to be
created on demand when there's a need for an extra message in the
minibuffer. Yes, this would move the mode-line one line up and down
when displaying the extra header line in the minibufer, but that might
not be a problem given that it's not such a frequent action.
next prev parent reply other threads:[~2009-01-13 18:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:18 Annoying paren match messages in minibuffer Geoff Gole
2009-01-12 15:20 ` Stefan Monnier
2009-01-13 2:26 ` Miles Bader
2009-01-13 14:00 ` Stefan Monnier
2009-01-13 15:55 ` Dan Nicolaescu
2009-01-13 18:27 ` Stefan Monnier
2009-01-13 18:33 ` Dan Nicolaescu [this message]
2009-01-14 22:15 ` Stefan Monnier
2009-01-14 22:30 ` Drew Adams
2009-01-13 13:58 ` Geoff Gole
2009-01-13 18:25 ` Stefan Monnier
2009-01-13 23:28 ` Juri Linkov
2009-01-14 13:46 ` Chong Yidong
2009-01-14 14:01 ` Stefan Monnier
2009-01-14 15:29 ` Drew Adams
2009-01-14 21:12 ` Juri Linkov
2009-01-14 21:52 ` Stefan Monnier
2009-01-14 22:22 ` Drew Adams
2009-01-14 23:10 ` Stefan Monnier
2009-01-15 0:52 ` Drew Adams
2009-01-15 2:41 ` Stefan Monnier
2009-01-16 19:10 ` Drew Adams
2009-01-16 20:52 ` Stefan Monnier
2009-01-16 23:42 ` Drew Adams
2009-01-17 2:15 ` Stefan Monnier
2009-01-14 22:13 ` Drew Adams
2009-01-14 21:12 ` Juri Linkov
2009-01-14 21:53 ` Stefan Monnier
2009-01-14 18:56 ` Geoff Gole
2009-01-14 21:14 ` Juri Linkov
2009-01-14 22:20 ` Geoff Gole
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 23:16 Chetan Pandya
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=200901131833.n0DIX33W010995@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=geoffgole@gmail.com \
--cc=miles@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).