Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Sebastian Tennant <sebyte@smolny.plus.com>
To: info-gnus-english@gnu.org
Subject: Re: Switching backends
Date: Thu, 03 May 2007 00:38:00 +0300	[thread overview]
Message-ID: <871whykitj.fsf@moley.org> (raw)
In-Reply-To: <86r6pzguz8.fsf@ketchup.de.uu.net>


Many thanks to all respondents.  I think I've got it, but until I try
I can't be sure :-/

Quoth Kai Grossjohann <kai@emptydomain.de>:
> This seems somewhat obvious, though, so I'm not sure if it really
> helps.

It certainly does help.  There's something about Gnus (probably the
fact that it is so infinitely configurable and possesses such a
dizzying array of variables) which has always made my head swim.

Sebastian

  parent reply	other threads:[~2007-05-02 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 12:05 Sebastian Tennant
2007-05-02 14:28 ` Kai Grossjohann
2007-05-02 18:43   ` Reiner Steib
2007-05-02 21:38   ` Sebastian Tennant [this message]
2007-05-04 19:19   ` nnir bug? Sebastian Tennant
     [not found] <mailman.87.1178110556.32220.info-gnus-english@gnu.org>
2007-05-02 13:09 ` Switching backends Karl Kleinpaste

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=871whykitj.fsf@moley.org \
    --to=sebyte@smolny.plus.com \
    --cc=info-gnus-english@gnu.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).