micro-editor / micro-editor/micro
Syntax highlighting in crontab, ssh_config/sshd_config, and other files
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Hi, as you can see above, the crontab syntax highlighting is not registering because when i run crontab -e to edit my crontab file, the directory is /tmp/crontab.* instead of the one specified here.
As for editing ssh_config & sshd_config in /etc/ssh/, could you implement syntax highlighting like in vim:
Also would it be possible to provide syntax highlighting for all files starting with # symbols for comments? (for all ft:unknown) Here i made a file called ~/repos/hi with no file extension. In vim the syntax highlighting for comments is like so:
Commit hash: cfcb2e45 (same on ba98b55)
OS: Linux - Garuda Gnome
Terminal: gnome-terminal
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 with runtime/syntax/crontab.yaml, then inspect how micro identifies syntax for temporary crontab files and extensionless files. Reproduce the cases with crontab -e, /etc/ssh/sshd_config, and an unknown file, and compare the result with the requested Vim-style highlighting. Done means the relevant crontab, SSH configuration, and comment lines receive syntax highlighting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, yaml
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100