unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8682@debbugs.gnu.org
Subject: bug#8682: 24.0.50; doc strings of `isearch-mode', `isearch-forward', etc.
Date: Fri, 15 Jul 2011 15:40:06 +0200	[thread overview]
Message-ID: <m3y5zz8xxl.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <CC502D3749BA4CA9B1D137888A2C40E8@us.oracle.com> (Drew Adams's message of "Tue, 17 May 2011 07:25:05 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> 1. At a minimum, the doc string of `isearch-mode' should say something
> like this:
>
> FORWARD non-nil means forward search; nil means backward search.
> REGEXP t means regexp search; nil means literal search.
> OP-FUN means ???????
> RECURSIVE-EDIT non-nil means recursive edit for a modal search.
> WORD-P non-nil means word search; nil means ignore word boundaries.

It's an internal function.  If you're not an isearch hacker, you'll
never see it, and if you are, you will know what those parameters mean.
The only thing that's useful in that doc string is the thing that's
already there, and which you want removed:

> And you can remove this sentence from the doc string - a function's doc
> should, in general, not mention callers:
>
> "It is called by the function `isearch-forward' and other related
> functions."

> 2. Doc strings of `isearch-forward' etc. also need to describe their
> args.  E.g. 
>
> Non-interactively:
> REGEXP-P means...
> NO-RECURSIVE-EDIT means...

I think any reasonable person would guess that REGEXP-P means "it's a
regexp", and NO-RECURSIVE-EDIT means "we're not in a recursive edit".

So I'm closing this report.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  parent reply	other threads:[~2011-07-15 13:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 14:25 bug#8682: 24.0.50; doc strings of `isearch-mode', `isearch-forward', etc Drew Adams
2011-05-17 14:39 ` Stefan Monnier
2011-05-17 14:46   ` Drew Adams
2011-05-17 17:32     ` Stefan Monnier
2011-05-17 19:12       ` Drew Adams
2011-07-15 13:40 ` Lars Magne Ingebrigtsen [this message]
2011-07-15 15:06   ` Drew Adams
2011-07-15 16:56     ` Juanma Barranquero
2011-07-15 18:30       ` Drew Adams
2011-07-15 14:43 ` Drew Adams
2011-07-15 15:02   ` Lars Magne Ingebrigtsen
2011-07-15 15:02   ` Lars Magne Ingebrigtsen
2011-07-18 14:06   ` Stefan Monnier
2011-07-18 14:13     ` Drew Adams
2013-05-20 22:50       ` Juri Linkov

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=m3y5zz8xxl.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=8682@debbugs.gnu.org \
    --cc=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 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).