From: Mike Dixon <in_my.t@gline.org>
Subject: Re: Little help sorting please...
Date: Sat, 21 Dec 2002 08:57:28 GMT [thread overview]
Message-ID: <m3ptrv2184.fsf@west_mm.org> (raw)
In-Reply-To: <84fzsvmeg8.fsf@lucy.cs.uni-dortmund.de>
> Mike Dixon <in_my.t@gline.org> writes:
>
> > Thanks Kai. Got a different error:
>
> Gah :-(
>
> > Wrong number of arguments: (lambda (group) (if group (format "nnfolder:%s.archive" group) "nnfolder:other.archive")), 0
> >
> > I'll play around with it some and see if I can determine what's causing
> > the error...
>
> I've peeked at the source, and maybe
>
> (setq gnus-message-archive-group 'mike-gnus-message-archive-group)
>
> is the simplest value that will do. But the one with the double pair
> of parens should also work, if...
>
> (defun mike-gnus-message-archive-group (group)
>
> you write (&optional group) instead of (group) in the defun line.
>
> (if group
> (format "nnfolder:%s.archive" group)
> "nnfolder:other.archive"))
>
> Tell about your findings...
>
> But maybe the group name isn't passed as often as it should be. Hm.
> Well, we will see.
> --
Hi Kai -
:-> 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").
I found "format" in my LISP Info file but the specifiers didn't indicate
behavior like that for %s. I located nnfolder.el and there's a
function/dir "file-name-as-directory" that I wonder if that's the root
cause of this (converted what I wanted as a filename into a dir path)? Is
this the default behavior of nnfolder used as it is here to convert "."
into directories? Do you know if there's some way I can use
"file-name-as-directory" in nnfolder.el such that my posts are stored in
filenames where it doesn't convert the "." in the group name into
directories (or is there a better way to accomplish this)? Incidentally,
when I save a thread (T #, O-f <name>) it creates one directory such as
"comp.protocols.tcp-ip" and saves the thread in there but does not convert
the "." in comp.protocols.tcp-ip into a nested series of directories
(i.e., comp/protocols/tcp-ip/).
I looked at "nnfolder" from the index of Info:gnus but unless I missed
something it doesn't seem to mention this dir-creating behavior. I hope
my question isn't too convoluted so to restate, what I'm after is an
archive file where the "." of the Usenet group name isn't converted to
directories - a filename like gnu.emacs.gnus.archive.
Mike
next prev parent reply other threads:[~2002-12-21 8:57 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 [this message]
[not found] ` <84vg1nbjht.fsf@lucy.cs.uni-dortmund.de>
2002-12-22 2:36 ` Mike Dixon
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=m3ptrv2184.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).