# Non-Markdown files should not use markdown rendering

**URL:** <https://community.bear.app/t/non-markdown-files-should-not-use-markdown-rendering/19392>\
**Category:** Lettera feedback\
**Tags:** bug\
**Created:** [June 22, 2026, 2:35pm UTC](https://community.bear.app/t/non-markdown-files-should-not-use-markdown-rendering/19392 "2026-06-22T14:35:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gormus](https://avatars.discourse-cdn.com/v4/letter/g/8797f3/32.png) [@gormus](https://community.bear.app/u/gormus)\
**Post date:** [June 22, 2026, 2:35pm UTC](https://community.bear.app/t/non-markdown-files-should-not-use-markdown-rendering/19392/1 "2026-06-22T14:35:11Z")

</div>

- **Lettera Version** : 1.0.0 (3980)
- **macOS Version** : 26.5.1 (25F80)
- **What were you doing** : Opening a folder containing various file formats
- **What feature did you use** : None. just opening listed files, whether they are Markdown files or not
- **What happened** : Most non-Markdown files were opened as plain text; but some were falsely rendered as if they were Markdown. i.e. I opened a bash script with a `.sh` extension; the inline comments prefixed with `#` were rendered as H1 headings 🤦
- **What did you expect to happen** : Non-Markdown files, especially if their extension is not `.md` or `.markdown` should not be rendered as Markdown.

I’d personally prefer all files that are not Markdown files are rendered read-only with syntax highlighting enabled, the very same one used for code-blocks.

For context; I open my development/code project folders in Lettera. Those projects contain scripts and various other files beside the main focus of markdown files.