Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mingjie Xing <mingjie.xing@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Share options between info and man page
Date: Wed, 25 Jun 2014 01:30:00 -0000	[thread overview]
Message-ID: <CADNgcEwpYHJQSyBtYcwu+P_GuWsNXLhyQiC5b75bZm77ZogOnw@mail.gmail.com> (raw)
In-Reply-To: <83wqc6qp2r.fsf@gnu.org>

2014-06-24 23:55 GMT+08:00 Eli Zaretskii <eliz@gnu.org>:
>> From: Mingjie Xing <mingjie.xing@gmail.com>
>> Date: Tue, 24 Jun 2014 15:08:29 +0800
>> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>>
>> 2014-06-23 21:45 GMT+08:00 Pedro Alves <palves@redhat.com>:
>> >
>> > Should we re-define it as a macro under ifset man ?
>> >
>> > @ifset man
>> > @macro t{text}
>> > \text\
>> > @end macro
>> > @end ifset
>> >
>> > (I don't actually know whether possible.)
>>
>> This does not work.
>
> What exactly doesn't work, and how?

The man pages are generated by texi2pod.pl which doesn't care about
texinfo macros.  So with the above macro re-definition, "C@t{++}"
would still be misrendered.

So what I suggest is to retain "C@t{++}" in gdb.texinfo, and add a
substitution "s/\@t\{([^\}]*)\}/$1/g;" in texi2pod.pl. Thus the format
will not be lost in info pages.


  reply	other threads:[~2014-06-25  1:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  8:40 Mingjie Xing
2014-06-09 14:52 ` Eli Zaretskii
2014-06-10  0:46   ` Mingjie Xing
2014-06-10  2:52     ` Eli Zaretskii
2014-06-10  7:00       ` Mingjie Xing
2014-06-10  7:03         ` Mingjie Xing
2014-06-10 17:56         ` Eli Zaretskii
2014-06-11 11:39           ` Pedro Alves
2014-06-12  3:36             ` Mingjie Xing
2014-06-23 13:45               ` Pedro Alves
2014-06-24  7:08                 ` Mingjie Xing
2014-06-24 15:56                   ` Eli Zaretskii
2014-06-25  1:30                     ` Mingjie Xing [this message]
2014-06-26  9:34                       ` Mingjie Xing
2014-07-07  1:12                         ` Mingjie Xing
2014-07-07 14:18                           ` Joel Brobecker
2014-07-07 15:26                             ` Eli Zaretskii
2014-07-07 15:31                               ` Joel Brobecker
2014-07-08  9:47                               ` Pedro Alves
2014-07-08 14:59                                 ` 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=CADNgcEwpYHJQSyBtYcwu+P_GuWsNXLhyQiC5b75bZm77ZogOnw@mail.gmail.com \
    --to=mingjie.xing@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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