From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: arthur.miller@live.com, 50646@debbugs.gnu.org
Subject: bug#50646: 28.0.50; narrow-to-defun sometimes narrows to wrong defun
Date: Sun, 19 Sep 2021 15:17:28 +0300 [thread overview]
Message-ID: <83o88o4v53.fsf@gnu.org> (raw)
In-Reply-To: <c30c35d6a8f96d0b62bac989fd9fd56f@webmail.orcon.net.nz> (message from Phil Sainty on Mon, 20 Sep 2021 00:06:26 +1200)
> Date: Mon, 20 Sep 2021 00:06:26 +1200
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: arthur.miller@live.com, 50646@debbugs.gnu.org
>
> On 2021-09-20 00:01, Eli Zaretskii wrote:
> > What "other circumstances"? This phrase only makes sense when
> > "some circumstances" were described before it.
>
> Circumstances other than `insert-file-contents-literally' was
> the intended meaning, but evidentially that phrasing can also be
> confusing.
Then I suggest to mention insert-file-contents and other functions (if
any) that do this explicitly. Something like
This is contrary to other functions, like `insert-file-contents',
which may modify a buffer in several ways after ...
next prev parent reply other threads:[~2021-09-19 12:17 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 [this message]
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 ` bug#50646: [External] : " Drew Adams
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
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=83o88o4v53.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50646@debbugs.gnu.org \
--cc=arthur.miller@live.com \
--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 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).