Unknown option gives user unfriendly error about lyra HOT 5 OPEN

After some investigation... This is technically not a bug. The current behavior is that it interprets the --foo as the value for the ProjectDirectory argument after having it not match the know options. Subsequently it sees the /my/project/directory and can't match it to anything, as it's not a known option, and it already parsed the one argument. Hence fails the parse at that point. And complains about it.

I'll have to think about it more to see if there's a way to deal with this use case.

from lyra.

It might well be not a bug technically, but this behaviour is very surprising and unwelcome. In practice this happens when the user makes a typo in the option name, e.g. suppose your program synopsis is a.out [--overwrite] <file>.... Running it as ./a.out --overrite file really ought to give an error about an unknown option rather than creating an output file called --overrite!

(and, of course, if you really wanted to create a file called like this, you should be able to use ./a.out -- --overrite file)

from lyra.

@vadz indeed, it's annoying. Which is why I haven't closed this :-) Addressing this is not easy because it break backwards compat. But I'm thinking that okay in this case. Just will take more thinking to minimize the impact.

from lyra.

Would you be interested in a PR implementing this? I'd like to finally do something about it, because as much as I like Lyra's API, we can't tell our users never to make typos in their command lines (spoiler: it doesn't work).

from lyra.

@vadz if you can think of a way to do it I'd love to have a fix for it!

from lyra.