AddressSanitizer reports a heap buffer overflow from skip_node_separator() on malformed info file

Steps to reproduce: Compile with -fsanitize=address, then run: info -f reproduce_bug.info Expected behavior: info does not trigger AddressSanitizer errors. Actual behavior: AddressSanitizer reports a heap-buffer-overflow from skip_node_separator() in info/search.c:645 Comments: This file w

Re: how to skip default css format lines in html output

On 5/6/21 1:13 PM, Gavin Smith wrote: On 5/6/21 12:36 PM, Gavin Smith wrote: On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: It seems wrong to include inline css in generated html files, especially when using the --ccs-ref or -C INFO_JS_DIR options. The documentation is complicated

Re: how to skip default css format lines in html output

> On 5/6/21 12:36 PM, Gavin Smith wrote: > > On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: > >> It seems wrong to include inline css in generated html files, > >> especially when using the --ccs-ref or -C INFO_JS_DIR options. > >> The documentation is complicated. The advice to use !

Re: how to skip default css format lines in html output

On 5/6/21 12:36 PM, Gavin Smith wrote: On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: It seems wrong to include inline css in generated html files, especially when using the --ccs-ref or -C INFO_JS_DIR options. The documentation is complicated. The advice to use !important to ov

Re: how to skip default css format lines in html output

On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote: > It seems wrong to include inline css in generated html files, > especially when using the --ccs-ref or -C INFO_JS_DIR options. > The documentation is complicated. The advice to use !important > to override the default style rules feels

Re: AddressSanitizer reports a heap buffer overflow from scan_node_contents() on malformed info file

On Sat, Feb 20, 2021 at 05:43:55PM -0500, Nathaniel Beaver wrote: > Steps to reproduce: > Compile with -fsanitize=address, then run: > > info -f reproduce_bug.info > > Expected behavior: > > info does not trigger AddressSanitizer errors. > > Actual behavior: > > AddressSanitizer reports a heap

Re: problem with groff.texi: @ref{} in PDF and HTML fomats

Hi, Gavin! At 2021-05-04T20:31:15+0100, Gavin Smith wrote: > On Sun, Apr 18, 2021 at 03:16:52AM +1000, G. Branden Robinson wrote: > > Not knowing anything about Texinfo internals, and seeing what happens when I > > comment these lines out, I suspect the problem lies with the following. > > > >