On 2020-12-29 19:22, Andry via Cygwin wrote:
Cannot repro... Logfile is created correctly and commands and their
output are logged there. The file encoding for the logfile is utf-8.
The issue found in the Windows 7 x64.
A couple of things though: 1. changing \ to / does not guarantee a
valid Cygwin path.
Not sure what you talking about. Always worked.
2. the cd does nothing because bash -l starts the shell in the home
directory.
I've tested it and it does.
3. Once you've started bash, you don't have to supply the full path so
"/bin/bash.exe" and "/bin/tee.exe" are fine (assuming your path and mounts
are set correctly)
You have to, because not logged shell does not have PATH registration to the
`/bin`.
Are any files on a remote share?
You cannot run cmd.exe on a remote share.
Are any of the paths relative?Do any of the paths have spaces in them?
Does it matter?
Seems to have been reported a few times with Windows Russian and fix suggested
was "chcp 1252" (which might not be too useful for many Russians), as there may
be encoding conversion bugs with UTF-8.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
