From: Eric Bavier <ericbavier@openmailbox.org>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org,
Help-Guix <help-guix-bounces+ericbavier=openmailbox.org@gnu.org>
Subject: Re: [UX] real names exposed
Date: Wed, 31 Aug 2016 18:33:53 -0500 [thread overview]
Message-ID: <b38f200f5083ed65d1813e281f9e8cd0@openmailbox.org> (raw)
In-Reply-To: <20160831231110.GB18814@jasmine>
On 2016-08-31 18:11, Leo Famulari wrote:
> On Wed, Aug 31, 2016 at 02:25:49PM -0400, Troy Sankey wrote:
>> I understand why this happens:
>>
>> % khal --help
>> Usage: .khal-real [OPTIONS] COMMAND [ARGS]...
>> [...]
>>
>> but I think it sorta sucks for user experience. Just thought I'd
>> point this
>> out, and I was wondering if there were any ideas to address this.
>>
>> Specifically, argv[0] references the name of the "real" executable,
>> rather than
>> the guix wrapper. This is almost always benign, but it looks ugly in
>> help
>> menus.
>
> I wonder if the Khal author (Christian) intends for users to rename the
> executable. Otherwise, why use argv[0]? Is it some side-effect of a
> documentation tool used by Khal?
>
> I would understand if khal and ikhal were the same executable, and
> behavior was changed based on argv[0], but that's not the case.
>
> It does look ugly.
It's not just khal. Most other executables and scripts that reference
argv[0] or $0 end up with the *=real string.
In our wrapper scripts, we pass -a to exec, which is supposed to address
this issue, but for some reason it seems ineffective.
`~Eric
--
`~Eric
next prev parent reply other threads:[~2016-09-01 0:09 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 [this message]
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
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=b38f200f5083ed65d1813e281f9e8cd0@openmailbox.org \
--to=ericbavier@openmailbox.org \
--cc=help-guix-bounces+ericbavier=openmailbox.org@gnu.org \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).