Gnus development mailing list
 help / color / mirror / Atom feed
From: "d. hall" <dhall@illusion.apk.net>
Cc: larsi@ifi.uio.no
Subject: Obscure bug with .newsrc
Date: Wed, 28 Feb 1996 06:41:56 -0500	[thread overview]
Message-ID: <199602281141.GAA00743@illusion.apk.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----

If gnus-save-newsrc-file is set to nil, and activate (gnus-group-restart)
function, it seems to erase groups from the group buffer.  I did this
accidentally today when I typed R when I forgot my focus was on the Emac X
window.  At first I thought it just decided to hide them by switching
displayed levels on me, but L did not produce my missing newsgroups.  In
gnus.el the function (gnus-group-restart)

(defun gnus-group-restart (&optional arg)
  "Force Gnus to read the .newsrc file."
  (interactive "P")
  (gnus-save-newsrc-file)
  (gnus-setup-news 'force)
  (gnus-group-list-groups arg))

Should a check be made before asking gnus-setup-news via 'force?  Or maybe
bugging out as soon as we know we're not supposed to read the newsrc file.
It's a matter of capibility and second guessing the user's intentions.

d.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMTQ/Z4X26urqpgG1AQG+KAP/RyRkavIaxXkXeV72p8T4Lv4DPATiK28l
uJsrg2JOzx+3V7HDJ8/OnZUDXlWLSXj1u/IDwyEC09f2cHn/Dc+0ZsFnBqGoocCD
BdUPaeReYivO9JiEG1Qd4ZlaQq7gSKNA+AUEhcjKvkqFGEHeI2wkThIcqYRrazeI
rWAWyYa8rvk=
=2oeU
-----END PGP SIGNATURE-----
-- 
Grok:
  [from the novel "Stranger in a Strange Land", by R. A. Heinlein,
  where it is a Martian word meaning roughly "to be one with"] v. To
  understand, usually in a global sense.
                                ~ from the jargon file


             reply	other threads:[~1996-02-28 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-28 11:41 d. hall [this message]
1996-02-29  8: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=199602281141.GAA00743@illusion.apk.net \
    --to=dhall@illusion.apk.net \
    --cc=larsi@ifi.uio.no \
    /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).