unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org, fgunbin@fastmail.fm, andreyk.mad@gmail.com,
	dgutov@yandex.ru
Subject: Re: Proced signals (was: Change in vc-git ls-files-unknown makes emacs hang)
Date: Sun, 22 Dec 2019 19:02:40 +0200	[thread overview]
Message-ID: <838sn4z427.fsf@gnu.org> (raw)
In-Reply-To: <87imm94msx.fsf_-_@mail.linkov.net> (message from Juri Linkov on Sat, 21 Dec 2019 23:51:18 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: Dmitry Gutov <dgutov@yandex.ru>,  Filipp Gunbin <fgunbin@fastmail.fm>,
>   andreyk.mad@gmail.com,  emacs-devel@gnu.org
> Date: Sat, 21 Dec 2019 23:51:18 +0200
> 
> BTW, why proced.el doesn't support SIGUSR2?  Is this because
> some standard doesn't declare SIGUSR2 as "portable"?

No, we already have there some signals that are less portable than
others.  I guess it wasn't deemed "important" enough; feel free to
add.



  reply	other threads:[~2019-12-22 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 14:16 Change in vc-git ls-files-unknown makes emacs hang Filipp Gunbin
2019-12-19 14:41 ` Dmitry Gutov
2019-12-19 20:44   ` Filipp Gunbin
2019-12-19 22:42     ` Dmitry Gutov
2019-12-20  7:33       ` Eli Zaretskii
2019-12-20 10:52         ` Filipp Gunbin
2019-12-20 14:13           ` Dmitry Gutov
2019-12-20 15:36             ` Filipp Gunbin
2019-12-20 15:40               ` Dmitry Gutov
2019-12-20 17:14                 ` Filipp Gunbin
2019-12-20 22:18                   ` Dmitry Gutov
2019-12-21 21:51         ` Proced signals (was: Change in vc-git ls-files-unknown makes emacs hang) Juri Linkov
2019-12-22 17:02           ` Eli Zaretskii [this message]
2019-12-19 20:45 ` Change in vc-git ls-files-unknown makes emacs hang Stefan Monnier

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=838sn4z427.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andreyk.mad@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=juri@linkov.net \
    /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).