bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Robert Elz
Subject: Re: "return" should not continue script execution, even if used inappropriately
Date: Fri, 25 Jan 2019 12:49:47 +0700

    Date:        Thu, 24 Jan 2019 21:12:01 -0800
    From:        don fong <address@hidden>
    Message-ID:  <address@hidden>

  | 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 "answers" have mostly been about "how to do this".

Yes, that would be the point, wouldn't it?

  |  however as i've stated multiple times: i'm not asking how
  | to do it, i'm explaining why this technique which is
  | denigrated in the bash FAQ is a good one and should be
  | more widely used.

And the "how to do this" is intended to show that there
are better, easier ways, but you are just not listening.
There are reasons that method is denigrated.

  | as you well know it's from a bash FAQ, bashFAQ/109
  | <https://mywiki.wooledge.org/BashFAQ/109> .

Actually, I forgot, but yes, you're right, it was the bash FAQ.

  |         sh -c '. scriptname' scriptname arg arg arg

  | that's either a terrible user experience, or requires a separate wrapper
  | script which would lose the advantages of a single self-contained file.

Once again, you're not listening.   That method is not
intended to solve the problem that you're concerned with.
It is for the original issue, in the original message in this
thread, where one of the constraints is that the script cannot
be altered.   None of the techniques, not the one you're
advocating, none of the others, can help that situation.
What's needed is a way to invoke the script so that it can
be tested, without changing it.    If you have a better
suggestion for that, please offer it.

  | On Thu, Jan 24, 2019 at 8:24 PM Robert Elz <address@hidden> wrote:
[...]

And once again, you are top posting.   Please stop.

kre

ps: for anyone unaware of the terminology, "top posting" is
when you put a reply to a message at the beginning, and
then include the whole original message after your reply.
Mailer user agents put that message there so you have some
context to aid in generating the reply, and so you can include
some quotes if appropriate.   Once that is any unquoted parts of
the original message should be deleted - the archives of the
mailing list do not need dozens of copies of ancient messages
that have all been included, top-posted in replies.   Nor do
any of the recipients.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]