Gnus development mailing list
 help / color / mirror / Atom feed
From: Henrik Enberg <kirneh74@hem.passagen.se>
Subject: Gnus agent expire broken
Date: 20 Nov 2000 20:19:53 +0100	[thread overview]
Message-ID: <m3aeau5u3q.fsf@hem.passagen.se> (raw)


Hi,

gnus-agent-expire seems to be broken.  

I'm using a cvs version from Oct 28 and no expiry has happend since
then.  I only realized that someting was wrong when I tried
M-x gnus-agent-expire interactivly, so it seem to fail quietly
otherwise.

Here's a backtrace:

Signaling: (wrong-type-argument number-or-marker-p 730µõ@)
  gnus-agent-expire()
  call-interactively(gnus-agent-expire)
  execute-extended-command(nil)
* call-interactively(execute-extended-command)
  recursive-edit()
  byte-code("Æ\b!ˆÇ\x11È ˆÉÇ!ˆpÊË\x1a^[\x1cÌ ˆ+ebˆÍ ˆ`ÎÏ!ˆÐyˆ`|ˆÑ ˆ
@Ò>fN\0Ócˆ
@Ô=f«\0ÕÖÊ\"ˆ×Ð!ˆØcˆÙyˆ,«\0
@Ú=fs\0Ûcˆ
A@\x16%Ü\x0e%p\"ˆÝcˆ×Ð!ˆÞcˆÙyˆ,«\0
@ß=fŠ\0àcˆÜ
A@p\"ˆÝcˆ,«\0
@Ê=f--\0ácˆ,«\0Ü
@Ç=f¤\0
A,¥\0
p\"ˆÝcˆâã!ˆÊÇÊ\x19\x1c\x1e&âã!ˆŠä ˆ,LJ" [debugger-buffer buffer-read-only print-length print-escape-newlines standard-output debugger-args pop-to-buffer nil erase-buffer set-buffer-multibyte t 50 backtrace debugger-mode search-forward "\n  debug(" 1 debugger-reenable (lambda debug) "Entering:\n" debug backtrace-debug 3 delete-char 42 0 exit "Return value: " prin1 10 32 error "Signaling: " "Beginning evaluation of function call form:\n" message "" recursive-edit debugger-value inhibit-trace] 3)
  debug(error (wrong-type-argument number-or-marker-p 730µõ@))
  gnus-agent-expire()
  call-interactively(gnus-agent-expire)
  execute-extended-command(nil)
* call-interactively(execute-extended-command)

Henrik
-- 
"Television -- teacher, mother, secret lover!"
        - Homer J. Simpson



             reply	other threads:[~2000-11-20 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-20 19:19 Henrik Enberg [this message]
2000-11-20 19:31 ` ShengHuo ZHU
2000-11-20 19:46   ` Henrik Enberg
2000-11-20 20:36     ` ShengHuo ZHU

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=m3aeau5u3q.fsf@hem.passagen.se \
    --to=kirneh74@hem.passagen.se \
    /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).