output.log 2>&1
but that is essentially the same as the .log file that is produced by default
when you run from the command line.
As your book is large you could try adding \writestatus commands at suitable
points so that when your messages appear in the log you know that processing
reached that far in the
d
end
for k, v in next, collected.en.environments do
if v ~= true then
filenames[k] = v
end
end
end
for k, v in next, collected do
local c = v.commands
local e = v.environments
for k, v in next, commoncommands do
t;
Taking you literally in that you want a *file* listing the occurences and not a
typeset page listing the occurrences then you could try using the following in
your document at the places where you currently put \requirementA etc:
\writestatus{RequirementMet}{Requirement A is met in sectio
} {
\definetypescriptprefix [b:adobesource#1##1]
[-\typescriptprefix{b:as:##1}]
\definetypescriptprefix [bi:adobesource#1##1]
[-\typescriptprefix{b:as:##1}it]
}
}
\starttypescript
[adobesource,adobesourcedisplay,adobesourcelight,adobesourcedisplaylight]
%
\writestatus{Serif
\def\stoptikzinput
{\autoparagraphmode\plusone
\popcatcodetable
\popmacro\meaning
\popoverloadmode}
\permanent\protected\def\tikzinputfile#1%
{\starttikzinput
\input{#1}\relax
\stoptikzinput}
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
% For now we
manual LMTX-primitives on page 21 tells me:
>>>>You can explicitly freeze an unfrozen macro.
>>>>...
>>>>A redefinition will now give: You can't redefine a frozen macro.
>>>> But is this true? The following code seems to contradict this:
&
.
...
A redefinition will now give: You can't redefine a frozen macro.
But is this true? The following code seems to contradict this:
\def\HOME{myhome}
\writestatus{1}{\meaning\HOME}
\letfrozen\HOME
\writestatus{2}{\meaning\HOME}
\def\HOME{other home}
\writestatus{3}{\meaning\HOME
edefinition will now give: You can't redefine a frozen macro.
>> But is this true? The following code seems to contradict this:
>> \def\HOME{myhome}
>> \writestatus{1}{\meaning\HOME}
>> \letfrozen\HOME
>> \writestatus{2}{\meaning\HOME}
>> \def\HOME{other
to contradict this:
\def\HOME{myhome}
\writestatus{1}{\meaning\HOME}
\letfrozen\HOME
\writestatus{2}{\meaning\HOME}
\def\HOME{other home}
\writestatus{3}{\meaning\HOME}

Is this mechanism broken? It looks so useful to prevent accidental redefinition!
here i run with
\enabledirectives
The manual LMTX-primitives on page 21 tells me:
You can explicitly freeze an unfrozen macro.
...
A redefinition will now give: You can't redefine a frozen macro.
But is this true? The following code seems to contradict this:
\def\HOME{myhome}
\writestatus{1}{\meaning\HOME
cted\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
% For now we need this but we need to educate the user to wrap settings in the
% wrappers. So some day the next line will go. I need to check what commands are
% possible outside a picture.
\overloadmode\zerocount
\newtoks\everytikzpic
fter a decade it is time
to remove the \type
15 %D {\pdf*} ones completely. For the moment I keep them commented
but even that will
16 %D go away.
17
18 \writestatus{loading}{ConTeXt Backend Macros / PDF}
19
20 \registerctxluafile{lpdf-ini}{optimize}
21 >> \registerctxlua
\relax \global
\advanceby #1\plusone \permanent \global #3#5=#1\relax \else \writestatus {warning}{no
room f
\newmuskip \scratchmuskip
\newmuskip \globalscratchmuskip \newmuskip \privatescratchmuskip
! Control sequence expected instead of undefined.
\syst_basics_alloca
\else \writestatus
{warning}{no room f
\newmuskip \scratchmuskip
\newmuskip \globalscratchmuskip \newmuskip \privatescratchmuskip
! Control sequence expected instead of undefined.
\syst_basics_allocate_yes #1#2#3#4#5->\ifnum #1<#4\relax \global
\advanceby
file
(\writestatus{SPLITPOINT}{\the\realpageno}) at the end of part 1, which I then
wanted to process with a script (e.g., read the page number, use pdftk to split
the complete PDF at this point to get PDFs for the individual volumes).
However, at the end I've just had to send the PDF containing
dface.
text {\it text {\bi text} text} text
\stoptext
\unprotect
\def\pack_layers_positioned_box_nop
{\vpack
{\writestatus{WOLF}{\getboxlly\b_layers}%
\writestatus{WOLF}{\getboxllx\b_layers}%
\vskip-\getboxlly\b_layers
\hskip-\getboxllx\b_layers
\hsize-\dimexpr
ult}]
\setvariables
[assignments]
[set={\setups[assignments:set]}]
\startsetups assignments:set
\writestatus{variables}{assignments:set is being called..}
\startalignment[middle]
\bTABLE[frame=off]
\setupTABLE[c][1][align=flushleft,style=bold,distance=2cm]
\setupTABLE[c][2][al
for
>> %C details.
>>
>> %D A fixed variant of the t-tikz module distributed with tikz. For practical
>> reasons
>> %D per 2021 we split the module for \MKIV\ and \LMTX. (Maybe some day I'll
>> optimize
>> %D TIKZ a bit.)
>> %D
>> %D All
on
> unix
> %D tds finally adopted a case insensitive approach.)
>
> %D Just in case someone does a hard input ...
>
> \ifdefined\pgfdefined\endinput \fi
> \ifdefined\pgfcoredefined\endinput \fi
>
> %D ... but normally we end up here:
>
> \startmodule[tikz]
>
sone
\popcatcodetable
\popoverloadmode}
\permanent\protected\def\tikzinputfile#1%
{\starttikzinput
\input{#1}\relax
\stoptikzinput}
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
% For now we need this but we need to educate the user to wrap settings in the
% wrappers. So
z.code.tex}
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
% For now we need this but we need to educate the user to wrap settings in the
% wrappers. So some day the next line will go. I need to check what commands are
% possible outside a picture.
\overloadmode\zerocount
zinput}
\tikzinputfile{t-pgf.tex}
\tikzinputfile{t-pgffor.tex}
\tikzinputfile{tikz.code.tex}
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
% For now we need this but we need to educate the user to wrap settings in the
% wrappers. So some day the next line will go. I need to
=lang-rep,
%Dversion=2013.04.28,
%D title=\CONTEXT\ Language Macros,
%D subtitle=Substitution,
%D author=Hans Hagen,
%D date=\currentdate,
%D copyright={PRAGMA ADE \& \CONTEXT\ Development Team}]
%C
%C This module is part of the \CONTEXT\ macro||pack
catcode`\!=12
\input t-pgf.tex
\input t-pgffor.tex
\input tikz.code.tex
\popcatcodetable
\popoverloadmode
\permanent\protected\def\tikzerrormessage#1#2#3%
{\writestatus{#1}{#2}}
\ifcase\contextlmtxmode
\let\starttikzsettings\relax
\let\stoptikzsettings \relax
\
sorry, not true:
Am 31.05.21 um 12:36 schrieb Werner Hennrich:
but the patch isn't loaded any more.
my
\writestatus\m!system{beware: LOCAL PATCH LOADED FOR xtable}
from inside the \else to \fi is indeed still in my console.
case re safe update closed -
thanks, Werner
es: lmmono10-regular.otf,
>libertinusmath-bold.otf, libertinusmath-regular.otf,
>libertinusserif-regular.otf
Looks like something is accidentally being typeset (maybe stored in a
box) before \starttext. You can reproduce this in MKIV with the
following
\writestatus{debug}{Before}
information to the log file:
\writestatus{!}{SPLIT HERE: \the\realpageno}
You should be then able to extract the split points from the log file and
extract the components from the complete PDF.
Or, if you know that you will need to split your document at certain structure
elements (chapters
e}\page}
\appendetoks
\writestatus{!}{}
\writestatus{!}{SPLIT HERE: \the\realpageno}
\writestatus{!}{}
\to \everystoptext
\dorecurse{10}{\samplefile{tufte}\page}
and then use this number in:
context --extra=select --selection=1:4oeps.pdf --once --autopdf
c
curse{10}{\samplefile{tufte}\page}
\appendetoks
\writestatus{!}{}
\writestatus{!}{SPLIT HERE: \the\realpageno}
\writestatus{!}{}
\to \everystoptext
\dorecurse{10}{\samplefile{tufte}\page}
and then use this number in:
context --extra=select --selection=1:4oeps.pdf --o
treat them as two individual books, but then I'd have to get the
last page number of volume 1 in volume 2.
On the console you see the pagenumbers right? What you need is the
realpage. You could actually do something:
\dorecurse{10}{\samplefile{tufte}\page}
\appendetoks
\writestatus
only noticeable difference is that now I need to
explicitly \usemodule[tikz] in order to use pgfplots. I checked and found the
line
\usemodule[t][tikz]
in t-pgfplots.tex. I guess that explains it.
> then you can define the \PackageError macro (I did it with some trial and
> error but
it with some trial
and error but the next seems to work:
\let\PackageError\writestatus
so I'll add something like that to m-tikz.mkiv
after all that I get this:
PGFPlots: reading {mfe-addplot.dat}
pgfplots> Sorry, could not retrieve column 't' from table
'\\pgfplotstableread@filename
Hi Jano,
It's not clear to me what you want to measure when but here is a weekend
playground (you're locked down anyway).
\def\MacroJano#1%
{\writestatus{JANO}{ONE}
\setbox0=\hbox\bgroup\xmlflush{#1}\egroup}
\startluacode
function document.FunctionJano(id
ait ->\begingroup \read 16 to \wait
\endgroup
\installsystemnamespace ...??#1\endcsname \writestatus \m!system {duplicate
system namespace '#1'}\wait
\else \global \advance \c_syst_helpers_n_of_names...
l.4554 \installsystemnamespace{extraevery}
Is it
fer "german"
xml > core > load error in [buffer: german]: invalid xml file -
parsed text
Minimal code to explain what is done:
% Loading from buffer.
\def\loadvocabularyfrombuffer#1{%
\writestatus{HVDM-VOC}{load vocabulary from buffer "#1"}%
\X
]
\unprotect
\writestatus{loading}{ConTeXt User Module / look}
\installnamespace {look}
\installcommandhandler \look {look} \look
\appendtoks
\setuevalue{\currentlook}{\do_look{\currentlook}}
\to \everydefinelook
\unexpanded
Hello list! I was reading the following:
https://wiki.contextgarden.net/Style_Alternatives
I wanted to figure out how to make a simple module. However, there's a
point in the example below which I don't understand
% macros=mkvi
\startmodule[look]
\unprotect
\writestatus{loading}{ConTeXt User
>>
>>
>> On 29/08/19 5:35 PM, Henning Hraban Ramm wrote:
>>>
>>>> Am 2019-08-28 um 21:54 schrieb Hans van der Meer :
>>>>
>>>> Is it possible to force lines written in the log with \writestatus to
>>>> have a specific
19, at 09:39, Henri Menke wrote:
>
>
>
> On 29/08/19 5:35 PM, Henning Hraban Ramm wrote:
>>
>>> Am 2019-08-28 um 21:54 schrieb Hans van der Meer :
>>>
>>> Is it possible to force lines written in the log with \writestatus to have
>>>
On 29/08/19 5:35 PM, Henning Hraban Ramm wrote:
>
>> Am 2019-08-28 um 21:54 schrieb Hans van der Meer :
>>
>> Is it possible to force lines written in the log with \writestatus to have
>> a specific color? The log can be very substantial and it would be nice to
> Am 2019-08-28 um 21:54 schrieb Hans van der Meer :
>
> Is it possible to force lines written in the log with \writestatus to have a
> specific color? The log can be very substantial and it would be nice to have
> some lines brought to attention by a different color.
As a tex
Is it possible to force lines written in the log with \writestatus to have a
specific color? The log can be very substantial and it would be nice to have
some lines brought to attention by a different color.
dr. Hans van der Meer
t; \ifx\temp\empty\normalday \else\temp\fi
> \edef\temp{\systemparameter\c!m}\scratchcountertwo
> \ifx\temp\empty\normalmonth\else\temp\fi
> \edef\temp{\systemparameter\c!y}\scratchcounterthree\ifx\temp\empty\normalyear
> \else\temp\fi}
>
> \writestatus\m!system{beware: some pa
stemparameter\c!m}\scratchcountertwo
\ifx\temp\empty\normalmonth\else\temp\fi
\edef\temp{\systemparameter\c!y}\scratchcounterthree\ifx\temp\empty\normalyear
\else\temp\fi}
\writestatus\m!system{beware: some patches loaded from cont-new.mkiv}
However I still get the wrong date with the ex
'/texmf-modules/tex/generic/pgfplots/pgfplots.code.tex' into the file
'cont-yes.mkiv' :
that one will be overwritten next update .. better use cont-loc.mkiv in
texmf-local/tex/context/user/ or so and add
\writestatus{}{pdfmark hack}
and keep an eye on tikz fixes
-
\unprotect
p; \CONTEXT\ Development Team}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for
%C details.
\writestatus{loading}{MetaPost Graphics / Grids}
%D This used to be a \TEX\ method, and a rather old one too. We keep it around but
%D
d).
>
> What am I doing wrong that such a thing happens?
>
> I’m on macOS 10.13.3 with minimals beta 2018.02.09 00:04.
>
> Cheers,
> Tim
>
>
> ––
>
> \starttext
>
> \definemacro\see[#1:#2]
> {\dosee{#1}{#2}}
>
> \starttexdefinition dosee #1#2
&
on macOS 10.13.3 with minimals beta 2018.02.09 00:04.
>
> Cheers,
> Tim
>
>
> ––
>
> \starttext
>
> \definemacro\see[#1:#2]
> {\dosee{#1}{#2}}
>
> \starttexdefinition dosee #1#2
> \doifdefinedelse{in#1}
> {\getvalue{in#1}[#1:#2]}
>
h minimals beta 2018.02.09 00:04.
Cheers,
Tim
––
\starttext
\definemacro\see[#1:#2]
{\dosee{#1}{#2}}
\starttexdefinition dosee #1#2
\doifdefinedelse{in#1}
{\getvalue{in#1}[#1:#2]}
{\writestatus{references}{reference format in#1 not defined}
\in[#1:#2]}
\stoptexdefinition %
author=Aditya Mahajan,
%D date=\currentdate,
%Dcopyright=Aditya Mahajan,
%Demail=adityam ieee org,
%D license=Simplified BSD License]
\writestatus{loading}{Simple matrix (ver: 2014.02.18)}
\startmodule[simplematrix]
\unprotect
\definenamespace
[simplematrix]
[ \c
In a document
a series of xml files is processed.
The nodes processed are as usual defined in
\xmlsetsetup{#1}\writestatus{}{MARKER}{node1|node2|..}{name:*}\stopxmlsetups
\xmlregistersetup{name:setups}
The root is called with \xmlprocessfile{root}{filename}{} and has a setup as
follows
On 2017-03-09 16:20, Hans Hagen wrote:
On 3/9/2017 4:39 AM, Rik Kabel wrote:
ConTeXters,
What is the best way to get the current section number in a basic format
(pt.ch.s.ss... as displayed in the log in structure sectioning entries)
for display in a custom log entry (via \writestatus)? I have
On 3/9/2017 4:39 AM, Rik Kabel wrote:
ConTeXters,
What is the best way to get the current section number in a basic format
(pt.ch.s.ss... as displayed in the log in structure sectioning entries)
for display in a custom log entry (via \writestatus)? I have tried
\fullheadnumber
ConTeXters,
What is the best way to get the current section number in a basic format
(pt.ch.s.ss... as displayed in the log in structure sectioning entries)
for display in a custom log entry (via \writestatus)? I have tried
\fullheadnumber and such, but cannot find something appropriate
levant contents of t-contests.mkiv are:
%M \usemodule[contests]
%M \loadsetups[t-contests.xml]
\writestatus{loading}{ConTeXt User Module / ConTests}
%D \subject{Implementation}
\unprotect
\ctxloadluafile{t-contests}
%D \macros{loadSuite}
%D
%D \showsetup{loadSuite}
\def\loadS
crlf
\xmlall{#1}{buffer/*}
\stopxmlsetups
\startxmlsetups xml:demo:b
\xmlstripnolines{#1}{.}
{\bf\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:demo:document
\writestatus{TEST}{start document}
start document "\xmldocument"\blank
\xmlflush{#
es-xml}{}}\crlf
>\xmlprocessbuffer{notes}{notes-xml}{}
>\blank
>Not ok with
>\type{\xmlprocessbuffer{notes}{notes-xml}{notes:takenotes}}\crlf
>\xmlprocessbuffer{notes}{notes-xml}{}
>\textrule{end of test \#2}
>\stoptext
>\stophiding
>
>%\starthiding
>% Test #3
>\startxmlsetup
er of = \xmlcount{#1}{note}
\stopxmlsetups
\startxmlsetups notes:include
\writestatus{DEBUG}{enter notes: include file
\xmlattribute{#1}{../include}{file}}
\xmlinclude{#1}{../include}{file}
\stopxmlsetups
\starttext
\type{\xmlprocessbuffer{notes}{notes-xml}{notes:notes}} will crash
\xmlpro
/lxml-tex.lua:579: in
>> function
><...-35/tex/texmf-context/tex/context/base/mkiv/lxml-tex.lua:567>
>> (...tail calls...)
>>
>>
>> De navolgende code is toch niet fout?
>>
>> De main input is
>>
>>
>>
>>
>>
ut?
>
> De main input is
>
>
>
>
>
>
> De file notes-example.xml bevat slechts
> subnodes etc
> omsluiten met ... doet niets anders.
>
> Ik doe het volgende (met loading tracker enabled
> \startxmlsetups notes:takenotes
> % Include files and buffers.
&
>
>
> De file notes-example.xml bevat slechts
> subnodes etc
> omsluiten met ... doet niets anders.
>
> Ik doe het volgende (met loading tracker enabled
> \startxmlsetups notes:takenotes
> % Include files and buffers.
> \xmlfilter{#1}{/include/command(notes:include
% Include files and buffers.
\xmlfilter{#1}{/include/command(notes:include)}
\stopxmlsetups
\startxmlsetups notes:include
% Include from file.
\doifnot{\xmlatt{#1}{file}}{\empty}
{\writestatus{HVDM-NOTE-DEBUG}{..looking for file \xmlatt{#1}{file}}
\xmlinclude{#1}{}{file}}
\stop
{\processcommalist[#1]\bibentry
\doifnotempty{#2}{\space#2\strut\par}}}
% Disabling citations altogether.
\def\Cdofootnotecite[#1][#2]{\ignorespaces}%
% Citations switched on.
\def\enablecitations{%
\writestatus{HVDM-ONDERWIJS}{citations enabled}%
\let\dofootnotecite\Adofootnotecite}
% Citations
be very much appreciated because I have not much time left to finish
the text.
Macro for calling a context run:
% Call context for figures #1 = mode, #2 = fontchoice, #3 = colorchoice, #4 =
file without .tex extension.
\def\callcontext[#1][#2][#3]#4{%
\writestatus{HVDM}{CALLING DIRECTLUA file=#4
xmltest:setups
\xmlsetsetup{\xmldocument}{root|test}{xmltest:*}
\stopxmlsetups
\xmlregistersetup{xmltest:setups}
\startxmlsetups xmltest:root
\writestatus{TEST}{calling xmltest:root}
\xmlconcat{#1}{test}{xxx}\crlf
\xmlconcat{#1}{test/command(xmltest:test)}{yyy}\crlf
\stopxmlsetups
\startxmlsetups
}{xmltest:*}
\stopxmlsetups
\xmlregistersetup{xmltest:setups}
\startxmlsetups xmltest:root
\writestatus{TEST}{calling xmltest:root}
\xmlconcat{#1}{test}{xxx}\crlf
\xmlconcat{#1}{test/command(xmltest:test)}{yyy}\crlf
\stopxmlsetups
\startxmlsetups xmltest:test
\xmlflush{#1}
\stopxmlsetups
\startbuffer
a weird issue (Win7 64bit).
Here is the minimal sample:
\starttext
\writestatus{Español}{con acentuación}
\message{En español usamos acentuación}
\stoptext
Text from \writestatus is displayed right as utf-8. But text from
\message isn’t displayed right.
Is this a bug or am I
:
Dear list,
I have this minimal sample:
\starttext
\writestatus{apples}{oranges}
\message{Have you checked this variable?}
\stoptext
Is there a way that I can pause the compilation proccess to show the
message and that compilation would continue by pressing any key?
Many thanks
On 4/24/2015 7:37 PM, Pablo Rodriguez wrote:
Dear list,
I have this minimal sample:
\starttext
\writestatus{apples}{oranges}
\message{Have you checked this variable?}
\stoptext
Is there a way that I can pause the compilation proccess to show the
message and that compilation
Dear list,
I have this minimal sample:
\starttext
\writestatus{apples}{oranges}
\message{Have you checked this variable?}
\stoptext
Is there a way that I can pause the compilation proccess to show the
message and that compilation would continue by pressing any key?
Many thanks
the message only in the first run? Is there any
conditional based on the run number?
How can I insert a new line in \message?
Many thanks for your help,
Pablo
On 04/24/2015 07:37 PM, Pablo Rodriguez wrote:
Dear list,
I have this minimal sample:
\starttext
\writestatus{apples}{oranges
don't know why the shell command does
not work.
Try this instead (I assume that windows comes with the echo command):
\starttext
\writestatus{test}{before calling shell command}
\immediate\write18{echo HELP}
\writestatus{test}{after calling shell command}
\stoptext
Post only the output
Hi Aditya.
Thanx for reply. I am sending result from output console from your
example ie:
\starttext
\writestatus{test}{before calling shell command}
\immediate\write18{echo HELP}
\writestatus{test}{after calling shell command}
\stoptext
Output is below.
Regarding the call ConTeXt, I often
Mahajan,
%Demail=adityam at ieee dot org,
%D license=Simplified BSD License]
\writestatus{loading}{Overview Page (ver: 2013.08.31)}
\startmodule [overviewpage]
\unprotect
\setupmodule
[\c!level=]
\installnamespace{overviewpage}
\initializeboxstack{\overviewpage
Hi,
Probably this is a minor thing. When processing the following module
template:
%D \module[
%D file=p-Mymod,
%D title=The Mymod Module,
%D author=The Author,
%D date=\currentdate,
%D ]
%M \usemodule[Mymod]
%D Hello
\writestatus{loading}{ConTeXt User Module / Mymod
]
%M \usemodule[Mymod]
%D Hello
\writestatus{loading}{ConTeXt User Module / Mymod}
\unprotect
\protect
\endinput
with:
context --ctx=s-mod p-Mymod.mkiv
then the console output contains:
system error: invalid parent type for parametercommand, type
defined
{\dosingleempty\dostartsolution}
\def\dostartsolution[#1]{
\getparameters[solution][height=1em,] % set defaults (needed in case
parameters missing)
\iffirstargument
\writestatus{DEBUG}{--First argument: |#1|}
\getparameters[solution][#1,]
\fi
\writestatus{DEBUG}{--\solutionheight--}
\startSOLUTION
version which
demonstrates that the change in behaviour must have occurred after january
second.
Minimal example follows.
Hans van der Meer
Module code in file module-test is:
\writestatus{HVDM}{Module has been read}
\endinput
Test code in file moduletest.tex is:
\usemodule[module-test
in behaviour must have occurred after january
second.
Minimal example follows.
Hans van der Meer
Module code in file module-test is:
\writestatus{HVDM}{Module has been read}
\endinput
Test code in file moduletest.tex is:
\usemodule[module-test]
\starttext
module testing look into the log
in file module-test is:
\writestatus{HVDM}{Module has been read}
\endinput
Test code in file moduletest.tex is:
\usemodule[module-test]
\starttext
module testing look into the log.
\stoptext
In the log I find:
This is LuaTeX, Version beta-0.79.1 (TeX Live 2014/dev) (rev 4972)
\write18 enabled.
open
example follows.
Hans van der Meer
Module code in file module-test is:
\writestatus{HVDM}{Module has been read}
\endinput
Test code in file moduletest.tex is:
\usemodule[module-test]
\starttext
module testing look into the log.
\stoptext
modules have names like
m-
x-
s-
p-
u-
and the lookup
-simplematrix,
%D version=2014.02.18,
%Dtitle=\CONTEXT\ User Module,
%D subtitle=Simple matrix,
%D author=Aditya Mahajan,
%D date=\currentdate,
%Dcopyright=Aditya Mahajan,
%Demail=adityam at ieee dot org,
%D license=Simplified BSD License]
\writestatus{loading
\nextbox
\cleanupbox\scratchbox % remove nodes that should not be seen in the
backend twice
\writestatus{overview}{saving first page of
\overviewsection\space\overview_current_headnumber}%
\savebox{\overview}{\overview_current_headnumber}{\box\scratchbox}%
\fi
On 2013–08–04 Michael Ash wrote:
(1) Is it possible to tell which version of a module is installed,
i.e., that I am using the 2013.07.31 version of letter? (The version
of context appears in the log file but not the version of the module.)
Often modules contain a line like
\writestatus
in it, the dimexpr does evaluates to 30 pt.
Where am I at fault?
Hans van der Meer
\setuppapersize[A6][A6]
\setupbodyfont[10pt]
\starttext
10pt\ \begingroup\switchtobodyfont[20pt]20pt\endgroup\ 10pt\par
\writestatus{==}{}
10pt\ \begingroup\switchtobodyfont[\the\dimexpr(3\bodyfontsize)] times
3
up the existing typescript files and sending them where
they can be incorporated. But if that is not al…
Hans van der Meer
Minimal Tex code:
\setuppapersize[A5][A5]
%\usetypescriptfile[euler]\usetypescript[euler]
\tracetypescriptstrue
\setupbodyfont[lmodern,10pt]
\starttext
Before\writestatus
There is a nasty problem when defining the \date.
First approach:
*** macro:-\date
\def\thedate{\date}\writestatus{***}{\meaning\thedate}
Alas, I get lateron a luatex error on \date:
! LuaTeX error [string \directlua ]:1: invalid escape sequence near '\d'.
Second
One step further, thanks.
But why does
\edef\thedate{\rawdate[]}\writestatus{***}{\meaning\thedate}
result in
** macro:-unknown march 2013
instead of 20 march 2013?
Hans van der Meer
On 20 mrt. 2013, at 14:39, Wolfgang Schuster schuster.wolfg...@gmail.com
wrote:
Am
Am 20.03.2013 um 14:52 schrieb Meer H. van der h.vanderm...@uva.nl:
One step further, thanks.
But why does
\edef\thedate{\rawdate[]}\writestatus{***}{\meaning\thedate}
result in
** macro:-unknown march 2013
instead of 20 march 2013?
Provide a *working* minimal example
I see. But this is not working too. Following your suggestion I now get:
\edef\thisdate{\ctxcommand{currentdate(month, ,day, ,
year,\currentlanguage)}}\writestatus{***}{\meaning\thisdate}
*** macro:-\labeltext {march} 20 2013
The problem is essentially the same.
I am most unhappy
Am 20.03.2013 um 15:29 schrieb Meer H. van der h.vanderm...@uva.nl:
I see. But this is not working too. Following your suggestion I now get:
\edef\thisdate{\ctxcommand{currentdate(month, ,day, ,
year,\currentlanguage)}}\writestatus{***}{\meaning\thisdate}
*** macro:-\labeltext
, \day, \month, and year are established at the beginning
of a job; ..
/citation
Now the results in ConTeXT with a minimal example, put into the log for easier
copying into the mail:
\starttext
\writestatus{}{\meaning\date - \date}
\writestatus{}{\meaning\day - \the\day}
\writestatus{}{\meaning
, \day, \month, and year are established at the beginning
of a job; ..
/citation
Now the results in ConTeXT with a minimal example, put into the log for easier
copying into the mail:
\starttext
\writestatus{}{\meaning\date - \date}
\writestatus{}{\meaning\day - \the\day}
\writestatus{}{\meaning
by TeX itself as it runs, so it is inappropriate to
initialize them: \time, \day, \month, and year are established at the
beginning of a job; ..
/citation
Now the results in ConTeXT with a minimal example, put into the log for
easier copying into the mail:
\starttext
\writestatus
Someone\footnote{Prof.\
3 ABC}
4 \stoptext
5
Ok, the next is only for those who want to spend some time on the
internals ...
\starttext
\def\TestA#1%
{\writestatus{Test A}{#1}%
\ctxlua{str = #1 print(str) context(str) io.savedata(temp.tmp,str)}}
\def\TestB#1%
{\writestatus{Test B}{#1
[maps] [tt] [mono] [modern] [default]
[encoding=ec,rscale=0.90]
\definetypeface [maps] [ss] [sans] [modern] [default]
[encoding=ec,rscale=0.95]
\stoptypescript
\writestatus{maps\space warning}{This, the MkII style, is OUTDATED and
UNSUPPORTED!}
\writestatus{maps\space warning}{Please
%
{\expandafter\ifx\csname\??fontinstanceclass\fontclass-\fontbody-\s!mm-#familytag-\fontsize-1\endcsname\relax
\writestatus{fonts}{math: unset for global bodyfont
\fontclass\space at \fontbody}%
\else
\scriptscriptfont#fam\csname\??fontinstanceclass\fontclass-\fontbody-\s!mm-#familytag-\fontsize
\xmlregistersetup{load:setups}
\startxmlsetups load:myroot
\writestatus{TEST-LOAD}{loading myroot}
\xmlall{#1}{include}
\xmlall{#1}{text}
\xmlall{includes}{text}
\stopxmlsetups
\startxmlsetups load:text
*** \xmlflush{#1} ***\par
\stopxmlsetups
\startxmlsetups load:include
\writestatus{TEST-LOAD
}
\startxmlsetups load:myroot
\writestatus{TEST}{loading myroot node = #1 = \xmlname{#1}}
% \xmlverbatim{#1}{text}\par
\xmldisplayverbatim{#1}{text}\par
% \xmlinlineverbatim{#1}{text}\par
\stopxmlsetups
\startxmlsetups load:text
\writestatus{TEST}{node = #1 = \xmlname{#1}}
\xmlflush{#1
Processing xml I get with:
\writestatus{}{\xmlattributedef{#1}{.}{default}{???}}
output: ???
and \writestatus{}{\xmlattribute{#1}{.}{default}} has no attribute
output
but with: \writestatus{}{\xmlattdef{#1}{default}{???}}
output
1 - 100 of 203 matches
Mail list logo
