Gnus development mailing list
 help / color / mirror / Atom feed
From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Documentation fix for gnus-slave
Date: Tue, 19 Feb 2002 13:32:14 -0500	[thread overview]
Message-ID: <m1beljhb9w1.fsf@blackbird.mitre.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

In response to a question on gnu.emacs.gnus, I propose the attached
patch to gnus.texi which explains why, when starting gnus-slave, one
might be prompted as to whether to read the auto-save file.
-- 
Dave Goldberg
david.goldberg6@verizon.net

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 858 bytes --]

Index: gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 6.262
diff -c -r6.262 gnus.texi
*** gnus.texi	2002/02/18 15:47:20	6.262
--- gnus.texi	2002/02/19 18:29:21
***************
*** 1117,1122 ****
--- 1117,1127 ----
  Information from the slave files has, of course, precedence over the
  information in the normal (i.e., master) @code{.newsrc} file.
  
+ If the @code{.newsrc*} files have not been saved in the master when the
+ slave starts, you may be prompted as to whether to read an auto-save
+ file.  If you answer "yes", the unsaved changes to the master will be
+ incorporated into the slave.  If you answer "no", the slave may see some
+ messages as unread that have been read in the master.
  
  @node Fetching a Group
  @section Fetching a Group

             reply	other threads:[~2002-02-19 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 18:32 David S. Goldberg [this message]
2002-02-20 15:17 ` ShengHuo ZHU
2002-02-20 15:17 ` ShengHuo ZHU
2002-02-19 18:32 David S. Goldberg

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=m1beljhb9w1.fsf@blackbird.mitre.org \
    --to=david.goldberg6@verizon.net \
    /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).