From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patchv3 12/11] New options {relative,basename}-with-system-absolute
Date: Wed, 30 Jan 2013 21:48:00 -0000 [thread overview]
Message-ID: <CADPb22SoELSecKH7t5+ROi=jx9ZJz-yEdx+tDaNdTD8Urg6_yw@mail.gmail.com> (raw)
In-Reply-To: <83obg6h1pf.fsf@gnu.org>
On Wed, Jan 30, 2013 at 12:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 30 Jan 2013 19:53:44 +0100
>> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>> Cc: gdb-patches@sourceware.org
>>
>> On Wed, 30 Jan 2013 19:30:03 +0100, Eli Zaretskii wrote:
>> > > Date: Wed, 30 Jan 2013 19:15:07 +0200
>> > > From: Eli Zaretskii <eliz@gnu.org>
>> > > Cc: gdb-patches@sourceware.org
>> > >
>> > > > -set filename-display basename|relative|absolute
>> > > > +set filename-display basename|relative|absolute|relative-with-system-absolute
>> > > > + |basename-with-system-absolute
>> > >
>> > > Can't say I like these too-old names.
>> > ^^^^^^^^^^^^^
>> > I meant too-long, of course.
>>
>> I sure agree; just I did not find a better name.
>
> Neither did I. relative-absolute and basename-absolute, perhaps?
The nice thing about {relative,basename}-with-system-absolute is that
they are clear.
It's not like these will be typed very often, and tab-completion can
reduce a lot of that.
I like the "long" names. What real problem is being solved by terse names?
$0.02
next prev parent reply other threads:[~2013-01-30 21:48 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 [this message]
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
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='CADPb22SoELSecKH7t5+ROi=jx9ZJz-yEdx+tDaNdTD8Urg6_yw@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--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