Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][python] 5 of 5 - Frame filter documentation changes
Date: Fri, 07 Dec 2012 15:54:00 -0000	[thread overview]
Message-ID: <83zk1pn9hi.fsf@gnu.org> (raw)
In-Reply-To: <83624doqdz.fsf@gnu.org>

> Date: Fri, 07 Dec 2012 17:04:08 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb-patches@sourceware.org
> 
> > >> +(gdb) disable frame-filter ``/build/test'' ``Build Test Program Filter''
> > > 
> > > Why the quotes? they were never mentioned before.  And in any case,
> > > use ".." here, not ``..'', as the conversion is not done in @example,
> > > AFAIR.
> > 
> > Quotes are needed so that options with spaces are correctly parsed
> > (like the name).  Quotes are not needed for the first "/build/test"
> > option.  I will remove those.  EMACS is quite insistent on placing
> > those quotes in @smallexample.
> 
> You are right about Emacs, but that's an Emacs bug.

Now fixed for the upcoming release 24.3 of Emacs.


  parent reply	other threads:[~2012-12-07 15:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 14:32 Phil Muldoon
2012-12-01 10:59 ` Eli Zaretskii
2012-12-05 19:11   ` Tom Tromey
2012-12-07 14:35   ` Phil Muldoon
2012-12-07 15:04     ` Eli Zaretskii
2012-12-07 15:34       ` Phil Muldoon
2012-12-07 15:54       ` Eli Zaretskii [this message]
2012-12-05 20:49 ` Tom Tromey
2012-12-07 14:55   ` Phil Muldoon
2013-03-11 22:14 Phil Muldoon
2013-03-12 17:24 ` Eli Zaretskii
2013-03-22 19:54 ` Tom Tromey
2013-04-19 14:24   ` Phil Muldoon
2013-04-22 17:03 Phil Muldoon
2013-04-26 11:54 ` Tom Tromey
2013-05-10 10:52   ` Phil Muldoon
2013-05-06  8:24 Phil Muldoon

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=83zk1pn9hi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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