unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: graceful shutdown of non-interactive Elisp program
Date: Sat, 13 Jun 2020 23:42:51 +0200	[thread overview]
Message-ID: <CAG7BpaqQ+KZro+v12x3y_v3wcQnB7wnP6qQ66sWDRx7EXEhEkw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

Hi,

I'm trying to make a Elisp program that is run in a non-interactive mode,
i.e. essentially as `emacs --batch --load myfile.el'. A normal way to
shutdown terminal programs is with C-c, which is expected to be "graceful"
shutdown, e.g. the program still has a chance to save files etc.

However, with Elisp I'm not sure how to achieve that except for constantly
modifying `kill-emacs-hook', which would be a nightmare from coding
perspective.

Naively I would expect this print "GOING DOWN" when aborted with C-c:

    $ emacs --batch --eval "(unwind-protect (while t) (message \"GOING
DOWN\"))"

For example, Python's handler of SIGINT raises an exception within the
program, which unwinds the stack as usual and, unless caught, cause program
termination after cleaning up as expected (e.g. running all `finally'
clauses and closing all `with' context managers). However, in Elisp, as I
understand, there is no way to have a say in handling SIGINT other than
adding a function to `kill-emacs-hook'.

Is that correct, or am I missing something here?

Paul

[-- Attachment #2: Type: text/html, Size: 1560 bytes --]

             reply	other threads:[~2020-06-13 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 21:42 Paul Pogonyshev [this message]
2020-06-13 22:59 ` graceful shutdown of non-interactive Elisp program Joost Kremers
2020-06-14 15:01 ` Eli Zaretskii
2020-06-14 16:47   ` Paul Pogonyshev

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=CAG7BpaqQ+KZro+v12x3y_v3wcQnB7wnP6qQ66sWDRx7EXEhEkw@mail.gmail.com \
    --to=pogonyshev@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).