From: Eli Zaretskii <eliz@gnu.org>
To: Charles Jackson <charles.b.jackson@protonmail.com>
Cc: 36914@debbugs.gnu.org
Subject: bug#36914: Font Ligatures
Date: Sun, 04 Aug 2019 18:32:52 +0300 [thread overview]
Message-ID: <834l2xdjyz.fsf@gnu.org> (raw)
In-Reply-To: <xUQAga-e27WNWZq6JAcGl-0xS2xTVjwZRRrnDk1JDe6XFdPDCOxwqEjUGxpePRTkjlXx78F94pOeTmZBkeWLKEiL0duPsUEsD9cwgvnNPhE=@protonmail.com> (message from Charles Jackson on Sun, 04 Aug 2019 03:05:28 +0000)
> Date: Sun, 04 Aug 2019 03:05:28 +0000
> From: Charles Jackson <charles.b.jackson@protonmail.com>
>
> I would think that it should be able to be turned on and off. as well as each ligature should be able to be turned on and off. If someone likes "fi" but not "ffi" then they should be able to turn "ffi" off. I would also think that it should be mode specific: "fi" should be enabled for text-mode but not for any prog-mode. On the other hand a ligature for != (becoming a not equals sign) should be enabled for C like language modes but /= should form the same ligature for Haskell and Lisp.
>
> Another important thing about ligatures that is different than pretty symbols mode is that the ligature should take up the same amount of space as the original characters. For example: the not equals ligature should not simply be the "≠" Unicode character because that only takes up one space but the original characters != or /= take up two spaces. this will solve the spacing (indenting) issue. Similarly the ligature for === in Javascript (that many programming ligature font enable) should take up a full three character widths.
>
> What do you think?
First, please keep the bug address on the CC list (use "Reply to
All"), so that this discussion is recorded by our issue tracker.
More to the point, I think this makes the job somewhat complicated,
especially the "same amount of space" part, and hope that someone
volunteers to do it.
Thanks.
prev parent reply other threads:[~2019-08-04 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 20:34 bug#36914: Font Ligatures Charles Jackson
2019-08-04 2:45 ` Eli Zaretskii
[not found] ` <xUQAga-e27WNWZq6JAcGl-0xS2xTVjwZRRrnDk1JDe6XFdPDCOxwqEjUGxpePRTkjlXx78F94pOeTmZBkeWLKEiL0duPsUEsD9cwgvnNPhE=@protonmail.com>
2019-08-04 15:32 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l2xdjyz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36914@debbugs.gnu.org \
--cc=charles.b.jackson@protonmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.