micro-editor / micro-editor/micro
Indicate default plugins when listing installed plugins
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Currently, micro -plugin list shows all installed plugins, but doesn't indicate which are default ones, and which were installed by the user.
How it could look:
$ micro -plugin list
The following plugins are currently installed:
editorconfig (1.0.0)
filemanager (3.5.0)
manipulator (1.4.0)
quoter (1.0.0)
wc (1.2.1)
literate (1.0.0) (default)
status (1.0.0) (default)
autoclose (1.0.0) (default)
comment (1.0.0) (default)
diff (1.0.0) (default)
ftoptions (1.0.0) (default)
linter (1.0.0) (default)
Or, separate them into two lists:
$ micro -plugin list
The following plugins are currently installed:
editorconfig (1.0.0)
filemanager (3.5.0)
manipulator (1.4.0)
quoter (1.0.0)
wc (1.2.1)
Default plugins:
literate (1.0.0)
status (1.0.0)
autoclose (1.0.0)
comment (1.0.0)
diff (1.0.0)
ftoptions (1.0.0)
linter (1.0.0)
Commit hash: b9763856
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running micro -plugin list at commit b9763856 and trace the command's plugin-listing entry point. Identify how installed and default plugins are represented, then update the listing so default plugins are clearly distinguished; done means the command output matches one of the proposed formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100