Re: "return" should not continue script execution, even if used inappropriately

Date:Thu, 24 Jan 2019 21:12:01 -0800 From:don fong Message-ID: | that's not only an unwarranted personal attack, but it's untrue. It wasn't a personal attack - I could show you one of those (off list) if you like. As to the latter part, see below. | the "ans

Re: "return" should not continue script execution, even if used inappropriately

> > This is also simple. He's just not listening to the answers that's not only an unwarranted personal attack, but it's untrue. the "answers" have mostly been about "how to do this". however as i've stated multiple times: i'm not asking how to do it, i'm explaining why this technique which i

Re: "return" should not continue script execution, even if used inappropriately

Please, both of you, stop top posting, it is anti-social, rude, and just lazy. If you go back to the original question (Jan 6) it was about a script that did "return" which did not stop the script executing whenencountered when the script was run as a command rather than via ".". It was later exp

Re: "return" should not continue script execution, even if used inappropriately

Well I didn't see any part of that discussion that describes that. Also it's a C thing. Please don't disgrace. -- konsolebox/m On Fri, Jan 25, 2019, 9:20 AM don fong Encapsulate your code in a main function and deal with it. >> > > yes, exactly. and that supposedly "crazy" python convention (it

Re: "return" should not continue script execution, even if used inappropriately

> > Encapsulate your code in a main function and deal with it. > yes, exactly. and that supposedly "crazy" python convention (its bash equivalent) is the best way i know of to "deal with it". On Thu, Jan 24, 2019 at 4:08 PM konsolebox wrote: > Encapsulate your code in a main function and deal

Re: "return" should not continue script execution, even if used inappropriately

Encapsulate your code in a main function and deal with it. -- konsolebox/m On Mon, Jan 21, 2019, 12:39 PM Robert Elz Date:Sun, 20 Jan 2019 17:43:04 -0800 > From:don fong > Message-ID: < > cahqakpxao-pbdr2e0tnhh_iouhlwdxq_fccbzo1gxrhpfv9...@mail.gmail.com> > > | i

`complete -p -- ` doesn't yield reusable input when "-F" is assigned an invalid identifier

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local /bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bi

Re: RETURN trap will inherit last RETURN trap cmd though set +T

On 2019-01-23 15:20, Chet Ramey wrote: > On 1/23/19 10:59 AM, Shen Herbert wrote: > > Configuration Information [Automatically generated, do not change]: > > Machine: x86_64 > > OS: linux-gnu > > Compiler: gcc > > Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe > > -fstack-protector-str