all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 55050@debbugs.gnu.org
Subject: bug#55050: 27.2; Doc strings for commands that do query-replacements
Date: Thu, 21 Apr 2022 13:50:24 +0200	[thread overview]
Message-ID: <87v8v27j0f.fsf@gnus.org> (raw)
In-Reply-To: <SJ0PR10MB5488E770D0948DFA9421F699F3F49@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Thu, 21 Apr 2022 02:46:16 +0000")

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

> This is about the doc of commands, such as
> `dired-do-find-regexp-and-replace', that use a query-replace dialog.
> There are a bunch of such commands now.  For the most part, they don't
> tell you anything about what to expect, in terms of a dialog.  In
> particular, they don't reference the doc of `query-replace`, which is
> (at least) where the dialog should be described.

I've now linked the latter from the doc string of the former.

> The only saving grace is that there's a prompt that suggests that if you
> hit `?' you might get some information about what you can do.  Assuming
> you notice that prompt, of course.
>
> The doc of all such commands should, directly or indirectly, tell you
> about the keys you can use and what they do - what you learn by hitting
> `?'.

I don't think that would be particularly useful.

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





  reply	other threads:[~2022-04-21 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  2:46 bug#55050: 27.2; Doc strings for commands that do query-replacements Drew Adams
2022-04-21 11:50 ` Lars Ingebrigtsen [this message]
2022-04-21 12:03 ` Eli Zaretskii
2022-04-21 16:04   ` Juri Linkov
2022-04-21 18:57     ` Eli Zaretskii

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=87v8v27j0f.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55050@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 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.