Le 03/11/2022 à 19:50, Chet Ramey écrivait :
The option is enabled by default. If you want to restore the previous
behavior, add `shopt -u patsub_replacement'.
Having it enabled by default is not good, because it introduces
side-effects for existing scripts.
Shell has historically perpetuate
On Fri, Nov 4, 2022, 08:56 Léa Gris wrote:
> Le 03/11/2022 à 19:50, Chet Ramey écrivait :
> > The option is enabled by default. If you want to restore the previous
> > behavior, add `shopt -u patsub_replacement'.
>
> Having it enabled by default is not good, because it introduces
> side-effects f
On Fri, Nov 04, 2022 at 09:50:03AM +0100, Alex fxmbsw7 Ratchev wrote:
> On Fri, Nov 4, 2022, 08:56 Léa Gris wrote:
>
> > Le 03/11/2022 à 19:50, Chet Ramey écrivait :
> > > The option is enabled by default. If you want to restore the previous
> > > behavior, add `shopt -u patsub_replacement'.
> >
On Fri, Nov 4, 2022, 12:33 Greg Wooledge wrote:
> On Fri, Nov 04, 2022 at 09:50:03AM +0100, Alex fxmbsw7 Ratchev wrote:
> > On Fri, Nov 4, 2022, 08:56 Léa Gris wrote:
> >
> > > Le 03/11/2022 à 19:50, Chet Ramey écrivait :
> > > > The option is enabled by default. If you want to restore the previ
On 11/4/22 3:56 AM, Léa Gris wrote:
Le 03/11/2022 à 19:50, Chet Ramey écrivait :
The option is enabled by default. If you want to restore the previous
behavior, add `shopt -u patsub_replacement'.
Having it enabled by default is not good, because it introduces
side-effects for existing scripts
I now very much regret not commenting on this proposal during the
pre-release period, and I apologise for not having done so.
On Fri, 4 Nov 2022, 05:50 Chet Ramey, wrote:
>
> The option is enabled by default. If you want to restore the previous
> behavior, add `shopt -u patsub_replacement'.
>
I
2022年11月4日(金) 23:26 Martin D Kealey :
> I now very much regret not commenting on this proposal during the
> pre-release period, and I apologise for not having done so.
I actually raised the concern in [1], but Chet's reply [2] at the time was
> I generally make new functionality that's controlled
that u word
comply to very outdated specs
i did word
bye
On Fri, Nov 4, 2022, 15:26 Martin D Kealey wrote:
> I now very much regret not commenting on this proposal during the
> pre-release period, and I apologise for not having done so.
>
> On Fri, 4 Nov 2022, 05:50 Chet Ramey, wrote:
>
> >
>
On Fri, Nov 04, 2022 at 01:30:16PM +0100, Alex fxmbsw7 Ratchev wrote:
> > 1) Put something like "shopt -u patsub_replacement 2>/dev/null || true"
> >at the top of your script.
> >
>
> there d be many such senselessnesses
>
> >
> > 2) Assign the result of the expansion to a temporary variable,
On Fri, Nov 4, 2022, 17:03 Greg Wooledge wrote:
> On Fri, Nov 04, 2022 at 01:30:16PM +0100, Alex fxmbsw7 Ratchev wrote:
> > > 1) Put something like "shopt -u patsub_replacement 2>/dev/null || true"
> > >at the top of your script.
> > >
> >
> > there d be many such senselessnesses
> >
> > >
>
On 11/4/22 12:22 PM, Alex fxmbsw7 Ratchev wrote:
what on yours i ask , o i see now , 4.2 ..
i quote right in ${ // - to me , preserved quotes are • an invalid youth
bug to be replaced with better by bash.c changes
which it seemfully did
The question is, as always, tradeoffs. Do you fix bugs or
addition to my greycat-answer mail
.. i didnt use & there at all , my fault .. but with & its no else
root@localhost:~# a=i_am_foo b=_ c=${b}am$b d=$b\&$b e=${a//"$c"/"$d"} ;
printf ' --> %s\n' "$e" "${a//"$c"/"$d"}"
--> i_&_foo
--> i_&_foo
sorry
short imo , the ' " not parsing is outdated
On Fri, Nov 4, 2022, 19:42 Chet Ramey wrote:
> On 11/4/22 12:22 PM, Alex fxmbsw7 Ratchev wrote:
>
> > what on yours i ask , o i see now , 4.2 ..
> > i quote right in ${ // - to me , preserved quotes are • an invalid youth
> > bug to be replaced with better by bash.c changes
> > which it seemfully
13 matches
Mail list logo
