jesseduffield / jesseduffield/horcrux
Are -t and -n options are available just before `split` subcommand?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 141
- PR merge metrics
- No merged PRs in 30d
Description
Or it's a malformed [documentation](https://github.com/jesseduffield/horcrux/blob/master/main.go#L63) and it's right to use options after `split` subcommand? I am asking as providing options before subcommand when they are not global is the bad idea: subcommand is like some sort of namespace which allows us access just some options and not all at once not to have a big mess.
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
Read main.go around line 63 and inspect how the -t and -n options are declared relative to the split subcommand. Confirm the supported command-line syntax, then update the referenced documentation so the option placement is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100