unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Juri Linkov <juri@jurta.org>
Cc: 12655@debbugs.gnu.org
Subject: bug#12655: 24.2; Cannot discover automatic-all or other multi-buffer replacement commands
Date: Mon, 15 Oct 2012 19:36:20 +0100	[thread overview]
Message-ID: <CAOnWdoiJGG2UwbZjsgB=s99J3UNbDW-iHnW8M8hjb5=Ux+Ax_Q@mail.gmail.com> (raw)
In-Reply-To: <87a9vnydgb.fsf@mail.jurta.org>

On 15 October 2012 16:14, Juri Linkov <juri@jurta.org> wrote:
>
> But you mentioned `C-h m' (`describe-mode').
> Do you mean to describe this feature in the docstrings of
> `tags-query-replace', `dired-do-query-replace-regexp',
> `vc-dir-query-replace-regexp' and `reftex-query-replace-document' ?

No. That would seem a bad place, as it would duplicate information
manually. It should be somewhere that is controlled by the multifile
map being hooked into the keymap. The place that documents the current
keymap, i.e. the mode help, seems to be a logical place for this.

> `automatic-all' is already documented in (info "(elisp) Search and Replace")

That is elisp coding documentation, not Emacs user documentation.

> Do you think it should be also documented in (info "(emacs) Tags Search") ?
>
> Then (info "(emacs) VC Directory Commands") should link to the node
> (info "(emacs) Tags Search") like (info "(emacs) Operating on Files") already does.
> With these links, this feature could be documented just in one Info node.

Might it be more logical to mention it in the documentation "(emacs)
Query Replace", where all the other keystrokes are documented?

-- 
http://rrt.sc3d.org





  reply	other threads:[~2012-10-15 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 11:40 bug#12655: 24.2; Cannot discover automatic-all or other multi-buffer replacement commands Reuben Thomas
2012-10-15 15:14 ` Juri Linkov
2012-10-15 18:36   ` Reuben Thomas [this message]
2012-10-15 22:16     ` Juri Linkov
2012-10-15 22:29       ` Reuben Thomas

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='CAOnWdoiJGG2UwbZjsgB=s99J3UNbDW-iHnW8M8hjb5=Ux+Ax_Q@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=12655@debbugs.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).