Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patchv2+doc] New gdbinit.5 man page + converted gdb.1+gdbserver.1
Date: Sat, 06 Apr 2013 06:47:00 -0000	[thread overview]
Message-ID: <20130405194255.GA7927@host2.jankratochvil.net> (raw)
In-Reply-To: <83r4ioessa.fsf@gnu.org>

On Fri, 05 Apr 2013 20:28:21 +0200, Eli Zaretskii wrote:
> It looks good in Info, but I didn't try the other formats.

It's all not that simple I really spent *a lot* of time trying a combination
which is acceptable for both info and man (+briefly checked PDF)

The man output can be tested with:
	make gdb.1;nroff -man gdb.1|less -r


> @c man begin SYNOPSIS gdb
> @quotation
> gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}] [@option{-batch}] [@option{-cd=}@var{dir}] [@option{-f}]@*
> @w{    }[@option{-b}@w{ }@var{bps}] [@option{-tty=}@var{dev}] [@option{-s} @var{symfile}] [@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]@*
> @w{    }[@option{-c}@w{ }@var{core}] [@option{-x}@w{ }@var{cmds}] [@option{-d}@w{ }@var{dir}] [@var{prog}|@var{core}|@var{procID}]@*
> @end quotation
> @c man end

./../../etc/texi2pod.pl:
@end quotation without @quotation at line 41625

One has to use:

------------------------------------------------------------------------------
@c man begin SYNOPSIS gdb
@quotation
gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}] [@option{-batch}] [@option{-cd=}@var{dir}] [@option{-f}]@*
@w{    }[@option{-b}@w{ }@var{bps}] [@option{-tty=}@var{dev}] [@option{-s} @var{symfile}] [@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]@*
@w{    }[@option{-c}@w{ }@var{core}] [@option{-x}@w{ }@var{cmds}] [@option{-d}@w{ }@var{dir}] [@var{prog} [@var{core}]|@var{procID}]
@end quotation
@c man end
------------------------------------------------------------------------------

but then the man page is not right:

------------------------------------------------------------------------------
SYNOPSIS
       gdb [-help] [-nh] [-nx] [-q] [-batch] [-cd=dir] [-f]    [-b bps]
       [-tty=dev] [-s symfile] [-e prog] [-se prog]    [-c core] [-x cmds]
       [-d dir] [prog [core]|procID]
------------------------------------------------------------------------------


> On second thought, this is even better, I think:
> 
> @c man begin SYNOPSIS gdb
> @example
>  gdb    [-help] [-nx] [-q] [-batch] [-cd=@var{dir}] [-f] [-b bps] [-tty=@var{dev}]
>         [-s @var{symfile}] [-e @var{prog}] [-se @var{prog}] [-c @var{core}] [-x @var{file}] [-ex @var{cmd}]
>         [-d @var{dir}] [@var{prog}[@var{core}|@var{procID}]]
> @end example
> @c man end

Again the man output is unusable:

------------------------------------------------------------------------------
NAME
       gdb - The GNU Debugger

SYNOPSIS
                gdb    [-help] [-nx] [-q] [-batch] [-cd=<dir>] [-f] [-b bps] [-tty=<dev>]
                       [-s <symfile>] [-e <prog>] [-se <prog>] [-c <core>] [-x <file>] [-ex <cmd>]
                       [-d <dir>] [<prog>[<core>|<procID>]]

DESCRIPTION
       The purpose of a debugger such as GDB is to allow you to see what is
------------------------------------------------------------------------------

I find it relatively good this way (with some minor adjustments to do)::

------------------------------------------------------------------------------
@c man begin SYNOPSIS gdb
 gdb    [-help] [-nx] [-q] [-batch] [-cd=@var{dir}] [-f] [-b bps] [-tty=@var{dev}]
        [-s @var{symfile}] [-e @var{prog}] [-se @var{prog}] [-c @var{core}] [-x @var{file}] [-ex @var{cmd}]
        [-d @var{dir}] [@var{prog}[@var{core}|@var{procID}]]
@c man end
------------------------------------------------------------------------------
NAME
       gdb - The GNU Debugger

SYNOPSIS
        gdb    [-help] [-nx] [-q] [-batch] [-cd=I<dir>] [-f] [-b bps] [-tty=I<dev>]
               [-s I<symfile>] [-e I<prog>] [-se I<prog>] [-c I<core>] [-x I<file>] [-ex I<cmd>]
               [-d I<dir>] [I<prog>[I<core>|I<procID>]]

DESCRIPTION
       The purpose of a debugger such as GDB is to allow you to see what is
------------------------------------------------------------------------------

But I found the initial indentation of "gdb" one space right is too disturbing
in the man page.


Therefore do you find acceptable the initial form I posted?

------------------------------------------------------------------------------
@c man begin SYNOPSIS gdb
gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}]
[@option{-batch}] [@option{-cd=}@var{dir}] [@option{-f}]
[@option{-b}@w{ }@var{bps}]
    [@option{-tty=}@var{dev}] [@option{-s} @var{symfile}]
[@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]
[@option{-c}@w{ }@var{core}] [@option{-x}@w{ }@var{cmds}]
    [@option{-d}@w{ }@var{dir}] [@var{prog} [@var{core}]|@var{procID}]
@c man end
------------------------------------------------------------------------------
       gdb - The GNU Debugger

SYNOPSIS
       gdb [-help] [-nh] [-nx] [-q] [-batch] [-cd=dir] [-f] [-b bps]
           [-tty=dev] [-s symfile] [-e prog] [-se prog] [-c core] [-x cmds]
           [-d dir] [prog|core|procID]

DESCRIPTION
       The purpose of a debugger such as GDB is to allow you to see what is
------------------------------------------------------------------------------


Thanks,
Jan


  reply	other threads:[~2013-04-05 19:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 20:14 [patch+doc] New gdbinit.5 man page Jan Kratochvil
2013-02-12 16:11 ` Eli Zaretskii
2013-02-12 16:22   ` Jan Kratochvil
2013-02-12 21:20     ` Tom Tromey
2013-02-13 17:42       ` Eli Zaretskii
2013-02-19 16:28         ` Jan Kratochvil
2013-02-19 18:03           ` Eli Zaretskii
2013-02-20  8:44             ` Jan Kratochvil
2013-02-20 19:26               ` Eli Zaretskii
2013-04-04 22:09                 ` [patchv2+doc] New gdbinit.5 man page + converted gdb.1+gdbserver.1 Jan Kratochvil
2013-04-05 11:47                   ` Eli Zaretskii
2013-04-05 13:03                     ` Jan Kratochvil
2013-04-05 13:03                       ` Eli Zaretskii
2013-04-05 17:50                         ` Jan Kratochvil
2013-04-05 16:33                           ` Jan Kratochvil
2013-04-05 18:13                           ` [doc patch] gdb.1: Add -p PID Jan Kratochvil
2013-04-05 18:40                             ` Eli Zaretskii
2013-04-06  9:01                               ` [commit] " Jan Kratochvil
2013-04-05 18:29                           ` [patchv2+doc] New gdbinit.5 man page + converted gdb.1+gdbserver.1 Eli Zaretskii
2013-04-05 19:06                             ` Jan Kratochvil
2013-04-05 19:43                               ` Eli Zaretskii
2013-04-06  6:47                                 ` Jan Kratochvil [this message]
2013-04-06  6:54                                   ` Eli Zaretskii
2013-04-06  8:45                                     ` [commit] " Jan Kratochvil

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=20130405194255.GA7927@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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