From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: wrapper fn for message and minibuffer-message?
Date: Thu, 6 Oct 2005 08:52:47 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEEBICNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1ENOIh-0000TP-3V@fencepost.gnu.org>
I'd even argue that this function should be called
"minibuffer-message",
since currently minibuffer-message is only used when
(minibufferp) is non-nil.
I agree that is a natural generalization. But I agree that this name
is not very clear for the current behavior, and even less clear for
the suggested behavior.
I guess you didn't like the name "display-message" either (or co-opting the
name "message" for the wrapper function).
I think the name "minibuffer-message" is clear for its _current_ behavior -
what's unclear about it?
I can't think of a better name for this function, but I do have
an idea for a cleaner interface for the feature. Have a variable
minibuffer-message-at-end which, if t, causes `message' to
display messages this way.
Not sure I understand. The important differences between `message' and
`minibuffer-message' today are these:
- `message' exits the minibuffer (and recursive edit);
`minibuffer-message' does not
- `message' logs the message to *Messages*;
`minibuffer-message' does not
- `minibuffer-message' wraps the message in " [...]";
`message' does not
How would your suggestion relate to the first two differences?
In particular, a programmer must be able to control whether or not the
function exits the minibuffer. Today, that is done by using one or the
other: `message' or `minibuffer-message'.
How would the variable be set? Only explicitly, or would it also be set
implicitly, according to `minibufferp'? If the latter, how would a program
override that implicit behavior?
It could use the same mechanism as now; or, maybe it would
be cleaner to change the lower levels of redisplay to display
the message at the end of the minibuffer when it is selected.
Sorry, I don't understand you, here. Could you elaborate a bit?
next prev parent reply other threads:[~2005-10-06 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 21:58 wrapper fn for message and minibuffer-message? Drew Adams
2005-10-05 15:53 ` Stefan Monnier
2005-10-05 16:23 ` Drew Adams
2005-10-06 5:28 ` Richard M. Stallman
2005-10-06 15:52 ` Drew Adams [this message]
2005-10-07 3:04 ` Richard M. Stallman
2005-10-07 22:29 ` Drew Adams
2005-10-09 18:16 ` Richard M. Stallman
2005-10-09 21:25 ` Drew Adams
2005-10-10 18:06 ` Richard M. Stallman
2005-10-10 19:52 ` Drew Adams
2005-10-15 13:08 ` Juri Linkov
2005-10-15 14:39 ` Drew Adams
2005-10-15 14:57 ` Juri Linkov
2005-10-16 14:40 ` Richard M. Stallman
2005-10-17 8:04 ` Searching in the minibuffer (was: wrapper fn for message and minibuffer-message?) Juri Linkov
2005-10-17 21:57 ` Richard M. Stallman
2005-10-18 8:05 ` Searching in the minibuffer Juri Linkov
2005-10-19 2:43 ` Richard M. Stallman
2005-10-19 15:55 ` Juri Linkov
2005-10-20 4:54 ` Richard M. Stallman
2005-10-21 15:38 ` Juri Linkov
2005-10-21 22:19 ` Richard M. Stallman
2005-10-21 22:30 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICEEBICNAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.