[DOC] doc.md + `man 1 lsd` fail to list custom theme-ing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
🤔 manpages should list file(s) associated to the program near the bottom of the the page.
Please add the following section @ https://github.com/lsd-rs/lsd/blob/master/doc/lsd.md?plain=1#L167
PS; I don't know how well PANDOC formats Markdown links to Manpages!
……………………………………………………………………………………………………………………………
# FILES
`$HOME/.config/lsd/config.yaml`
`$HOME/.config/lsd/colors.yaml`
`$HOME/.config/lsd/icons.yaml`
: Download the optional configuration files from the Github LSD repository.
[ConfigurationTemplate](https://github.com/lsd-rs/lsd/tree/master?tab=readme-ov-file#config-file-content)
[ThemeColors](https://github.com/lsd-rs/lsd/tree/master?tab=readme-ov-file#color-theme-file-content)
[ThemeIcons](https://github.com/lsd-rs/lsd/tree/master?tab=readme-ov-file#icon-theme-file-content)
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 in doc/lsd.md around line 167 and inspect how it is converted to the `man 1 lsd` page. Add a FILES section listing the three configuration paths and their repository links, then verify that the generated manpage formats the Markdown links acceptably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100