From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Something very wrong here
Date: Wed, 05 Sep 2001 12:02:18 +0200 [thread overview]
Message-ID: <vafu1yit0ph.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m1wv3eibrk.fsf@reader.newsguy.com> (Harry Putnam's message of "Tue, 04 Sep 2001 19:58:55 -0700")
Harry Putnam <reader@newsguy.com> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>>> First off, I guess setting nnml-marks-is-evil is no way to find out
>>> what is causing my problems. So dropping that for now.
>>
>> I think setting nnml-marks-is-evil would be worth a shot. Setting it
>> effectively disables the .marks file handling, after all.
>
> How is that done on a server? When I attempt to edit my nnml server
> with ^ in group buffer and then `e' on the nnml server. I'm told the
> server cannot be edited.
You can't edit secondary servers. For them, you have to change the
value of gnus-secondary-select-methods in ~/.gnus or wherever.
(This applies only if you use a list like (nnml "foo" ...) in
gnus-secondary-select-methods. If you have a string like "nnml:foo"
or "foo" or something like this there, then `e' ought to work, I
guess.)
kai
--
Symbol's function definition is void: signature
next prev parent reply other threads:[~2001-09-05 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 2:37 Harry Putnam
2001-09-04 13:47 ` Kai Großjohann
2001-09-04 14:38 ` Simon Josefsson
2001-09-04 16:12 ` Harry Putnam
2001-09-04 17:54 ` Kai Großjohann
2001-09-05 2:58 ` Harry Putnam
2001-09-05 10:02 ` Kai Großjohann [this message]
2001-09-04 19:08 ` Simon Josefsson
2001-09-05 20:03 ` Harry Putnam
2001-09-05 20:29 ` Simon Josefsson
2001-09-05 22:47 ` Harry Putnam
2001-09-05 23:42 ` Harry Putnam
2001-09-05 21:45 ` Kai Großjohann
2001-09-05 22:13 ` Harry Putnam
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=vafu1yit0ph.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).