all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
Cc: eggert@cs.ucla.edu, 23938-done@debbugs.gnu.org
Subject: bug#23938: Commit 237244bbd5ce753bcdf79634561de515bd76c687 broke display of composed characters on master
Date: Mon, 11 Jul 2016 17:21:20 +0300	[thread overview]
Message-ID: <838tx8dzmn.fsf@gnu.org> (raw)
In-Reply-To: <5782DB52.1060806@live.com> (message from Clément Pit--Claudel on Mon, 11 Jul 2016 01:33:38 +0200)

> From: Clément Pit--Claudel <clement.pitclaudel@live.com>
> Date: Mon, 11 Jul 2016 01:33:38 +0200
> Cc: Paul Eggert <eggert@cs.ucla.edu>
> 
> Running the following in Emacs 24 and 25-rc pops a buffer displaying "bd". On master, it displays "b" and "d" on top of each other.
> 
>     (with-current-buffer (get-buffer-create "*test*")
>       (erase-buffer)
>       (fundamental-mode)
>       (insert "test")
>       (compose-region (point-min) (point-max) '(?b (Br . Bl) ?d))
>       (pop-to-buffer (current-buffer)))
> 
> Bisecting points to the following commit:
> 
>     237244bbd5ce753bcdf79634561de515bd76c687 is the first bad commit
>     commit 237244bbd5ce753bcdf79634561de515bd76c687
>     Author: Paul Eggert <eggert@cs.ucla.edu>
>     Date:   Mon May 30 16:09:25 2016 -0700
> 
>         Omit IF_LINT code that no longer seems needed
> 
>         Nowadays GCC is smarter, or the Emacs code has mutated, or both,
>         and now is as good a time as any to remove uses of IF_LINT that
>         now seem to be unnecessary.
>         (...)

Thanks, fixed.





  parent reply	other threads:[~2016-07-11 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 23:33 bug#23938: Commit 237244bbd5ce753bcdf79634561de515bd76c687 broke display of composed characters on master Clément Pit--Claudel
2016-07-11 14:20 ` Paul Eggert
2016-07-11 14:21 ` Eli Zaretskii [this message]
2016-07-11 14:36   ` Paul Eggert
2016-07-11 15:04     ` 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

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

  git send-email \
    --in-reply-to=838tx8dzmn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23938-done@debbugs.gnu.org \
    --cc=clement.pitclaudel@live.com \
    --cc=eggert@cs.ucla.edu \
    /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.