all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40977@debbugs.gnu.org, Hartmut Goebel <h.goebel@crazy-compilers.com>
Subject: bug#40977: --load-path does not honor ~
Date: Sat, 2 May 2020 15:55:00 +0200	[thread overview]
Message-ID: <CAJ3okZ231BEc2pnkn9cikP4PY6xY4+ywPcuhpYObFsXW7U=zBQ@mail.gmail.com> (raw)
In-Reply-To: <87k11u8oo6.fsf@gnu.org>

On Sat, 2 May 2020 at 15:14, Ludovic Courtès <ludo@gnu.org> wrote:

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

Instead of 'notabug' , I propose to tag this bug as 'wontfix' and
retitle it as: "Tilde-expansion in --long-options=".

Is it ok?


Best regards,
simon

ps:
Quoting the 'wontfix' explanation [1]: ``this is a choice between two
arbitrary ways of doing things and the maintainer and submitter prefer
different ways of doing things``.
[1] https://debbugs.gnu.org/Developer.html#tags




  reply	other threads:[~2020-05-02 13:56 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
2020-05-02 13:55           ` zimoun [this message]
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

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

  git send-email \
    --in-reply-to='CAJ3okZ231BEc2pnkn9cikP4PY6xY4+ywPcuhpYObFsXW7U=zBQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=40977@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=ludo@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.