From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch+doc] New gdbinit.5 man page
Date: Tue, 12 Feb 2013 16:22:00 -0000 [thread overview]
Message-ID: <20130212162141.GA4287@host2.jankratochvil.net> (raw)
In-Reply-To: <83621x5x7d.fsf@gnu.org>
On Tue, 12 Feb 2013 17:11:18 +0100, Eli Zaretskii wrote:
> I do not necessarily object, but what would be the purpose of this?
> Why is this better than maintaining man pages in their roff format?
It is in fact Tom's idea to make the man pages in texinfo:
Re: [patch] gdb_gcore man/help/install [+doc] #2
http://sourceware.org/ml/gdb-patches/2011-12/msg00659.html
Message-ID: <m3obv3mhp8.fsf@fleche.redhat.com>
> We still need an info node for invoking gcore.
But that may have applied only to gcore (/usr/bin/gcore) which currently does
not have its gdb.texinfo description. You are right gdbinit files are already
described in gdb.texinfo.
But then:
[patch] gdb_gcore man/help/install [+doc] #2
http://sourceware.org/ml/gdb-patches/2011-12/msg00157.html
Message-ID: <20111206002555.GA12329@host2.jankratochvil.net>
> From the practical point of view with the goal to generate only the nroff .1
> format I think the choice is clear from nroff, pod and texinfo.
> The most simple format for maintenance is pod. Therefore I did not use
> texi2pod at all.
nroff is not well writable + maintainable format. And writing some man pages
(like gdbinit.5) in pod and other man pages (like gdbcore.1) in texinfo seems
to be needlessly complicated to me, then I find texinfo-for-all as the most
simple way to got forward.
I already wrote gcore.1 in nroff, gcore.1 in pod and now gdbinit.5 in texinfo
se we have already looped back while choosing the right format...
Jan
next prev parent reply other threads:[~2013-02-12 16:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 20:14 Jan Kratochvil
2013-02-12 16:11 ` Eli Zaretskii
2013-02-12 16:22 ` Jan Kratochvil [this message]
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
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=20130212162141.GA4287@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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