![]() Yes, there are a few extensions available for this, but they don’t hit the mark. The other really big hole in VS Code is the lack of good spell/grammar checking. You have the nice shiny live version sitting right next to your eye, with all the nice CSS applied, but you can’t really use it much because the actual editing happens elsewhere - shame really. For the actual writing part however, my attention was forced on the other pane - the markdown itself where, apart from the syntax highlighting, could really be any generic text editor. The live preview is good, but I never really found myself using it apart from quick checks to see if I hadn’t screwed up the markup and that everything looks the way I intended. I can’t imagine writing a book etc in VS Code for example, even if markdown is a pretty good option for it. Even with all the extensions available for markdown and the live preview version you can get in another pane, there are some big holes in the overall experience when you want to get away from the markup. It worked just fine, it’s really just a text editor, but there is autocomplete templates and syntax highlighting etc for markdown files.įor small dev markdown files and documentation this is all that’s really needed, but for longer pieces of text, I found myself wanting something a little better (more like Word I will admit). Since VS Code has come into popularity, I had always used it to write blog posts like this one in markdown. Typora - A Better Markdown Editor VS Code Doesn’t Cut It
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |