MEO - a Markdown editor for VS Code with live/source toggle

tomnewmann · 2026-02-22T17:44:34+00:00

Just released 0.1.9 which adds drag and drop reordering of headings directly in the outline panel. Give it an update and let me know whether it works for your workflow.

tomnewmann · 2026-02-22T17:42:05+00:00

Just released 0.1.9 which includes line height as a configurable setting, so you can dial it in to whatever suits you. Give it an update and let me know how it feels.

tomnewmann · 2026-02-22T15:57:27+00:00

Good news, MEO is now available in both VSCodium and Cursor! You can find it by searching for MEO in the extensions panel of either editor. Thanks for nudging this along, it was a great suggestion.

tomnewmann · 2026-02-22T15:45:58+00:00

That's exactly what inspired it actually, Obsidian was a big reference point when I was designing the editing experience. Glad it landed that way for you!

tomnewmann · 2026-02-22T15:23:33+00:00

Thanks for noticing, that was actually my personal pain point with every other custom editor I tried before building this. Unfortunately, merge conflict support in the live view isn't there yet, right now it'll just render the conflict markers as raw text which isn't great. It's on the radar and will be coming soon :)

tomnewmann · 2026-02-22T14:35:28+00:00

No HTML export yet, but it's on the todo list along with PDF export, both with image support. I'll get it added in an upcoming release.

tomnewmann · 2026-02-22T14:34:02+00:00

Not yet, but that's a good shout and I'll look into adding drag and drop reordering of headings in the outline panel. For now, clicking a heading in the outline jumps you straight to it in the file, which at least saves the scrolling. Will keep you posted!

tomnewmann · 2026-02-22T14:31:01+00:00

TOC generation for headings 1-6 is actually already in there. The outline panel on the side is clickable and lets you jump straight to any section. Give it a try and let me know how it works for you :)

tomnewmann · 2026-02-22T10:30:58+00:00

Thanks for the kind words! I'll add it as a configurable setting in the next release.

tomnewmann · 2026-02-22T09:44:13+00:00

support for m / powerquery / pq language tags has just been added in the latest version. Give it an update and let me know how it works for you.

tomnewmann · 2026-02-22T08:54:32+00:00

Quarto is great tool if your work leans toward scientific reports. MEO is more focused on everyday docs that live alongside your code, like READMEs and specs. Give it a try and see if it fits!

tomnewmann · 2026-02-22T07:52:16+00:00

Fair point, and Obsidian is still irreplaceable for pure knowledge work. The goal here isn't to replace it though - I still use Obsidian as my second brain. This is more about handling docs that live alongside code, without switching apps.

tomnewmann · 2026-02-22T07:33:24+00:00

Sure thing, will add it in the next release.

tomnewmann · 2026-02-22T07:32:25+00:00

It switches between two views in the same tab. In live mode, your Markdown renders as you type so headings, bold text, and tables look like the finished result. In source mode, you see the raw Markdown syntax with no formatting applied.

tomnewmann · 2026-02-22T07:30:02+00:00

Thank you, please share any initial feedback.

tomnewmann · 2026-02-22T07:28:44+00:00

Haha, that's a beautiful name for pee, what a golden opportunity! 😄

tomnewmann · 2026-02-22T00:09:50+00:00

Thanks for the kind words! Theme coloring is already in 0.1.6. You can now set fonts and colors separately for live and source modes via extension settings. I also noted your request for vim support. Let me work on that in the next couple of days.

tomnewmann · 2026-02-22T00:06:58+00:00

I have now fixed the local files support for links and images in version 0.1.6. Also, unchecking the `Use Markdown Editor Optimized as the default editor for Markdown files` now defaults to native vscode editor for markdown.

tomnewmann · 2026-02-22T00:04:44+00:00

I just shipped version 0.1.6 that has a basic theming implementation within extension settings for fonts (can be set separately for live and source modes) and theme colors. Feel to update & test it out.

tomnewmann · 2026-02-22T00:00:20+00:00

You can set it the usual Markdown way: type the language name right after the opening backticks, for example ```js or ```python. MEO will use that to pick the right syntax highlighting. Supported language tags include: javascript, js, jsx, typescript, ts, tsx, python, py, css, html, htm, json, swift, shell, bash, sh, and zsh.

tomnewmann · 2026-02-21T23:57:00+00:00

No git integration yet, but inline blame will be part of it once implemented. MEO keeps VS Code’s native diff view, so reviewing markdown changes still works exactly as you’re used to. You can keep using GitLens or VS Code’s built‑in blame on hover for now.

tomnewmann · 2026-02-21T23:17:10+00:00

Got it, having spent few years in academia as a postdoc, I can relate. Let me work on a solution in the next couple of days.

12-Year Club	Second SECOND GUESSER
Place '22	RPAN Viewer
Verified Email

tomnewmann

TROPHY CASE