[NTG-context] Re: Wiki - test/proposal to further clarify documentation
> On 17 Apr 2024, at 13:17, Henning Hraban Ramm wrote: > > Am 17.04.24 um 13:57 schrieb Bruce Horrocks: >> - There are at least two books, and a third being written but not yet >> released: these fit into the Tutorials and Explanation quadrants. > > Which published books do you mean? Not published in the sense of having an ISBN assigned but the ones I had in mind were: - "ConTeXt Mark IV An Excursion" by Ton Otten (ma-cd-en.pdf in the distribution) - "A not so short introduction to ConTeXt Mark IV" by Joaquín Ataz-López and your in-progress one. Regards, — Bruce Horrocks Hampshire, UK ___ 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 ___
[NTG-context] Re: preventing column break after section title
On Thu, Apr 18 2024, Peter Münster wrote: > How could I prevent a column break after the second section title please? Ok, found it: \setupitemize[each][autointro] -- Peter ___ 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 ___
[NTG-context] preventing column break after section title
Hi,
How could I prevent a column break after the second section title please?
Minimal example:
\starttext
\startcolumns[n=2]
\section{title 1}
\dorecurse{22}{bla\par}
\section{title 2} % Here starts a new column.
\startitemize
\dorecurse{15}{\item bla}
\stopitemize
\stopcolumns
\stoptext
I’ve tried "\setuphead[section][after={\columnbreak[no]}]", but it does
not help.
TIA for any hints,
--
Peter
___
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
___
[NTG-context] Re: Wiki - test/proposal to further clarify documentation
Am 17.04.24 um 23:25 schrieb Garulfo: - exactly, it's not a question of proposing new documents, but of proposing another complementary way of accessing and browsing existing ones. - Actually, the wiki is (or can be) a hub for the 4 needs: - "Reference" like https://wiki.contextgarden.net/Command/setuphead - "How-To Guides" like https://wiki.contextgarden.net/Titles - "Tutorials": - hosted https://wiki.contextgarden.net/Detailed_Example - linked https://github.com/mpsmath/stepbystep - "Explanation" : mostly linked manuals and books https://wiki.contextgarden.net/Command/setuphead and https://wiki.contextgarden.net/Titles are examples of how difficult it can be to understand where to find a particular information. It might be worth keeping only the key examples on reference pages like https://wiki.contextgarden.net/Command/*** and moving the "how-to" examples to a separate page (or pages). I agree. Let’s accept this as a rule for further wiki editing. Also, explain parameters with top priority in Command/setup* pages (keeping them in Command/define* pages etc. doesn’t hurt, but at least experienced users should know where to find something without searching). Hraban ___ 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 ___
[NTG-context] Re: How to isolate serious errors from warnings?
Am 18.04.24 um 02:09 schrieb Joel via ntg-context: I'm about to have a lengthy (2,000+ page) document published. Normally if it compiles and looks okay, I regard that as meaning no errors appeared, but I've noticed that sometimes ConTeXt will still compile, even if something isn't displayed on screen as it should: (1) I tried placing a table inside a startitemize environment, as instead of it not compiling, it left a message in the document warning that wasn't supported. (2) In another case, I had an image that ConTeXt couldn't find, as I mispelled the filenmame, and it fully compiled and made a PDF, without me noticing. (3) Or maybe in some case, a font couldn't be found for a specific character, so a single character in the file isn't displaying. Those are just some examples; I intended for something to be printed on the PDF, but it isn't showing there. Since a document of this size will have a lot of messages, is there a way to adjust the settings, from "show everything" to "show some" to "show only serious errors"? Or maybe to use > to send the errors to another file for careful study? (using Linux if that matters) You can enable trackers like \enabletrackers[figures.*] But that just gives more log messages for debugging. You get the list of all trackers with: context --global m-trackers.mkiv For your use case, directives are more helpful, like \enabledirectives[logs.errors=*] (i.e. break at every error) AFAIK that just handles missing characters, references and modules ATM, but this information might be outdated. You get all directives with context --global m-directives.mkiv Hraban ___ 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 ___
