From: Ram Bhamidipaty <rbhamidipaty@roku.com>
To: John Wiegley <jwiegley@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "22220@debbugs.gnu.org" <22220@debbugs.gnu.org>
Subject: bug#22220: 24.5; no documentation for default process sentinel
Date: Wed, 23 Dec 2015 17:45:22 +0000 [thread overview]
Message-ID: <BLUPR0101MB15538305853C52F7681D187EBAE60@BLUPR0101MB1553.prod.exchangelabs.com> (raw)
In-Reply-To: <m2k2o59ii6.fsf@newartisans.com>
This is what I ran into: I am working on some code using the emacs process facility. And I started seeing messages (from the default sentinel) that I did not expect. When I _skimmed_ through the sentinel section I did not notice that a default sentinel is added to all processes. I acknowledge that skimming the docs was not the right thing to do - since I missed the fact that there is a default sentinel.
From my point of view - I would have been nice - if the default sentinel info were a bit more prominent.
So - I proposed that the name and behavior of the default sentinel be documented. It might not be needed - in the sense that the name itself is not required - but if there were a block of text in the info section like "-- Function: xxx default-sentinel" that would be more prominent - and probably harder to miss.
-Ram
-----Original Message-----
From: John Wiegley [mailto:jwiegley@gmail.com]
Sent: Wednesday, December 23, 2015 9:34 AM
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ram Bhamidipaty <rbhamidipaty@roku.com>; 22220@debbugs.gnu.org
Subject: Re: bug#22220: 24.5; no documentation for default process sentinel
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> It would be nice if the default process sentinel were explicitly documented
>> - at least the name and formal description.
> As for the name, why is that important? You can always get it installed for
> the process using nil as the argument to set-process-sentinel, and the
> implementation is in C, so how would the name help?
I must admit to a similar confusion. Aside from the fact that more could be
said: does more need to be said?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2015-12-23 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 1:20 bug#22220: 24.5; no documentation for default process sentinel Ram Bhamidipaty
2015-12-22 17:12 ` Eli Zaretskii
2015-12-22 23:25 ` Ram Bhamidipaty
2015-12-23 3:40 ` Eli Zaretskii
2015-12-23 17:34 ` John Wiegley
2015-12-23 17:45 ` Ram Bhamidipaty [this message]
2015-12-23 17:56 ` Eli Zaretskii
2015-12-23 18:05 ` Ram Bhamidipaty
2015-12-23 18:15 ` John Wiegley
2015-12-23 17:54 ` Ram Bhamidipaty
2015-12-23 18:20 ` 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=BLUPR0101MB15538305853C52F7681D187EBAE60@BLUPR0101MB1553.prod.exchangelabs.com \
--to=rbhamidipaty@roku.com \
--cc=22220@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.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).