On Fri, Jan 26, 2018 at 11:31:40AM +0100, Klemens Nanni wrote:
> On Fri, Jan 26, 2018 at 09:41:45AM +0100, Klemens Nanni wrote:
> > On Wed, Jan 24, 2018 at 04:15:24PM +0100, m...@josuah.net wrote:
> > > I found a bug in ksh's parameter expansion on an edge case:
> > >
> > > true $(true "${USER#'
On Fri, Jan 26, 2018 at 09:41:45AM +0100, Klemens Nanni wrote:
> On Wed, Jan 24, 2018 at 04:15:24PM +0100, m...@josuah.net wrote:
> > I found a bug in ksh's parameter expansion on an edge case:
> >
> > true $(true "${USER#'"'}")
> >
> > /home/sh[4]: no closing quote
> >
> > The problem s
On Wed, Jan 24, 2018 at 04:15:24PM +0100, m...@josuah.net wrote:
> I found a bug in ksh's parameter expansion on an edge case:
>
> true $(true "${USER#'"'}")
>
> /home/sh[4]: no closing quote
>
> The problem seems to occurs when all of these conditions are present:
>
> 1. On ${var#p
On Wed, Jan 24, 2018 at 04:15:24PM +0100, m...@josuah.net wrote:
> I found a bug in ksh's parameter expansion on an edge case:
>
> true $(true "${USER#'"'}")
>
> /home/sh[4]: no closing quote
>
> The problem seems to occurs when all of these conditions are present:
>
> 1. On ${var#p
I found a bug in ksh's parameter expansion on an edge case:
true $(true "${USER#'"'}")
/home/sh[4]: no closing quote
The problem seems to occurs when all of these conditions are present:
1. On ${var#pattern} or ${var%pattern} parameter expansion
2. When the pattern contains a si
