From: Leo Famulari <leo@famulari.name>
To: Troy Sankey <sankeytms@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: [UX] real names exposed
Date: Wed, 31 Aug 2016 19:11:10 -0400 [thread overview]
Message-ID: <20160831231110.GB18814@jasmine> (raw)
In-Reply-To: <147266794967.23966.13712862947716543821@what>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-31 23:11 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 [this message]
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
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=20160831231110.GB18814@jasmine \
--to=leo@famulari.name \
--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).