From: Oystein Viggen <oysteivi@tihlde.org>
Cc: ding <ding@gnus.org>
Subject: Re: summary of unread messages on pop server?
Date: Fri, 17 May 2002 21:10:04 +0200 [thread overview]
Message-ID: <03g00qd20j.fsf@colargol.tihlde.org> (raw)
In-Reply-To: <ruor8kau3mf.fsf@billwlx.wolfram.com> (Bill White's message of "Fri, 17 May 2002 11:43:20 -0500")
* [Bill White]
> -----------------------------------------
> ssh machinename <then keep that connection open>
> mail
> x
> -----------------------------------------
>
> Is there a better way to get the list of unread messages?
I run "watch frm" in an xterm next to my XEmacs. frm is a small program
that lists out the sender and subject of the messages in your mailbox.
I think it is a part of elm.
> An elisp way, perhaps, or some shell thingy whose output I can stick
> in a buffer every minute or so?
Well, if you set up ssh to authenticate itself with a crypto key instead
of the password, you can have it log in automatically. Then you can run
"ssh machinename frm" from emacs.
Oystein
--
This message was brought to you by the letter ß and the number e.
next prev parent reply other threads:[~2002-05-17 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 16:43 Bill White
2002-05-17 19:10 ` Oystein Viggen [this message]
2002-05-17 22:24 ` Wes Hardaker
2002-06-04 16:15 ` Bill White
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=03g00qd20j.fsf@colargol.tihlde.org \
--to=oysteivi@tihlde.org \
--cc=ding@gnus.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.
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).