From: Bart Schaefer <schaefer@brasslantern.com>
To: Russell Hoover <rj@panix.com>, zsh-users@sunsite.dk
Subject: Re: New mail notification not working
Date: Sun, 9 Sep 2001 18:25:46 +0000 [thread overview]
Message-ID: <1010909182546.ZM21902@candle.brasslantern.com> (raw)
In-Reply-To: <20010909133309.A3317@panix.com>
On Sep 9, 1:33pm, Russell Hoover wrote:
} Subject: Re: New mail notification not working
}
} Thanks -- I asked that because the last sentence for the ``mailpath''
} entry in the manual
} [...] might well lead one to believe that, in the case of maildirs, unless
} I specified the ``new'' subdir, zsh would check the ``tmp'' and ``cur''
} subdirs as well
The manual doesn't tell anything about maildir support, mostly because
the person who contibuted the mailstat code didn't include a man patch
to go with it. One side-effect of that code is that when checking new
mail, zsh can't tell that maildirs are directories -- mailstat returns
data as if the folder were one huge file. That's why it's so expensive
in the absence of the (broken) optimization.
} > Anyway, mailstat() is using a single static structure to keep track of
} > the last-modified time of the maildir "new" subdir. This means that it
} > only works correctly if you have exactly one maildir directory in your
} > mailpath
}
} To understand this fully I seem to need to make a distinction: you say
} "exactly one maildir directory in your mailpath" -- Does that mean that
} I must have only one *defined* in my mailpath, or only one in existence?
Exactly one named in the value of the mailpath parameter.
} (I'd be quite satisfied, for now at least, to have notification working
} just for my inbox.)
[...]
} Shouldn't notification be working if I just have either of these defined
} in my .zshrc:
}
} export MAIL=$HOME/.mailspool/rj
}
} or: mailpath=($HOME/.mailspool/rj'?New mail has arrived.')
That should work, but see below.
} (btw, should the opening quote-mark above be where it is, or should it
} be just before ``$HOME'', or does it matter?)
It does matter; you have it right.
} (a) From within either mutt's index or pager, I press `e' in mutt
} to edit the raw message;
If you have mutt (or any of several other mail programs) running
continuously in another window, zsh won't regularly notify you of new
mail no matter what the mailbox format is, because there is a race
between mutt and the shell to see which one finds the new message
first. Once mutt finds the message and adds it to its index, the
file access time will have changed and zsh won't consider the message
to be new any more.
If your maildirs are on NFS-mounted file systems, NFS attribute caching
can also affect whether zsh correctly detects new mail.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-09-09 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-09 17:33 Russell Hoover
2001-09-09 18:25 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-19 18:39 Russell Hoover
2001-08-19 18:55 ` Bart Schaefer
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=1010909182546.ZM21902@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=rj@panix.com \
--cc=zsh-users@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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).