Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Re: missing feedback
Date: 15 Apr 1996 13:13:06 -0700	[thread overview]
Message-ID: <m27mvhkzzh.fsf@deanna.miranova.com> (raw)
In-Reply-To: craffert@ml.com's message of 15 Apr 1996 11:45:06 -0700

>>>>> "Colin" == Colin Rafferty <craffert@ml.com> writes:

Colin> Henry S Thompson writes:
>> Also, is there any way to be saved from myself in a way which gnus
>> manages because .newsrc is actually in a buffer, namely that if I am
>> running Gnus on one machine, run it AGAIN (e.g. from home) and read a
>> bunch of news and exit, then quitting Gnus on the first machine the
>> next day DOESN'T notice that .newsrc[.eld] has changed and simply
>> overwrites?

Colin> If this ability was added, I would want there to be a variable to turn
Colin> it off.

It's been in September Gnus for quite awhile now.  See the Sgnus
manual section on Slave Gnusi for details.

   Linkname: September Gnus Manual - Slave Gnusiï
        URL: http://www.miranova.com/sgnus-man/gnus_6.html#SEC5

Colin> Actually, since this would be a new feature that could impact
Colin> performance (NFS at my job stinks), I would prefer to have the default
Colin> be to NOT check.

You have to explicitly ask for it to get it.  Running two Gnus
sessions on the same newsrc without interlock checking is asking for
trouble though.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.


  reply	other threads:[~1996-04-15 20:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-04-15 16:16 Henry S. Thompson
1996-04-15 18:45 ` Colin Rafferty
1996-04-15 20:13   ` Steven L Baur [this message]
1996-04-15 18:47 ` Colin Rafferty
1996-04-15 19:00   ` Paul D. Smith
1996-04-15 19:45     ` William Perry
1996-04-15 19:51       ` Paul D. Smith
1996-04-16 21:58 ` Lars Magne Ingebrigtsen

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=m27mvhkzzh.fsf@deanna.miranova.com \
    --to=steve@miranova.com \
    /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).