unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 56423@debbugs.gnu.org
Subject: bug#56423: 29.0.50; Hi-lock in dired broken by toggling wdired-mode
Date: Thu, 07 Jul 2022 16:29:15 +0300	[thread overview]
Message-ID: <835yk959w4.fsf@gnu.org> (raw)
In-Reply-To: <87bku15g5e.fsf@web.de> (message from Michael Heerdegen on Thu, 07 Jul 2022 13:14:05 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 56423@debbugs.gnu.org
> Date: Thu, 07 Jul 2022 13:14:05 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > It sounds like you described the "normal" ways of returning?  I mostly
> > had in mind the "abnormal" ones, via one of the non-local exits.  If
> > that is possible, we should set up unwind-protect form.
> 
> Ah - ok.  But AFAIK there is no non-local way of exiting possible.

Not even with C-g at some un-opportune moment?  If so, there's no
problem, indeed.





  reply	other threads:[~2022-07-07 13:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 16:22 bug#56423: 29.0.50; Hi-lock in dired broken by toggling wdired-mode Michael Heerdegen
2022-07-06 18:58 ` Michael Heerdegen
2022-07-06 19:19   ` Michael Heerdegen
2022-07-07  5:35     ` Eli Zaretskii
2022-07-07 10:26       ` Michael Heerdegen
2022-07-07 10:35         ` Eli Zaretskii
2022-07-07 11:14           ` Michael Heerdegen
2022-07-07 13:29             ` Eli Zaretskii [this message]
2022-07-07 15:09               ` Michael Heerdegen
2022-07-07 15:19                 ` Michael Heerdegen
2022-07-07 16:03                   ` Eli Zaretskii
2022-07-08 12:04                     ` Michael Heerdegen
2022-07-08 12:22                       ` Eli Zaretskii
2022-07-08 12:57                         ` Michael Heerdegen
2022-07-08 12:59                           ` 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

  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=835yk959w4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56423@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).