Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: .newrc.eld renamed
Date: Thu, 15 Nov 2001 12:52:30 -0800	[thread overview]
Message-ID: <m1k7wrbvu9.fsf@reader.newsguy.com> (raw)
In-Reply-To: <ilug07f9982.fsf@dhcp128.extundo.com> (Simon Josefsson's message of "Thu, 15 Nov 2001 19:31:41 +0100")

Simon Josefsson <jas@extundo.com> writes:

>> C-h i m gnus i  newsrc.eld  gives one hit.. not promising
>
> The text in this hit explains it, at least in my copy.  You probably
> used Netscape or something that created a .newsrc-foo and Gnus picked
> that up.  From the Info node:
>
>    You can turn off writing the `.newsrc' file by setting
> `gnus-save-newsrc-file' to `nil', which means you can delete the file
> and save some space, as well as exiting from Gnus faster.  However,
> this will make it impossible to use other newsreaders than Gnus.  But
> hey, who would want to, right?  Similarly, setting
> `gnus-read-newsrc-file' to `nil' makes Gnus ignore the `.newsrc' file
> and any `.newsrc-SERVER' files, which is convenient if you have a
> tendency to use Netscape once in a while.

This doesn't explain it at all in my reading, but I guess it does mean
what I'm seeing.  This would not have and did not tip me
off. Newsrc.eld is not mentioned there.  It is mentioned in the para
above but not in connection of being renamed.

It should clearly say that newsrc.eld might be renamed by some other
application having been used.  Or that .newrc might be and then gnus
will rename .newrc.eld too.  Still not clear to me what actually
happened there.

I think the culprit may have been slrn since I don't recall using
netscape for news ever.  But I think slrn uses something else like:
~/.jnewsrc.



  reply	other threads:[~2001-11-15 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 16:48 Harry Putnam
2001-11-15 18:31 ` Simon Josefsson
2001-11-15 20:52   ` Harry Putnam [this message]
2001-11-16  8:17 ` Kai Großjohann

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=m1k7wrbvu9.fsf@reader.newsguy.com \
    --to=reader@newsguy.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).