<table> <tr> <td colspan="3" align="center"> <h3>CodeMirror Options</h3> </td> </tr> <tr> <td width="225px" rowspan="7" align="center"> <img src="./assets/joplin.svg" width="64"><br>
npm install joplin-plugin-cmoptionsCodeMirror Options | ||
| ||
| Adds some CodeMirror options to Joplin's settings, such as line numbers and line wrapping. | ||
| Links: | ||
| Built with: | generator-joplin | |
| Inspired by: | Joplin Line Numbers Plugin | |
| Other plugins by me: | Search & Replace, MultiMarkdown Table Tools | |
This is a simple plugin for Joplin that exposes some CodeMirror options to the user, such as line wrapping or line numbers.
> Note:
> This plugin only affects the Markdown editor (CodeMirror), not the WYSIWYG editor (TinyMCE).
See the screenshots below:
#### Options

#### Line numbers

#### Vim-like relative line numbers

- Go to the settings (Tools → Options) → Plugins
- Search for CodeMirror Options
- Click 'Install' and restart Joplin
- Enjoy
- Download the *.jpl file from the releases section
- Go to the settings (Tools → Options) → Plugins
- Click the gear next to 'Manage your plugins' and choose 'Install from file'
- Select the downloaded *.jpl file
- Restart Joplin
- Enjoy
- After installation, a new section will appear in the options. (see screenshot)
- Tweak to your heart's content.
Text from "generator-joplin"
This is a template to create a new Joplin plugin.
The main two files you will want to look at are:
- /src/index.ts, which contains the entry point for the plugin source code.
- /src/manifest.json, which is the plugin manifest. It contains information such as the plugin a name, version, etc.
The plugin is built using Webpack, which creates the compiled code in /dist. A JPL archive will also be created at the root, which can use to distribute the plugin.
To build the plugin, simply run npm run dist.
The project is setup to use TypeScript, although you can change the configuration to use plain JavaScript.
To update the plugin framework, run npm run update.
In general this command tries to do the right thing - in particular it's going to merge the changes in package.json and .gitignore instead of overwriting. It will also leave "/src" as well as README.md untouched.
The file that may cause problem is "webpack.config.js" because it's going to be overwritten. For that reason, if you want to change it, consider creating a separate JavaScript file and include it in webpack.config.js. That way, when you update, you only have to restore the line that include your file.