Hi Vince,
On Thu, May 14, 2015 at 7:14 PM, Vince Rice wrote:
> Oh my, the rabbit-hole gets deeper. I don't know the difference between wide
> character and multi-byte. (snip)
Maybe this will help:
http://www.joelonsoftware.com/articles/Unicode.html
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++
We have a new desktop PC with Windows 7 Professional installed. Corporate IT
had to set it up with a domain to allow access to the corporate intranet. We
have installed cygwin 64-bit:
$ uname -a
CYGWIN_NT-6.1 2.0.2(0.287/5/3) 2015-05-08 17:00 x86_64 Cygwin
On initial access, there was no pas
On 5/14/2015 22:47, Mark Rivers wrote:
> Additional information:
>
> - This is Cygwin 2.0.1, 32-bit on a Windows 7 64-bit machine.
>
> The "file" utility claims it is an archive file:
> $ file ../../lib/cygwin-x86/PlxApi.lib
> ../../lib/cygwin-x86/PlxApi.lib: current ar archive
Try using gendef
On 05/14/2015 02:18 PM, Mikhail Usenko wrote:
> Also when a bash script is launched from an external program
> with connected stdio from/to the program using a UNIX domain
> socket generated by socketpair() the read builtin works OK.
Thanks for the additional information. I can indeed duplicate th
Also when a bash script is launched from an external program
with connected stdio from/to the program using a UNIX domain
socket generated by socketpair() the read builtin works OK.
--
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Docume
On Thu, 14 May 2015 13:53:38 -0600
Eric Blake <...> wrote:
>
> Umm, are you sure you haven't turned on the igncr shell option in your
> cygwin environment?
>
$ set -o
allexport off
braceexpand on
emacs on
errexit off
errtraceoff
functrace off
hashall
On 05/14/2015 01:32 PM, Mikhail Usenko wrote:
>
> Cygwin version: 2.0.2-1
>
> [linux]$ bash --version
> GNU bash, version 4.3.33(1)-release (i686-redhat-linux-gnu)
> [cygwin]$ bash --version
> GNU bash, version 4.3.33(1)-release (x86_64-unknown-cygwin)
>
> Testcase:
> [linux]$ echo -ne "\r\n
On 05/14/2015 11:14 AM, Vince Rice wrote:
Your mails are hard to read:
https://cygwin.com/acronyms/#PCYMTWLL
>>
>> None. UTF16 is not a valid locale. It is a valid encoding (wide
>> character), but locales must operate on multi-byte sequences, not wide
>> characters. So you HAVE to convert fro
Cygwin version: 2.0.2-1
[linux]$ bash --version
GNU bash, version 4.3.33(1)-release (i686-redhat-linux-gnu)
[cygwin]$ bash --version
GNU bash, version 4.3.33(1)-release (x86_64-unknown-cygwin)
Testcase:
[linux]$ echo -ne "\r\n" | { read t; echo "$t"; } | od -A n -t x1
0d 0a
[cygwin]$ echo
> On May 14, 2015, at 11:43 AM, Eric Blake wrote:
>
> On 05/14/2015 10:32 AM, Vince Rice wrote:
>
> …
>>
>> Now, pardon my continued ignorance, but which of those variables needs to be
>> set to UTF16 in order for grep to work? And I assume it (they?) should be
>> set to en_US.UTF-16?
>
> No
On 05/14/2015 10:32 AM, Vince Rice wrote:
> locale run from a cmd.exe session says that everything is “C.UTF-8”, while
> locale run from mintty says that everything is en_US.UTF-8. A “which” in both
> cases shows that the locale being run is cygwin’s, so I assume mintty does
> something slightl
On May 14, 2015, at 10:56 AM, Andrey Repin wrote:
>
> Greetings, Vince Rice!
>
>> uname says "CYGWIN_NT-6.1 machinename 1.7.35(0.287/5/3) 2015-03-04 12:07
>> i686 Cygwin”.
>> I’m running grep 2.21.2, which cygcheck -c says is OK.
>
>> Does Cygwin’s grep support Unicode files? The output from a
> Does Cygwin’s grep support Unicode files? The output from a SQL Server SQL
> Agent job is a Unicode file, i.e. if you look at it in a hex editor every
> other character is 00 because each character is taking up two bytes. The
> filename itself is fine, it’s the contents that is Unicode. I can’t g
On 14.5.2015 17:42, Vince Rice wrote:
> uname says "CYGWIN_NT-6.1 machinename 1.7.35(0.287/5/3) 2015-03-04
> 12:07 i686 Cygwin”. I’m running grep 2.21.2, which cygcheck -c says
> is OK.
>
> Does Cygwin’s grep support Unicode files? The output from a SQL
> Server SQL Agent job is a Unicode file, i.
uname says "CYGWIN_NT-6.1 machinename 1.7.35(0.287/5/3) 2015-03-04 12:07 i686
Cygwin”.
I’m running grep 2.21.2, which cygcheck -c says is OK.
Does Cygwin’s grep support Unicode files? The output from a SQL Server SQL
Agent job is a Unicode file, i.e. if you look at it in a hex editor every other
Additional information:
- This is Cygwin 2.0.1, 32-bit on a Windows 7 64-bit machine.
The "file" utility claims it is an archive file:
$ file ../../lib/cygwin-x86/PlxApi.lib
../../lib/cygwin-x86/PlxApi.lib: current ar archive
The "nm" utility appears to interpret the file OK:
rivers@rivers-mobi
Achim Gratz writes:
> I'm having problems with some bash scripts that were developed (not be
> me) and working OK in Cygwin 1.6.x versions, but not in 1.7.x (tested on
> 1.7.6, 1.7.7 and the latest snapshot). After some gnashing of teeth and
> pulling of hair I've whittled it down to a problem wit
Stephen John Smoogen writes:
> I have replicated this using Cygwin ssh to a Linux server. However I
> also replicated it using Linux -> Linux
That I already knew, and it's indeed fixed by making tcsh your default
shell over on Cygwin. I can't do that in the case I mentioned since I
still haven't
Keith Christian writes:
> Still seeing the following errors on stderr while running various
> commands and scripts.
>
> Usually these errors do not seem to impact anything, but occasionally
> they do, such as when data fails to be written to files created during
> script runs.
>
>
> 0 [main]
19 matches
Mail list logo
