From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: signal-USR1-hook woes
Date: 08 Sep 2003 08:27:09 +0200 [thread overview]
Message-ID: <ud6eb4wxu.fsf@elta.co.il> (raw)
In-Reply-To: <3f5bd95c$0$49102$e4fe514c@news.xs4all.nl> (bjdouma@xs2.xs4all.nl)
> Newsgroups: gnu.emacs.help
> From: bjdouma@xs2.xs4all.nl (Bauke Jan Douma)
>
> (message "list-emacs-open-files: done")
> (let (
> (buf_list (buffer-list))
> )
Yikes! Why do you insist on formatting Lisp code as if it were C or
(God forbid) Pascal? It makes it very hard to read and comprehend.
> Alas, it doesn't work. It does work from within emacs by
> calling M-x list-emacs-open-files or by eval'ing
> (signal-process (emacs-pid) 10).
> When doing kill -USR1 <emacs-pid>, all that happens is I get a
> visual bell, the file is not written.
> An strace reveals that the signal is sent allright.
>
> I am doing something wrong, but what?
Well, is your function at all called? Does the message you produce at
the beginning of your function gets inserted into the *Messages*
buffer?
In other words, the first question you should answer is: is the
signal delivered to Emacs and handled, but your function has a bug,
or is the signal itself handled incorrectly by Emacs?
And it will help immensely if you tell what version of Emacs is that
and on what platform.
next prev parent reply other threads:[~2003-09-08 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 1:20 signal-USR1-hook woes Bauke Jan Douma
2003-09-08 6:27 ` Eli Zaretskii [this message]
[not found] ` <mailman.344.1062998727.18171.help-gnu-emacs@gnu.org>
2004-02-29 5:50 ` Ed L Cashin
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=ud6eb4wxu.fsf@elta.co.il \
--to=eliz@elta.co.il \
/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.
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).