From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: sunlin7@hotmail.com, 74881@debbugs.gnu.org
Subject: bug#74881: 31.0.50; [PATCH] * lisp/vc/ediff-util.el: Remove temp files on kill-emacs
Date: Sun, 29 Dec 2024 09:04:47 +0200 [thread overview]
Message-ID: <86jzbjq8a8.fsf@gnu.org> (raw)
In-Reply-To: <875xn3jm1x.fsf@web.de> (message from Michael Heerdegen on Sun, 29 Dec 2024 02:49:14 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, "74881@debbugs.gnu.org"
> <74881@debbugs.gnu.org>
> Date: Sun, 29 Dec 2024 02:49:14 +0100
>
> Second: Can we move the `ignore-errors' inwards so that an error in one
> case doesn't abort the complete loop?
Binding inhibit-interaction non-nil could cause the body signal an
error, so this should be taken into account if we move ignore-errors
inwards. This code must NOT signal any errors, ever. Which AFAIU
means that if we want ignore-errors not to abort the rest of the loop
(why not, btw? these are just temporary files, after all), we should
redesign this loop such that it catches the errors and continues with
the rest of the buffers.
> > ;;; Setup functions
> >
> > @@ -488,6 +496,7 @@ ediff-setup
> > (if (ediff-buffer-live-p ediff-meta-buffer)
> > (ediff-update-meta-buffer
> > ediff-meta-buffer nil ediff-meta-session-number))
> > + (add-hook 'kill-emacs-hook #'ediff--delete-temp-files-on-kill-emacs)
>
> Would it be ok to avoid the above loop completely by using the buffer
> local version of `kill-emacs-hook' instead?
You assume that the temporary Ediff files are always visited in some
buffer? Is that assumption true?
next prev parent reply other threads:[~2024-12-29 7:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 5:59 bug#74881: 31.0.50; [PATCH] * lisp/vc/ediff-util.el: Remove temp files on kill-emacs Lin Sun
2024-12-15 8:04 ` Eli Zaretskii
2024-12-15 17:25 ` Lin Sun
2024-12-27 5:38 ` Lin Sun
2024-12-27 8:10 ` Eli Zaretskii
2024-12-27 17:34 ` Lin Sun
2024-12-28 7:38 ` Eli Zaretskii
2024-12-28 8:04 ` Lin Sun
2024-12-28 12:41 ` Eli Zaretskii
2024-12-28 17:40 ` Lin Sun
2024-12-29 1:49 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 2:25 ` Lin Sun
2024-12-30 1:37 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 2:07 ` Lin Sun
2024-12-30 22:37 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 7:04 ` Eli Zaretskii [this message]
2024-12-29 23:34 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 13:02 ` Eli Zaretskii
2024-12-30 22:34 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86jzbjq8a8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74881@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=sunlin7@hotmail.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 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).