From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: bash: igncr shell option breaks my PS1 prompt
Date: Tue, 30 Aug 2016 13:16:00 -0000 [thread overview]
Message-ID: <9940d9b9cd565fbb0d5b395565197dfd@xs4all.nl> (raw)
In-Reply-To: <8980687a-967e-88d8-2a94-f485731fafe9@redhat.com>
On 2016-08-29 19:43, Eric Blake wrote:
> On 08/28/2016 03:20 PM, Gene Pavlovsky wrote:
>> Re-posting a reply I got from Henri (aka Houder) houder@xs4all.nl
>> His letter follows:
>>
>> Hi Gene,
>>
>> Reread your entry to the mailing list ...
>>
>>> Apparently the latest bash in Cygwin modified the read builtin to use
>>> Cygwin-specific shell option igncr to control ignoring \r characters
>>> in the input (still not clear if that ignores \r\n sequences, or \r
>>> followed by anything else will be also ignored).
>>
>
> If the igncr shell option (currently Cygwin-specific, but Chet says
> that
> he is amenable to reviewing it for upstream inclusion in 4.5 once 4.4
> is
> released any day now) is enabled, then it eats ALL \r, regardless of
> context. In other words, it ignores all carriage returns, as per the
> name.
... uhm ... what about the explanation in the help?
64-@@ bash --version
GNU bash, version 4.3.46(6)-release (x86_64-unknown-cygwin)
...
64-@@ help set
set: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
Set or unset values of shell options and positional parameters.
Change the value of shell attributes and positional parameters, or
display the names and values of shell variables.
Options:
...
-o option-name
Set the variable corresponding to option-name:
...
igncr on cygwin, ignore \r in line endings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
... this help message should be 'upgraded', should it not?
igncr: removes ALL \r's from value (Cygwin) ?
Henri
--
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:[~2016-08-30 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 16:20 Gene Pavlovsky
2016-08-27 18:31 ` Andrey Repin
2016-08-29 5:18 ` Gene Pavlovsky
2016-08-30 2:21 ` Eric Blake
2016-08-30 7:49 ` Andrey Repin
2016-08-30 16:57 ` Nellis, Kenneth
2016-08-30 17:38 ` Houder
2016-08-30 13:16 ` Houder [this message]
2016-08-30 17:04 ` Eric Blake
2016-08-30 20:50 ` Houder
2016-09-02 11:52 ` Gene Pavlovsky
2016-09-02 13:32 ` Eric Blake
2016-09-04 9:11 ` Gene Pavlovsky
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=9940d9b9cd565fbb0d5b395565197dfd@xs4all.nl \
--to=houder@xs4all.nl \
--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).