micro-editor / micro-editor/micro

Support installing plugins from a local directory

Open
#1,990 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
29.6k
Forks
1.4k
Avg merge
2d 18h
Merged PRs (30d)
10

Description

It would be convenient if micro -plugin install would accept a path to a directory as an argument. This would be a bit more convenient for development. It's better than editing my source code in my home directory or constantly copyin g things. The alternatve that I currently use though is I use the environment variable to tell micro its configuration is located in my development tree: MICRO_CONFIG_HOME=$(pwd)/micro $(pwd)/result/bin/micro , however I still have to either put the code in the config dir, or symlink individual files because of the symlink bug.

There are also two possible scenarios

  • the target is copied into micro's directory as with normal plugins: this means editing the original directory will not influence what's running
  • it's symlinked: opposite of the above

It's not obvious to me that either of these would necessarily be superior so both could be done.

Symlink support would need to be fixed for the latter: https://github.com/zyedidia/micro/issues/1949

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the micro -plugin install command path and read issue #1949 for the symlink limitation. Decide whether a local directory should be copied, symlinked, or support both, then verify the chosen behavior for a directory argument and development edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.