From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Phil Sainty <psainty@orcon.net.nz>
Cc: "arthur.miller@live.com" <arthur.miller@live.com>,
"50646@debbugs.gnu.org" <50646@debbugs.gnu.org>
Subject: bug#50646: [External] : bug#50646: 28.0.50; narrow-to-defun sometimes narrows to wrong defun
Date: Sun, 19 Sep 2021 15:25:06 +0000 [thread overview]
Message-ID: <SJ0PR10MB54880EF54727244A5045E112F3DF9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83o88o4v53.fsf@gnu.org>
> Something like
>
> This is contrary to other functions, like `insert-file-contents',
> which may modify a buffer in several ways after ...
[very minor nit]:
Use "such as", not "like", here.
"Such as" explicitly includes `insert-file-contents'
among the "other functions". "Like" does not
necessarily include it.
But in practice, many, maybe most, people don't and
won't make/understand/notice the difference.
https://www.grammarbank.com/such-as-vs-like.html
https://grammar.yourdictionary.com/vs/how-such-as-vs-like-are-different-and-which-to-choose.html
https://www.quickanddirtytips.com/education/grammar/like-versus-such-as
next prev parent reply other threads:[~2021-09-19 15:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 17:06 bug#50646: 28.0.50; narrow-to-defun sometimes narrows to wrong defun arthur.miller
2021-09-18 14:09 ` Lars Ingebrigtsen
2021-09-18 17:27 ` Arthur Miller
2021-09-18 18:34 ` Arthur Miller
2021-09-19 8:34 ` Arthur Miller
2021-09-19 3:41 ` Phil Sainty
2021-09-19 6:36 ` Arthur Miller
2021-09-19 10:56 ` Phil Sainty
2021-09-19 20:02 ` Arthur Miller
2021-09-19 8:33 ` Arthur Miller
2021-09-19 10:04 ` Phil Sainty
2021-09-19 12:01 ` Eli Zaretskii
2021-09-19 12:06 ` Phil Sainty
2021-09-19 12:17 ` Eli Zaretskii
2021-09-19 12:53 ` Phil Sainty
2021-09-19 13:43 ` Eli Zaretskii
2021-09-19 14:21 ` Phil Sainty
2021-09-19 15:22 ` Eli Zaretskii
2021-09-19 15:25 ` Drew Adams [this message]
2021-09-19 19:57 ` Arthur Miller
2021-09-20 6:02 ` Lars Ingebrigtsen
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=SJ0PR10MB54880EF54727244A5045E112F3DF9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=50646@debbugs.gnu.org \
--cc=arthur.miller@live.com \
--cc=eliz@gnu.org \
--cc=psainty@orcon.net.nz \
/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.