Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: dima@Chg.RU
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Patch to gdb.texinfo
Date: Mon, 13 Mar 2000 00:59:00 -0000	[thread overview]
Message-ID: <200003130859.DAA25938@indy.delorie.com> (raw)
In-Reply-To: <200003121611.TAA45044@netserv1.chg.ru>

> Please apply this patch to gdb.texinfo (revision 1.1.1.14).
> This fixes several typos and markup inconsistences.

Thanks!  A few comments:

>  @kindex quit @r{[}@var{expression}@r{]}
>  @kindex q
>  @item quit
> +@item quit @r{[}@var{expression}@r{]}

This should be @itemx, not @item (since this is in a @table).  Or did
you intend to remove "@item quit"?

> -String constants are a sequence of character constants surrounded
> -by double quotes (@code{"}).
> +String constants are a sequence of character constants (without
> +single quotes) surrounded by double quotes (@code{"}).

I think "without single quotes" is ambiguous.  I suggest "not
including single quote characters @samp{'}" instead.  I also suggest
to use @samp, not @code here.  A bare @code is IMHO not suitable for
character constants, as it lacks the delimiting quotes.

> -For complicated cases, you can specify an arbitrary number of @r{-T}@var{section} @var{address}
> +For complicated cases, you can specify an arbitrary number of @samp{@r{-T}@var{section} @var{address}}

I don't see the rationale for this change.  Could you please explain?
From dima@Chg.RU Mon Mar 13 01:06:00 2000
From: Dmitry Sivachenko <dima@Chg.RU>
To: eliz@is.elta.co.il
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Patch to gdb.texinfo
Date: Mon, 13 Mar 2000 01:06:00 -0000
Message-id: <200003130906.MAA63437@netserv1.chg.ru>
References: <200003121611.TAA45044@netserv1.chg.ru> <200003130859.DAA25938@indy.delorie.com>
X-SW-Source: 2000-03/msg00222.html
Content-length: 1170

   >  @kindex quit @r{[}@var{expression}@r{]}
   >  @kindex q
   >  @item quit
   > +@item quit @r{[}@var{expression}@r{]}

   This should be @itemx, not @item (since this is in a @table).  Or did
   you intend to remove "@item quit"?

Yes, you are right.  It's my typo.

   > -String constants are a sequence of character constants surrounded
   > -by double quotes (@code{"}).
   > +String constants are a sequence of character constants (without
   > +single quotes) surrounded by double quotes (@code{"}).

   I think "without single quotes" is ambiguous.  I suggest "not
   including single quote characters @samp{'}" instead.  I also suggest
   to use @samp, not @code here.  A bare @code is IMHO not suitable for
   character constants, as it lacks the delimiting quotes.

I agree.

   > -For complicated cases, you can specify an arbitrary number of @r{-T}@var{section} @var{address}
   > +For complicated cases, you can specify an arbitrary number of @samp{@r{-T}@var{section} @var{address}}

   I don't see the rationale for this change.  Could you please explain?

Look at the printable copy.  Single quotes around `-Tsection address'
looks better.

--dima



       reply	other threads:[~2000-03-13  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003130906.MAA63437@netserv1.chg.ru>
     [not found] ` <200003121611.TAA45044@netserv1.chg.ru>
2000-03-13  0:59   ` Eli Zaretskii [this message]
2000-03-13  1:33     ` Eli Zaretskii

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=200003130859.DAA25938@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=dima@Chg.RU \
    --cc=gdb-patches@sourceware.cygnus.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