From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: document frankly how a user is to just read his mail
Date: Thu, 8 Jun 2006 02:15:36 +0300 [thread overview]
Message-ID: <20060607231535.GA77296@gothmog.pc> (raw)
In-Reply-To: <E1Fo297-0001C4-Tz@jidanni1>
On 2006-06-08 01:48, Dan Jacobson <jidanni@jidanni.org> wrote:
> The top of the gnus info tree should have an article: What if I
> don't want to ever read 'news' and only want to read 'mail' and all
> my mail currently is in /var/spool/mail/$USER? How should I then set
> up gnus?
>
> You may think that "1.3 The Server is Down" is good enough, but I
> say you have surely lost the user by then.
>
> Indeed
> $ mutt
> would be much faster than trying to read the gnus documentation.
>
> http://www.useit.com/alertbox/ rating for gnus surely is 0.
>
> And how would one translate
> $ mutt -f file
> into gnus language? Surely one need a post-doc degree to find out.
>
> Why don't you have a info page saying how to do
> $ mail
> $ mail -f file
> $ mutt
> $ mutt -f file
> but in the gnus language or even from, gasp,
> $ emacs -f gnus 'what goes here?' #the command line.
> Or maybe it is impossible.
>
> And regarding your
> "Address: "
> prompt, after guessing your B command might be usable. Well who
> could ever figure out how to tell it the name of a local file. The
> user is just left poking in the dark as usual.
I've recently been taught that the best way to open an mbox file
quickly in Gnus is to use:
C-u G f /path/to/mbox RET m
This is surely a bit more complex than:
mutt -f /path/to/mbox
but you still have to set up mutt correctly before being able to do
anything useful with that command.
next prev parent reply other threads:[~2006-06-07 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 17:48 Dan Jacobson
2006-06-07 23:15 ` Giorgos Keramidas [this message]
2006-06-16 3:35 Dan Jacobson
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=20060607231535.GA77296@gothmog.pc \
--to=keramida@ceid.upatras.gr \
--cc=bugs@gnus.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).