William Hopkins writes:
> On 09/03/13 at 03:45pm, Joe Pfeiffer wrote:
>> Stephen Powell writes:
>> >
>> > Interesting. If "break" appears out of context, you should get
>> > an error message something like:
>> >
>> >bash: break: only meaningful in a 'for', 'while', or 'until' loop
>> >
>> >
On Mon, 02 Sep 2013 12:26:17 -0400 (EDT), Stephen Powell wrote:
>
> Interesting. If "break" appears out of context, you should get
> an error message something like:
>
>bash: break: only meaningful in a 'for', 'while', or 'until' loop
>
> You didn't get an error message, so part of bash thi
On Tue, 2013-09-03 at 20:01 -0400, William Hopkins wrote:
> On 09/03/13 at 03:45pm, Joe Pfeiffer wrote:
> > Stephen Powell writes:
> > >
> > > Interesting. If "break" appears out of context, you should get
> > > an error message something like:
> > >
> > >bash: break: only meaningful in a 'f
On 09/03/13 at 03:45pm, Joe Pfeiffer wrote:
> Stephen Powell writes:
> >
> > Interesting. If "break" appears out of context, you should get
> > an error message something like:
> >
> >bash: break: only meaningful in a 'for', 'while', or 'until' loop
> >
> > You didn't get an error message, so
On 09/02/13 at 08:29am, David Guntner wrote:
> Darac Marjal grabbed a keyboard and wrote:
> > On Mon, Sep 02, 2013 at 08:06:17AM -0700, David Guntner wrote:
> >> Matej Kosik grabbed a keyboard and wrote:
> >>
> >> What do you mean by "appears in a subshell?"
> >
> > From "man 1 bash":
> > (list) l
Stephen Powell writes:
>
> Interesting. If "break" appears out of context, you should get
> an error message something like:
>
>bash: break: only meaningful in a 'for', 'while', or 'until' loop
>
> You didn't get an error message, so part of bash thinks it is in context.
> Yet it did not exit
David Guntner writes:
> Darac Marjal grabbed a keyboard and wrote:
>> On Mon, Sep 02, 2013 at 08:06:17AM -0700, David Guntner wrote:
>>> Matej Kosik grabbed a keyboard and wrote:
Hello,
This morning I have been puzzled by bash.
After typing the following command:
On Mon, 02 Sep 2013 05:27:55 -0400 (EDT), Matej Kosik wrote:
>
> This morning I have been puzzled by bash.
> After typing the following command:
>
> for i in `seq 1 5`;do echo $i; test $i = 3 && break; done
>
> I see:
>
> 1
> 2
> 3
>
> Which is OK.
>
> However, if the
Darac Marjal grabbed a keyboard and wrote:
> On Mon, Sep 02, 2013 at 08:06:17AM -0700, David Guntner wrote:
>> Matej Kosik grabbed a keyboard and wrote:
>>> Hello,
>>>
>>> This morning I have been puzzled by bash.
>>> After typing the following command:
>>>
>>> for i in `seq 1 5`;do echo $i; te
On Mon, Sep 02, 2013 at 08:06:17AM -0700, David Guntner wrote:
> Matej Kosik grabbed a keyboard and wrote:
> > Hello,
> >
> > This morning I have been puzzled by bash.
> > After typing the following command:
> >
> > for i in `seq 1 5`;do echo $i; test $i = 3 && break; done
> >
> > I see:
> >
Matej Kosik grabbed a keyboard and wrote:
> Hello,
>
> This morning I have been puzzled by bash.
> After typing the following command:
>
> for i in `seq 1 5`;do echo $i; test $i = 3 && break; done
>
> I see:
>
> 1
> 2
> 3
>
> Which is OK.
>
> However, if the "break" co
Hello,
This morning I have been puzzled by bash.
After typing the following command:
for i in `seq 1 5`;do echo $i; test $i = 3 && break; done
I see:
1
2
3
Which is OK.
However, if the "break" command appears in a subshell:
for i in `seq 1 5`;do echo $
12 matches
Mail list logo
