From: "Richard M. Stallman" <rms@gnu.org>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: Searching in the minibuffer
Date: Fri, 21 Oct 2005 18:19:56 -0400 [thread overview]
Message-ID: <E1ET5Ey-0003mj-61@fencepost.gnu.org> (raw)
In-Reply-To: <87vezrvstv.fsf@jurta.org> (message from Juri Linkov on Fri, 21 Oct 2005 18:38:04 +0300)
`minibuffer-message'
doesn't allow lazy-highlighting timers to start.
Clearly that could be fixed. The real question is whether it is
useful to display the isearch prompt at the end in that way. If that
is useful, changing the code to avoid these minor problems will not be
hard. Don't think in terms of using the existing `minibuffer-message'
function's code.
next prev parent reply other threads:[~2005-10-21 22:19 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
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 [this message]
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
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=E1ET5Ey-0003mj-61@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).