This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)]
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 10 Oct 2011 16:15:38 +0100
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
> Ulrich Weigand <uweigand@de.ibm.com>,
> eliz@gnu.org
>
> On Monday 10 October 2011 15:57:49, Jan Kratochvil wrote:
> > +@ifset HAVE_MAKEINFO_CLICK
> > +The code can have possible execution paths
> > +@clicksequence{main@click{}a@click{}b@click{}c@click{}d@click{}f} or
> > +@clicksequence{main@click{}a@click{}b@click{}e@click{}f}, @value{GDBN} cannot find which
> > one from the inferior state.
> > +@end ifset
>
> Leaving a piece of the manual out like that is not okay.
I agree.
> If this feature is too new for the currently required makeinfo
> version (which is it, btw?), we have two real choices:
>
> 1. bump the minimum required makeinfo version so we can use it
> 2. don't use the new feature
I don't want to do (1), because 4.8 is not too old relatively to 4.12,
and many people still use it. OTOH, there's nothing wrong with using
ASCII art in this case.
Jan, how strong are your feelings about using @arrow or @click?