Dirk-Jan C. Binnema wrote:
>Hi,
>>>>>> On Thu, 15 Jul 2010 22:32:54 +0200, David Maus ("DM") wrote:
> DM> [1 <text/plain; US-ASCII (7bit)>]
> DM> Dirk-Jan C. Binnema wrote:
> >> Hi all,
> >> I'm playing around a bit the message expiration in Wanderlust; in theory, it's
> >> a quite useful feature, as it enables me to automatically delete/refile old
> >> messages. However, it does not seem to work very well with me, and often
> >> requires me to get into a situation where I need to restart emacs(!).
> DM> Could you provide a backtrace of the errors?
> DM> M-x toggle-debug-on-error RET
> DM> hit the bugs and remove possible confidential information?
>First use case is where I try to expire my 'system' folder (which receives all
>kinds of useless messages from various programs); in my wl-expire-alist:
> ("^\\.system$" (date 3) remove)
>First it updates the message
>db, then I get the 'Wrong type argument: listp, nil'. However, I do /not/ get
>any backtrace. When I then try to enter the folder, or do anything (even when
>trying M-x toggle-debug-on-error), I either get that same error again. And I
>cannot move the cursor anymore. Emacs menus are still accessible though, it's
>not a general hang. But just about whatever I do gives me 'Wrong type
>argument: listp, nil'.
Interesting. Do you call expire in Folder mode or Summary mode? Here
expiring a maildir folder works perfectly in Summary mode, but in
Folder mode I get an error -- although a different one (WL not being
capable of finding the file the correspondents to a maildir message
number).
A question about this one:
> - when trying to expire my 'System' folder, I get
> "Wrong type argument: listp, nil"
> but
> when I try to enter the folder afterwards I get:
> "Format specifier doesn't match argument type", after which WL (or emacs)
> is not very useful anymore, and tells me
> "Symbol's value as variable is void: nil". After that, I cannot even close
> emacs properly, but have to kill it.
Do you have a way to reproduce this behavior? IIRC I hit a problem
with the same symptoms occasionally and "Symbol's value as variable is
void: nil" sound horrible: Meaning that Emacs somehow forgot that the
symbol nil is ... nil. What ever WL might do wrong: THIS should not
never happen :( (read: It could be a Emacs bug).
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
Attachment:
pgp2hAdbFLgBo.pgp
Description: PGP signature