From: Joel Brobecker <brobecker@adacore.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: tromey@redhat.com, james.pandavan@googlemail.com, gdb@sourceware.org
Subject: Re: gdb v7.0 - user defined command's document section - space prefixed end
Date: Wed, 04 Nov 2009 21:18:00 -0000 [thread overview]
Message-ID: <20091104211826.GZ4573@adacore.com> (raw)
In-Reply-To: <19185.60662.189998.315630@pkoning-laptop.lab.equallogic.com>
> Yes, but "end" is not a Python keyword, so that isn't a reason to stop
> recognizing <whitespace>end.
I was thinking that the change of behavior was unintended, but Volodya
should be able to confirm, or at least give us more details.
--
Joel
prev parent reply other threads:[~2009-11-04 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 6:12 James Pandavan
2009-11-03 14:33 ` Joel Brobecker
2009-11-03 18:58 ` James Pandavan
2009-11-03 19:43 ` Joel Brobecker
2009-11-03 19:51 ` Daniel Jacobowitz
2009-11-03 22:03 ` Jim Ingham
2009-11-06 21:42 ` Vladimir Prus
2009-11-06 21:49 ` Daniel Jacobowitz
2009-11-07 1:14 ` Vladimir Prus
2009-11-13 23:41 ` Daniel Jacobowitz
2009-11-19 7:17 ` Vladimir Prus
2009-11-04 20:47 ` Tom Tromey
2009-11-04 21:07 ` Paul Koning
2009-11-04 21:18 ` Joel Brobecker [this message]
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=20091104211826.GZ4573@adacore.com \
--to=brobecker@adacore.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@sourceware.org \
--cc=james.pandavan@googlemail.com \
--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