-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still having issues with filenames starting with "cache" #584
Comments
Thank you for reporting this. I can not reproduce this:
|
Strange; I just now installed Rust via rustup on a separate account on my machine, to check that it's not something in my environment, and |
Oh dear, I was fooled by this again. This is actually described in #557. Everything worked fine for me because I had a I realize now that it was a bad decision to use subcommands and positional arguments at the same time. If someone has ideas for a nice command-line interface that replaces Regarding this specific instance of the bug.. I will look into it. |
Hi, First of all, thanks for I'm just ran into this problem, however this is with a file named
About your question: maybe get rid of subcommands alltogether, and convert |
Thank you for the feedback!
Yes, we should get rid of the subcommand. The question is how we design the new command-line interface. There are multiple commands:
would all of these become |
Aha, good point. Maybe having a separate command altogether like you suggested ( |
If I might suggest The name would be future proof and also provide an avenue for moving some of the informational options like You could also do things such as |
Thinking a bit more about this.... there's also things I don't like (whether it's Also, having a separate Maybe there are any other solutions which would prevent a second binary? |
I think the general pattern is not unheard of; for instance the However, I'd suggest considering another name instead of
Just my 2 cents.
One traditional Unix approach comes to mind, which, strictly speaking, avoids a second binary, but I'm not sure whether it is portable to Windows: Have the |
@rotty: Thank you for the feedback. Just now, I found a way to fix this (particular instance of this) bug. There are now a few test cases that make sure that we can always print files named I guess we'll give this another try as long as another corner case comes up 😄 |
Fixed in bat v0.12. |
Using current master (4ee0b2e), there still seems to be an issue that looks like #557:
Giving
--
doesn't give a workaround:The text was updated successfully, but these errors were encountered: