[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #111058] Problem transmitting script arguments
From: |
anonymous |
Subject: |
[sr #111058] Problem transmitting script arguments |
Date: |
Sat, 4 May 2024 06:08:41 -0400 (EDT) |
URL:
<https://savannah.gnu.org/support/?111058>
Summary: Problem transmitting script arguments
Group: The GNU Bourne-Again SHell
Submitter: None
Submitted: Sat 04 May 2024 10:08:41 AM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: GNU/Linux
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sat 04 May 2024 10:08:41 AM UTC By: Anonymous
I have the following problem with transmitting arguments to a bash script
onward to an inside program call.
Lets name the inside program 'Z'.
An open number of arguments have to be transmitted from the script environment
to Z's environment. If an argument aa is given enclosed in double-quotes to
the script (because there are blanks within the value) these double-quotes are
removed when bash gets hold of it. When I transmit aa by use of $x, $* or $@,
the double-quotes are not resurrected by bash, which I think is a tragic
mistake because the call of Z obviously suffers a semantic error.
So far I could not solve the problem. As this kind of problem cannot be new,
is there any recommended way to solve it?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111058>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [sr #111058] Problem transmitting script arguments,
anonymous <=
- Message not available