-
Ok, thought I'd share with you this bizarre bug I encountered. Whenever there is a file, or a folder, that has the name "1", running Neper -V would give this error: I have zero idea about why this is happening, so I thought I'd just share it here with you, in case later you (very unlikely) also run into this. Note that to reproduce this bug, the "1" file has to be either a folder with the name "1", or a file with the name "1" (no extension). I'm running Neper 4.2.1 on OSX 10.15.7 Catalina. Cheers, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Neper is probably interpreting the expression as a number (because it can) instead of a file name. This is an expected behavior at least for some options. What is your command? |
Beta Was this translation helpful? Give feedback.
Neper is probably interpreting the expression as a number (because it can) instead of a file name. This is an expected behavior at least for some options. What is your command?