From: Harry Putnam <reader@newsguy.com>
Subject: Is there a new agent bug?
Date: Wed, 09 Jan 2002 09:51:18 -0800 [thread overview]
Message-ID: <m1hepvpgsr.fsf@reader.newsguy.com> (raw)
I quit using the agent for a while but now wanted to start fresh
again.
The steps I took were to close gnus down. Get cvs updated, then
rename ~/News/agent to ~/News/agentX and restart gnus, having
uncommented (gnus-agentize) in ~/.gnus.
First thing I noticed was that our gnu had shed his red coat and grew
a white one.... Has that been changed or is this the first indicator
of some local screw up?
Other things seemed to be working, and the needed directories: agent and
sub directories were created, except no agent/lib appeared.
I thought maybe that only happened if I did something with the agent
category interface (`J C' in group buffer)
So proceeded to call `J C' in group buffer. There I see the expected
default:0
So pressing `p' to edit the predicate, I see `nil', so I enter `true'
and remove `nil'. Attempting to save that edit buffer gives this
back trace:
Debugger entered--Lisp error: (wrong-type-argument consp nil)
setcar(nil true)
(lambda (predicate) (setcar (cdr ...) predicate) (gnus-category-write) (gnus-category-list))(true)
gnus-edit-form-done()
call-interactively(gnus-edit-form-done)
Creating the News/agent/lib directory by hand doesn't help. I get
the same backtrace
Can anyone confirm that there is a problem there? Or is it something local?
next reply other threads:[~2002-01-09 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 17:51 Harry Putnam [this message]
2002-01-09 17:56 ` Kai Großjohann
2002-01-10 3:39 ` Harry Putnam
2002-01-19 21:10 ` Lars Magne Ingebrigtsen
2002-01-20 17:08 ` Kai Großjohann
2002-01-09 19:48 ` Paul Stodghill
2002-01-10 3:40 ` Harry Putnam
2002-01-19 21:11 ` 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=m1hepvpgsr.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).