From: Michael Snyder <msnyder@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] New 'to' command
Date: Mon, 13 Jan 2003 21:14:00 -0000 [thread overview]
Message-ID: <3E232C2F.9A5EB7A0@redhat.com> (raw)
In-Reply-To: <15905.56281.661173.8077@localhost.redhat.com>
Elena Zannoni wrote:
>
> Daniel Jacobowitz writes:
> > On Sun, Jan 12, 2003 at 02:20:40PM -0500, Elena Zannoni wrote:
> > >
> > > Following up from the long long long thread:
> > > http://sources.redhat.com/ml/gdb-patches/2002-12/msg00584.html
> > >
> > > Here is a new command called 'to', which takes a location (any
> > > location) specified like for the break command, and simply continues
> > > to it, with the restriction that the current frame is not exited.
> > >
> > > I have left the current 'until' command alone, except for a modification
> > > of the help string.
> > >
> > > If this is agreed upon, I'll submit doco changes and testsuite.
> >
> > Well, I like it just because it's nice to see us moving forwards... and
> > "to" is as good a name as any, I guess. I'm worried that it doesn't
> > pass the obviousness test:
> >
> > - Hypothesize a forgetful Dan. This is easy; I can provide one any
> > time you need one.
> > - He remembers a long thread about until and to
> > - But he's forgotten which one does which!
> > - And he didn't think of checking in "help"!
> > - So, how does he figure out which does which?
> >
> > I think that the names of two commands should suggest logically
> > different behaviors, or we're just setting up more confusion. I don't
> > see how given "until 900" and "to 900" the user could figure out which
> > wants the current frame.
> >
>
> I am not attached to either name, I just couldn't come up with better
> ones. My main rationale was to leave 'until' untouched.
>
> > That said, I don't mind this solution. I'll get used to it; I suspect
> > anyone else who wants to use it can too. Let's see if you satisfy
> > everyone else :)
> >
>
> Let's hope...
I have no complaints. Only -- wasn't "until" broken?
Is it still broken?
Should we make "until" and "to" mutually exclusive, ie.
should "until" reject locations outside the current frame?
next prev parent reply other threads:[~2003-01-13 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 19:16 Elena Zannoni
2003-01-12 19:41 ` Daniel Jacobowitz
2003-01-12 21:15 ` Elena Zannoni
2003-01-13 21:14 ` Michael Snyder [this message]
2003-01-14 20:21 ` Fernando Nasser
2003-01-14 21:05 ` Elena Zannoni
2003-01-14 21:07 ` Daniel Jacobowitz
2003-01-14 21:17 ` Elena Zannoni
2003-01-12 20:50 Michael Elizabeth Chastain
2003-01-12 21:15 ` Elena Zannoni
2003-01-14 21:14 Michael Elizabeth Chastain
2003-01-14 21:17 ` Elena Zannoni
2003-01-14 22:11 ` Fernando Nasser
2003-01-15 0:07 ` Elena Zannoni
2003-01-15 7:48 ` Eli Zaretskii
2003-01-15 19:16 ` Michael Snyder
2003-01-16 14:29 ` Fernando Nasser
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=3E232C2F.9A5EB7A0@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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