From: craffert@ml.com (Colin Rafferty)
Subject: Re: missing feedback
Date: 15 Apr 1996 14:47:54 -0400 [thread overview]
Message-ID: <ocrratpwch1.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: "Henry S. Thompson"'s message of Mon, 15 Apr 96 17:16:29 BST
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?
Also, if you use XEmacs, you don't need to start a new editor from home,
just have gnuserv create a new display on your tty (or $DISPLAY). I do
this all the time.
--
Colin Rafferty
next prev parent reply other threads:[~1996-04-15 18:47 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
1996-04-15 18:47 ` Colin Rafferty [this message]
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=ocrratpwch1.fsf@spssunp.spspme.ml.com \
--to=craffert@ml.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).