From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: gnanny: tr: warning: an unescaped backslash at end of string is not portable
Date: Mon, 31 Dec 2018 14:47:00 -0000 [thread overview]
Message-ID: <eeab5b48-e8a0-6d6c-303e-835edd36ac5b@cs.umass.edu> (raw)
In-Reply-To: <5C29F63E.9010606@tlinx.org>
On 12/31/2018 5:58 AM, L A Walsh wrote:
> This is being run on cygwin w/bash, version 4.4.12(3)-release.
>
>
> Have a table of windows files, sample line (it's all 1 line):
>> Â cat test
> D,"c:\windows\system32\FMS.DLL",2010-11-20 19:24:33,2010-11-20
> 03:59:27,93696,A,0x00024E23,0x00024E23,x86,GUI,"CV",0x04480000,Unknown,0x00019000,Not
> Loaded,1.1.6000.16384,1.1.6000.16384,6.1,9.0,6.1,6.1
>
> I run 'tr' to switch around the backslashes to slashes:
>
>> Â tr '\' '/' <test
> tr: warning: an unescaped backslash at end of string is not portable
> D,"c:/windows/system32/FMS.DLL",2010-11-20 19:24:33,2010-11-20
> 03:59:27,93696,A,0x00024E23,0x00024E23,x86,GUI,"CV",0x04480000,Unknown,0x00019000,Not
> Loaded,1.1.6000.16384,1.1.6000.16384,6.1,9.0,6.1,6.1
>
>
> 1) First question: what unescaped backslash? The '\n is escaped via the surrounding quotes.
>
> 2) how should one escape it?
>
> Is this a bug?
It is referring to your input '\' and would prefer '\\'.
Best - Eliot Moss
--
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
next prev parent reply other threads:[~2018-12-31 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 12:32 L A Walsh
2018-12-31 14:47 ` Eliot Moss [this message]
2018-12-31 15:01 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eeab5b48-e8a0-6d6c-303e-835edd36ac5b@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).