# New Highlighter: Addressing your feedback and next steps

**URL:** https://community.bear.app/t/new-highlighter-addressing-your-feedback-and-next-steps/13771
**Category:** Bear feedback
**Created:** [September 19, 2024, 10:04am UTC](https://community.bear.app/t/new-highlighter-addressing-your-feedback-and-next-steps/13771 "2024-09-19T10:04:30Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![matteo](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/matteo/32/21_2.png) [@matteo](https://community.bear.app/u/matteo)
#### Post date: [September 19, 2024, 12:47pm UTC](https://community.bear.app/t/new-highlighter-addressing-your-feedback-and-next-steps/13771/4 "2024-09-19T12:47:42Z")

</div>

> [@AleemShaun](#):
>
> I’m curious about the rationale for exporting a colour emoji in the highlight markdown syntax (for all non-default colours) - what’s the perceived benefit? I’d prefer it was just standard markdown syntax regardless of the chosen colour.

There are several advantages to doing this:

1. You can re-import the Markdown into Bear, and your color formatting will remain intact.

2. Markdown is designed to be readable without a specialized editor, so preserving the color information in plain text ensures that the meaning remains clear:

3. Ideally, if this gains popularity, other editors could easily adopt support for it as well. 😊

> [@AleemShaun](#):
>
> Also, is there any possibility/likelihood of being able to select a different default colour option?

This is a bit challenging, as changing the default syntax color would alter the meaning in all of your existing notes. We’ve considered it, but we worry it could create confusion.

---

_[View the full topic](https://community.bear.app/t/new-highlighter-addressing-your-feedback-and-next-steps/13771)._