On Sat, Mar 4, 2017 at 10:12 AM, Chet Ramey wrote:
> On 3/4/17 1:04 AM, Misaki wrote:
> > Variables are not saved when using a pipe because both sides are in a
> > subshell environment.
>
> If you want this to happen, enable the `lastpipe' shell option.
>
Thank yo
On Sun, Mar 5, 2017 at 9:39 AM, L A Walsh wrote:
> Chet Ramey wrote:
>
>> On 3/4/17 12:53 AM, Misaki wrote
>>
>>> Full-width character, followed by at least one full word with a space
>>> after it.
>>>
>>> Example: あa a
>>> With tra
On Sat, Mar 4, 2017 at 11:54 AM, Chet Ramey wrote:
> On 3/4/17 12:53 AM, Misaki wrote:
>
> > 15 Mar 2015
> > bash bug
> > Full-width character, followed by at least one full word with a space
> after it.
> >
> > Example: あa a
> >
> > With t
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
Variables are not saved when using a pipe because both sides are in a
subshell environment.
A common place where a user may encounter this is when dealing with
multiple items:
bash bug??
>
> Does not change the value of $new:
>
> echo hi| for i in 3; do new=3; done
>
>
> reason for piping:
> echo
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
