From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nnml backend unavailable when constructing some nnml- variables
Date: Mon, 30 May 2011 22:31:49 +0200 [thread overview]
Message-ID: <m362osyloq.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87bozhnlph.fsf@gmx.de>
michael.zombok@googlemail.com writes:
> I tried to set up a machine specific .gnus file which sets some
> variables based on 'system-name'. The nnml backend does not seem to like
> that, because when I set some of the variables with the following
>
>> (nnml-directory (concat cpath "/addons/gnus-mail/mail/"))
>> (nnml-active-file (concat cpath "/addons/gnus-mail/mail/active"))
> < (nnml-newsgroups-file (concat cpath "/addons/gnus-mail/mail/newsgroups"))
I think your message was truncated, because it ended there.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-05-30 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 16:30 michael.zombok
2011-05-30 20:31 ` Lars Magne Ingebrigtsen [this message]
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=m362osyloq.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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).