From: Eli Zaretskii <eliz@gnu.org>
To: Ian Nehera <delta29@shaw.ca>
Cc: 51236@debbugs.gnu.org
Subject: bug#51236: 27.2/28 small typos/faq correction?
Date: Sun, 17 Oct 2021 09:10:22 +0300 [thread overview]
Message-ID: <838rysgp0x.fsf@gnu.org> (raw)
In-Reply-To: <EC5CB9F7-2076-48E7-9D4D-CFA5CEB23139@shaw.ca> (message from Ian Nehera on Sat, 16 Oct 2021 15:01:22 -0700)
> From: Ian Nehera <delta29@shaw.ca>
> Date: Sat, 16 Oct 2021 15:01:22 -0700
> Cc: 51236@debbugs.gnu.org
>
> > On Oct 16, 2021, at 12:46 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > "Data" is plural, so I think using plural form here is non incorrect.
>
> It’s not incorrect, it just jumped out to me when I read it. Similar to:
> - There is no data on the disk.
> as opposed to:
> - There are no data on the disk.
> "Data is” and “data are" are both technically correct so I guess this
> one's more of a style choice than a typo.
Yes.
> > What would you suggest to update and how? Both C-y and M-y are
> > mentioned in the manual, and the manual is always more detailed than
> > any other documentation. Could you state the problem you see with the
> > current text?
>
> The cross-referenced manual page (Isearch Yanking) doesn’t mention that
> `isearch-yank-pop’ (27.2) can yank text when the previous command wasn’t
> a yank. The only place it gets mentioned is in a comment in the source:
>
> ;; Fall back on `isearch-yank-kill' for the benefits of people
> ;; who are used to the old behavior of `M-y' in isearch mode. In
> ;; future, this fallback may be changed if we ever change
> ;; `yank-pop' to do something like the kill-ring-browser.
>
> A separate function was made for the `kill-ring-browser’ functionality in 28.1
> (isearch-yank-pop) but the old behaviour is still the default (isearch-yank-pop-only).
> If that’s going to be the case long term, there should be a note of it in the manual.
> Maybe something like:
>
> …usual ‘M-y’ (‘yank-pop’) command (see Yanking). [However unlike the usual
> ‘M-y’, ‘isearch-yank-pop’ will act like ‘C-y’ when the previous command wasn’t
> a yank. That is, it will yank the most recent kill.] Clicking ‘mouse-2’ in the…
I see no reason to have those details in the manual. Many Emacs
commands have some DWIM-ish aspects, and we don't always document all
of them in such detail.
Does anyone else think it's important to have those details in the
manual?
next prev parent reply other threads:[~2021-10-17 6:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 5:03 bug#51236: 27.2/28 small typos/faq correction? Ian Nehera
2021-10-16 7:46 ` Eli Zaretskii
2021-10-16 22:01 ` Ian Nehera
2021-10-17 6:10 ` Eli Zaretskii [this message]
2021-10-18 7:35 ` Lars Ingebrigtsen
2021-10-18 21:44 ` Ian Nehera
2021-10-19 2:34 ` Eli Zaretskii
2021-10-19 18:13 ` Ian Nehera
2021-10-20 18:27 ` Stefan Kangas
2021-10-20 20:44 ` Ian Nehera
2021-10-20 21:02 ` Stefan Kangas
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=838rysgp0x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51236@debbugs.gnu.org \
--cc=delta29@shaw.ca \
/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).