From: anti-spam-pranav@cisco.com (Pranav K. Tiwari)
Subject: illegal regexp after upgrading 20.7 -> 21.2
Date: Sun, 26 Jan 2003 22:17:57 -0800 [thread overview]
Message-ID: <uu1fv3ylm.fsf@cisco.com> (raw)
Tried to upgrade to 21.2 from 20.7, but 21.2 doesn't like a regexp I use
for mail splitting. Backtrace is attached - can anyone find something
offending?
thx,
-p
Debugger entered--Lisp error: (invalid-regexp "Invalid regular expression")
* re-search-forward("^Subject:.*=\\(?gb2312?\\|?euc-kr?\\|?Euc-kr?\\|?ks_c_5601-1987?\\)" nil t)
byte-code("\bÆ\x19^[(I\x1a^[,Cd ...."
nnimap-split-to-groups((("INBOX.SPAM" "^Content-Type:.*\\(gb2312\\|euc-kr\\|Euc-kr\\|ks_c_5601-1987\\)") ("INBOX.SPAM" "^Subject:.*=\\(?gb2312?\\|?euc-kr?\\|?Euc-kr?\\|?ks_c_5601-1987?\\)")))
nnimap-split-articles(nil "cbin2-mira-01")
nnimap-request-scan(nil "cbin2-mira-01")
gnus-request-scan(nil (nnimap "cbin2-mira-01" (nnimap-address "cbin2-mira-01.cisco.com") (nnimap-authinfo-file "~/personal/netrc") (nnimap-list-pattern ("Inbox*"))))
gnus-get-unread-articles(3)
gnus-group-get-new-news(3)
(if (eq arg nil) (gnus-group-get-new-news pkt:gnus-default-get-news-level) (gnus-group-get-new-news arg))
pkt:gnus-group-get-new-news()
(progn (switch-to-buffer "*Group*") (pkt:gnus-group-get-new-news))
(if (get-buffer "*Group*") (progn (switch-to-buffer "*Group*") (pkt:gnus-group-get-new-news)) (funcall pkt:gnus-function))
(lambda nil (interactive) (if (get-buffer "*Group*") (progn ... ...) (funcall pkt:gnus-function)))()
* call-interactively((lambda nil (interactive) (if (get-buffer "*Group*") (progn ... ...) (funcall pkt:gnus-function))))
next reply other threads:[~2003-01-27 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 6:17 Pranav K. Tiwari [this message]
[not found] ` <m3hebtopc3.fsf@defun.localdomain>
2003-01-28 6:57 ` Pranav K. Tiwari
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=uu1fv3ylm.fsf@cisco.com \
--to=anti-spam-pranav@cisco.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).