From: Harry Putnam <reader@newsguy.com>
Subject: Re: unplugged/failure to display expunged
Date: 27 Sep 1999 19:10:52 -0700 [thread overview]
Message-ID: <m3ln9rdbv7.fsf@satellite.local.lan> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "28 Sep 1999 02:46:19 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > Not sure why there is a 2 number difference. But anyway, can I edit
> > the active file and expect the display to show 2123 messages, with out
> > hosing something else?
>
> Yes. But it would be interesting to find out why the active file
> entry for this group got hosed.
I can't think of how to figure it out. I did look in the backups I
have on board (3 days worth) and the active file is already hosed back
to Sept 25. It must have been before that when I was able to see all
messages.
I may have fired up gnus in a situation that caused it to run 5.5 (ie
no pointer to pgnus*/lisp) And I have recently started running some
code I adopted from a post of yours in batch mode:
I'm running it with the pointer to pgnus/lisp added and the "push"
line commented since under certain condition (not sure what) that push
caused gnus to stumble.
I run it like so:
emacs -batch -l ~/.emacs-dir/batch-fetch.el -f lars-fetch-news
(batch-fetch.el contains the code below)
batch-fetch.el
----------------
(setq load-path (cons (expand-file-name "/usr/local/pgnus-0.96/lisp") load-path))
(defun lars-fetch-news ()
(interactive)
;(push "/usr/local/pgnus-0.96/lisp" load-path)
(let ((init-file-user "")
(gnus-always-read-dribble-file t))
(gnus))
(gnus-group-send-drafts)
(gnus-agent-fetch-session)
(gnus-group-quit))
next prev parent reply other threads:[~1999-09-28 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 11:26 Harry Putnam
1999-09-27 18:01 ` Lars Magne Ingebrigtsen
1999-09-28 0:17 ` Harry Putnam
1999-09-28 0:46 ` Lars Magne Ingebrigtsen
1999-09-28 2:10 ` Harry Putnam [this message]
1999-09-28 2:29 ` Harry Putnam
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=m3ln9rdbv7.fsf@satellite.local.lan \
--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).