9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Curious about faces and showmail
Date: Wed,  3 Oct 2007 16:36:10 -0400	[thread overview]
Message-ID: <20071003203545.4B1F81E8C26@holo.morphisms.net> (raw)
In-Reply-To: <fe9690e056e532a91a5ab387af83f242@comcast.net>

> Turns out this had kind of unpredictable behavior. In the
> times I tried it 3-5 emails would open, but I couldn't really
> predict which ones it would be. Just on a hunch, I added
> sleep(250) under showmail() in the for() loop, and so far it
> works. I was just wondering why showmail() needs that
> delay and if such a need is common. I did a quick grep for
> sleep() in sources, and, while it shows up, it doesn't seem
> especially common. How does one know when one needs it?

easy: you only need to insert sleeps
when the surrounding code is broken.

that said, i don't know which of the
surrounding programs is broken.

you can start "cat /mnt/plumb/showmail"
in a new window and then do your sleep-less
click and see if all the plumbing messages
show up.  that will tell you whether the
plumber is dropping messages.

if the plumber is not dropping messages,
the next thing to do is see why the messages
aren't making your mail reader show mail.

are you using acme mail or nedmail?
probably the latter.  in that case the plumber
is supposed to be starting a window for every
message.  maybe sometimes the nedmail 
fails and the window disappears before you
get a chance to see it.

russ



  reply	other threads:[~2007-10-03 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 15:55 Gregory Pavelcak
2007-10-03 20:36 ` Russ Cox [this message]
2007-10-03 21:55   ` erik quanstrom
2007-10-04  0:33   ` Gregory Pavelcak

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071003203545.4B1F81E8C26@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).