github/zyedidia.micro
2
0
Fork 0
mirror of https://github.com/zyedidia/micro.git synced 2026-03-16 22:07:09 +09:00
Code Issues Packages Projects Releases Wiki Activity

Small Documentation Improvement (#3786)

Browse Source
This commit is contained in:
cutelisp
2025-07-25 20:02:33 +01:00
committed by GitHub
parent d7e43d4974
commit f97cba34d2
5 changed files with 14 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
runtime/help/copypaste.md
View File

@@ -23,7 +23,7 @@ Here is a list of terminal emulators and their status:
* `st`: supported.
* `rxvt-unicode`: not natively supported, but there is a Perl extension
[here](http://anti.teamidiot.de/static/nei/*/Code/urxvt/).
[here](https://anti.teamidiot.de/static/nei/*/Code/urxvt/).
* `xterm`: supported, but disabled by default. It can be enabled by putting
the following in `.Xresources` or `.Xdefaults`:

10
runtime/help/plugins.md
View File

@@ -509,8 +509,8 @@ Micro also has a built in plugin manager, which you can invoke with the
For the valid commands you can use, see the `commands` help topic.
The manager fetches plugins from the channels (which is simply a list of plugin
metadata) which it knows about. By default, micro only knows about the official
channel which is located at github.com/micro-editor/plugin-channel but you can
metadata) which it knows about. By default, micro only knows about the [official
channel](https://github.com/micro-editor/plugin-channel) but you can
add your own third-party channels using the `pluginchannels` option and you can
directly link third-party plugins to allow installation through the plugin
manager with the `pluginrepos` option.
@@ -537,9 +537,9 @@ This file will contain the metadata for your plugin. Here is an example:
}]
```
Then open a pull request at github.com/micro-editor/plugin-channel, adding a
link to the raw `repo.json` that is in your plugin repository.
Then open a pull request at the [official plugin channel](https://github.com/micro-editor/plugin-channel),
adding a link to the raw `repo.json` that is in your plugin repository.
To make updating the plugin work, the first line of your plugin's lua code
should contain the version of the plugin. (Like this: `VERSION = "1.0.0"`)
Please make sure to use [semver](http://semver.org/) for versioning.
Please make sure to use [semver](https://semver.org/) for versioning.