Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Linh Dang <linh@linhdang.home>
Subject: Re: rant OR what's missing from gnus
Date: Mon, 09 Sep 2002 17:53:19 -0400	[thread overview]
Message-ID: <uadmqesog.fsf@linhdang.home> (raw)
In-Reply-To: <878z2buyjb.fsf@sixfingeredman.net>

Adrian Kubala <adrian@sixfingeredman.net> writes:

>
> - Confusing server and group configuration. I expect to just be able
>   to define everything clearly in one spot in .gnus, but no, some
>   things /must/ be stored in .newsrc, and some things must be done
>   manually through various parts of the gnus interface -- I expect
>   that from Windows, but not gnus.

Gnus also decide to override your settings for nnfolder-directory and
co with the following code in gnus-start.el


    ;; Make sure the archive server is available to all and sundry.
    (when gnus-message-archive-method
      (unless (assoc "archive" gnus-server-alist)
	(push `("archive"
		nnfolder
		"archive"
		(nnfolder-directory
		 ,(nnheader-concat message-directory "archive"))
		(nnfolder-active-file
		 ,(nnheader-concat message-directory "archive/active"))
		(nnfolder-get-new-mail nil)
		(nnfolder-inhibit-expiry t))
	      gnus-server-alist)))


I've been pulling my hair until i found the above piece of code. Don't
get me wrong, GNUS is still better than anyother alternative IMHO, but
it's more confusing than it needs to be.

-- 
Linh Dang


       reply	other threads:[~2002-09-09 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878z2buyjb.fsf@sixfingeredman.net>
2002-09-09 21:53 ` Linh Dang [this message]
     [not found] ` <877khv9p6y.fsf@virgil.koldfront.dk>
     [not found]   ` <slrnanpflk.3r5.wobo@molch.wolf-b.de>
2002-09-10  3:28     ` Galen Boyer
2002-09-10  4:12       ` Harry Putnam
2002-09-10 12:05     ` 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=uadmqesog.fsf@linhdang.home \
    --to=linh@linhdang.home \
    /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).