# Issue with 'stuck' font in Juno/Atom

**URL:** <https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735>\
**Category:** Juno\
**Tags:** juno\
**Created:** [February 1, 2018, 10:46am UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735 "2018-02-01T10:46:31Z")\
**Posts on this page:** 5\
**Page:** 1

<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:** [February 1, 2018, 10:46am UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735/1 "2018-02-01T10:46:31Z")

</div>

I have an issue with Juno that is perhaps an Atom issue, but I’m not sure.

The font selection for the editor pane is stuck at the Hasklig font. I used that some months ago, but then wanted to change to a different one. When I change fonts in Settings → Font Family, the fonts are correctly updated in the Juno REPL and also in the workspace pane, but for some reason _not_ in the editor pane.

I’m on a Mac, and have even tried to disable the Hasklig font in Font Book, which should make it unavailable for all apps, but it’s still there inside the Atom editor pane, after a restart. This behaviour has persisted across several Atom/Juno updates, and I’m now using the latest version of both.

Perhaps this is more properly an Atom issue, but the weirdness of the interaction with the REPL/workspace panes, made me want to ask here first.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [February 1, 2018, 11:39am UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735/2 "2018-02-01T11:39:21Z")

</div>

Can you open the Electron dev tools via `Ctrl-Shift-I`, click on the `Select an element in the page to inspect it` button and then click on some text in an editor, then click on “Computed” on the right and post a screenshot of the expanded `font-family` entry?  
Also, check your stylesheet (via `Application: Open Your Stylesheet`) – there might be something like

```css
atom-text-editor {
  font-family: Hasklig !important;
}

```

in there, which would explain those issues.

---

<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:** [February 1, 2018, 5:43pm UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735/3 "2018-02-01T17:43:19Z")

</div>

Here’s the screenshot.

 ![53](https://global.discourse-cdn.com/julialang/original/3X/b/a/ba9160e32afdbc53c262ba06c5376d2bb950886c.png)

The styles.less file had this empty entry:

```julia
.atom-text-editor {

}

```

I’ve been trying to change the font to Fira Code which shows up with a strike-through.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [February 3, 2018, 2:51pm UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735/4 "2018-02-03T14:51:12Z")

</div>

Can you tell me where clicking on the top-most `<style>...</style>` takes you?

---

<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:** [February 4, 2018, 11:21am UTC](https://discourse.julialang.org/t/issue-with-stuck-font-in-juno-atom/8735/5 "2018-02-04T11:21:09Z")

</div>

Clicking on that `<style>...</style>` was a bit confusing. Not sure exactly what happened.

I managed to solve the problem anyway. It turns out that I had installed a package “atom-hasklig” which apparently overrode the font settings. When I disabled that package, font settings started to behave reasonably.

It seems like the package was necessary to enable font ligatures for Hasklig, while ligatures work by default for Fira Code.