bug#47790: 27.2; XDG_DATA_HOME evaluation in move-file-to-trash

[Basil L. Contovounesios]

Thierry Volpiatto <thievol@posteo.net> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>>> Cc: Eli Zaretskii <eliz@gnu.org>,  47790@debbugs.gnu.org
>>> Date: Thu, 15 Apr 2021 13:12:29 +0100
>>> 
>>> IME when someone says "set FOO to $HOME/.foo" without any further
>>> qualification they are implicitly referring to the expansion of
>>> $HOME.
>>
>> That's what I knew, but Thierry seems to say otherwise.
>
> Well, it is common to set PATH like this:
>
> PATH="$HOME/bin:$PATH"
>
> you find this in ~/.profile or ~/.bashrc on many distros.

Any variables enclosed in double quotes "..." are expanded when this
expression is evaluated by the shell.

You can confirm this by running 'echo "$PATH"'.

> I didn't find documentaion about this though.

See one of the following:
- 'man 1 dash', headings 'Double Quotes' and 'Parameter Expansion'.
- 'man 1 bash', headings 'QUOTING' and 'Parameter Expansion'.
- (info "(bash) Double Quotes")
  https://gnu.org/software/bash/manual/html_node/Double-Quotes.html

> Anyway the problem is if one do this with XDG_DATA_HOME and trash files
> from different directories, a copy of his home directory will be done in
> each of those directories under literally "$HOME/user".

But this only happens when you set XDG_DATA_HOME to a string that
includes shell variables, right?  If so...

> If you consider this is fine and normal you can close this bug report.

...then I don't think that was ever implied as being supported, and I
don't see the need to support it, but that's just one impression.

Thanks,

-- 
Basil