unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ram Bhamidipaty <rbhamidipaty@roku.com>
Cc: 22220@debbugs.gnu.org
Subject: bug#22220: 24.5; no documentation for default process sentinel
Date: Wed, 23 Dec 2015 05:40:00 +0200	[thread overview]
Message-ID: <83r3idq1db.fsf@gnu.org> (raw)
In-Reply-To: <BLUPR0101MB155319D64C61E68865272098BAE50@BLUPR0101MB1553.prod.exchangelabs.com> (message from Ram Bhamidipaty on Tue, 22 Dec 2015 23:25:28 +0000)

> From: Ram Bhamidipaty <rbhamidipaty@roku.com>
> CC: "22220@debbugs.gnu.org" <22220@debbugs.gnu.org>
> Date: Tue, 22 Dec 2015 23:25:28 +0000
> 
> It would be nice if the default process sentinel were explicitly documented - at least the name and formal description. 

The description is what I cited from the manual; there's nothing else
to be said about that, because that's all that the default sentinel
does.

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?





  reply	other threads:[~2015-12-23  3:40 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 [this message]
2015-12-23 17:34       ` John Wiegley
2015-12-23 17:45         ` Ram Bhamidipaty
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=83r3idq1db.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22220@debbugs.gnu.org \
    --cc=rbhamidipaty@roku.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).