From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Aidan Kehoe <kehoea@parhasard.net>
Cc: ding@gnus.org, xemacs-patches@xemacs.org
Subject: Re: [PATCH] Support opaque display-table objects on XEmacs
Date: Tue, 27 May 2008 22:34:08 +0200 [thread overview]
Message-ID: <v9od6r5vwf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <buo7idnggl5.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Thu, 22 May 2008 12:31:18 +0900")
On Thu, May 22 2008, Miles Bader wrote:
> Aidan Kehoe <kehoea@parhasard.net> writes:
>> This patch adds support for the non-sequence display tables of XEmacs 21.5,
>> without any run-time overhead on GNU. A patch that’s equivalent in
>> functionality for that version has been integrated into the XEmacs package
>> repository; this conflicts with that, though--sorry Mike!--and is more
>> compatible with GNU.
I gather that it should be applied to the stable and development
branch. Right?
>> I’ve tested this (somewhat superficially) with XEmacs 21.5, 21.4
>> and GNU.
(Just call the later "Emacs".)
>> Please advise me if this is the wrong list to submit this to.
It's the right list. Thanks.
>> I have papers on file with the FSF for Gnus and for GNU Emacs as a
>> whole, so that shouldn’t be an issue.
Confirmed.
>> * gnus-util.el (gnus-put-display-table): New.
>> (gnus-get-display-table): New.
>> Macros that expand to an #'aset call under GNU, and to a runtime choice
>> under XEmacs.
Is writing “#'” a new XEmacsy ChangeLog convention?
>> * gnus-sum.el (gnus-summary-set-display-table):
>> Use #'gnus-{put,get}-display-table, gnus-set-display-table for the
>> display table, instead of #'aset.
>> * gnus-xmas.el (gnus-xmas-summary-set-display-table):
>> Use #'gnus-{put,get}-display-table, gnus-set-display-table for the
>> display table.
It's better (e.g. for searching) to spell out the macro names (not
using {put,get}).
>> @@ -3431,8 +3431,8 @@
>> 256)))
>> (while (>= (setq i (1- i)) 127)
>> ;; Only modify if the entry is nil.
>> - (unless (aref table i)
>> - (aset table i [??]))))
>> + (unless (get-display-table i table)
>> + (put-display-table i [??] table))))
>> (setq buffer-display-table table)))
>
> Should those be `gnus-get-display-table' and `gnus-put-display-table'?
Aidan?
>> +(defmacro gnus-put-display-table (range value display-table)
>> + "Set the value for char RANGE to VALUE in DISPLAY-TABLE. "
>> + (if (featurep 'xemacs)
>> + (progn
Useless `progn'?
>> + `(if (fboundp 'put-display-table)
>> + (put-display-table ,range ,value ,display-table)
>> + (if (sequencep ,display-table)
>> + (aset ,display-table ,range ,value)
>> + (put-char-table ,range ,value ,display-table))))
`cond' would be more readable than an `if'-cascade, IMHO.
>> + `(aset ,display-table ,range ,value)))
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-05-27 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 22:57 Aidan Kehoe
2008-05-22 3:31 ` Miles Bader
2008-05-27 20:34 ` Reiner Steib [this message]
2008-05-27 21:02 ` Aidan Kehoe
2008-05-27 21:21 ` Reiner Steib
2008-06-09 20:03 ` [PATCH] Support opaque display-table objects on XEmacs (revised) Aidan Kehoe
2008-06-14 15:48 ` Reiner Steib
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=v9od6r5vwf.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=kehoea@parhasard.net \
--cc=xemacs-patches@xemacs.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).