Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Eichin <eichin@cygnus.com>
Cc: ding@ifi.uio.no
Subject: nnml-active-number fails creating new groups (September Gnus v0.79)
Date: 25 Apr 1996 20:17:45 -0400	[thread overview]
Message-ID: <xe1g29rvnx2.fsf@maneki-neko.cygnus.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 24 Apr 1996 04:45:20 +0000


I have gotten in the habit of adding new patterns to my
nnmail-split-methods list, then respooling (B r nnml RET) into them to
create the new groups. That seems to have broken between 0.77 and
0.79; now I get a (void-function-last) if I don't (require 'cl) by
hand. If I do the require, I get (wrong-type-argument
number-or-marker-p (1 . "1")) in nnmail-active-number. Any
suggestions? How should I be creating new nnml:mail groups?

;;; before require'ing cl
Signalling: (void-function last)
  last(((971 . "971") (970 . "970") (969 . "969") (968 . "968") (967 . "967") (966 . "966") (965 . "965") (964 . "964") (963 . "963") (962 . "962") (961 . "961") (960 . "960") (959 . "959") (958 . "958") (957 . "957") (956 . "956") (955 . "955") (954 . "954") (953 . "953") (952 . "952") (951 . "951") (950 . "950") (949 . "949") (948 . "948") (947 . "947") (946 . "946") (945 . "945") (944 . "944") (943 . "943") (942 . "942") (941 . "941") (940 . "940") (939 . "939") (938 . "938") (937 . "937") (936 . "936") (935 . "935") (934 . "934") (933 . "933") (932 . "932") (931 . "931") (930 . "930") (929 . "929") (928 . "928") (927 . "927") (926 . "926") (925 . "925") (924 . "924") (923 . "923") (922 . "922") ...))
  nnml-active-number("mail.debian.bugs")
  nnmail-article-group(nnml-active-number)
  nnml-save-mail()
  nnml-request-accept-article(nil "" t)
  gnus-request-accept-article(nil (nnml "") t)
  eval((gnus-request-accept-article nil (quote (nnml "")) t))
  nnml-request-move-article(70 "mail.personal" "" (gnus-request-accept-article nil (quote (nnml "")) t) t)
  gnus-request-move-article(70 "nnml:mail.personal" "" (gnus-request-accept-article nil (quote (nnml "")) t) t)
  gnus-summary-move-article(nil nil (nnml ""))
  gnus-summary-respool-article(nil (nnml ""))
* call-interactively(gnus-summary-respool-article)

;;; after require'ing cl
Signalling: (wrong-type-argument number-or-marker-p (1 . "1"))
  nnml-active-number("mail.debian.bugs")
  nnmail-article-group(nnml-active-number)
  nnml-save-mail()
  nnml-request-accept-article(nil "" t)
  gnus-request-accept-article(nil (nnml "") t)
  eval((gnus-request-accept-article nil (quote (nnml "")) t))
  nnml-request-move-article(70 "mail.personal" "" (gnus-request-accept-article nil (quote (nnml "")) t) t)
  gnus-request-move-article(70 "nnml:mail.personal" "" (gnus-request-accept-article nil (quote (nnml "")) t) t)
  gnus-summary-move-article(nil nil (nnml ""))
  gnus-summary-respool-article(nil (nnml ""))
* call-interactively(gnus-summary-respool-article)

If it helps, hitting 'e active RET' gives
(971 1 . "1")

and that's probably why the 1+ is failing...


                 reply	other threads:[~1996-04-26  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=xe1g29rvnx2.fsf@maneki-neko.cygnus.com \
    --to=eichin@cygnus.com \
    --cc=ding@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).