micro-editor / micro-editor/micro

create user.micro merge to each colorscheme without create them under user colorscheme folder

Open
#3,490 5 comments 0 reactions 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

I have implement org highlight with syntax/org.yaml

filetype: org

detect:
    filename: "\\.org$"

rules:
      # headlines
    - headline:  "^\\*+ .*"
    - priority:  "^\\*+ (\\[.+\\] |[A-Z]+ )+"

      # comment
    - comment: "# .*"

      # tables
    - table: "[[:space:]]*\\|.+\\|"

      # bold italic delete underline mono
    - emphasize: "\\*[^ *][^*]*[^ *]\\*"
    - italic: "/[^ ].*[^ ]/"
    - delete: "\\+[^ ].*[^ ]\\+"
    - underline: "_[^ ].*[^ ]_"
    - mono: "[=~][^ =~].*[^ =~][^=~]"

      # lists
    - list: "^([[:space:]]*[+-] |^[[:space:]]*[0-9a-zA-Z]+[).] )(\\[.\\] )?"

      # links
    - link: "\\[(\\[[^]]+\\]){1,2}\\]"

      # urls
    - url: "https?://[^ )>]+"

      # block
    - block:
        start: "^#\\+begin_.*"
        end: "^#\\+end_[^ ]*"
        rules: []
    - block: "^#\\+.*"

and create colorscheme/user.micro

color-link headline "bold #282828,#E6DB74"
color-link priority "#CB4B16,#282828"
color-link table "#66D9EF,#282828"
color-link emphasize "bold #AE81FF,#282828"
color-link italic "#E6DB74,#282828"
color-link mono "#ABE674,#282828"
color-link delete "#505050,#282828"
color-link underline "#BDE6AD,#282828"
color-link list "#F92672,#282828"
color-link link "#CB4B16,#282828"
color-link url "bold #CB4B16,#282828"
color-link block "#C6EF74,#282828"

and copy every buildin colorscheme file to micro user colorscheme folder, then append 'include "user"' to every .micro file. is there a way to avoid create so much duplicated files and merge user.micro to any colorscheme selected, maybe an option?

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 by examining colorscheme/user.micro, the built-in colorscheme files, and how their include directives are handled. Determine where selected colorschemes are loaded, then define the smallest change that applies user colors without duplicating every .micro file; done means the user rules appear with any selected built-in colorscheme.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.