I rerun `install.sh` after replacing `strc-lev.lua` and the error goes
away. Thanks Hans!
On Tue, 28 May 2024 at 20:20, Hans Hagen wrote:
> On 5/28/2024 10:48 AM, Sylvain Hubert wrote:
> > ConTeXt LMTX version: 2024.05.27 18:16
> >
> > Reproducible example:
> &g
rt wrote:
> > ConTeXt LMTX version: 2024.05.27 18:16
> >
> > Reproducible example:
> >
> > \definesectionlevels
> > [default]
> > [section, subsection, subsubsection, subsubsubsection,
> subsubsubsubsection]
> >
> > \starttext
>
Well, you define less levels than you need.
Try this :
%
\definesectionlevels
[default]
[
%chapter, % uncomment this line to make it work
section, subsection, subsubsection, subsubsubsection, subsubsubsubsection]
\starttext
ConTeXt LMTX version: 2024.05.27 18:16
Reproducible example:
\definesectionlevels
[default]
[section, subsection, subsubsection, subsubsubsection, subsubsubsubsection]
\starttext
\startsectionlevel
\startsectionlevel
\startsectionlevel
\startsectionlevel
\startsectionlevel
\startsectionlevel
start/stopsectionlevel for sectioning commands
instead. That way, users could add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
given the amount of r
ntent]
> [list={section,subsection}]
> for n=2.
>
> I'm considering using \start/stopsectionlevel for sectioning commands
> instead. That way, users could add \definesectionlevels to the document
> preamble to use whatever sectioning scheme they wanted. However, this would
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
it should be possible to map toc:2 to a combinedlist definition.
I can't require the user
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are known
it should be possible to map toc:2 to a combine
On 12/24/21 1:29 PM, Denis Maier wrote:
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your
exporter about the used sectionlevels. Once the used commands are
upport "toc:2".
I probably wasn't clear. You will support toc:2.
This:
#+Context_Section_Levels: '(chapter section subsection)
will translate into a definesectionlevels command and inform your exporter about the used sectionlevels. O
[content]
[list={section,subsection}]
for n=2.
I'm considering using \start/stopsectionlevel for sectioning commands
instead. That way, users could add \definesectionlevels to the document
preamble
users could add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
Thanks,
could add \definesectionlevels to the document
preamble to use whatever sectioning scheme they wanted. However, this
would mean that the exporter wouldn't know what sectioning commands to
use the TOC setup.
Than
subsubsubsubsection), you may need to define your own using
\definesectionlevels.
Best regards
Andreas
Am 2016-03-11 09:08, schrieb m...@silentumbrella.com:
Greetings,
Is it possible to have
\starttext
\startchapter
Hey a chapter!
\startsection
something.one
\startsection
someting.one.one
and finds itself out (by the nesting of the command)
> if its behave
> as \startpart or \startchapter or \startsection or \startsubsection or
> \startsubsubsection …
You’re looking for the \startsectionlevel command.
%\definesectionlevels[default][part,chapter,section,subsection]
\starttext
Quoting from the thread "Adaptive section structuring" of September
2012:
> %\definesectionlevels[default][section,subsection,subsubsection]
> \definesectionlevels[mine][title,subject,subsubject]
>
> \starttext
>
> \startsectionlevel [title=Alpha]
>
told you before: you are awesome!
This is exactly what I was looking for. Due to this I also found \currentstructurereference and a bunch of other commands :)
Once you know that "structure" is the keyword, "strc-sec.*" is just around the corner.
Regarding your earlier mail (\defi
hieve two things:
>
> 1) a macro (that will print a list) should also add a heading. However, the
> heading should always be one level beneath the current heading and without
> numbering. Example: within a \section it should be a \subsubject, within a
> \chapter it should be a \subjec
vel
> \stoptext
You can’t mix sectionlevels and normal section command. When you want a \section
for the first level change the level settings with
\definesectionlevels
[default]
[section,
subsection,
subsubsection,
subsubsubsection,
subsubsubsubsection]
and use
\starttext
\s
stopstructure
> \stopstructure
> \stoptext
>
> This would ease moving around sections, which might end up as
> subsections and vice versa.
%\definesectionlevels[default][section,subsection,subsubsection]
\definesectionlevels[mine][title,subject,subsubject]
\starttex
20 matches
Mail list logo