home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!pavo.csi.cam.ac.uk!camcus!ph10
- From: ph10@cus.cam.ac.uk (Philip Hazel)
- Newsgroups: comp.mail.elm
- Subject: Re: X11R5 xbiff and elm (FYI)
- Message-ID: <1992Sep15.091417.16715@infodev.cam.ac.uk>
- Date: 15 Sep 92 09:14:17 GMT
- References: <183514@pyramid.pyramid.com>
- Sender: news@infodev.cam.ac.uk (USENET news)
- Organization: University of Cambridge Computing Service
- Lines: 25
- Nntp-Posting-Host: bootes.cus.cam.ac.uk
-
- In article <183514@pyramid.pyramid.com>, bms@penguin.eng.pyramid.com (Bruce Schlobohm) writes:
- |>
- [...]
- |> So here is what was tripping me up:
-
- It tripped me too.
-
- |> I would iconify the xterm window which was running my elm session, and
- |> walk away from my desk. Upon returning, I would check the xbiff picture,
- |> notice that no new mail had arrived, and would continue to work in one
- |> of my other windows. At some point I would restore the elm window,
- |> and be surprised to see that new mail had arrived, sometimes hours earlier.
- [...]
- |> The solution for elm, is to set "timeout = 0" in ~/.elm/elmrc.
- |> This will prevent elm from scanning for new mail when you aren't
- |> actively entering elm commands.
-
- An alternative solution, if you want elm to have all the new messages waiting
- for you when you open up the window again, is to continue to run the X11R4
- version of xbiff.
-
- --
- Internet: P.Hazel@ucs.cam.ac.uk University Computing Service,
- JANET: P.Hazel@uk.ac.cam.ucs Computer Laboratory, Pembroke St,
- Phone: +44 223 334714 Cambridge CB2 3QG, England.
-