X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=AWL,BAYES_00,MISSING_HEADERS,RCVD_IN_JMF_BR,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Date: Tue, 24 Feb 2009 13:09:02 -0600 (CST)
From: Tim McDaniel <tmcd AT panix DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: gcc compile problem: error: stray \168 in program
In-Reply-To: <loom.20090224T174854-882@post.gmane.org>
Message-ID: <Pine.NEB.4.64.0902241305040.27486@panix2.panix.com>
References: <22145156 DOT post AT talk DOT nabble DOT com> <22156979 DOT post AT talk DOT nabble DOT com>  <49A29E64 DOT 4060300 AT gmail DOT com> <Pine DOT NEB DOT 4 DOT 64 DOT 0902230943420 DOT 25957 AT panix1 DOT panix DOT com>  <22186369 DOT post AT talk DOT nabble DOT com> <loom DOT 20090224T174854-882 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, 24 Feb 2009, Eric Blake <ebb9 AT byu DOT net> wrote:
> grip <Chandramohan.USecure <at> gmail.com> writes:
>
>> 1. From the command prompt from windows, I tried this
>>     - od -tx1 <ENTER>
>>     - "<ENTER> (Note: I have to type double quotes twice always
>>                       and I get two double quotes. I use backspace
>>                       to remove one every time. A single double
>>                       quotes produces no output on the screen)
>
> That seems fishy.  You are probably better off getting to the root
> of why " isn't working the first time around.  Perhaps a faulty
> .inputrc setting is at play?  Or maybe a strange stty setting?

Escape character in your terminal program, even?  Though that seems
unlikely to me: the terminal programs I've used of late look for ~ as
the first character on a line only, and the double quotes are not at
the start of a line.

-- 
Tim McDaniel, tmcd AT panix DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/