Re: [Help-bash] How to print a bash variable in the most succinct way?

[Peng Yu]

On Tue, Aug 16, 2016 at 9:46 AM, Chet Ramey <address@hidden> wrote:
> On 8/15/16 11:36 PM, Peng Yu wrote:
>> On Wed, Aug 10, 2016 at 7:40 AM, Greg Wooledge <address@hidden> wrote:
>>> On Wed, Aug 10, 2016 at 05:47:03AM -0500, Peng Yu wrote:
>>>> I need the most human readable repesentation. The one returned by declare
>>>> has redundancy in it. E.g., [1]= is not really necessary.
>>>
>>> Stop complaining that autogenerated code is less elegant than
>>> human-written code.  Write the code yourself if you don't like what a
>>> computer wrote for you.
>>
>> https://www.gnu.org/software/parallel/env_parallel.html
>>
>> env_parallel uses something like `declare -p` to extract the current
>> environment so that the variables and functions in the current bash
>> can be used to parallel sessions. But env_parallel also remove
>> variables like BASH_* with grep as they should not be inherented in
>> child parallel session.
>
> This isn't a very good idea.  If you have to do something like this, it's
> better to mark or tag the variables you want to `export', write them to a
> file, and have the child process read the file.

What if I want to export every variable that bash does not use
internally? The problem of manually specifying the variables needed is
that it not a scalable solution when the bash code involves many
variables. Any other better walk-around?

-- 
Regards,
Peng