bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1831: 23.0.60; Emacs.app cannot display acctended characters in *gre


From: Alan J Third
Subject: bug#1831: 23.0.60; Emacs.app cannot display acctended characters in *grep* buffer
Date: Sat, 09 Jan 2016 23:08:08 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin)

Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> A similiar failure can be observed when typing <some character>C-q 0 3
> 2 3 <some non-decimal event> or <some character>C-q 1 4 4 3 in octal.
> In GNU Emacs 23.0.60 C-q 0 3 2 3 produces a COMBINING DOT BELOW, which
> is combined with the previously typed character. In the end something
> ugly appears, as shown above. In Emacs.app only a blank spot is left.
> C-u C-x = shows:
>
>               character: ̣ (803, #o1443, #x323)
>       preferred charset: unicode (Unicode (ISO10646))
>              code point: 0x0323
>                  syntax: w    which means: word
>                category: ^:Combining
>       Combining diacritic or mark
>             buffer code: #xCC #xA3
>               file code: #xCC #xA3 (encoded by coding system utf-8-unix)
>                 display: composed to form "̣" (see below)
>       
>       Composed using this font:
>         nil:-apple-NimbusMonL-medium-normal-normal-Regular-10-*-*-*-*-*- 
> iso10646-1
>       by these glyphs:
>         [0 0 803 0 6 0 5 5 0 [0 0 6]]
>       
>       Character code properties: customize what to show
>         name: COMBINING DOT BELOW
>         old-name: NON-SPACING DOT BELOW
>         general-category: Mn (Mark, Nonspacing)
>       
>       There are text properties here:
>         fontified            t
>
> Using a font like Lucida Grande that has ọ, o, and COMBINING DOT
> BELOW, I cannot compose ọ from o and COMBINING DOT BELOW. Again, in
> GNU Emacs 23.0.60 this at least creates something ugly.

Hi, sorry it's taken so long to get back to you about this. I can
reproduce the issue in 24.5, but not in 25, so I'm going to close this
bug as fixed.

-- 
Alan Third





reply via email to

[Prev in Thread] Current Thread [Next in Thread]