Re: Calling QSH with variables from CL -- MIDRANGE-L

Subject: Re: Calling QSH with variables from CL
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Wed, 19 Aug 2020 13:47:21 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Good point - I ran into this when using a function of ImageMagick, IIRC, where it required double-quotes around file name or some such - and there might also have been single quotes in building up the command statement.

Hence my cautionary message!!

Cheers
Vern

On 8/19/2020 10:43 AM, Jack Woehr wrote:

On Wed, Aug 19, 2020 at 4:48 AM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

QShell may also use full quotes, instead of an apostrophe - full quotes
do not need to be escaped.

One thing to remember about using full quotes with Unixy shells is that
metachar expansion happens inside full quotes and not inside apostrophes.

That doesn't mean you shouldn't use 'em, it means you have to be aware
what's going to appear inside them.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.