From: jam@jamux.com (John A. Martin)
Subject: Re: Trouble selecting group in recent cvs
Date: Sat, 30 Nov 2002 00:07:09 -0500 [thread overview]
Message-ID: <87vg2fir2a.fsf@athene.jamux.com> (raw)
In-Reply-To: <2nadjran1d.fsf@zsh.cs.rochester.edu>
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
>>>>> "ZSH" == ShengHuo ZHU
>>>>> "Re: Trouble selecting group in recent cvs"
>>>>> Fri, 29 Nov 2002 20:01:18 -0500
ZSH> 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.
ZSH> It is probably related to gnus-byte-compile. It seems that
ZSH> gnus-byte-compile doesn't work correctly in some versions of
ZSH> XEmacs for some unknown reasons. The work around is to set
ZSH> gnus-use-byte-compile to nil in .gnus. Or (defalias
ZSH> 'gnus-byte-compile 'identity)
Good job! Thanks much.
In .gnus I had (defun gnus-byte-compile (gnus-compile)). I don't
remember why, but being a beginner with gnus I must have seen a
suggestion to do that.
Replacing that with (defalias 'gnus-byte-compile 'identity) works fine
as does using neither. This is now with:
,----[ xemacs21-nomule 21.4.10-2 ]
| XEmacs 21.4 (patch 10) "Military Intelligence" [Lucid]
| (i386-debian-linux) of Sun Nov 24 2002 on eeyore
`----
jam
[-- Attachment #2: Type: application/pgp-signature, Size: 154 bytes --]
next prev parent reply other threads:[~2002-11-30 5:07 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
2002-11-30 5:07 ` John A. Martin [this message]
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=87vg2fir2a.fsf@athene.jamux.com \
--to=jam@jamux.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).