From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Azat Khuzhin <a3at.mail@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Show (tilde-)expanded filenames to the user?
Date: Fri, 09 Aug 2013 15:22:00 -0000 [thread overview]
Message-ID: <52050944.7070304@redhat.com> (raw)
In-Reply-To: <87ppto3qu7.fsf@fleche.redhat.com>
On 08/08/2013 08:49 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> But, I think we should have a policy here, and all commands
> Pedro> should follow it. Those that don't would be considered
> Pedro> bugs. The question then is, which policy is most appropriate?
> Pedro> grepping around for "tilde_expand", it seems to be the
> Pedro> showing expanded filenames is more common.
>
> I tend to think that showing the expanded name is best.
> My reason is that this way the user sees what actually happened.
Alright, I audited tilde_expand uses throughout the tree, and
noticed most indeed show the expanded string to the user. I'm
pushing a few patches to fix easy cases that didn't do that.
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2013-08-09 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 21:04 [PATCH] gcore: expand tilde in filename, like in "dump memory" command Azat Khuzhin
2013-08-08 17:42 ` [RFC] Show (tilde-)expanded filenames to the user? (was: Re: [PATCH] gcore: expand tilde in filename, like in "dump memory" command.) Pedro Alves
2013-08-08 18:16 ` Azat Khuzhin
2013-08-08 19:50 ` [RFC] Show (tilde-)expanded filenames to the user? Tom Tromey
2013-08-09 15:22 ` Pedro Alves [this message]
2013-08-08 17:43 ` [PATCH] gcore: expand tilde in filename, like in "dump memory" command Pedro Alves
2013-08-08 17:51 ` Azat Khuzhin
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=52050944.7070304@redhat.com \
--to=palves@redhat.com \
--cc=a3at.mail@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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