unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13449@debbugs.gnu.org
Subject: bug#13449: 24.3.50; Perl mode composed symbols not visible
Date: Tue, 15 Jan 2013 16:41:09 +0000	[thread overview]
Message-ID: <CAPM58ojGRK0VEBjNmg0aDMr2cZL0XJNE6xpnZLaXoed6qCWg5w@mail.gmail.com> (raw)
In-Reply-To: <837gnequws.fsf@gnu.org>

On 15 January 2013 16:21, Eli Zaretskii wrote:

> I cannot reproduce this on my XP SP3 box, with today's development
> sources.  Your Emacs is quite old (2 months ago), but I doubt that
> this problem is due to some bug we had at that time.

Sorry, I should have said: the bug is still present in 111524 (early
this morning); 110872 (two months ago) was the earliest build that I
happen to have hanging around that exhibits the bug.

> When you go to those "space characters" and type "C-u C-x =", what
> does Emacs say about these two characters in the buffer that it pops
> up?

The following (except that the "=>" is not visible in the Emacs buffer):

             position: 388 of 13355 (3%), column: 34
            character: = (displayed as =) (codepoint 61, #o75, #x3d)
    preferred charset: ascii (ASCII (ISO646 IRV))
code point in charset: 0x3D
               syntax: . 	which means: punctuation
             category: .:Base, a:ASCII, l:Latin, r:Roman
             to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
          buffer code: #x3D
            file code: #x3D (encoded by coding system undecided-dos)
              display: composed to form "=>" (see below)

Composed with the following character(s) ">" by the rule:
	(?=>)
The component character(s) are displayed by these fonts (glyph codes):
 =>: uniscribe:-outline-Source Code
Pro-normal-normal-normal-mono-13-*-*-*-c-*-iso10646-1 (#x01)
See the variable `reference-point-alist' for the meaning of the rule.

Character code properties: customize what to show
  name: EQUALS SIGN
  general-category: Sm (Symbol, Math)
  decomposition: (61) ('=')

There are text properties here:
  composition          [Show]
  fontified            t





  reply	other threads:[~2013-01-15 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 10:17 bug#13449: 24.3.50; Perl mode composed symbols not visible Richard Copley
2013-01-15 16:21 ` Eli Zaretskii
2013-01-15 16:41   ` Richard Copley [this message]
2013-01-15 16:51     ` Richard Copley
2013-01-15 17:08       ` Eli Zaretskii
2013-01-15 17:14     ` Eli Zaretskii
     [not found]       ` <CAPM58oiM-0U2540Guc87Ue-tOfD3yWw_a1tYmHrVaFyOgE1rPg@mail.gmail.com>
2013-01-15 18:56         ` Eli Zaretskii
     [not found]           ` <CAPM58oi=ZoO4Ot17jxaBf0WV601EzFg0k0dU1B3krQ+2LcRBWg@mail.gmail.com>
2013-01-16 18:55             ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPM58ojGRK0VEBjNmg0aDMr2cZL0XJNE6xpnZLaXoed6qCWg5w@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=13449@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).