all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Paul Pogonyshev <pogonyshev@gmail.com>, 57684@debbugs.gnu.org
Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair
Date: Fri, 09 Sep 2022 16:20:23 +0000	[thread overview]
Message-ID: <ac8810f15c34d8003e33@heytings.org> (raw)
In-Reply-To: <87bkrowmiw.fsf@gnus.org>


>> This issue is being worked on, see the (not yet finished) 
>> feature/improved-locked-narrowing branch.
>
> Is there much to be done on that branch before merging?
>

I don't know yet.  Not "that much" I think, but there are a number of 
things that need to be fixed/improved.





  reply	other threads:[~2022-09-09 16:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 19:37 bug#57684: locked narrowing breaks existing code without an apparent way to repair Paul Pogonyshev
2022-09-08 19:57 ` Gregory Heytings
2022-09-08 20:30   ` Paul Pogonyshev
2022-09-09  1:46     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 16:16   ` Lars Ingebrigtsen
2022-09-09 16:20     ` Gregory Heytings [this message]
2022-09-13 20:54       ` Paul Pogonyshev
2022-09-13 21:06         ` Gregory Heytings
2022-09-13 21:13           ` Paul Pogonyshev
2022-09-13 21:35             ` Gregory Heytings
2022-09-14  2:34         ` Eli Zaretskii
2022-09-14  9:45           ` Paul Pogonyshev
2022-09-14 11:57             ` Eli Zaretskii
2022-09-16  3:38               ` Richard Stallman
2022-09-16  6:04                 ` Eli Zaretskii
2022-09-17  3:40                   ` Richard Stallman
2022-09-17  6:33                     ` Eli Zaretskii

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=ac8810f15c34d8003e33@heytings.org \
    --to=gregory@heytings.org \
    --cc=57684@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=pogonyshev@gmail.com \
    /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.