gdb v7.0 - user defined command's document section - space prefixed end
Vladimir Prus
vladimir@codesourcery.com
Thu Nov 19 07:17:00 GMT 2009
On Friday 13 November 2009 17:36:05 Daniel Jacobowitz wrote:
> On Fri, Nov 06, 2009 at 08:56:40PM +0300, Vladimir Prus wrote:
> > Note that comment has disappeared, but it's not me -- process_next_line is given
> > an empty string, presumably because readline is trying to act smart.
>
> It's command_line_input, from top.c. It also does history expansion.
> Oh, well... for another day.
>
> This patch is OK. Please include changelogs...
>
> > + if (parse_commands)
> > + {
> > + /* If commands are parsed, we skip initial spaces. Otherwise,
> > + which is the case for Python commands and documentation
> > + (see the 'document' command), spaces are preserved. */
> > + p = p2;
> > + }
> >
> > if (parse_commands)
> > {
> >
>
> Want to combine the two if statements?
Yes, thanks. Here's the final version I've checked in.
- Volodya
-------------- next part --------------
A non-text attachment was scrubbed...
Name: final.diff
Type: text/x-patch
Size: 2248 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb/attachments/20091119/9f1e1151/attachment.bin>
More information about the Gdb
mailing list