public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Odd behavior of scripts in dos mode
Date: Thu, 26 Apr 2012 14:41:00 -0000	[thread overview]
Message-ID: <4F995E78.7020607@redhat.com> (raw)
In-Reply-To: <jnbl6p$qav$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]

On 04/26/2012 08:13 AM, Andrew DeFaria wrote:
> I remember that Cygwin used to not be able to run scripts that were
> converted or were in "DOS" mode - had trailing carriage returns in the
> file. It would fail because the #! line might have /bin/bash\r which was
> not a file (bash with a carriage return that is). But the behavior has
> changed. Now it seems to ignore the trailing carriage return and it
> execs bash itself. But it fails later on with other carriage returns.

If you want bash to ignore carriage returns, then ask it to do so:
http://sourceware.org/ml/cygwin-announce/2011-02/msg00027.html

> 4. This version of bash has a cygwin-specific set option, named "igncr",
> to force bash to ignore \r, independently of cygwin's mount style.  As
> of bash-3.2.3-5, it controls regular scripts, command substitution, and
> sourced files.  I hope to convince the upstream bash maintainer to
> accept this patch into a future bash release even on Linux, rather than
> keeping it a cygwin-specific patch, but only time will tell.  There are
> several ways to activate this option:
> 4a. For a single affected script, add this line just after the she-bang:
>  (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
> 4b. For a single script, invoke bash explicitly with the option, as in
> 'bash -o igncr ./myscript' rather than the simpler './myscript'.
> 4c. To affect all scripts, export the environment variable BASH_ENV,
> pointing to a file that sets the shell option as desired.  Bash will
> source this file on startup for every script.
> 4d. Added in the bash-3.2-2 release: export the environment variable
> SHELLOPTS with igncr included in it.  It is read-only from within bash,
> but you can set it before invoking bash; once in bash, it auto-tracks
> the current state of 'set -o igncr'.  If exported, then all bash child
> processes inherit the same option settings; with the exception added in
> 3.2.9-11 that certain interactive options are not inherited in
> non-interactive use.
> 4e. bash-4.1.9-1 dropped support for 'shopt -s igncr'; it did not make
> sense to support the option through both set and shopt, and SHELLOPTS
> proved to be more powerful.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]

  parent reply	other threads:[~2012-04-26 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 14:14 Andrew DeFaria
2012-04-26 14:26 ` Earnie Boyd
2012-04-26 14:33   ` Andrew DeFaria
2012-04-26 16:07   ` Buchbinder, Barry (NIH/NIAID) [E]
2012-04-26 14:41 ` Eric Blake [this message]
2012-04-26 17:22   ` Andrew DeFaria

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=4F995E78.7020607@redhat.com \
    --to=eblake@redhat.com \
    --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).