Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Mike Dixon <in_my.t@gline.org>
Subject: Re: Little help sorting please...
Date: Sun, 22 Dec 2002 02:36:19 GMT	[thread overview]
Message-ID: <m38yyiu65q.fsf@west_mm.org> (raw)
In-Reply-To: <84vg1nbjht.fsf@lucy.cs.uni-dortmund.de>



> Mike Dixon <in_my.t@gline.org> writes:
> 
> > :-> The archive file my post is saved to using the above is at the end of
> > a nested set of dirs.  For instance, if the group name is gnu.emacs.gnus
> > and I post to that group, and my archive file is therefore named
> > gnu.emacs.gnus.archive, using the code above I end up with
> > ~/*/gnu/emacs/gnus/archive which is where the copy of my post is stored.  I 
> > was hoping for a filename such as ~/*/gnu.emacs.gnus.archive (which it
> > looked like I was going to get with "nnfolder:%s.archive"). 
> 
> Why is the filename important if you can access the stuff via the
> group nnfolder+archive:gnu.emacs.gnus.archive?  It should not be

Because I don't know how to :->  

I don't comprehend the whole Gnus virtual server/backend stuff (not for
lack of trying).  So like many I stick with what one is able to get
working satisfactorily, not wanting to disturb what's arrived at, which
for me was putting posts into files such as "sent-to-gnus.emacs.gnus."  I
use Gnus to read Usenet - not to become a Gnus-jock and most of the
subtleties of Gnus are therefore lost on me.

> That said, investigate the variables gnus-use-long-file-name and
> nnmail-use-long-file-names.  (Only Lars knows why one is singular and
> the other is plural.  Don't ask...)

Thanks Kai - I'll look into them (or take another stab at trying to
understand the whole backend thing).

Thanks for your help and patience.

Mike


  parent reply	other threads:[~2002-12-22  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3bs3mifun.fsf@west_mm.org>
2002-12-16 10:06 ` Kai Großjohann
2002-12-17  2:46   ` Mike Dixon
2002-12-17  9:38     ` Kai Großjohann
     [not found]       ` <m3adj3y9rn.fsf@west_mm.org>
     [not found]         ` <84fzsvmeg8.fsf@lucy.cs.uni-dortmund.de>
2002-12-21  8:57           ` Mike Dixon
     [not found]             ` <84vg1nbjht.fsf@lucy.cs.uni-dortmund.de>
2002-12-22  2:36               ` Mike Dixon [this message]
2002-12-22 14:07                 ` Kai Großjohann
     [not found]                   ` <m3isxdfcar.fsf@west_mm.org>
2002-12-29  8:42                     ` Mark Dixon

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=m38yyiu65q.fsf@west_mm.org \
    --to=in_my.t@gline.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).