From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Trouble selecting group in recent cvs
Date: Fri, 29 Nov 2002 20:01:18 -0500 [thread overview]
Message-ID: <2nadjran1d.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <87of88oukx.fsf@athene.jamux.com> (jam@jamux.com's message of "Fri, 29 Nov 2002 17:54:38 -0500")
jam@jamux.com (John A. Martin) writes:
[...]
> ,----
> | (defun gnus-summary-highlight-line-0 ()
> | (if (and (eq gnus-summary-highlight-line-trigger
> | gnus-summary-highlight)
> | gnus-summary-highlight-line-cached)
> | gnus-summary-highlight-line-cached
> | (setq gnus-summary-highlight-line-trigger gnus-summary-highlight
> | gnus-summary-highlight-line-cached
> | (let* ((cond (list 'cond))
> | (c cond)
> | (list gnus-summary-highlight))
> | (while list
> | (setcdr c (cons (list (caar list) (list 'quote (cdar list))) nil))
> | (setq c (cdr c)
> | list (cdr list)))
> | (gnus-byte-compile (list 'lambda nil cond))))))
> `----
>
> the while is exited with nil. It is for sure nil over the first few
> iterations. I can't seem to get edebug to run up to a breakpoint and
> show the value coming out of the loop. For example, SPACE doesn't
> seem to work here for me.
It is probably related to gnus-byte-compile. It seems that
gnus-byte-compile doesn't work correctly in some versions of XEmacs
for some unknown reasons. The work around is to set
gnus-use-byte-compile to nil in .gnus.
Or (defalias 'gnus-byte-compile 'identity)
ShengHuo
next prev parent reply other threads:[~2002-11-30 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 23:37 John A. Martin
2002-11-29 13:22 ` Kai Großjohann
2002-11-29 14:13 ` John A. Martin
2002-11-29 15:36 ` Kai Großjohann
2002-11-29 22:54 ` John A. Martin
2002-11-30 1:01 ` ShengHuo ZHU [this message]
2002-11-30 5:07 ` John A. Martin
2002-11-30 17:33 ` Kai Großjohann
2002-11-30 20:51 ` John A. Martin
2002-11-30 21:50 ` Kai Großjohann
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=2nadjran1d.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).