unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Re: Infinite loop in pop3-retr
Date: Mon, 30 May 2011 22:12:58 -0300	[thread overview]
Message-ID: <jwvtycbvfkc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3k4d86r5u.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 30 May 2011 19:21:01 +0200")

>>> Firstly, I think that probably there is a simpler way to check if
>>> process is active than by testing process status but I don't know that.
>> Actually, no, this is the way to do it.
> Which reminds me.  Instead of sprinkling all the code with

>   (memq (process-status process) '(open run))

> which isn't very...  pretty...  (there's probably hundreds variations of
> these invocations in Gnus and the other network oriented packages)
> wouldn't it be nice if we had a nice, simple function like
> `process-alive-p' or something like that?  It would just basically be

> (defun process-alive-p (process)
>   (memq (process-status process)
>         '(run open listen connect)))
        
Sounds fine to me.  Tho I wonder if `stop' should be in this list.


        Stefan



  reply	other threads:[~2011-05-31  1:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  8:43 Infinite loop in pop3-retr tomga
2011-05-27  0:35 ` Stefan Monnier
2011-05-27  9:33   ` Tomasz Gajewski
2011-05-27 12:55     ` Stefan Monnier
2011-05-30 17:21       ` Lars Magne Ingebrigtsen
2011-05-31  1:12         ` Stefan Monnier [this message]
2011-05-31 18:22           ` Lars Magne Ingebrigtsen
2011-05-31 21:45             ` Stefan Monnier
2011-06-01 11:48               ` Lars Magne Ingebrigtsen
2011-06-12 22:43                 ` Chong Yidong
2011-06-14 14:58                   ` Lars Magne Ingebrigtsen
2011-05-30 17:18     ` Lars Magne Ingebrigtsen
2011-05-31  6:36       ` Tomasz Gajewski

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=jwvtycbvfkc.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).