From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: No Gnus feature request: simpler file structure for synching
Date: Wed, 07 Jan 2004 13:44:09 +0100 [thread overview]
Message-ID: <87u138j5d2.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <873casgr4f.fsf@naz.lickey.com>
Matt Armstrong <matt@lickey.com> writes:
> (setq gnus-secondary-select-methods
> '((nnml ""
> (nnml-directory "/home/matt/g/nnml")
> (nnml-active-file "/home/matt/g/nnml/active")
> (nnml-newsgroupsfile "/home/matt/g/nnml/newsgroups"))))
>
>
> I haven't figured out the lispy magic required to use "~/g/nnml"
> etc. in the gnus-secondary-select-methods setq above.
(setq gnus-secondary-select-methods
`((nnml ""
(nnml-directory ,(expand-file-name "~/g/nnml"))
(nnml-active-file ,(expand-file-name "~/g/nnml/active"))
(nnml-newsgroupsfile ,(expand-file-name "~/g/nnml/newsgroups")))))
The trick is in the ` (backtick) and , (comma).
But maybe it works to just say (nnml-directory "~/g/nnml")? Maybe
Gnus groks the tilde.
Kai
next prev parent reply other threads:[~2004-01-07 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 0:24 No Gnus feature request: simpler file structure for synching between two machines John Owens
2004-01-07 7:22 ` No Gnus feature request: simpler file structure for synching Matt Armstrong
2004-01-07 8:27 ` Steve Youngs
2004-01-07 12:44 ` Kai Grossjohann [this message]
2004-01-07 14:28 ` Reiner Steib
2004-01-07 14:59 ` Kai Grossjohann
2004-01-07 17:42 ` nnir problems (was: No Gnus feature request: simpler file structure for synching) Reiner Steib
2004-01-07 16:20 ` No Gnus feature request: simpler file structure for synching Steven E. Harris
2004-01-08 22:23 ` Reiner Steib
2004-01-08 22:51 ` Steven E. Harris
2004-01-08 22:58 ` Paul Jarc
2004-01-07 17:07 ` John Owens
2004-01-07 17:47 ` Kai Grossjohann
2004-01-07 19:17 ` Josh Huber
2004-01-07 21:32 ` Simon Josefsson
2004-01-08 19:49 ` Steinar Bang
2004-01-11 21:49 ` Kai Grossjohann
2004-01-12 22:15 ` Steinar Bang
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=87u138j5d2.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).