From: Richard Stallman <rms@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Search minibuffer history
Date: Mon, 16 Jul 2007 11:49:41 -0400 [thread overview]
Message-ID: <E1IASpR-00011a-QT@fencepost.gnu.org> (raw)
In-Reply-To: <87tzs55t7o.fsf@jurta.org> (message from Juri Linkov on Sun, 15 Jul 2007 23:04:43 +0300)
It is getting pretty good now, but some of these doc strings need
clarification.
+ (defun minibuffer-history-isearch-end ()
+ "Clean up the minibuffer after terminating an incremental search."
That doc string needs to identify the usage more precisely.
This is not used after just any isearch, only after a specific kind.
+ (defun minibuffer-history-isearch-search ()
+ "Return the function for isearch that searches in the minibuffer history."
I can't understand that sentence.
+ (defun minibuffer-history-isearch-message (&optional c-q-hack ellipsis)
+ "Display the minibuffer history search prompt.
+ It is either the standard isearch prompt displayed by `isearch-message'
+ in case of a search error, or an overlay with the isearch prompt displayed
+ over the original minibuffer prompt in case of successful search."
I don't understand "it is either" in that doc string.
Are you talking about _how_ this function does its job?
If so, please say that explicitly.
next prev parent reply other threads:[~2007-07-16 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 20:59 Search minibuffer history Juri Linkov
2007-07-10 5:38 ` Richard Stallman
2007-07-10 13:14 ` Juri Linkov
2007-07-10 22:01 ` Richard Stallman
2007-07-10 22:31 ` Juri Linkov
2007-07-11 21:04 ` Richard Stallman
2007-07-11 22:55 ` Juri Linkov
2007-07-12 21:23 ` Richard Stallman
2007-07-15 20:04 ` Juri Linkov
2007-07-16 15:05 ` Stefan Monnier
2007-07-16 20:54 ` Juri Linkov
2007-07-16 15:49 ` Richard Stallman [this message]
2007-07-21 18:17 ` Juri Linkov
2007-07-11 21:04 ` 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=E1IASpR-00011a-QT@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).