Preston Thorpe

The referenced thread in the issue >https://lists.gnu.org/archive/html/bug-coreutils/2023-07/msg00030.html If I can get a thumbs up, I'll change it to: ` mv: cannot overwrite 'e/dir': Directory not empty ` (the agreed upon...

I know it looks like unnecessary code duplication, but I could not get the show! macro to work without repeating ```Rust match multi_progress { Some(ref pb) => pb.suspend(|| show!(e)), None...

Sorry for the noise, would you like me to rebase that into one commit?

@tertsdiepraam with the work-around, did you still want a note about moving to `io::Error::DirectoryNotEmpty` when it becomes avail in stable Rust?

Should be all set. Nushell PR is ready, when this is merged. (based it off my main branch, so these changes are included)

Ok I re-read the GNU list. ``` All things considered, how about if we go back to something like coreutils 5.93, except output strerror (errno) too? That is, something like...

Ok, but not only in the circumstances where it's being overwritten? It sounded like what they were referring to was removing the source file from the error message, in all...

@tertsdiepraam Verifying an example of what you would like changed. ``` mv: cannot move '../test1/file' to 'test1/file': not replacing 'test1/file' ``` It refers to the destination. Sorry I haven't had...

> > What if instead of having the parser build the js file, we instead have it only check the syntax, and if the syntax is correct it calls some...

We can easily spin up an electron app that we can squeeze right into the compiler to do these lookups in O(∞) no problem at all.