unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 47790@debbugs.gnu.org
Subject: bug#47790: 27.2; XDG_DATA_HOME evaluation in move-file-to-trash
Date: Sat, 24 Apr 2021 11:30:06 +0000	[thread overview]
Message-ID: <87o8e3c3xa.fsf@posteo.net> (raw)
In-Reply-To: <878s58t0d0.fsf@tcd.ie>

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]


"Basil L. Contovounesios" <contovob@tcd.ie> writes:

> 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 already know this.

>> 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

I know this as well... but this is unrelated to the problem you have in
emacs.

>> 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.

Fair enough, so you can close this.

Thanks.

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  reply	other threads:[~2021-04-24 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  8:05 bug#47790: 27.2; XDG_DATA_HOME evaluation in move-file-to-trash Thierry Volpiatto
2021-04-15  8:20 ` Eli Zaretskii
2021-04-15 10:37   ` Thierry Volpiatto
2021-04-15 12:12     ` Basil L. Contovounesios
2021-04-15 12:23       ` Eli Zaretskii
2021-04-24  7:14         ` Thierry Volpiatto
2021-04-24 10:58           ` Basil L. Contovounesios
2021-04-24 11:30             ` Thierry Volpiatto [this message]
2021-04-24 12:19               ` Basil L. Contovounesios

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8e3c3xa.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=47790@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).