From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: fix for char-int lossage in message-make-caesar-translation-table
Date: 18 Aug 2000 16:55:56 -0400 [thread overview]
Message-ID: <2nn1iaxp9f.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Charles G Waldman's message of "Fri, 18 Aug 2000 15:37:44 -0500"
Charles G Waldman <cgw@fnal.gov> writes:
> Decoding rot-13 messages in Gnus fails on XEmacs because the
> function message-make-caesar-translation-table was using character
> constants as indices for the `substring' function, which is
> expecting an int. FSF Emacs may let you carelessly mix chars and
> ints, but XEmacs won't.
>
> I also changed some bizarre arithmetic. Where I come from, x + n +
> 26 - n is usually referred to as x + 26.
>
>
> ChangeLog for gnus/lisp:
>
> Fri Aug 18 15:35:03 2000 Charles G. Waldman <cgw@alum.mit.edu>
> * message.el (message-make-caesar-translation-table):
> Don't use chars as ints. Simplify arithmetic.
This patch is not necessary.
In XEmacs, message-xmas-make-caesar-translation-table (messagexmas.el)
is used instead of message-make-caesar-translation-table.
ShengHuo
parent reply other threads:[~2000-08-18 20:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200008182037.PAA00461@buffalo.fnal.gov>]
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=2nn1iaxp9f.fsf@tiger.jia.vnet \
--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).