From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: denis.maier@unibe.ch, ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Title for tabulate
Date: Sun, 28 Nov 2021 14:26:06 +0100 [thread overview]
Message-ID: <94934c65-77eb-1d2d-1235-3d1f4667564d@xs4all.nl> (raw)
In-Reply-To: <090af8e4b06f434c994990521e8acc4a@unibe.ch>
On 11/28/2021 1:22 PM, denis.maier@unibe.ch wrote:
>
>> -----Ursprüngliche Nachricht-----
>> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Hans Hagen
>> via ntg-context
>> Gesendet: Sonntag, 28. November 2021 12:40
>> An: Denis Maier via ntg-context <ntg-context@ntg.nl>
>> Cc: Hans Hagen <j.hagen@xs4all.nl>
>> Betreff: Re: [NTG-context] Title for tabulate
>>
>> On 11/28/2021 9:15 AM, Denis Maier via ntg-context wrote:
>>
>>> A couple of questions :
>>>
>>> - Is it possible to have the title be typeset only once? I.e., it
>>> should not repeat on each page.
>> why not just use
>>
>> \subsubsubject{xxxxxxxx}
>
> That sounds like a neat solution. I'll investigate.
> Does that play nicely with structurelevels? I mean, let's say I'm somewhere higher, e.g. on chapter, the next level would be section. If I now invoke this subsubsubject manually, does that break the levels structure?
often it's ok as subjects are unnumbered but you can play safe:
\definehead[myownhead][subsubsubsubsubsubject]
\myownhead
you can then always go lower (more sub) if needed
and using dedicated head commands is also cleaner
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-11-28 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 8:15 Denis Maier via ntg-context
2021-11-28 11:40 ` Hans Hagen via ntg-context
2021-11-28 12:22 ` Denis Maier via ntg-context
2021-11-28 13:26 ` Hans Hagen via ntg-context [this message]
2021-11-30 11:41 ` Denis Maier via ntg-context
2021-12-14 17:16 Benjamin Buchmuller via ntg-context
2021-12-14 18:16 ` Hans Hagen via ntg-context
2021-12-16 10:39 ` Benjamin Buchmuller via ntg-context
2021-12-16 11:46 ` Hans Hagen via ntg-context
2021-12-17 7:25 ` Benjamin Buchmuller via ntg-context
2021-12-17 8:24 ` Hans Hagen via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94934c65-77eb-1d2d-1235-3d1f4667564d@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=denis.maier@unibe.ch \
--cc=j.hagen@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).