Open ghost opened 3 years ago
Another weird one.
Looks like this in the msys2 shell:
barbara_user@LAPTOP-3HO6905G MINGW64 /build $ ldd ./ve01.exe | grep '\/mingw.*.dll' -o | xargs -I{} cp "{}" . ldd: .v/e01.exe: No such file or directory ldd: : No such file or directory
Yet looks like this when I copy and paste it directly from the msys2 shell to this post:
barbara_user@LAPTOP-3HO6905G MINGW64 /build $ ldd ./ve01.exe | grep '\/mingw.*.dll' -o | xargs -I{} cp "{}" . ldd: .v/e01.exe: No such file or directory ldd: : No such file or directory
Again.
Appears as this in the msys2 shell:
barbara_user@LAPTOP-3HO6905G MINGW64 /01 $ cp /mingw64/bin/libpng16-16.dll /01 bash: $'\302\203cp': command not found
When copied into here:
barbara_user@LAPTOP-3HO6905G MINGW64 /01 $ cp /mingw64/bin/libpng16-16.dll /01 bash: $'\302\203cp': command not found
Again, it's every 20 minutes or so and I stopped using notepad I'm using Gedit now, this has been happening for years.
barbara_user@LAPTOP-3HO6905G MINGW64 ~ $ pacman -S --download-only mingw-w64-x86_64-gcc-libs mingw-w64-x86_64-adwaita-icon-theme mingw-w64-x86_64-atk mingw-w64-x86_64-cairo mingw-w64-x86_64-gdk-pixbuf2 mingw-w64-x86_64-glib2 mingw-w64-x86_64-json-glib mingw-w64-x86_64-libepoxy mingw-w64-x86_64-pango mingw-w64-x86_64-shared-mime-info mingw-w64-x86_64-gtk3 pacman: unknown option -- download-only
Describe the issue
When using the shell (msys2, ming32, ming64) sometimes a command will not work and it will give a weird garbled or odd reason why. If you close and reopen the shell and retype the command (not using the bash history or copy and paste) it will work normally.
Steps to Reproduce the Problem
Additional Context: Operating System, Screenshots
Here are some examples.
barbara_user@LAPTOP-3HO6905G MINGW64 / $ pacman -S mingw-w64-x86_64-vala bash: $'\302\226pacman': command not found
Then I close and reopen the shell retype it and it works correctly.
barbara_user@LAPTOP-3HO6905G MINGW64 / $ pacman -S mingw-w64-x86_64-vala warning: mingw-w64-x86_64-vala-0.50.1-1 is up to date -- reinstalling resolving dependencies...
If I simply close and reopen and press up to use the previous command it shows this as the previous command.
barbara_user@LAPTOP-3HO6905G MINGW64 ~ $ pacman -Smingw-w64-x86_64-vala
I thought it may be because of a space before pacman but if you type it manually it makes no difference.
I'm using Windows 10 with current packages. I'm sometimes copying and pasting from the default notepad.
When copying and pasting examples to this post some had strange characters that weren't visible in notepad or an msys2 shell.
Example, when copied from an msys2 shell or notepad to this post it initially looks like this. (Actually a slightly different weird symbol while in the editing screen, a square box with 00 96 in it.)
$ pacman -S mingw-w64-x86_64-vala bash: $'\302\226pacman': command not found
That looks like the command below in both notepad and an msys2 shell.
$ pacman -S mingw-w64-x86_64-vala bash: $'\302\226pacman': command not found