all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen C. Gilardi" <scgilardi@gmail.com>,
	Paul Eggert <eggert@cs.ucla.edu>
Cc: 19496@debbugs.gnu.org
Subject: bug#19496: 25.0.50; term.c, produce_composite_glyh, cmp->pixel_width uninitialized
Date: Sat, 03 Jan 2015 20:17:26 +0200	[thread overview]
Message-ID: <83fvbrafux.fsf@gnu.org> (raw)
In-Reply-To: <0FD61621-E12F-4183-B1A3-BFA8482B7FA5@gmail.com>

> From: "Stephen C. Gilardi" <scgilardi@gmail.com>
> Date: Sat, 3 Jan 2015 09:20:52 -0500
> 
> emacs -Q
> open an emacs lisp file that contains (lambda ... )
> turn on prettify-symbols-mode
> the lambda form is converted to (λ ... ), and should be displayed that way, but instead it's displayed as
> (\
> λ
>  ...)
> 
> This commit is the first on master to show the problem: 20791069fa34b486c018ba7f27982bdc6ad2a4ea (found by git bisect)

I think that commit was mistaken, and should be reverted, because
before it this worked correctly.  CC'ing Paul, who made the change,
and Handa-san, who probably wrote it.

Paul, was there a use case where you saw a problem with the original
code?  If so, can you show it?

> I don't see an obvious fix.

Why do you think the previous code is not TRT?

> There seems to be some confusing use in the code between "width in columns" and "width in pixels". It's possible that the pixel_width field in "struct it" is not named precisely for how it’s used--in a terminal, the width may actually be used as a number of columns rather than a number of pixels.

On a text terminal, each glyph is 1 pixel wide.  So on a text terminal
these two are identical.





  reply	other threads:[~2015-01-03 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 14:20 bug#19496: 25.0.50; term.c, produce_composite_glyh, cmp->pixel_width uninitialized Stephen C. Gilardi
2015-01-03 18:17 ` Eli Zaretskii [this message]
2015-01-03 22:39   ` Paul Eggert

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=83fvbrafux.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19496@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=scgilardi@gmail.com \
    /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.