From: Mike Kupfer <m.kupfer@acm.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: bug: emphasization not performed at end-of-line
Date: Tue, 14 Jul 2009 18:46:41 -0700 [thread overview]
Message-ID: <4856.1247622401@rawbw.com> (raw)
In-Reply-To: Your message of "Mon, 13 Jul 2009 20:53:57 +0900." <b4mab38u7ca.fsf@jpl.org>
>>>>> "Katsumi" == Katsumi Yamaoka <yamaoka@jpl.org> writes:
Katsumi> The problem is due to the difference of the character syntax of
Katsumi> the newline character between XEmacs 21.5 and the others.
Katsumi> This form
Katsumi> (char-syntax ?\n text-mode-syntax-table)
Katsumi> returns `?\.' in XEmacs 21.5 whereas `? ' in XEmacs 21.4 and
Katsumi> FSFmacs.
Thanks for isolating it to this issue. That helped a lot. This has
now been fixed in the Mercurial repo for XEmacs. (And thanks to Karl
for reporting the issue in the first place.)
cheers,
mike
prev parent reply other threads:[~2009-07-15 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 18:30 Karl Kleinpaste
2009-07-10 18:46 ` Adam Sjøgren
2009-07-10 18:56 ` Karl Kleinpaste
2009-07-13 11:53 ` Katsumi Yamaoka
2009-07-13 14:57 ` Karl Kleinpaste
2009-07-15 1:46 ` Mike Kupfer [this message]
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=4856.1247622401@rawbw.com \
--to=m.kupfer@acm.org \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).