# Display of =\> using JuliaMono

**URL:** https://discourse.julialang.org/t/display-of-using-juliamono/48619
**Category:** Tooling
**Tags:** question
**Created:** [October 19, 2020, 11:05am UTC](https://discourse.julialang.org/t/display-of-using-juliamono/48619 "2020-10-19T11:05:20Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)
#### Post date: [October 19, 2020, 11:05am UTC](https://discourse.julialang.org/t/display-of-using-juliamono/48619/1 "2020-10-19T11:05:20Z")

</div>

I’ve been facing a somewhat strange issue using the JuliaMono font, where the `Dict` map character `=>` displays differently depending on the type of the key.

![Selection_036](https://global.discourse-cdn.com/julialang/original/3X/b/6/b64bf9dd0bb36a3192b4f1e09b85f95a9137ef6c.png)

I am using Sublime text as my editor, wondering if anyone else has faced this and if there’s a way to get them to appear identical. Unfortunately it doesn’t appear that the repo is being actively maintained.

---

<div class="post-metadata">

### Author: ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)
#### Post date: [October 19, 2020, 11:28am UTC](https://discourse.julialang.org/t/display-of-using-juliamono/48619/2 "2020-10-19T11:28:40Z")

</div>

It’s pretty weird. Here are some examples:  
 ![image](https://global.discourse-cdn.com/julialang/original/3X/b/8/b85aa0bb4fcc4707e1ce8c107b3b79d6fa6a9b2c.png)  
It seems to fail when the arrow is preceeded by an alphanumeric character, a parenthesis and then another alphanumeric character.

If I switch to a different syntax, say, markdown, everything displays correctly with ligatures, so there is some connection to the Julia syntax scheme. If I switch to python syntax, no ligatures are shown.

---

<div class="post-metadata">

### Author: ![cormullion](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cormullion/32/49131_2.png) [@cormullion](https://discourse.julialang.org/u/cormullion)
#### Post date: [October 22, 2020, 7:44pm UTC](https://discourse.julialang.org/t/display-of-using-juliamono/48619/3 "2020-10-22T19:44:41Z")

</div>

The Sublime Text documents say:

> Additionally, the sequence of characters that comprise the ligature must all be part of the same token, as defined by the syntax being used to display the file.

I have no idea what these tokens are, because SublimeText’s syntax files are not my idea of bedtime reading - but it’s possible that the syntax rules are interfering with the text-shaping process.

The font-drawing process only happens once (until a redraw), so perhaps certain combinations of characters are bypassed in certain contexts? The font is probably not to blame, because it’s not doing anything very complicated (no look-aheads or look-behinds, for example).

---

<div class="post-metadata">

### Author: ![cormullion](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cormullion/32/49131_2.png) [@cormullion](https://discourse.julialang.org/u/cormullion)
#### Post date: [October 22, 2020, 7:53pm UTC](https://discourse.julialang.org/t/display-of-using-juliamono/48619/4 "2020-10-22T19:53:17Z")

</div>

Also from the same document:

> See if the ligatures appear when using the “Plain Text” syntax for the file. If so, the syntax is likely breaking the symbols into distinct tokens, preventing a ligature from being used.

So it’s probably a job for the author of the syntax file…
