From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sources.redhat.com
Subject: Re: [RFA] New substitute-path commands
Date: Fri, 14 Jul 2006 13:06:00 -0000 [thread overview]
Message-ID: <20060714130558.GA24712@nevyn.them.org> (raw)
In-Reply-To: <u64i0mq01.fsf@gnu.org>
On Fri, Jul 14, 2006 at 01:37:18PM +0300, Eli Zaretskii wrote:
> > Date: Thu, 13 Jul 2006 14:27:46 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> >
> > The interface is as follow:
> >
> > (gdb) set substitute-path FROM TO
> > (gdb) unset substitute-path [FROM]
> > (gdb) show substitute-path
> >
> > The "set" command will add a substitution rule.
>
> If this _adds_ a rule, then "set SOMETHING" is not a good UI, IMO.
> How about just "substitute-path", similar to "dir", which also _adds_
> a directory?
This was my suggestion, so I'll defend it :-) I think of it as set "the
substitution path for FROM" to "TO". The parallel is set env VAR
VALUE, which sets the environment variable VAR to VALUE.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-14 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060707052219.GA971@adacore.com>
[not found] ` <u8xn5rbx7.fsf@gnu.org>
[not found] ` <20060707191203.GD971@adacore.com>
[not found] ` <uhd1sp9uv.fsf@gnu.org>
[not found] ` <20060710054027.GF971@adacore.com>
[not found] ` <ud5cdnsml.fsf@gnu.org>
[not found] ` <20060710214706.GA2390@adacore.com>
[not found] ` <20060710215114.GA31444@nevyn.them.org>
[not found] ` <20060710215630.GB2390@adacore.com>
[not found] ` <20060710215839.GA31772@nevyn.them.org>
2006-07-13 21:27 ` Joel Brobecker
2006-07-13 21:41 ` Daniel Jacobowitz
2006-07-14 10:37 ` Eli Zaretskii
2006-07-14 13:06 ` Daniel Jacobowitz [this message]
2006-07-14 13:43 ` Eli Zaretskii
2006-07-14 13:46 ` Daniel Jacobowitz
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=20060714130558.GA24712@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.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