On Thu, Jul 27, 2023 at 11:13:52PM -0700, Per Bothner wrote:
> My priority issue was to be able to vary the splitting level,
> but allow sidebar entries to go deeper than the splitting level.
>
> This seems to be working acceptably at this point, by leaving out @node
> commands.
> See e.g. https:
My priority issue was to be able to vary the splitting level,
but allow sidebar entries to go deeper than the splitting level.
This seems to be working acceptably at this point, by leaving out @node
commands.
See e.g. https://domterm.org/Settings.html
Source: https://github.com/PerBothner/DomTer
On Wed, Jul 26, 2023 at 09:57:08PM +0100, Gavin Smith wrote:
> I agree that it might be difficult to do an @anchor association with
> a following @section correctly. It would be less straightforward
> to parse as the association of @anchor would depend on what came
> after it. However, it might b
On Wed, Jul 26, 2023 at 02:55:20PM +0200, Patrice Dumas wrote:
> Hello,
>
> Resuscitating an old thread as I tried to progress on the issue.
I hadn't had a clear idea of how to resolve this issue and wasn't
even confident that a resolution was possible. I don't know if
I can give the issue the a
Hello,
Resuscitating an old thread as I tried to progress on the issue.
On Fri, Jan 28, 2022 at 05:39:04PM +0100, Patrice Dumas wrote:
> On Sun, Jan 23, 2022 at 10:20:03AM -0800, Per Bothner wrote:
> >
> > On 1/22/22 02:07, Gavin Smith wrote:
> > > @chapter or @section without @node would become
On Sun, Jan 23, 2022 at 10:20:03AM -0800, Per Bothner wrote:
>
> On 1/22/22 02:07, Gavin Smith wrote:
> > @chapter or @section without @node would become a lot like
> > @heading except perhaps there could also be an @anchor generated
> > for the chapter heading as well as appearing in the table of
On 1/22/22 02:07, Gavin Smith wrote:
@chapter or @section without @node would become a lot like
@heading except perhaps there could also be an @anchor generated
for the chapter heading as well as appearing in the table of
contents. There would have to be a check that the name of the
automatic
On Sat, Dec 25, 2021 at 12:58:58PM +0100, Patrice Dumas wrote:
> On Sun, Oct 10, 2021 at 08:56:35AM -0700, Per Bothner wrote:
> >
> >
> > On 10/10/21 07:10, Patrice Dumas wrote:
> > > I am probably missions something, but isn't what you want obtained with
> > > --split=chapter and using sectionin
On Sun, Oct 10, 2021 at 08:56:35AM -0700, Per Bothner wrote:
>
>
> On 10/10/21 07:10, Patrice Dumas wrote:
> > I am probably missions something, but isn't what you want obtained with
> > --split=chapter and using sectioning commands like @section,
> > @subsection?
>
> The fundamental problem is
On Sat, Oct 09, 2021 at 06:42:11PM -0700, Per Bothner wrote:
> Compare
> https://domterm.org/Wire-byte-protocol.html
> with
> https://domterm.org/Frontends.html
>
> The former is a section, it is divided into subsections,
> which appear in the sidebar (when the page is selected) and in the
On 10/10/21 07:10, Patrice Dumas wrote:
I am probably missions something, but isn't what you want obtained with
--split=chapter and using sectioning commands like @section,
@subsection?
The issue is that there are some topics (chapters) that are large enough
to want to split into multiple pa
Hello,
I am probably missions something, but isn't what you want obtained with
--split=chapter and using sectioning commands like @section,
@subsection?
On Sat, Oct 09, 2021 at 06:42:11PM -0700, Per Bothner wrote:
> Compare
> https://domterm.org/Wire-byte-protocol.html
> with
> https://do
Compare
https://domterm.org/Wire-byte-protocol.html
with
https://domterm.org/Frontends.html
The former is a section, it is divided into subsections,
which appear in the sidebar (when the page is selected) and in the Contents.
The latter is a chapter. It is divided into pseudo-subsection
13 matches
Mail list logo
