unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 40977@debbugs.gnu.org, Hartmut Goebel <h.goebel@crazy-compilers.com>
Subject: bug#40977: --load-path does not honor ~
Date: Sat, 02 May 2020 15:14:01 +0200	[thread overview]
Message-ID: <87k11u8oo6.fsf@gnu.org> (raw)
In-Reply-To: <20200430193439.0db54d2f@scratchpost.org> (Danny Milosavljevic's message of "Thu, 30 Apr 2020 19:34:39 +0200")

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>> After processing options, guix need to "expanduser()" (as it is called
>> in Python) on all arguments which are paths.  
>
> Please don't do it.
>
> UNIX has its warts, and this is a well-known one (use ${HOME} instead).

Seconded.

Tilde expansion is performed by the shell.  In the case of
‘--foo=~/bar’, tilde expansion does not happen because ~ is right in the
middle of a string.

It’s admittedly annoying, but it’s not something Guix itself should
paper over.  Doing that would open a can of worms, as illustrated by the
example Tobias gave.

Ludo’.




  parent reply	other threads:[~2020-05-02 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  8:15 bug#40977: --load-path does not honor ~ Hartmut Goebel
2020-04-30 15:31 ` zimoun
2020-04-30 16:37   ` zimoun
2020-04-30 16:42   ` Hartmut Goebel
2020-04-30 16:50     ` zimoun
2020-04-30 17:34       ` Danny Milosavljevic
2020-04-30 17:53         ` Leo Famulari
2020-04-30 18:14           ` zimoun
2020-05-02 13:14         ` Ludovic Courtès [this message]
2020-05-02 13:55           ` zimoun
2020-05-02 22:14             ` Ludovic Courtès
2020-04-30 19:21     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-30 20:54       ` zimoun
2020-05-01  6:51         ` Bengt Richter
2020-05-01 15:24       ` zimoun

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87k11u8oo6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40977@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=h.goebel@crazy-compilers.com \
    /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/guix.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).