Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "harel barzilai" <barzilai@gmail.com>
Subject: Re: Learning gnus for email only
Date: 1 Jan 2007 20:41:50 -0800	[thread overview]
Message-ID: <1167712910.230585.70580@a3g2000cwd.googlegroups.com> (raw)
In-Reply-To: <v9sleuhd1i.fsf@marauder.physik.uni-ulm.de>

Reiner Steib wrote:
> On Mon, Jan 01 2007, harel barzilai wrote:
>
> > (I was somewhat relieved to find
> > http://www.cyphertext.net/~gfish/mrd/gnus-overview.html which stated,
> [...]
> > 1) Am I correct in my impression that I should NOT take the advice
> >    from the FAQ that
> >
> > ;; Q4.11 Using Gnus for mail and never news
>
> I already told you in the previous thread *not* to rely on the
> outdated FAQ.  The text of "gfish" refers to "Pterodactyl Gnus" (Gnus
> 5.8) as a "new" version of Gnus, so it is probably outdated as well.
>
> Please don't rely on random private web pages and consult the manual
> that comes with Gnus and the Gnus tutorial instead.
>
> Bye, Reiner.

Reiner, first, I thank you for the tutorial url, though which I am now
struggling to get through,
having earlier worked through other pages. Please note I was *not*
relying on "random
private web pages" for anything other than quoting him saying he, too,
was not
able to get enough information from
http://gnus.org/manual.html...luckly, again, I'm not
trying to follow the tutorial url instead, though looks like I will
still need to post a followup question
or two here after reading it..

As for the faq.org yes, that is clearly out of date...perhaps someone
can request they
either update or remove the out-dated gnus faq from their site? google
gives
http://www.gnu.org/software/emacs/emacs-faq.text as second hit for
"gnus faq" while
http://www.faqs.org/faqs/gnus-faq/ still comes out at #1, alas..

HB

> --
>        ,,,
>       (o o)
> ---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2007-01-02  4:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1167115181.099537.35020@a3g2000cwd.googlegroups.com>
     [not found] ` <85vejxndbo.fsf@robf.de>
2006-12-29  5:20   ` Emacs Mailer Options harel barzilai
2006-12-29  9:08     ` Reiner Steib
2006-12-29 12:13       ` Slackat
2006-12-29 16:38     ` Giorgos Keramidas
2006-12-31  6:55       ` harel barzilai
2007-01-01  7:14 ` Learning gnus for email only (Was: Re: Emacs Mailer Options) harel barzilai
2007-01-01 17:28   ` Learning gnus for email only Reiner Steib
2007-01-02  4:41     ` harel barzilai [this message]
2007-01-02  5:40     ` harel barzilai
2007-01-02  6:48       ` Slackat
2007-01-02 20:36       ` harel barzilai
2007-01-02 22:51         ` Reiner Steib
2007-01-05  2:35           ` harel barzilai
2007-01-05 10:54             ` Springfield
2007-01-06  5:22               ` harel barzilai
2007-01-06 13:09                 ` Reiner Steib
2007-01-06 13:40                   ` Slackrat
2007-01-06 14:20                     ` Reiner Steib
2007-01-05 12:23             ` Reiner Steib
     [not found] ` <1167547830.044677.30770@v33g2000cwv.googlegroups.com>
     [not found]   ` <1168062671.653432.216140@i15g2000cwa.googlegroups.com>
     [not found]     ` <87k5zzyhfy.fsf@kobe.laptop>
2007-01-12  5:53       ` Emacs Mailer Options harel barzilai

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=1167712910.230585.70580@a3g2000cwd.googlegroups.com \
    --to=barzilai@gmail.com \
    /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).