From: Geoffrey Alan Washburn <geoffw@cis.upenn.edu>
To: emacs-devel@gnu.org
Subject: Re: modify-syntax-entry and UTF8?
Date: Wed, 23 May 2007 11:09:22 -0400 [thread overview]
Message-ID: <46545922.1050002@cis.upenn.edu> (raw)
In-Reply-To: <m3tzu5q9ax.fsf@lugabout.jhcloos.org>
James Cloos wrote:
>>>>>> "Geoffrey" == Geoffrey Alan Washburn <geoffw@cis.upenn.edu> writes:
>
> Geoffrey> No, what I wrote is exactly what I meant, unless the author of
> Geoffrey> the TeX-input method incorrectly defined \langle and \rangle.
>
> Ah. That does put a different spin on things.
>
> And in fact, the UCS has expanded since that was written, and characters
> were added for exactly TeX's \langle and \rlangle (and a few others in
> latin-ltx.el which currently point to CJK characters instead of math chars).
>
> latin-ltx.el should be updated to use ⟨ U+27E8 MATHEMATICAL LEFT ANGLE
> BRACKET for \langle and ⟩ U+27E9 MATHEMATICAL RIGHT ANGLE BRACKET for \rangle.
Ah, that is good to know. Is there any straightforward way to override
this in my .emacs file?
> What does C-uC-x= output when point is on the characters in your
> (modify-syntax-entry) calls and when point is on one of the characters
> you are trying to match in the buffer you are editing? What are the
> mode and coding-system of the buffer you are editing? What is the
> coding-system of the .el file?
So when using the correct glyphs I get
character: ⟨ (10216, #o23750, #x27e8)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x27E8
syntax: (⟩ which means: open, matches ⟩
buffer code: #xE2 #x9F #xA8
file code: #xE2 #x9F #xA8 (encoded by coding system utf-8-unix)
display: no font available
...
and
character: ⟩ (10217, #o23751, #x27e9)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x27E9
syntax: )⟨ which means: close, matches ⟨
buffer code: #xE2 #x9F #xA9
file code: #xE2 #x9F #xA9 (encoded by coding system utf-8-unix)
display: no font available
...
which as I understand it means that they should already be treated as
matching delimiters.
However, if create an empty scratch buffer and I move the cursor on top
of either of the glyphs they become highlighted, but with the face that
is used for matched delimiters rather than the face mismatch/unmatched
delimiters. Adding both glyphs to an empty buffer in correctly and
incorrectly matching permutations gives the same behavior.
So I am inclined to believe Stefan's hypothesis that modify-syntax-entry
is working correctly here and instead whatever code actually interprets
the syntax table or performs the actual adjustment to the faces for
highlighting has a bug of some sort.
I'm also somewhat curious that emacs tells me that no font is available
for these glyphs, but Thunderbird seems to be able to locate a font that
can be used to display them.
next prev parent reply other threads:[~2007-05-23 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 17:24 modify-syntax-entry and UTF8? Geoffrey Alan Washburn
2007-05-21 23:06 ` James Cloos
2007-05-22 8:47 ` Geoffrey Alan Washburn
2007-05-22 13:25 ` James Cloos
2007-05-23 15:09 ` Geoffrey Alan Washburn [this message]
2007-05-23 16:56 ` Stefan Monnier
2007-05-25 13:48 ` Geoffrey Alan Washburn
2007-05-25 14:23 ` Miles Bader
2007-05-25 14:26 ` Geoffrey Alan Washburn
2007-05-25 14:54 ` Geoffrey Alan Washburn
2007-05-25 17:53 ` Miles Bader
2007-05-25 18:20 ` Geoffrey Alan Washburn
2007-05-25 22:06 ` James Cloos
2007-05-28 16:04 ` Geoffrey Alan Washburn
2007-05-29 12:43 ` highlights of parentheses in lisp-interaction-mode (was: Re: modify-syntax-entry and UTF8?) James Cloos
2007-05-29 13:27 ` highlights of parentheses in lisp-interaction-mode martin rudalics
2007-05-29 16:34 ` James Cloos
2007-06-04 0:17 ` highlights of parentheses in lisp-interaction-mode (was: Re: modify-syntax-entry and UTF8?) Richard Stallman
2007-05-22 9:48 ` modify-syntax-entry and UTF8? Stefan Monnier
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=46545922.1050002@cis.upenn.edu \
--to=geoffw@cis.upenn.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.