From: Ian Nehera <delta29@shaw.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51236@debbugs.gnu.org
Subject: bug#51236: 27.2/28 small typos/faq correction?
Date: Sat, 16 Oct 2021 15:01:22 -0700 [thread overview]
Message-ID: <EC5CB9F7-2076-48E7-9D4D-CFA5CEB23139@shaw.ca> (raw)
In-Reply-To: <834k9hif88.fsf@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.
> 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…
If the old `M-y’ behaviour WON’T be the default long term, then the FAQ should be
change to something along the lines of:
[‘C-y’ and ‘M-y’ work the same in searches as they do in normal editing.] See…
Thanks,
Ian
> On Oct 16, 2021, at 12:46 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Ian Nehera <delta29@shaw.ca>
>> Date: Fri, 15 Oct 2021 22:03:08 -0700
>>
>> Hi, I found a couple small typos in 27.2 that are still present in the source for 28.1.
>
> Thank you for your reports.
>
>> doc/lispref/searching.texi line 2174: missing ’s’ on "describe"
>> - Because the match data normally describe[s] …
>>
>> url-retrieve-synchronously doc-string
>> lisp/url/url.el line 229:
>> - Original: ...or nil if there are no data associated with it (the …
>> - Change V1: there [is] no data ...
>> - Change V2: or nil if [the buffer contains] no data […] (the …
>
> "Data" is plural, so I think using plural form here is non incorrect.
>
>> The other thing I found is that the Emacs FAQ.
>>
>> doc/misc/efaq.texi line 1905:
>> Yanking text in isearch recommends ‘M-y’ for yanking text out of the kill
>> ring. This works, but the cross referenced manual page only mentions
>> the usual ‘C-y’ method with ‘M-y’ yanking previous kills. Is the manual
>> out of date or should the FAQ be updated?
>
> 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?
>
> Thanks again for your interest in Emacs documentation.
next prev parent reply other threads:[~2021-10-16 22:01 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 [this message]
2021-10-17 6:10 ` Eli Zaretskii
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=EC5CB9F7-2076-48E7-9D4D-CFA5CEB23139@shaw.ca \
--to=delta29@shaw.ca \
--cc=51236@debbugs.gnu.org \
--cc=eliz@gnu.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).