Greetings, Corinna Vinschen!
> On Nov 28 19:08, Andrey Repin wrote:
>> > If we implement the above, we
>> > would just have to add a cmd wrapper script in /bin to make sure
>> > $PATH is set correctly and to make sure CMD starts up in $HOME,
>> > something along the lines of:
>>
>> > $ cat /bin/cmd
>> > #!/bin/dash
>> > PATH=/bin:$PATH
>> > cd $HOME
>> > # Don't rely on COMSPEC!
>> > cmd=$(cygpath -ua "${SYSTEMROOT}\\System32\\CMD.EXE")
>> > exec "${cmd}"
>>
>> I hope you don't expect it to work inside mintty.
> Oh, it does. CMD itself isn't the biggest problem, many other native
> tools are.
Yes, CMD itself do output... something. As long as encoding isn't an issue.
But I have PROMPT=%USERNAME%%COMPUTERNAME%. Imagine if one of them turned out
to contain non-ASCII characters.
>> Cygwin tools may function
>> properly in this case, but the shell itself - I have my doubts. And other
>> native tools would certainly have issues with encoding, if not with any
>> output
>> at all.
>> Said that, it would need to be a simple .cmd file, so that it'd run in native
>> console.
>> Something like
>>
>> @ECHO OFF
>> PATH=%~dp0;%PATH%
>> START "" /B "%SystemRoot%\System32\cmd.exe" /K
>> EXIT
> Fine with me, but it also has to cd to %HOME%, which is given in
> POSIX syntax...
That may be an issue, unless %HOME% is set somewhere else.
If you have ideas, where to look, I may be able to provide the code to do it.
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 29.11.2014, <01:17>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
