From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: nnimap splitting weirdness
Date: Sat, 08 Mar 2014 16:56:56 +0800 [thread overview]
Message-ID: <874n399ig7.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87zjl39p6q.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Any hints on what might be going on? I'm using git gnus and GNU Emacs
>> 24.3.1.
>
> Perhaps you could add a hack to Fset to watch for assignments to
> nnimap-split-fancy and trigger a backtrace.
>
> Andreas.
This seemed like an interesting idea, but I haven't quite been able to
get it to work. `fset' doesn't seem right, that's only for defining
functions. Is that what you meant? I tried to advise `set', because I'd
always thought all variable assignment eventually made use of set, but
nothing happened when I tested a setq form with nnimap-split-fancy.
Advising `setq' directly resulted in "Lisp nesting exceeds
`max-lisp-eval-depth'", perhaps just because I'm doing the advice wrong:
(defadvice setq (before hands-off-nnimap-splitting
(&rest args))
"Try to figure out who's setting nnimap-split-fancy back to nil."
(message "args: %s" args)
ad-do-it
)
(ad-activate 'setq)
Anyone have any pointers here?
Also, on the subject of the original problem, I see there's both these:
gnus-sum.el:(defvar nnimap-split-fancy)
nnimap.el:(defvoo nnimap-split-fancy nil
I don't suppose it matters that there are two definitions for the same
variable? I don't know enough about variable assignment to know if this
is normal.
Thanks,
Eric
next prev parent reply other threads:[~2014-03-08 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 3:30 Eric Abrahamsen
2014-03-06 3:46 ` Malcolm Purvis
2014-03-08 8:59 ` Eric Abrahamsen
2014-03-08 11:26 ` Malcolm Purvis
2014-03-06 18:06 ` Andreas Schwab
2014-03-08 8:56 ` Eric Abrahamsen [this message]
2014-03-08 10:13 ` Eric Abrahamsen
2014-03-07 17:04 ` Lars Ingebrigtsen
2014-03-10 6:18 ` Eric Abrahamsen
2014-03-10 12:29 ` Malcolm Purvis
2014-03-20 4:54 ` Eric Abrahamsen
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=874n399ig7.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/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).