From: "Давыдов, Кирилл Александрович" <davidov_ka@edu.surgu.ru>
To: ntg-context@ntg.nl
Subject: [NTG-context] Vanishing floats with location=split and \start ... \stopsplittext within
Date: Tue, 4 Jun 2024 18:57:27 +0500 [thread overview]
Message-ID: <CANCDDAoyhYZhokdiM29HhOtakcECYrf6JO9f0jMqSWESZGMj0g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1574 bytes --]
Greetings,
I have run into an issue whilst using \start ... \stopsplittext. I intended
to use it for large code listings (using the t-vim module), however floats
with location=split using that environment seem to vanish if there is
nearly not enough text before the float to fill a page. Not only that, a
second float like that seems to lead to fatal errors related to an unclosed
group, however the document compiles regardless. The following MWE is an
example of this. I am using ConTeXt version 2024.05.27 18:16.
\definefloat[codelisting][codelistings]
\setupcaption[codelisting][location=top]
\setuplabeltext[english][codelisting=Listing ]
%\showboxes
\starttext
\input knuth
\input knuth
\input knuth
\input knuth
% Filler. Filler. Filler. Filler. % uncomment to push out a full page. the
float will appear
\startplacecodelisting[
title=My great C program on display!,
location=split,
]
\startsplittext
\tt \input zapf
\stopsplittext
\stopplacecodelisting
\input ward
\startplacecodelisting[
title=My second great C program on display!,
location=split,
]
\startsplittext
\tt \input ward
\stopsplittext
\stoptext
On a related note, one can also observe that with specific amounts of text
a float may end up being split in two on a single page, however I could not
replicate it. Additionally, code listings done with t-vim's commands seem
to lose line numbering within \start ... \stopsplittext in splittable
floats, but I figure that's more on the module authors. In any case, is
there more I can do other than not use floats for code listings?
[-- Attachment #1.2: Type: text/html, Size: 1788 bytes --]
[-- Attachment #2: Type: text/plain, Size: 511 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2024-06-04 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 13:57 Давыдов, Кирилл Александрович [this message]
2024-06-04 16:22 ` [NTG-context] " Hans Hagen via ntg-context
2024-06-04 18:44 ` Kirill Davidov
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=CANCDDAoyhYZhokdiM29HhOtakcECYrf6JO9f0jMqSWESZGMj0g@mail.gmail.com \
--to=davidov_ka@edu.surgu.ru \
--cc=ntg-context@ntg.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).