On 2018-03-27 03:56, Andrey Repin wrote:
>>> Locale settings affecting Cygwin binary.
>>> If you
>>> set LANG=ru_RU.CP866
>>> (f.e.)
>>> before invoking cygwin testcase in native CMD, you will likely see it
>>> working better.
>> Thanks for this advise, Andrey. I see that it reacts, but works worth
Greetings, Dmitry Katsubo!
>> Locale settings affecting Cygwin binary.
>>
>> If you
>> set LANG=ru_RU.CP866
>> (f.e.)
>> before invoking cygwin testcase in native CMD, you will likely see it
>> working better.
> Thanks for this advise, Andrey. I see that it reacts, but works worth :)
> I think i
On 2018-03-22 15:21, Dmitry Katsubo via cygwin wrote:
On 2018-03-22 18:10, Kaz Kylheku wrote:
That may be so, yet there may be an issue here for someone packaging
Cygwin programs for use as native Windows applications.
That is to say, there could potentially be something here that the
Cygnal
On Fri, 23 Mar 2018 08:39:21, Thomas Wolff wrote:
Due to the weird cmd.exe behaviour, you cannot. However, cygwin could
apply a workaround by magic unquoting.
This is correct. note that "run" has this "workaround" already via the "--quote"
option. that code could perhaps be applied in other pla
Am 22.03.2018 um 12:24 schrieb Andrey Repin:
...
when I put quotes around file that has
non-ASCII symbols, these quotes are passed to argv of the process literally,
otherwise they are removed. I would expect that there is a consistency.
Parameter unquoting done by the shell.
CMD does that diffe
On 2018-03-22 18:10, Kaz Kylheku wrote:
> That may be so, yet there may be an issue here for someone packaging
> Cygwin programs for use as native Windows applications.
>
> That is to say, there could potentially be something here that the Cygnal
> project could address:
>
> http://www.kylheku.co
On 2018-03-22 14:25, Andrey Repin wrote:
> Greetings, Mikhail Usenko!
>
>> In bare cmd.exe native-msvcrt binary is working OK with quoted non-ascii
>> arguments, while cygwin-flavor binary is not. But I don't know exactly which
>> level here: cmd.exe or msvcrt.dll/cygwin1.dll is responsible for
>>
On 2018-03-22 12:24, Andrey Repin wrote:
>
> This is not cygwin, this is bare Windows.
This is executable linked against cygwin1.dll. I personally call such
binaries "Cygwin programs". However it is run from Windows.
> Parameter unquoting done by the shell.
> CMD does that differently from POSIX
On 2018-03-22 04:24, Andrey Repin wrote:
Greetings, Dmitry Katsubo!
Dear Cygwin community,
I observe the following on my Cygwin:
This is not cygwin, this is bare Windows.
That may be so, yet there may be an issue here for someone packaging
Cygwin programs for use as native Windows applic
Greetings, Mikhail Usenko!
> In bare cmd.exe native-msvcrt binary is working OK with quoted non-ascii
> arguments, while cygwin-flavor binary is not. But I don't know exactly which
> level here: cmd.exe or msvcrt.dll/cygwin1.dll is responsible for
> such a behavior.
Locale settings affecting Cygw
ll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7fa0590)
KERNEL32.DLL => /cygdrive/c/Windows/system32/KERNEL32.DLL
(0x7fa030e0000)
KERNELBASE.dll => /cygdrive/c/Windows/system32/KERNELBASE.dll
(0x7fa028f)
cygwin1.dll => /usr/bin/cygwin1.dll (0x18004)
---
Greetings, Dmitry Katsubo!
> Dear Cygwin community,
> I observe the following on my Cygwin:
This is not cygwin, this is bare Windows.
> when I put quotes around file that has
> non-ASCII symbols, these quotes are passed to argv of the process literally,
> otherwise they are removed. I would exp
Dear Cygwin community,
I observe the following on my Cygwin: when I put quotes around file that has
non-ASCII symbols, these quotes are passed to argv of the process literally,
otherwise they are removed. I would expect that there is a consistency.
I have written a small C program that displays a
13 matches
Mail list logo
