From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patchv3 12/11] New options {relative,basename}-with-system-absolute
Date: Fri, 01 Feb 2013 08:09:00 -0000 [thread overview]
Message-ID: <83a9rocv6v.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22SwcNmbC2NZ0p8--=62StKGpFxRaa0-YN3EkLAvw19JBw@mail.gmail.com>
> Date: Thu, 31 Jan 2013 19:41:31 -0800
> From: Doug Evans <dje@google.com>
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
>
> What about basename-with-system-absolute is not clearer than basename-absolute?
What isn't clear is _when_ absolute file names are printed.
"With-system" is not specific/descriptive enough to tell that. I can
come up with shorter names with the same deficiency, such as
basename-or-absolute or basename-ifnot-system or even mostly-basename.
IOW, as long as the name itself does not eliminate the need to consult
the documentation, I see no justification for longer names. A long
name that would not need to consult documentation would be something
like
basename-but-if-from-system-libraries-then-absolute
but is, of course, preposterously long.
(I'm OK with ending this bykeshedding; I just wanted to explain why I
think the suggested names can be shrunk considerably without hampering
user experience in any way. I would be happy to come up with
significantly better, but shorter names, but I cannot.)
next prev parent reply other threads:[~2013-02-01 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 22:10 [patchv2 " Jan Kratochvil
2013-01-30 7:48 ` [patchv3 " Jan Kratochvil
2013-01-30 17:15 ` Eli Zaretskii
2013-01-30 18:30 ` Eli Zaretskii
2013-01-30 18:53 ` Jan Kratochvil
2013-01-30 20:11 ` Eli Zaretskii
2013-01-30 21:48 ` Doug Evans
2013-01-31 3:49 ` Eli Zaretskii
2013-01-31 18:07 ` Doug Evans
2013-01-31 18:54 ` Eli Zaretskii
2013-02-01 3:41 ` Doug Evans
2013-02-01 8:09 ` Eli Zaretskii [this message]
2013-02-02 18:12 ` Jan Kratochvil
2013-02-01 20:59 ` Tom Tromey
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=83a9rocv6v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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