unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Steve Molitor <stevemolitor@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to use "smart kerning" font features in Emacs using composition-function-table
Date: Mon, 27 Nov 2023 17:22:39 +0200	[thread overview]
Message-ID: <83plzv8bls.fsf@gnu.org> (raw)
In-Reply-To: <CAJrM8VW0P+-cO_cup6W-teoJV46nZTcsPrFbaKdXDD_CK_5Rxw@mail.gmail.com> (message from Steve Molitor on Mon, 27 Nov 2023 08:47:41 -0600)

> From: Steve Molitor <stevemolitor@gmail.com>
> Date: Mon, 27 Nov 2023 08:47:41 -0600
> 
> Thanks again. Last question: Does it make sense to optimize for shorter
> matches? For example, I could pull out the space to only match "words",
> and pull out and handle the "/" separately, to avoid matching against
> long file paths.

Optimize for what purpose?  If almost everything is going to be
matched anyway, I think it is better to send larger chunks of text to
the shaping engine, as that causes fewer calls and the shaping engine
will be able to produce better visuals.



  parent reply	other threads:[~2023-11-27 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 15:48 How to use "smart kerning" font features in Emacs using composition-function-table Steve Molitor
2023-11-26 17:52 ` Eli Zaretskii
2023-11-26 19:49   ` Steve Molitor
2023-11-26 20:16     ` Eli Zaretskii
2023-11-26 20:42       ` Steve Molitor
2023-11-27 12:03         ` Eli Zaretskii
     [not found]           ` <CAJrM8VW0P+-cO_cup6W-teoJV46nZTcsPrFbaKdXDD_CK_5Rxw@mail.gmail.com>
2023-11-27 15:22             ` Eli Zaretskii [this message]
2023-11-27 16:16               ` Steve Molitor
2023-11-28  5:18           ` Yuan Fu
2023-11-28 13:27             ` Steve Molitor
2023-11-29  0:58               ` Yuan Fu
2023-11-28 14:20             ` Eli Zaretskii
2023-11-29  0:57               ` Yuan Fu

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=83plzv8bls.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stevemolitor@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 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).