From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= Newsgroups: gmane.emacs.devel Subject: Re: Ligatures Date: Mon, 18 May 2020 22:44:27 -0400 Message-ID: <26ede471-3881-43e3-1253-6b21658343e9@gmail.com> References: <20200517124125.000013a4@web.de> <97C7EAB7-10AB-4702-ABC8-EB6C1C50ABDB@gnu.org> <20200517165953.000044d2@web.de> <83lflqblp0.fsf@gnu.org> <83ftbybio3.fsf@gnu.org> <83zha69xs2.fsf@gnu.org> <83367x9qeq.fsf@gnu.org> <83y2pp88lw.fsf@gnu.org> <83pnb182ce.fsf@gnu.org> <65807546-ed40-a175-640d-9da7a1548d8a@gmail.com> <83o8qk8xv6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="36305"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 19 04:45:19 2020 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 1jasFr-0009Ky-AI for ged-emacs-devel@m.gmane-mx.org; Tue, 19 May 2020 04:45:19 +0200 Original-Received: from localhost ([::1]:52412 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jasFq-0003NC-AE for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 22:45:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45952) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jasF7-0002ur-Pa for emacs-devel@gnu.org; Mon, 18 May 2020 22:44:33 -0400 Original-Received: from mail-qk1-x72d.google.com ([2607:f8b0:4864:20::72d]:40030) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jasF6-0005u8-4D; Mon, 18 May 2020 22:44:33 -0400 Original-Received: by mail-qk1-x72d.google.com with SMTP id g185so12971556qke.7; Mon, 18 May 2020 19:44:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=wbHMzCcL5jw0gti07WyrW3wS9/mOyAHn7ebbhkgnlpQ=; b=MHT3tO7BIrmaeEb37Ei3tYvXZLCuaqF9mLS2eQPCwIFKvC9f2s10+Ydirkno8e623I oZBq9sT/tQLqv8zYQl3aKtpxA/gRxNQt7afRPKSEoFwSJkxH9R47fAqfh4JJvAOcZt6B xb/7G8GG7hwSUA4p4TYxJAzyfc/Jd2KPQxuaf2hOYSteHa4GqhNID9H2FcDRNFgseeUq uERK7RoK4Y6pvGQdC6Bd3pZPoAOLV88EbGFcdj/XNGaId2OD2mV/OhltIhohSJBDXKYS dq0+ETJD+lVDl9w1RSjViQgabJJmba7LxnDk6/iZwTwEmPYrdbXFtYVVuwBIVXRHp0QJ pcPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=wbHMzCcL5jw0gti07WyrW3wS9/mOyAHn7ebbhkgnlpQ=; b=WM2bct6yPsjpIZfL2GUFfxF65Sew841OzyegQSQz+HZZzzoFfKGKDF8bw8fzslQaRv cWZMgpJEmSu7ss9/Bzm2E1taj6MEnmWEAyETgEcQmwVpc3kvNIIaUF93KyxlcjDyrRF4 QHKqvcfVTjxz/rTEkMrsDIiqKGqB/cBVzJl1WSxystX4vKUgUPeKs5yqFnMMZgeJzGjP XzAypY/fWZYKlfXer6C/3xDph9pYwSAGk1uP4aPaH67qZv5wNO6WLjQL402HZ410LLis 19Ckif+Nq/Y6/Z91iZk31mOvuXaKvLTYCO8TzID0zrxrcLMYptH/SLbSNlxFMgsIWnTN Ei7w== X-Gm-Message-State: AOAM530Kqz5g9JNfNOq5T+IA3NNnv5qMaHAmqfc4Ho8Gv1zYqq1ElYWZ YTSZtmWPOh6+zPx3WLuYHLjODg1J X-Google-Smtp-Source: ABdhPJwdr5Yuae9ARwX9d4r0tx692CcCQOU3tqVpeGwVDDQbAKQFFnSXYd/Z076td61wmYb00bMg5Q== X-Received: by 2002:a05:620a:5bc:: with SMTP id q28mr18904064qkq.60.1589856269828; Mon, 18 May 2020 19:44:29 -0700 (PDT) Original-Received: from ?IPv6:2601:184:4180:66e7:bda5:ac5c:1de0:b677? ([2601:184:4180:66e7:bda5:ac5c:1de0:b677]) by smtp.googlemail.com with ESMTPSA id y23sm11635780qta.37.2020.05.18.19.44.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 May 2020 19:44:29 -0700 (PDT) In-Reply-To: <83o8qk8xv6.fsf@gnu.org> Content-Language: en-GB Received-SPF: pass client-ip=2607:f8b0:4864:20::72d; envelope-from=cpitclaudel@gmail.com; helo=mail-qk1-x72d.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:250845 Archived-At: On 18/05/2020 22.25, Eli Zaretskii wrote: >> From: Clément Pit-Claudel >> Date: Mon, 18 May 2020 15:44:01 -0400 >> >>> The idea is that this is used only rarely. Most use cases don't need >>> to deconstruct a ligature that way; after all, that's what ligatures >>> are for. >> >> In an earlier thread, you mentioned programming font ligatures — wouldn't it be very common to deconstruct such ligatures, like → into ->? > > No, I don't think so. Why would this be common? I thought it would be the default. Emacs shows →, and you can put the point either before (|→), in the middle (-|>), or after (→|). This is what prettify-symbols-unprettify-at-point exists for, I believe, though it doesn't work perfectly often the composed glyph doesn't have the same width as the non-composed one. Here's a fairly common case: when writing html or XML, you may type <, then >, then press C-b and type the tag name; or you may use < and a paredit-like setup that inserts the > automatically. If the font has a ligature for <> and you can't put the point in the middle, this breaks. Same for || — the notation |x| { … } is used for lambdas in some languages; if you type || then try to move the point back inside the composed || glyph it won't work. >> Maybe the effect wouldn't be jarring with monospaced fonts, but for these the simple approach of subdividing the glyph works nicely too. > > It might work in some simple cases, but I wonder what gains would that > give the users. It sounds very unusual to me to do something like > that, and I don't think we ever heard any such complaints until now, > although prettify-symbols-mode exists for several years. I thought I did complain in the past, but I can't find the thread any more :/ prettify-symbols-unprettify-at-point helps, and it's the default in some popular Emacs configs.