From: Diagon <gnu.org@niwas.net>
To: "ding" <ding@lists.math.uh.edu>
Subject: Re: Copying between babyl files.
Date: Fri, 21 Aug 2015 16:07:24 -0700 [thread overview]
Message-ID: <14f52844612.da69404864836.7538045950198190193@niwas.net> (raw)
In-Reply-To: <87oai1xax3.fsf@igel.home>
---- On Fri, 21 Aug 2015 02:12:24 -0700 Andreas Schwab wrote ----
>Diagon <gnu.org@niwas.net> writes:
>
>> nndoc+/<path/filename>:<filename>
>
>nndoc is a read-only backend. If you want to copy to a babyl file you
>should use the nnbabyl backend.
Andreas - Thanks for your response. Excuse the untutored questions, but:
(1) why does it work fine if I use "o" (gnus-summary-save-article), but fails using "B c" (gnus-summary-copy-article), even while in both cases I have used gnus-group-make-doc-group (see (2)).
(2) I am using "M-0 G f" (gnus-group-make-doc-group) to temporarily add the file I want to copy to. (M-0 is to make sure it knows it's a babyl file.) What is the alternative you are suggesting?
>Andreas.
/D
prev parent reply other threads:[~2015-08-21 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 22:31 Diagon
2015-08-21 9:12 ` Andreas Schwab
2015-08-21 23:07 ` Diagon [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=14f52844612.da69404864836.7538045950198190193@niwas.net \
--to=gnu.org@niwas.net \
--cc=ding@lists.math.uh.edu \
/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).