CLI shows help for commands that does not exist
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Search first
- I searched and no similar issues were found
What Happened?
See title
Reproduce the Bug
"$HOME"/.local/bin/logseq --graph "eee" destroy-the-world2 --help
Usage: logseq destroy-the-world2 <subcommand> [options]
Subcommands:
Global options:
--config <path> Path to cli.edn (default <root-dir>/cli.edn)
-g, --graph <graph> Graph name
--root-dir <path> Path to CLI root dir (default ~/logseq)
--timeout-ms <ms> Request timeout in ms (default 10000)
-o, --output <mode> Output format (choices: human, json, edn; default: human)
-v, --verbose Enable verbose debug logging to stderr
--profile Enable stage timing profile output to stderr
-h, --help Show command help
--version Show CLI version
Command options:
See `logseq destroy-the-world2 <subcommand> --help`
Expected Behavior
It should clarify that the command does not exist. Optionally suggest existing command with similar name for typo.
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260624
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
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
Reproduce the issue with logseq --graph "eee" destroy-the-world2 --help, then locate the CLI command-resolution entry point that handles unknown commands. Verify how valid and invalid commands are distinguished and add or update coverage for the nonexistent-command case; done means the command reports that it does not exist instead of displaying subcommand help.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100