After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762832 - Ligature support
Ligature support
Status: RESOLVED DUPLICATE of bug 584160
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: VTE Maintainers
VTE Maintainers
: 767149 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-02-28 21:00 UTC by shibe
Modified: 2019-12-15 11:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description shibe 2016-02-28 21:00:49 UTC 
It would be nice if libvte would have support for font ligatures such as those used in hasklig https://github.com/i-tu/Hasklig and Fira Code.
Comment 1 Egmont Koblinger 2016-02-28 22:01:16 UTC 
Well, there are some gotchas here that don't occur with graphical apps (e.g. graphical text editors).

In a terminal text editor (vim, emacs, ...) near the left and right margins you can easily have a character displayed that is meant to be part of a ligature, yet the terminal emulator doesn't know it because its other half is outside of the canvas. This could result in weird scrolling behavior, or faulty characters (even faulty ligatures: ones that combine only two characters out of three) being displayed.

When such text is simply cat'ed, we could implement this behavior (do ligature joining on visual lines), or could locate ligatures in logical paragraphs and cut the rendered glyph in half across a line boundary if required. Both of which are problematic in some ways (not from the implementation point of view, but from the user-visible final result point of view).

I think such fonts are mainly useful in IDEs that use fixed width font, yet are aware of the entire contents rather than just the currently displayed part.
Comment 2 Christian Persch 2016-02-29 08:57:03 UTC 

*** This bug has been marked as a duplicate of bug 584160 ***
Comment 3 Egmont Koblinger 2016-06-02 10:25:32 UTC 
*** Bug 767149 has been marked as a duplicate of this bug. ***
Comment 4 Prabesh bhattarai 2019-12-15 04:01:57 UTC 
So so to read this.

When all terminals of worlds are moving forward to make things more modern and cool, and here we are in GNOME terminal.

And it dates back to 2016. Four year from now. And still no effort, no approach.

#Bummer
Comment 5 Prabesh bhattarai 2019-12-15 04:03:06 UTC 
(In reply to Prabesh bhattarai from comment #4)
> So so to read this.

So sad to read this. :)
Comment 6 Christian Persch 2019-12-15 11:21:12 UTC 
This type of comment is precisely that is NOT needed here. Please read https://wiki.gnome.org/Apps/Terminal/ReportingBugs and esp. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html *before* commenting on any bug report here.