"error: 'udpate' is not a flatpak command." - youuu know what i friggin' meant, command line
@jplebreton What if when git got the subcommand "git git checkout" it just did what you wanted. Would that be a better or a worse universe.
@mcc yeah, i think grammar / syntax mistakes probably shouldn't be treated the same as typos, especially transposed letters. if i were building a CLI app today where it made sense to catch that sort of thing, i'd probably try a confirmation: "you typed 'udpate', but that's not a recognized command and is very similar to 'update', shall i run 'update'? Y/N"
@jplebreton Yeah, part of why the "Hint:" approach is good is that people inevitably wind up scripting command line tools, and unfortunately the UX you want as a human typing commands (where you'd prefer it to be kind of "soft" and work with you interactively to figure out what you want) can be actively deleterious when scripting.
@mcc @jplebreton it would be great if there was a convention that e.g. a cli program that had a suggested fix could set like an environment variable with the suggestion, and then you could just do a quick command to say "yes, that" (in the same way !! in some shells is a quick way to repeat the last command)
(of course the impossibly broken problem of spaces, quotes and escaping in shell commands and envvars probably precludes this idea from actually _working_)
@vfig @mcc @jplebreton There is, at least, this installable shell script: https://github.com/nvbn/thefuck that allows you to have the terminal try to intuit what you meant by typing `fuck` - it's reasonably accurate too and defaults to asking you first before trying to execute anything
