From: Glenn Morris <rgm@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Byte-compilation warnings on w32
Date: Fri, 29 Aug 2008 13:56:12 -0400 [thread overview]
Message-ID: <2f7i9z903n.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1KZ1gs-00054U-A7@etlken.m17n.org> (Kenichi Handa's message of "Fri, 29 Aug 2008 19:58:54 +0900")
Kenichi Handa wrote:
> Oops, I committed a half-cooked version by mistake. Just corrected.
Looks like you also need to change tibetan-composition-function
to use font-shape-gstring (great function name, BTW) in place of
font-shape-text.
next prev parent reply other threads:[~2008-08-29 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 8:21 Byte-compilation warnings on w32 Eli Zaretskii
2008-08-29 10:58 ` Kenichi Handa
2008-08-29 14:44 ` Eli Zaretskii
2008-08-29 17:56 ` Glenn Morris [this message]
2008-09-06 18:56 ` Glenn Morris
2008-09-07 0:11 ` Kenichi Handa
2008-09-07 0:29 ` Glenn Morris
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=2f7i9z903n.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).