René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Typo suggestion prints \"Did you mean ''?\" when no command is close","articleBody":"hey.. found a small bug when i was trying out the CLI..\n\n  when u type a command thats close to a real keyword, it gives a good suggestion like :\n\n      $ context-dev brnd\n      No help topic for 'brnd'. Did you mean 'context-dev brand'?\n\n  but when the command is not close to anything, the suggestion comes out empty:\n\n      $ context-dev qqqq\n      No help topic for 'qqqq'. Did you mean ''?\n\n  so it shows \"Did you mean ''?\" with nothing inside the quotes.\n\n  i think the cause is in pkg/cmd/suggest.go: suggestCommand always returns a\n  \"Did you mean '...'?\" string, even when it didnt find a close match. the\n  original urfave/cli version returns an empty string in that case, and the\n  caller only prints a suggestion when its not empty - so here the empty one\n  slips through.\n\n  happy to send a small PR for this if its useful - basically return an empty\n  string when nothing's close, so it just stays quiet. real typos like 'brnd'\n  would keep working.\n\n  _side thought_ (separate from the bug, feel free to ignore): when nothing is\n  close, instead of showing nothing, maybe it could nudge people toward the\n  command list? something like:\n\n      No help topic for 'qqqq'. Run 'context-dev --help' to see available commands.\n\n  or if a couple of commands are actually similar, just list those few. not sure\n  if that fits the direction u want - happy to help either way","author":{"url":"https://github.com/pranav-dp","@type":"Person","name":"pranav-dp"},"datePublished":"2026-06-13T16:28:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2/context-dev-cli/issues/2"}