Re: [bug #64752] [request] make the "next" hyperlink take you the next page, even if deeper in the hierarchy

Just use an Info reader on the manual and then you can use the ‘space bar’ to walk forward through the whole hierarchy of the manual and ‘delete’ to walk backwards. -- rsw > On Oct 14, 2023, at 10:25 AM, Patrice Dumas wrote: > > Follow-up Comment #6, bug #64752 (project octave): > > It is

Re: [help-texinfo] Newbie seeks feedback on a Texinfo learning project

With the newest Texinfo releases, you can use @ktable and have the kbd index entries automatically generated. -- Bob > On Sep 16, 2016, at 10:06 AM, Eli Zaretskii wrote: > > . A table that lists key bindings, such as this one: > >@table @kbd >@item C-c C-a >... >

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

On Tue, Jul 26, 2016 at 2:23 PM, Gavin Smith wrote: > > The external manuals then link to constant > > node names but these always point into the index.html file which > redirects > > them to the specific chapter node entries. > > I doubt that a web page that can

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

On Tue, Jul 26, 2016 at 12:51 PM, Patrice Dumas wrote: > The file names of the chapter > split cannot be known when generating the manual linking to your manual, > so there has to be redirections from split manuals in node files. > ​My question is can the redirection links

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

On Tue, Jul 26, 2016 at 10:25 AM, Gavin Smith wrote: > The nodes corresponding to sections > also had files output, but these didn't contain the actual contents of > the sections, they were redirection pages > ​So this is what I need to prevent, as I think many users

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

And here is the makeinfo script I use. Bob makeinfo Description: Binary data

Re: [help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

On Sat, Jul 23, 2016 at 1:09 PM, Gavin Smith wrote: > > As a matter of fact, it did work. The nodes that were level of section > or lower had redirection pages output for them instead. > ​Is it that you got one file per chapter and the section nodes were in the chapter

[help-texinfo] 'makeinfo --html --split=chapter' splits at Texinfo node boundaries, not chapters

Hi: Is the chapter splitting feature supposed to work? I am using 6.1dev for the makeinfo version; the problem has been there since at least 6.0. I only see a reference to 'node' in my makeinfo script though I didn't inspect it enough to see if it would grab the chapter argument; the output

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jul 5, 2016 at 12:40 PM, Robert Weiner <r...@gnu.org> wrote: >>> > If not, does that mean >>> > Hyperbole doesn't support key sequences documented by other GNU >>> > packages? >>> >>> Yes, it means you cannot activate key

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jul 5, 2016 at 1:36 PM, Gavin Smith wrote: > It's not necessary to achieve uniformity across the various output > formats in this area. There's no reason why output on paper or on a > graphical display should be subject to the limitations of a typewriter > that

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jul 5, 2016 at 12:23 PM, Eli Zaretskii <e...@gnu.org> wrote: >> From: Robert Weiner <r...@gnu.org> >> On a topic like this, if you really care >> about it, we would ask that you look at and try out Hyperbole before >> finalizing your own judgement on

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jul 5, 2016 at 10:35 AM, Eli Zaretskii wrote: >> On Sun, Jul 3, 2016 at 11:25 AM, Eli Zaretskii wrote: >> > the result [of using braces around key sequences in Info manuals) will >> > confuse the reader >> >> This is an assumption you are making that has not

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Sat, Jul 2, 2016 at 4:41 PM, Gavin Smith wrote: > @ifnotinfo > @macro Keyseq {arg} > @kbd{@{\arg\@}} > @end macro > @end ifnotinfo > @ifinfo > @macro Keyseq {arg} > @t{@{\arg\@}} > @end macro > @end ifinfo Thank you. This produces braces as desired in .pdf, .html

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Sat, Jul 2, 2016 at 2:52 PM, Gavin Smith <gavinsmith0...@gmail.com> wrote: > On 28 June 2016 at 20:41, Robert Weiner <r...@gnu.org> wrote: >>>> or you could use @kbd itself in its definition. >> >> >> From my .pdf reader, it looks like @

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jun 28, 2016 at 3:05 PM, Robert Weiner <r...@gnu.org> wrote: > On Tue, Jun 28, 2016 at 2:39 PM, Gavin Smith <gavinsmith0...@gmail.com> > wrote: > >> It should be the same text face if you use a command like @code in it, >> or you could use @kbd itself in i

Re: [help-texinfo] Want curly braces around key sequences (Was: Overfull vbox in Concept Index leads to a blank page in the middle of the index)

On Tue, Jun 28, 2016 at 12:01 PM, Gavin Smith wrote: > I'd say I haven't read the Hyperbole manual in depth and don't really > know what the braced key sequences mean: if they are just key > sequences to be typed, I'd suggest using @kbd instead with the regular > single

Re: [help-texinfo] Overfull vbox in Concept Index leads to a blank page in the middle of the index

I like to use curly braces around key sequences as I think they set them off and make them easier to read than other delimiters like the single quotes used in the Info versions of manuals. For example, {C-x o} is easy to read whether in info, html or pdf form. Is there an option I can use to get

Re: [help-texinfo] Overfull vbox in Concept Index leads to a blank page in the middle of the index

il.com> wrote: > >> On 14 June 2016 at 22:02, Robert Weiner <r...@gnu.org> wrote: >> I am finishing a Texinfo manual and getting this one error where an overfull >> vbox in TeX causes a blank page in the Concept Index. I don't see anything >> wrong with any of the i

Re: [help-texinfo] Overfull vbox in Concept Index leads to a blank page in the middle of the index

On Wed, Jun 15, 2016 at 3:57 PM, Gavin Smith <gavinsmith0...@gmail.com> wrote: > On 14 June 2016 at 22:02, Robert Weiner <r...@gnu.org> wrote: > > I am finishing a Texinfo manual and getting this one error where an > overfull > > vbox in TeX causes a blank page in t

[help-texinfo] Overfull vbox in Concept Index leads to a blank page in the middle of the index

Hi: I am finishing a Texinfo manual and getting this one error where an overfull vbox in TeX causes a blank page in the Concept Index. I don't see anything wrong with any of the index entries but the problem always occurs at the same spot in the index. Could someone have a look at the .log file