From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: bash: igncr shell option breaks my PS1 prompt
Date: Tue, 30 Aug 2016 20:50:00 -0000 [thread overview]
Message-ID: <c153e423b803ace79e1e8ec999883488@xs4all.nl> (raw)
In-Reply-To: <0294c48e-8e96-f554-3e05-6b7771dfb96e@redhat.com>
On 2016-08-30 15:40, Eric Blake wrote:
> On 08/30/2016 02:49 AM, Houder wrote:
>> ... uhm ... what about the explanation in the help?
>>
>> -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?
>
> Sure, I'll tweak that text, once I can find what about igncr is making
> PS1 misbehave on \n. But help would be welcome, if anyone else is also
> interested in looking into the cygwin-specific patches and actually
> reviewing them.
Not only \n ... also on \r:
64-@@ bash --version
GNU bash, version 4.3.46(6)-release (x86_64-unknown-cygwin)
...
64-@@ set -o igncr
64-@@ echo $SHELLOPTS
braceexpand:emacs:hashall:histexpand:history:igncr:ignoreeof:interactive-comments:monitor
64-@@ PS1='$(date)\n# '
bash: command substitution: line 1: syntax error near unexpected token
`)'
bash: command substitution: line 1: `date)'
# PS1='$(date)\r# '
bash: command substitution: line 1: syntax error near unexpected token
`)'
bash: command substitution: line 1: `date)'
HOWEVER:
# PS1='$(date)\012# '
Tue Aug 30 19:36:15 CEST 2016
# PS1='$(date)\012\n# ' # <==== \n!
Tue Aug 30 19:36:21 CEST 2016
# PS1='$(date)\012\r# ' # <==== \r!
Tue Aug 30 19:36:26 CEST 2016
#
Perhaps this may help ... in finding the error.
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 17:47 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
2016-08-30 17:04 ` Eric Blake
2016-08-30 20:50 ` Houder [this message]
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=c153e423b803ace79e1e8ec999883488@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).