public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: bash-4.0 regression heads up (escaped semicolons in subshells)
Date: Sun, 22 Feb 2009 02:38:33 +0200	[thread overview]
Message-ID: <1235263113.23876.19.camel@localhost> (raw)
In-Reply-To: <200902211929.29115.vapier@gentoo.org>

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

On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote:
> On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote:
> > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote:
> > > On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> > > > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote:
> > > > > looks like bash-4.0 has broken semicolon escaping in subshells.  this
> > > > > comes up when using find's -exec like we do in a few places in
> > > > > eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;);
> > > > > shift you can work around the issue in a couple of ways:
> > > > >  - quote the semicolon:
> > > > > 	.... ';')
> > > > >  - use backticks
> > > > > 	`find .... \;`
> > > > >
> > > > > i'll tweak the eclasses to use quoting for now
> > > >
> > > > is this a bug or broken on purpose?
> > >
> > > i say it's a bug, but i'm not the bash maintainer
> > >
> > > i imagine it's fall out from attempts to fix support for case statements
> > > in subshells
> >
> > Then the bug should be fixed, instead of changing usage to something
> > apparently less common, as the conversion could miss some.  And more
> > importantly users still want to use \; for find -exec ending on their
> > command line and their very own scripts.
> > And who knows how many shell scripts shipped by packages use the
> > escaping method.
> 
> i think you missed the entire point of this thread: there's a bug in bash-4.0 
> that code is likely to hit.

I think you missed the entire point of my reply.
That bug should be fixed, not workarounds applied all over the tree, as
users still want to be able to escape semi-colons.


-- 
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-22  0:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 23:27 [gentoo-dev] bash-4.0 regression heads up (escaped semicolons in subshells) Mike Frysinger
2009-02-21 23:38 ` [gentoo-dev] " Ryan Hill
2009-02-21 23:55   ` Mike Frysinger
2009-02-22  0:00     ` Mart Raudsepp
2009-02-22  0:29       ` Mike Frysinger
2009-02-22  0:38         ` Mart Raudsepp [this message]
2009-02-22  0:44           ` Mike Frysinger
2009-02-22  0:54             ` Mart Raudsepp
2009-02-22  1:28               ` Mike Frysinger
2009-02-22  7:40                 ` Nirbheek Chauhan
2009-02-24 15:52             ` Daniel Gryniewicz
2009-02-24 15:56               ` Mike Frysinger
2009-02-22  1:02     ` Ryan Hill
2009-02-22 22:30 ` [gentoo-dev] " Dawid Węgliński
2009-02-22 22:39   ` Mike Frysinger
2009-02-22 23:03     ` Dawid Węgliński
2009-02-23  0:00       ` Mike Frysinger
2009-02-24  4:16       ` Mike Frysinger

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=1235263113.23876.19.camel@localhost \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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