Using VSCode + Joplin as a note taking tool

joplin, joplin-vscode-plugin

Why I use Joplin

Note: Open source, platform independent and markdown based easy to migrate this is an important point because no one knows which note taking tool is the ultimate winner, if not the right one, then at least easy to migrate.

I have used some note-taking tools, including Impression, OneNote, Notion, but eventually gave up.
The key is that some of my core needs are not met:

1. the search should be fast
2. the editor experience should be good
3. data should be able to export all
4. based on the standard md, can be directly copied to other platforms
5. can be based on it for secondary development
6. not dead yet

Let's take a closer look at the features of the above tools

Impression Notes

Well, there is an international/domestic version of Impression Notes, but the domestic version is obviously a typical example of receiving money for not doing the right thing, and nothing has changed for a long time. Also, markdown support is not official, but requires a third-party plugin (it seems to be supported after the late 18 update). And recently Impression Notes also grabbed the domestic notion's image trademark, really can be said to be a unique domestic spectacle up.

OneNote

Honestly, if you're used to using Office to organize documents, OneNote is still very good, the editing experience is consistent with Word, and the search is extremely fast. But unfortunately, I am a firm everything is markdown based person, so I don't like OneNote.

Notion

Notion is one of the more satisfying note taking tools I've encountered so far, but there are 3 main things I'm not too happy about.

1. the editor is rather stuck
2. the search is very slow
3. can't export all data

Specific reference: Notion experience

Joplin, on the other hand, is a note taking tool that I can solve the above problems of notion, while open source and free, allowing me to participate in it.

Main advantages.

1. search is fast, very fast
2. can be opened using an external editor
3. data are in their own hands , providing a one-time export of all the functions
4. using the standard md, can be copied directly to other platforms
5. can be based on it for secondary development

Main disadvantages.

1. ui/ux is a bit rudimentary
2. no vsc plug-in makes it not very convenient to use external editors

Why I have to write this plug-in for vscode

1. as a professional editor in the editing function vscode is unmatched by the notes tool. For example, shortcut key support
2. vscode is not only an editor, but also has a very large ecosystem of plugins, so in markdown formatting, linter verification, pdf export and other features have long been implemented, no need to repeat the wheel in the notes tool to build -- and may be the square wheel In fact, I've been using vscode for markdown editing, and git + vscode for storing company-related documents. I've also been using joplin to store my personal notes, but I've realized over time that what I need is vscode's editing + joplin's sync/search functionality.

So I wrote this plugin for people who have the same needs as me.

Reference: Future of Joplin

Introduction

Integrate joplin in VSCode and implement the common features of Joplin.

! Preview image

Plugins

First a short list of my note taking related plugins, they all implement a specific feature and can be combined.

• Markdown All in One: Markdown language support
• markdown lint: Markdown linter tool
• Prettier: multi-language formatting tool, very good support for markdown
• PicGo: image upload (this is a third-party program)
• Markdown PDF: Markdown export PDF
• Draw.io Integration: draw.io Flowchart Integration
  • Markdown Preview Mermaid Support: mermaid flowchart support DSL, but draw.io is better
• vscode-mindmap: mind map integration (this is the fork version, but it's much better)
• Local History: local history
• Code Spell Checker: Word spell checker
• joplin-vscode-plugin: joplin notes integration

You may notice that some of these plugins have nothing to do with markdown, but they are still important for editing, for example the spell checking feature only recently (v1.4.*) implemented in Joplin already exists in existing VSCode plugins.

These plugins solve the problems my generation also submitted in joplin vs. vscode-like editors differences, so I won't go into them here.

Problems solved

I've briefly browsed the last two weeks of Joplin posts, and the following problems seem to have been solved/implemented in VSCode

• Please add an easy to access markdowns: Quickly add lists
• Markdown keyboard shortcuts: markdown shortcut support
• Duplicate line command: Copy and paste to the next line
• Please auto replace to Bullet/Number/Checkbox list: Again, add the list quickly
• Auto attach images as resources after external editor: Paste images after external editor supports Joplin
• Integration of PlantUML: PlantUML integration
• Find and Replace: Find and Replace support
• Making Joplin recognise YAML front matter: markdown yaml metadata support
• Plugin: Note Tabs: Multi-tab support
• Option to show line numbers in editor: Show line numbers
• Incomplete TOC sidebar: outline support
• Feature request: Folding sections of text: code Block Folding

Effects

Finally, the configured VSCode editor edits Markdown as follows