Instead of using the ‘~’ in the file path, try using the ‘${HOME}’ variable
instead. If you must use the ‘~’, you will likely need to escape it in many
places. Another thing to note, if you use single quotes ( ‘ ) instead of double
quotes ( “ ) , most places in bash scripts won’t try to expand t
On 07/07/2022 12:52 AM, Jon LaBadie wrote:
> On Wed, Jul 06, 2022 at 09:41:14PM -0400, H wrote:
>> I have run into a bash variable string problem that I think I have nailed
>> down to the variable string containing a tilde (~). Not sure if my
>> conclusion is correct and could use some help.
>>
>
On 07/06/2022 11:27 PM, Chris Schanzle wrote:
> Agree with Gordon's other response having specific examples of where it
> worked and didn't work would help us help you, but these things can get messy
> quickly.
>
> Since you quoted the tilde path, it is not expanded when assigned to your
> array
On 07/06/2022 10:42 PM, Gordon Messmer wrote:
> On 7/6/22 18:41, H wrote:
>> To my consternation this worked fine in some places but not in others.
>
>
> It might be easier to explain if you had an example of where it worked. The
> bash man page has a section titled "EXPANSION" that details the o
On Wed, Jul 06, 2022 at 09:41:14PM -0400, H wrote:
I have run into a bash variable string problem that I think I have nailed down
to the variable string containing a tilde (~). Not sure if my conclusion is
correct and could use some help.
To make a long(er) story short, an associative array va
On 7/6/22 18:41, H wrote:
To my consternation this worked fine in some places but not in others.
It might be easier to explain if you had an example of where it worked.
The bash man page has a section titled "EXPANSION" that details the
order in which expansions happen. Since tilde expansi
6 matches
Mail list logo
