From: ludo@gnu.org (Ludovic Courtès)
To: Troy Sankey <sankeytms@gmail.com>
Cc: help-guix@gnu.org,
Help-Guix <help-guix-bounces+ericbavier=openmailbox.org@gnu.org>
Subject: Re: [UX] real names exposed
Date: Sun, 04 Sep 2016 21:38:30 +0200 [thread overview]
Message-ID: <87wpirihft.fsf@gnu.org> (raw)
In-Reply-To: <147294126799.23966.17879039892323433100@what> (Troy Sankey's message of "Sat, 03 Sep 2016 18:21:07 -0400")
Troy Sankey <sankeytms@gmail.com> skribis:
> I suspect the scope of this UX "bug" is larger than python. I think this probably affects every executable written in an interpreted
> language and using a shebang.
Exactly, that’s also the conclusion that I reached. :-/
Ludo’.
next prev parent reply other threads:[~2016-09-04 19:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 18:25 [UX] real names exposed Troy Sankey
2016-08-31 23:11 ` Leo Famulari
2016-08-31 23:33 ` Eric Bavier
2016-09-01 8:59 ` Ludovic Courtès
2016-09-03 15:30 ` Troy Sankey
2016-09-03 22:21 ` Troy Sankey
2016-09-04 19:38 ` Ludovic Courtès [this message]
2016-09-03 22:33 ` Ludovic Courtès
2016-09-04 19:41 ` Ludovic Courtès
2016-09-06 3:09 ` Eric Bavier
2016-09-07 22:04 ` Ludovic Courtès
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=87wpirihft.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix-bounces+ericbavier=openmailbox.org@gnu.org \
--cc=help-guix@gnu.org \
--cc=sankeytms@gmail.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.
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).