unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: nicolaso@google.com, lumarzeli30@gmail.com, emacs-devel@gnu.org
Subject: Re: Supporting stylistic sets
Date: Mon, 26 Sep 2022 22:20:24 +0300	[thread overview]
Message-ID: <83y1u6j62v.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8X=1V8YUbE6tNnaaDp12xex61bSr8ST3orOrFhf73gNrw@mail.gmail.com> (message from Yuri Khan on Tue, 27 Sep 2022 02:06:35 +0700)

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Tue, 27 Sep 2022 02:06:35 +0700
> Cc: Nicolas Ouellet-payeur <nicolaso@google.com>, lumarzeli30@gmail.com, emacs-devel@gnu.org
> 
> On Tue, 27 Sept 2022 at 01:55, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > And second, it is not good enough to have the property on the "-:---"
> > part, because that's where the input-method mnemonics are displayed,
> > and those frequently do need ligations, if they use characters from
> > scripts which require that.
> 
> Maybe just put a zwnj between every two directly adjacent fields to
> prevent ligation?

It's possible.  But then (1) we'd need to always have the ZWNJ there;
(2) some mode-line constructs are produced by formatting text with
tricky format specs, and some could come from the user or some Lisp
program that are utterly unaware of these subtleties; and (3) Emacs by
default displays ZWNJ as a thin space.  So this is not the best
solution, IMO.

I tend to think this is just one aspect of a more general problem,
which is: how do users/Lisp programs control which characters will or
will not ligate in what situations?  For example, take ffi: you might
not want the characters f f i to ligate in a variable name, or in some
major modes as opposed to others, etc.  When we figure out how to
specify when to ligate, we need that specification support the mode
line and other places (like maybe be tab bar/tab line).



  reply	other threads:[~2022-09-26 19:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 12:54 Supporting stylistic sets समीर सिंह Sameer Singh
2022-09-23 15:37 ` Eli Zaretskii
2022-09-23 17:27   ` समीर सिंह Sameer Singh
2022-09-23 17:31     ` Nicolas Ouellet-payeur
2022-09-23 18:09       ` Eli Zaretskii
2022-09-23 19:20         ` Nicolas Ouellet-payeur
2022-09-23 20:10           ` Eli Zaretskii
     [not found]             ` <CADuLPF5sKi4NMcGSdy1GAi8=KHBfUcVa3tV=XwnhPfWxroAJCA@mail.gmail.com>
2022-09-26 17:07               ` Eli Zaretskii
2022-09-26 17:46                 ` Nicolas Ouellet-payeur
2022-09-26 18:28                   ` Eli Zaretskii
2022-09-26 19:06                     ` Yuri Khan
2022-09-26 19:20                       ` Eli Zaretskii [this message]
2022-09-23 17:55     ` Eli Zaretskii
2022-09-23 18:26       ` Visuwesh
2022-09-23 18:55         ` Eli Zaretskii
2022-09-24  4:59           ` Visuwesh
2022-09-24  6:33             ` Eli Zaretskii
2022-09-24  8:42               ` Visuwesh
2022-09-24  4:43       ` समीर सिंह Sameer Singh
2022-09-24  6:55         ` Eli Zaretskii
2022-09-24  8:00           ` समीर सिंह Sameer Singh
2022-09-24  8:27             ` Eli Zaretskii
2022-09-24  8:34               ` समीर सिंह Sameer Singh
2022-09-24  8:38                 ` Eli Zaretskii
2022-09-24  8:41                   ` समीर सिंह Sameer Singh
2022-09-24  8:50                   ` समीर सिंह Sameer Singh
2022-09-24 12:09                     ` समीर सिंह Sameer Singh
2022-09-24 12:35                       ` Eli Zaretskii
2022-09-24 12:45                         ` समीर सिंह Sameer Singh
2022-09-24 13:00                           ` Eli Zaretskii
2022-09-24 13:10                             ` समीर सिंह Sameer Singh
2022-09-24 14:18                               ` Eli Zaretskii
2022-09-24 14:26                                 ` समीर सिंह Sameer Singh
2022-09-24 15:01                                   ` Eli Zaretskii
2022-09-24 15:02                                     ` समीर सिंह Sameer Singh
2022-09-24 15:21                                       ` Eli Zaretskii
2022-09-24 15:50                                         ` समीर सिंह Sameer Singh
2022-09-24 16:14                                           ` Eli Zaretskii
2022-09-24 16:42                                             ` Yuri Khan
2022-09-24 17:02                                               ` Eli Zaretskii
2022-09-24 17:09                                             ` समीर सिंह Sameer Singh
2022-09-24 17:11                                               ` समीर सिंह Sameer Singh
2022-09-25 22:19                                             ` Clément Pit-Claudel

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=83y1u6j62v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lumarzeli30@gmail.com \
    --cc=nicolaso@google.com \
    --cc=yuri.v.khan@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).