3 ms·
Exactly that, plus it doesn't really serve well as platform. I mean VSCode renders Markdown previews correctly, not some ASCII based approximation. It renders i
by p2t2p 5y ago
Exactly that, plus it doesn't really serve well as platform. I mean VSCode renders Markdown previews correctly, not some ASCII based approximation. It renders images if I happen to click on one. Extensions can actually provide decent UI, thank's to that CSVs never looked better in my text editors.
- underatree 5y agoI use Emacs's markdown mode for syntax highlighting. I have never used live export, but looked for it in its dropdown menu, found it, and clicked it: https://i.imgur.com/0LG6nnS.png https://i.imgur.com/0LG6nnS.png It renders images and doesn't rely on ASCII for its rendering. I agree Emacs could benefit from some polish, on the whole.
- p2t2p 5y agoI compared it two what I see in my VSCode (https://imgur.com/a/u9naqVi https://imgur.com/a/u9naqVi) and fair enough, it got way better since I tried it last time.
- AlanYx 5y agoBoth the examples you give seem kind of arguable; I'd almost say they demonstrate the opposite. The problem with VSCode's built-in Markdown previews is that they're not extensible, so there are a variety of alternate Markdown renderer plugins, for example to better work with the various wiki-like Markdown plugins. Emacs also has Markdown previewing, but it is extensible by design. I'm not an expert in either VSCode or Emacs (I use both off and on), but inline image handling seems like it works better in Emacs. I've never figured out how to show Markdown images inline in the actual text editor part of VSCode (as opposed to the preview), whereas that's super easy in Emacs.