From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: wrapper fn for message and minibuffer-message?
Date: Sun, 9 Oct 2005 14:25:21 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEEDECNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1EOfj1-0006KO-3z@fencepost.gnu.org>
I still have the same question: Would the variable also be
set to non-nil implicitly, whenever `minibufferp'?
(That was the behavior I originally suggested: use
`minibuffer-message' when the minibuffer is active.)
That is certainly not what I have in mind. These are both useful
operations in the minibuffer. The individual command would bind
`minibuffer-message-at-end' to non-nil when it wants the message to
appear at the end of the minibuffer.
Do you mean that low-level redisplay would, in effect, use
`minibuffer-message' when the minibuffer is active and
`message' otherwise?
No, it would implement the behavior of `minibuffer-message'
when `minibuffer-message-at-end' is non-nil.
OK. If I understand you correctly, you would keep functions `message' and
`minibuffer-message' as they are now. You would not eliminate either
function. The former's default behavior would use nil for
`minibuffer-message-at-end'; the latter would use non-nil.
The only change you would make would be to introduce the variable, so that a
user could bind `minibuffer-message-at-end' to flip the behavior of either
function from its default behavior. When `minibuffer-message-at-end' is nil,
the minibuffer content is temporarily replaced by the message (as is done
today by `message'); when it is non-nil, the content remains, and the
message is appended to it.
You are not interested in any wrapper function that uses the minibuffer
state (active or inactive) to determine the `minibuffer-message-at-end'
behavior.
Is that correct?
I ask because it's still not clear to me what you propose. You said that the
variable allowed a "cleaner interface for the feature", and I thought the
feature in question was the one I originally suggested: using the minibuffer
state to determine the `minibuffer-message-at-end' behavior.
next prev parent reply other threads:[~2005-10-09 21:25 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
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 [this message]
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=DNEMKBNJBGPAOPIJOOICEEDECNAA.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.