This is the mail archive of the
mailing list for the Cygwin project.
Re: Quotes changed to odd characters in gcc error msgs
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Wed, 13 Jan 2016 12:52:19 -0700
- Subject: Re: Quotes changed to odd characters in gcc error msgs
- Authentication-results: sourceware.org; auth=none
- References: <7ddb3b6ed96c4cabe49cb1fb5559c32b at mail dot gmail dot com>
On Jan 13, 2016, at 8:05 AM, Chuck Roberts <email@example.com> wrote:
> My TERM variable says "cygwinâ.
That means youâre running under the built-in Windows console, not MinTTY, which means you donât get UTF-8 support by default.
You could try âchcp 65001â but the real fix is to use MinTTY. MinTTY has *many* features not available in the Windows Console. Even the vastly upgraded version included with Windows 10 is a pale wannabe compared to MinTTY. man mintty for details.
> 2) I'm using PSPad to edit some of my .C files.
Careful, there. Unix is traditionally case-sensitive, and some programs coming from that tradition treat .C files differently from .c files. One such tool is gcc, which will interpret your file as C++ even if you invoke it as gcc instead of g++.
GNU make also assumes .C is C++.
C++ is not 100% forwards compatible with C:
On Windows, NTFS is case-insensitive by default, but also case-preserving, so saving a file as *.C will invoke this automatic C++ treatment under Cygwin.
> the directory listing of files using 'ls -l' has the occasional
> file concatenated with the next file, like a carriage return is missing
This may be a Windows Console bug, too. Again, switch to MinTTY. Itâs the default for a reason.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple