# Font in editor no longer monospaced?

**URL:** https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087
**Category:** Development
**Created:** [30 Novembre 2017, 12:09pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087 "2017-11-30T12:09:15Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)
#### Post date: [30 Novembre 2017, 12:09pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/1 "2017-11-30T12:09:15Z")

</div>

Is this intentional? Running discourse-1.9.0.beta14~git446.610d7a9412

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [30 Novembre 2017, 12:59pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/2 "2017-11-30T12:59:56Z")

</div>

By editor you mean the composer? It has never been monospaced.

---

<div class="post-metadata">

### Author: ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)
#### Post date: [30 Novembre 2017, 1:14pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/3 "2017-11-30T13:14:43Z")

</div>

hmm I had the feeling it was in the past. It would be nice to have that as an option especially for posts with lots of code blocks.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [30 Novembre 2017, 1:35pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/4 "2017-11-30T13:35:21Z")

</div>

Use code formatting for code blocks?

---

<div class="post-metadata">

### Author: ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)
#### Post date: [30 Novembre 2017, 1:36pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/5 "2017-11-30T13:36:30Z")

</div>

err the output is not the problem … I usually write longer posts in a text editor anyway. but e.g. when you use “------” to mark sections then the heading length and the length of the “----” part no longer mathc. this can be confusing.

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [30 Novembre 2017, 1:45pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/6 "2017-11-30T13:45:58Z")

</div>

I’m not sure I understand what you’re talking about? Are we still on monospace/code blocks?

---

<div class="post-metadata">

### Author: ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)
#### Post date: [30 Novembre 2017, 2:01pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/7 "2017-11-30T14:01:10Z")

</div>

no. I am talking about that a monospaced font might be better for editing markdown formatted content

## Just take this as an example

The line under the heading doesnt match the length anymore in the composer.

This can be confusing. (see the markdown source of my comment)

---

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [30 Novembre 2017, 2:29pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/8 "2017-11-30T14:29:54Z")

</div>

I see, but considering only one " `-`" is enough to promote the line to a title, I think there’s no need for monospace.

---

<div class="post-metadata">

### Author: ![darix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darix/32/114280_2.png) [@darix](https://meta.discourse.org/u/darix)
#### Post date: [30 Novembre 2017, 2:30pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/9 "2017-11-30T14:30:53Z")

</div>

would it be hard to implement an user option to switch the font for the composer?

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [30 Novembre 2017, 2:45pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/10 "2017-11-30T14:45:13Z")

</div>

I’ve thought about this a bit before and I don’t hate the idea. The benefit of using a monospaced font is that it’s a quick indication of “this isn’t a WYSIWYG editor” and further distinguishes the editing space from the preview in the composer.

There are some downsides though; monospaced fonts do take a bit longer to read and have some general quirks. [IA Writer has spun these as benefits](https://ia.net/topics/in-search-of-the-perfect-writing-font/), but kind of caved and developed their own new “kind-of monospace” typeface to avoid those quirks.

 ![23 AM](https://global.discourse-cdn.com/meta/original/3X/2/2/228e1159da947d919033e03a9cfe4d8df3ed1a8a.png)

Either way, there aren’t any significant problems this solves with our existing editor, and it’s pretty easy for admins to customize this themselves on their instance - so any sort of additional feature wouldn’t be high priority.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [30 Novembre 2017, 10:12pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/11 "2017-11-30T22:12:06Z")

</div>

For the record I also much prefer monospace for markdown formatting. @codinghorror [is not keen](https://meta.discourse.org/t/code-areas-use-different-font-with-different-spacing/29715/5) on making this a global default at all.

Font was never monospace in the editor from the first release of Discourse.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [30 Novembre 2017, 11:54pm UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/12 "2017-11-30T23:54:00Z")

</div>

Oh my gosh what is with all the people seeing a feature that has been the same in Discourse since 2013 and suddenly exclaiming “you have changed this!” when .. _we haven’t!_

It’s like they are seeing the editor / composer for the first time, suddenly.. quite a victory of design, let’s applaud 👏 @awesomerobot

---

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [1 Dicembre 2017, 12:04am UTC](https://meta.discourse.org/t/font-in-editor-no-longer-monospaced/75087/13 "2017-12-01T00:04:04Z")

</div>

Monospace or no, I for one embrace our new awesome layout overlords. 🎉
