From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to use "smart kerning" font features in Emacs using composition-function-table Date: Mon, 27 Nov 2023 17:22:39 +0200 Message-ID: <83plzv8bls.fsf@gnu.org> References: <83ttp89zbk.fsf@gnu.org> <83il5o9so6.fsf@gnu.org> <83edgb9zem.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14023"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Steve Molitor Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 27 16:23:20 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r7dSB-0003Rn-SM for ged-emacs-devel@m.gmane-mx.org; Mon, 27 Nov 2023 16:23:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r7dRq-0002zc-E1; Mon, 27 Nov 2023 10:22:58 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r7dRo-0002z2-Bg for emacs-devel@gnu.org; Mon, 27 Nov 2023 10:22:56 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r7dRo-0001Rp-3C; Mon, 27 Nov 2023 10:22:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=ejim4rWpuIaGD0wuKINwrQComCRLPHRtLtw4Fuzkrc4=; b=JqsYiJezp0ae AmnVKMiGUFyWAZmRPN2qVITyE3s0EAfZKZXMNMwISJJg49cseIDCNgTeYRUdCvqe4WtsOT67hfWxF rPOQsm2wun+EIGmzCD2m3OhFPH3Du88L2a2IpHtPOa3XjVN0oaVKlTjPcCQblBQlID9Ao+i38XiBW HhEVjWerHSxye4Hn5jnybQbPYeQPGcBXIePMMHdKCvoojU+hoF4O2/PRzlleg9AmvZSH/sUTDCBxw HPNYmn4PekU3gRG4DwgrGcxkKRLPWlb/BlAxhiicZNMayYWmPxvRP3G7LYt74goMxK948Slqu9k1H NkiKk2ibNvAIG724vZv8EA==; In-Reply-To: (message from Steve Molitor on Mon, 27 Nov 2023 08:47:41 -0600) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313275 Archived-At: > From: Steve Molitor > 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.