From: Gerry Agbobada <gagbobada@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Question about composite.c
Date: Sat, 25 Apr 2020 17:32:07 +0200 [thread overview]
Message-ID: <CAHhDRB_Z0+gFfbE-1gc5ZsgpepE7PjYAejUUSDOqASg=9MCG0g@mail.gmail.com> (raw)
In-Reply-To: <83pnbv7foi.fsf@gnu.org>
No problem, I'll keep looking at the code and I'll try to report the issue
properly (with a bug and on the correct mailing list) if I ever manage to
either reproduce it on master or find the exact code path I follow in
my example.
Gerry AGBOBADA
Le sam. 25 avr. 2020 à 17:23, Eli Zaretskii <eliz@gnu.org> a écrit :
>
> > From: Gerry Agbobada <gagbobada@gmail.com>
> > Date: Sat, 25 Apr 2020 15:53:49 +0200
> > Cc: Emacs developers <emacs-devel@gnu.org>
> >
> > I can confirm the bug is fixed by
> > commit fe903c5ab7354b97f80ecf1b01ca3ff1027be446
> > Author: Eli Zaretskii
> > Date: Sat Feb 8 15:41:36 2020 +0200
> > Allow composition of pure-ASCII strings in the mode line
> >
> > * src/composite.c (Fcomposition_get_gstring): Allow unibyte strings if
> > they are pure
> > ASCII, by copying text into a multibyte string.
>
> Thanks, that was my guess.
>
> > If it's possible to backport this commit in emacs 27 I think it would
> > save a lot of headaches.
>
> Sorry, the change is somewhat risky, and that's why it went to master.
prev parent reply other threads:[~2020-04-25 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:17 Question about composite.c Gerry Agbobada
2020-01-21 18:15 ` Eli Zaretskii
2020-01-21 18:57 ` Gerry Agbobada
2020-01-21 19:15 ` Eli Zaretskii
2020-01-22 8:55 ` Gerry Agbobada
2020-04-14 22:43 ` Gerry Agbobada
2020-04-15 1:10 ` Noam Postavsky
2020-04-15 7:39 ` Gerry Agbobada
2020-04-25 12:44 ` Eli Zaretskii
2020-04-25 13:06 ` Gerry Agbobada
2020-04-25 13:29 ` Gerry Agbobada
2020-04-25 13:53 ` Gerry Agbobada
2020-04-25 15:23 ` Eli Zaretskii
2020-04-25 15:32 ` Gerry Agbobada [this message]
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='CAHhDRB_Z0+gFfbE-1gc5ZsgpepE7PjYAejUUSDOqASg=9MCG0g@mail.gmail.com' \
--to=gagbobada@gmail.com \
--cc=eliz@gnu.org \
--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.