t; > example file below should have worked:
> >
> > \setupindenting[yes,medium]
> >
> > \setuptyping[buffer][
> > indentnext=no,
> > ]
> >
> > \starttext
> >
> > \startbuffer
> > \startformula
> > \int_a^b f'(x)\,dx
> >
On 6/30/2020 9:50 PM, Mikael Sundqvist wrote:
Hi,
I want to avoid indentation after \typebuffer (or set indentnext to auto
perhaps). I am probably missing something simple, but I thought that the
example file below should have worked:
\setupindenting[yes,medium]
\setuptyping[buffer
Hi,
I want to avoid indentation after \typebuffer (or set indentnext to auto
perhaps). I am probably missing something simple, but I thought that the
example file below should have worked:
\setupindenting[yes,medium]
\setuptyping[buffer][
indentnext=no,
]
\starttext
\startbuffer
\startformula
following the example you provided this works perfectly! Many
thanks.
When your goal is to format C or C++ code you can load the scite module
which provides support for additional languages.
The \setuptyping line is necessary because the module selects the wrong
formatter for C++ but this should
it?
Best wishes,
Tomáš
\setupstartstop[DefaultSnippet][before=,after=,style=]
\defineframedtext[MPtyping][background=color,backgroundcolor=gray,width=\makeupwidth,offset=2dd,loffset=6dd,roffset=6dd,frame=on,]
\setuptyping[MP][before=\startMPtyping,after=\stopMPtyping,indentnext=auto,]
search
[DefaultSnippet][before=,after=,style=]
\defineframedtext[MPtyping][background=color,backgroundcolor=gray,width=\makeupwidth,offset=2dd,loffset=6dd,roffset=6dd,frame=on,]
\setuptyping[MP][before=\startMPtyping,after=\stopMPtyping,indentnext=auto
h,frame=on,offset=1cc,]
# >\setuptyping[MP][before={\startMPT},after={\stopMPT},]
# >\startMP bla \stopMP
# >\stoptext
# >
# >Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as
TL2019)
# >and I have got _two_ boxes -- the outer one is correct and frames the typing
wframe\defineframedtext[MPT][background="" class="">\setuptyping[MP][before={\startMPT},after={\stopMPT},]\startMP bla \stopMP\stoptextNow I tried it with ConTeXt from TL2019 (TL2018 produces the same result as TL2019)and I have got _two_ boxes -- the outer one is correct and fr
,frame=on,offset=1cc,]
\setuptyping[MP][before={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext
Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as
TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing
environment
as in the past
Hi all,
if I compile the following (minimised) code with ConTeXt from TL2017,
I receive expected result -- one framed gray box with correct width.
\starttext\showframe
\defineframedtext[MPT][background=color,backgroundcolor=gray,width=\makeupwidth,frame=on,offset=1cc,]
\setuptyping[MP][before
=263mm,
bottomheight=1mm,
footerdistance=10mm]
\usetypescript[pagella]
\setupbodyfont[pagella,12pt]
\setupcolors[state=start]
\setuptype[style={\switchtobodyfont[11pt,tt]}]
\setuptyping[style={\switchtobodyfont[11pt,tt]}]
\setupfootertexts[section][]
\setupfooter[alternative
Wolfgang will cook up a patch ...
The best solution is to remove the values from all three keys because
for now each of them is applies twice (even the style).
\setuptyping
[before=\hairline,
after=\hairline,
style=\tt\em]
\starttext
\starttyping[option=tex]
\donothing
\stoptyping
On 4/28/2019 5:56 PM, Aditya Mahajan wrote:
On Sun, 28 Apr 2019, Wolfgang Schuster wrote:
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparameter\c!after},
On Sun, 28 Apr 2019, Wolfgang Schuster wrote:
The problem are these settings in buff-imp-default.mkiv:
\setupstartstop
[DefaultSnippet]
[\c!before={\typingparameter\c!before},
\c!after={\typingparameter\c!after},
\c!style={\typingparameter\c!style}]
In buff-imp-tex.mkiv these values
[TexSnippet]
[DefaultSnippet]
Wolfgang
Aditya Mahajan schrieb am 28.04.2019 um 17:00:
Hi,
The following minimal example:
\definetextbackground
[EXAMPLE]
[
location=paragraph,
rulethickness=1pt,
leftoffset=5em,
rightoffset=0mm,
]
\setuptyping[option=tex
Hi,
The following minimal example:
\definetextbackground
[EXAMPLE]
[
location=paragraph,
rulethickness=1pt,
leftoffset=5em,
rightoffset=0mm,
]
\setuptyping[option=tex, before=\startEXAMPLE, after=\stopEXAMPLE]
\starttext
\starttyping
A = B + C
> On 11 Jan 2019, at 00:13, Wolfgang Schuster
> wrote:
>
> Hans Åberg schrieb am 10.01.19 um 22:52:
>>> On 10 Jan 2019, at 22:14, Wolfgang Schuster
>>> wrote:
>>>
>>> Hans Åberg schrieb am 10.01.19 um 22:04:
>>>> There seem
Hans Åberg schrieb am 10.01.19 um 22:52:
On 10 Jan 2019, at 22:14, Wolfgang Schuster
wrote:
Hans Åberg schrieb am 10.01.19 um 22:04:
There seems to be no option for \setuptyping[indentnext=...] following the TeX
convention to indent new paragraphs, as followed by a blank row
> On 10 Jan 2019, at 22:14, Wolfgang Schuster
> wrote:
>
> Hans Åberg schrieb am 10.01.19 um 22:04:
>> There seems to be no option for \setuptyping[indentnext=...] following the
>> TeX convention to indent new paragraphs, as followed by a blank row, but not
&g
Hans Åberg schrieb am 10.01.19 um 22:04:
There seems to be no option for \setuptyping[indentnext=...] following the TeX
convention to indent new paragraphs, as followed by a blank row, but not
otherwise.
Are you looking for the auto option of the indentnext key?
\setupindenting[yes,medium
There seems to be no option for \setuptyping[indentnext=...] following the TeX
convention to indent new paragraphs, as followed by a blank row, but not
otherwise.
___
If your question is of interest to others
me what I may be missing?
>
> Load the scite module (\usemodule[scite]) or add spaces between the
> arguments (\setuptyping [...] [...]).
Many thanks for your reply, Wolfgang.
I totally overlooked that spaces were missing in the code, so the lines
couldn’t be split.
Man
Pablo Rodriguez schrieb am 13.11.18 um 19:58:
Dear list,
I have the following sample:
\showframe
\setuppapersize[A6]
\setuptyping[TEX][align={right, broad}]
\starttext
\startTEX
\showframe
\setuppapersize[A5]
\setuptyping[TEX][align={right
Dear list,
I have the following sample:
\showframe
\setuppapersize[A6]
\setuptyping[TEX][align={right, broad}]
\starttext
\startTEX
\showframe
\setuppapersize[A5]
\setuptyping[TEX][align={right,broad}]
\starttext
\startTEX
e:
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Repl
To limit the smaller font to \starttyping it should be
\setuptyping [typing] [style=\ttxx]
or
\setuptyping [typing] [style=smalltype]
because \starttyping is a generated command like \startXML.
Wolfgang
Taco Hoekwater schrieb am 10.09.18 um 11:32:
Hi Hans,
Replace your two
Hi Hans,
Replace your two setuptyping lines with:
\setuptyping[style=\ttxx]
\definetyping[XML]
\setuptyping[XML][option=XML,style=italic]
nothing else needs to change
Best wishes,
Taco
> On 10 Sep 2018, at 11:22, Hans van der Meer wrote:
>
>
Taco Hoekwater
Elv
I want to differentiate the typing of XML-code with \startXML and other text with \starttyping.That doesn’t work as I expect or I misinterpret something.The minimal example shows that in the following code there is no difference between using \startXML or \starttyping
typingsetup.pdf
on, subject][style=\ssa]
%
\setupindenting[first,always,2em]
\setupinterlinespace[line=1.5em]
\setupheads[indentnext=yes]
\setupwhitespace[big]
\setupfootnotes[bodyfont=9pt]
%
\setuplinenumbering[style=small,location=text,color=darkgreen]
\setuptype[style=\ttx]
%\setuptype[space=on]
\s
...]
>> Note that even partial XML is highlighted correctly.
> Dear Christoph,
>
> many thanks for your reply.
>
> Your module is really great fine. It supports both \setuptype and
> \setuptyping options.
>
> It is really a pity that it lacks TeX, since I’m focused on Co
On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
On 12/21/2017 08:05 PM, Aditya Mahajan wrote:
On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
[...]
I don’t remember which were the options in t-vim, but I need the
options from \setuptyping and \setuptype.
Currently vim does not support
On 12/21/2017 08:05 PM, Aditya Mahajan wrote:
> On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
>> [...]
>> I don’t remember which were the options in t-vim, but I need the
>> options from \setuptyping and \setuptype.
>
> Currently vim does not support these primarily beca
ks for your reply.
Your module is really great fine. It supports both \setuptype and
\setuptyping options.
It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet
(after all, it would be a Spanish introduction to ConTeXt ;-)). XML will
come later.
I’m afraid that XML comments
ind these that i don't want
> to break
Then I will have to wait for that implementation. Sorry for not being
able to provide the patch myself.
scite is great for coloring, but it lacks the options from \setuptype
and \setuptyping. I don’t need escapes, but many of the other options.
I need
which were the options in t-vim, but I need the
options from \setuptyping and \setuptype.
Currently vim does not support these primarily because I don't use XML so
I never thought of this.
Could you send me a minimal example showing how \xmlprettyprinttext is
used and I can check how
r which were the options in t-vim, but I need the
options from \setuptyping and \setuptype.
Many thanks for your help again,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well,
=context]
\definevimtyping[lua][syntax=lua]
instead of the \setuptyping commands. If you have a lot of code snippets,
create an subdirectory called output and also set
\setupvimtyping[directory=output]
Let me know if there are any errors and I can look into it (except if the
error is related
cern with all these beta releases,
> ConText is great and for the most part easy to use, I am more worried that
> my existing ConText environment (setup) becomes broken, and/or resulting
> in complete different PDF output.
> I have no way of knowing, apart from visually inspecting a lot
including some code examples via \typefile (with a bit of text in
either Cyrillic, Chinese, Japanese or Korean)
could be achieved with a simple local font switch, or setting a regime or
via \setuptyping but not on a global level
with \definefontsynonym, definefontfallback etc.
My fix is to change
, Hans Hagen <pra...@wxs.nl> wrote:
> On 12/5/2017 11:10 PM, Wim Neimeijer wrote:
>
>> I wish it is that simple, but alas, I need to
>> to inform \typefile of the font as well,
>> possibly via setuptyping ?
>>
> if you mix scripts you need to either use font that
On 12/5/2017 11:10 PM, Wim Neimeijer wrote:
I wish it is that simple, but alas, I need to
to inform \typefile of the font as well,
possibly via setuptyping ?
if you mix scripts you need to either use font that has the glyphs or
you have to create a bodyfint with a combination of fonts ... i'm
I wish it is that simple, but alas, I need to
to inform \typefile of the font as well,
possibly via setuptyping ?
The following works with texlive 2017 (pdflatex), meaning I have the fonts
installed.
I also ran
$ mtxrun --script font --reload
\documentclass{article}
\usepackage[T1]{fontenc
s standard tags.
Using the scite module removes the three issues (XML comment chars are
in a different color, both from comment content and from any other
element). But the scite module doesn’t allow the options \setuptyping has.
Would it be possible that whole comments may be formatted in the
On 09/06/2017 12:16 AM, Hans Hagen wrote:
> On 9/5/2017 11:20 PM, Pablo Rodriguez wrote:
>>
>> Could we discuss the main issue (a broader one) after the meeting (by
>> the end of the month)?
> > depends on what the broader issue is ... supporting margin is no big
>
On 9/5/2017 11:20 PM, Pablo Rodriguez wrote:
On 09/05/2017 09:31 PM, Hans Hagen wrote:
On 9/5/2017 6:33 PM, Pablo Rodriguez wrote:
[...]
4. \setuptyping and \setuptype don’t work with the scite buffers.
well, it's a different (basically unrelated) mechanism that kicks in ...
one can't have
On 09/05/2017 09:31 PM, Hans Hagen wrote:
> On 9/5/2017 6:33 PM, Pablo Rodriguez wrote:
>> [...]
>> 4. \setuptyping and \setuptype don’t work with the scite buffers.
> well, it's a different (basically unrelated) mechanism that kicks in ...
> one can't have it all
Wei
On 9/5/2017 6:33 PM, Pablo Rodriguez wrote:
Hans,
after updating to latest beta (from 2017.09.05 15:10) to enjoy the new
none method in the scite buffers, I have the following sample:
\setupindenting[yes, always, big]
\usemodule[scite]
\setuptyping[margin=2cm]
\startbuffer
Hans,
after updating to latest beta (from 2017.09.05 15:10) to enjoy the new
none method in the scite buffers, I have the following sample:
\setupindenting[yes, always, big]
\usemodule[scite]
\setuptyping[margin=2cm]
\startbuffer[typebuffer]
| \ConTeXt\ \ConteXt \par
On 08/30/2017 02:50 AM, Aditya Mahajan wrote:
> On Tue, 29 Aug 2017, Hans Hagen wrote:
>> On 8/29/2017 9:02 PM, Pablo Rodriguez wrote:
>>> [...]
>>> In that case, what enables [lines=yes] in \setuptyping?
>> linebreaks
>
> There is only a subtle d
On 08/29/2017 11:28 PM, Hans Hagen wrote:
> On 8/29/2017 9:02 PM, Pablo Rodriguez wrote:
>> [...]
>> In that case, what enables [lines=yes] in \setuptyping?
> linebreaks
Many thanks for your reply, Hans.
I’m afraid this isn’t what I get in the following sample:
lines in the sample above?
empty lines are always collapsed
Many thanks for your reply, Hans.
In that case, what enables [lines=yes] in \setuptyping?
linebreaks
There is only a subtle difference between the two:
\setuppapersize[A6]
\showframe
\starttext
\starttyping[lines=no]
Here is some text
are always collapsed
Many thanks for your reply, Hans.
In that case, what enables [lines=yes] in \setuptyping?
linebreaks
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH
es are always collapsed
Many thanks for your reply, Hans.
In that case, what enables [lines=yes] in \setuptyping?
I need this to provide a sample in a ConTeXt introduction of empty lines
collapse in ConTeXt.
Many thanks for your
On 8/29/2017 4:43 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\setuptyping[TEX][lines=yes]
\starttext
\startTEX
code
one line before
two lines before
three lines before
\stopTEX
\stoptext
I thought the lines key should
Dear list,
I have the following sample:
\setuptyping[TEX][lines=yes]
\starttext
\startTEX
code
one line before
two lines before
three lines before
\stopTEX
\stoptext
I thought the lines key should display multiple lines when they are in
the code.
How
[scite]
\setuptyping[TEX][escape={[[,]]}]
\starttext
\startTEX
\test[[\em test]]
\stopTEX
\stoptext
The reported error is:
[ctxlua]:221: attempt to index local 'specification' (a nil value)
stack traceback:
[ctxlua]:221: in function <[ctxlua]:220>
[C]: in function 'lpegmatch'
...ext/tex
Hi,
I noticed that the scite module (m-scite.mkiv) has undergone some changes
recently. When using this module to highlight source code, then the escape
mechanism does not seem to work anymore.
MWE:
\enabletrackers[buffers.visualize]
\usemodule[scite]
\setuptyping[TEX][escape={[[,]]}]
\starttext
Dear list,
sorry for insisting, but I need to solve this.
I have to explain to newcomers (in my Spanish introduction to ConTeXt)
what comments are and multiple lines don’t affect the final PDF document.
I have the following sample:
\setuptyping[lines=yes]
\starttext
\startTEXpage
Dear list,
I have the following sample:
\setuptyping[TEX][lines=no]
\definetyping[TEXlines][lines=yes, option=TEX]
\starttext
\startxtable[frame=off,option=stretch]\startxrow
\startxcell\startTEX
\starttext
Esto
es un
único párrafo.
Y aquí está el
{Dealing with XML}
\xmlprocessbuffer{main}{demo}{}
\subject{In standard \ConTeXt}
\setuptyping[option=TEX]
\setuptype[option=TEX]
I can use colored code blocks:
\starttyping
\starttext
\ConTeXt\ is awesome!
\stoptext
\stoptyping
But I'm
ject{Dealing with XML}
\xmlprocessbuffer{main}{demo}{}
\subject{In standard \ConTeXt}
\setuptyping[option=TEX]
\setuptype[option=TEX]
I can use colored code blocks:
\starttyping
\starttext
\ConTeXt\ is awesome!
\stoptext
\stoptyping
But I'm afraid I cann
ample#1{%
> \startTEX
> #1
> \stopTEX
> #1
> }
>
> Stops with the error:
Without or without definitions, there should be no expansion inside
\starttyping...\stoptyping.
Even with some expansion, I get an infinite loop:
\starttext
\setuptyping[TEX][escape=yes]
\def\CodeEx
le[vim]
\definevimtyping
[python]
[syntax=python,
escape=on,
before={\starttextbackground[verbatim]},
after={\stoptextbackground}]
\setuptyping
[before={\starttextbackground[verbatim]},
after={\stoptextbackground}]
\starttext
\starttyping[escape=yes]
# Returns /BTEX\m{\sum_{i=1}
On Fri, 2017-06-16 at 22:53 +0200, Hans Åberg wrote:
> How does one choose font for \starttyping? It is apparently different from
> that of \tt.
No it is \tt, see buff-ver.mkiv
\setuptyping
[
%...
sty
ge you need global setups.
begin example
\setuplinenumbering
[TEX]
[location=inmargin,
style=\tt\tfx,
color=darkgreen]
\setuptyping
[TEX]
[numbering=line]
Does 'numbering=line' here mean that the \setuptyping[TEX] will search for a
line-numbering style of
yle assigned by \setuplinenumbering (but
works OK on other pages)?
It’s a side effect of the way how line numbering works. To get the
correct style for the last page you need global setups.
begin example
\setuplinenumbering
[TEX]
[location=inmargin,
style=\tt\tfx,
color=darkgreen]
\setupt
size[z]
\definebodyfontenvironment[default][z=.75]
\setuplinenumbering[location=inmargin,style={\tfz\tt},color=darkgreen,]
\setuptyping[TEX][style=\tfz,numbering=line,]
\typefile[TEX]{t3.mkiv}
\stop
\if+-
Some dummy text
Some dummy text
Some dummy text
Some dummy text
Some dumm
]
\definebodyfontenvironment[default][z=.75]
\setuplinenumbering[location=inmargin,style={\tfz\tt},color=darkgreen,]
\setuptyping[TEX][style=\tfz,numbering=line,]
\typefile[TEX]{t3.mkiv}
\stop
\if+-
Some dummy text
Some dummy text
Some dummy text
Some dummy text
Some dummy text
=no,offset=0pt]
\setuptyping[before=,after=]
\starttyping
print("Hello World!")
\stoptyping
\stopframed
}
\stoptext
On 11/08/2016 03:10 PM, Henri Menke wrote:
> Dear list,
>
> To answer this question on TeX.SX
> https://tex.stackexchange.com/questions/33813
;> The idea here is to display Unicode input files as is, so finding a
>> monospace font for all those characters may be difficult. Just changing to
>> sans did not work though.
>>
>> \setupbodyfont[xits,10pt]
>> \setuptyping[style=normal]
>>
>> \sta
would suffice. The typing environment, it seems, combines the two, and the
monospace part cannot be turned off.
The typing environment uses only a monospaced font as default style but you can
also
use it with a serif or sans serif font, e.g. \setuptyping[style=sans].
The code below works. O
uffice. The typing environment, it seems, combines the two,
>> and the monospace part cannot be turned off.
>>
> The typing environment uses only a monospaced font as default style but you
> can also
> use it with a serif or sans serif font, e.g. \setuptyping[style=sans
ospaced font as default style but
you can also
use it with a serif or sans serif font, e.g. \setuptyping[style=sans].
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wik
gt;> For files enclosure in {} for buffers in [], for files optional
>> parameters, for buffers not.
>> Is it possible to make the syntax of these two the same, because their
>> usage parallels each other?
>
> Hi Hans,
>
> I wonder whether any of these two opti
ame, because their
> usage parallels each other?
Hi Hans,
I wonder whether any of these two options may help you:
\setuptyping[buffer][style=\ttx]
\startbuffer[test]
content of buffer
\stopbuffer
\starttext
\typebuffer[test][style=\ss\red]
\typefile[style=\ttx
]
\setupcolors [state=start]
\setuptyping [option=color]
\definetyping [C][option=C, tab=4]
\definecolor [Ccomment][darkblue]
\definetyping [CPP]
[option=C,tab=2,
bodyfont=small]
\starttext
\startC
int main() { return 0; } // Comment
pacing and size of the symbols.
That is apparently not only usefull for narrower text in long lists,
but has a usefullness in other cases too.
Why should I have to use other mechanisms in order to get similar
appearance than just through a symmetry between \setuptype and
setuptyping?
\setuptyping
On 24 Feb 2016, at 13:37, Wolfgang Schuster
<schuster.wolfg...@gmail.com<mailto:schuster.wolfg...@gmail.com>> wrote:
Meer, Hans van der<mailto:h.vanderm...@uva.nl>
24. Februar 2016 um 13:25
Why does \setuptyping has a parameter bodyfont= and is \setuptype missing it?
I
Meer, Hans van der <mailto:h.vanderm...@uva.nl>
24. Februar 2016 um 13:25
Why does \setuptyping has a parameter bodyfont= and is \setuptype
missing it?
I am asking because in typesetting with
\setuptype[style=small]\type{something}
I get another font and size than with
\setuptyping[bo
Why does \setuptyping has a parameter bodyfont= and is \setuptype missing it?
I am asking because in typesetting with
\setuptype[style=small]\type{something}
I get another font and size than with
\setuptyping[bodyfont=small]\starttyping ... \stoptyping
whereas in both the same is wanted
during \typefile command?
E.g. 10 spaces...
\setuptyping[file][tab=10]
Wolfgang
--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o. | mailto:pon...@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
Procházka Lukáš Ing. - Pontex s. r. o. mailto:l...@pontex.cz
24. August 2015 13:30
Hello,
is there a way to specify width for a tabulator ('\t') being read in a
text file during \typefile command?
E.g. 10 spaces...
\setuptyping[file][tab=10]
Wolfgang
Hello,
suppose the following code:
\starttext
\starttyping
Aaa
Bbb
\stoptyping
\stoptext
It produces:
Aaa
Bbb
How to force ConTeXt not to gobble spaces after \setuptyping, to get:
Aaa
Bbb
i.e. to obey two blanksbefore Aaa?
Thank you in advance.
Best regards
On 06/07/2015 02:48 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Hello,
[..]
How to force ConTeXt not to gobble spaces after \setuptyping, to get:
[...]
i.e. to obey two blanksbefore Aaa?
Hi Lukáš,
it may be a bug, since it happens with latest beta (2015.05.24 12:42)
and beta from
\scratchbox}%
\endgroup}
\protect
\defineparagraphs[Test][n=2]
\setuptyping[numbering=line,tab=no]
\starttext
\startparagraphs[Test]
\startparagraphscell
\input ward
\starttyping
One
Two
Three
Folks,
Switching the option to “color” in \setuptyping has the effect of resetting the
font from typewriter (constant width) to paragraph font (if you uncomment it in
the following MWE).
I don’t see why that should be. Is it a bug or can someone explain?
My intent was to use syntax
Am 09.04.2015 um 14:02 schrieb robin.kirk...@csiro.au:
Folks,
Switching the option to “color” in \setuptyping has the effect of resetting
the font from typewriter (constant width) to paragraph font (if you uncomment
it in the following MWE).
I don’t see why that should
][
frame=off,
location=paragraph,
background=color,
backgroundcolor=yellow]
\setuptyping[typing][
%option=color,
before={\starttextbackground[code]},
after=\stoptextbackground]
\starttext
\startplacefigure[location=bottom]
\externalfigure[cow][width=0.5\textwidth
?
\setuptyping[TEX]
\startTEX
RSpec.describe Post, :type = :model do
end
\stopTEX
You can add a framedtext environment around the verbatim text and use
“location=middle” to center it.
\setuptyping
[TEX]
[before={\startframedtext[location=middle]},
after=\stopframedtext]
\starttext
cannot figure out how to do that. With the code below how can I
centre the whole block horizontally on the page?
\setuptyping[TEX]
\startTEX
RSpec.describe Post, :type = :model do
end
\stopTEX
You can add a framedtext environment around the verbatim text and use
“location
Hello All,
I am trying to centre a multi-line verbatim text horizontally on the page
but I cannot figure out how to do that. With the code below how can I
centre the whole block horizontally on the page?
\setuptyping[TEX]
\startTEX
RSpec.describe Post, :type = :model do
end
\stopTEX
Hi,
How do I escape to TeX from inside an inline typing command? It works fine
from a typing environment.
MWE:
\setuptyping[TEX][escape={[[,]]}]
\definetype[typeTEX][option=TEX]
\starttext
\startTEX
\I\can [[\em escape]]
\stopTEX
\typeTEX{\I\cannot [[\em escape]]}
\stoptext
Thank you for any
Am 17.02.2015 um 16:04 schrieb Christoph Reller christoph.rel...@gmail.com:
Hi,
How do I escape to TeX from inside an inline typing command? It works fine
from a typing environment.
MWE:
\setuptyping[TEX][escape={[[,]]}]
\definetype[typeTEX][option=TEX]
\starttext
\startTEX
[it]
\setupcolors[state=start]
\definepapersize[ZaffiriBook][width=130mm,height=205mm]
\setuppapersize[ZaffiriBook, portrait][ZaffiriBook, portrait]
\setuppagenumber[state=stop]
\setuppagenumbering[location={footer, margin}]
\setupindenting[yes, medium]
\setupheads[indentnext=yes]
\setuptyping
[before
]
\setuppapersize[ZaffiriBook, portrait][ZaffiriBook, portrait]
\setuppagenumber[state=stop]
\setuppagenumbering[location={footer, margin}]
\setupindenting[yes, medium]
\setupheads[indentnext=yes]
\setuptyping
[before={\setupbodyfont[6pt]},
after={\setupbodyfont[9pt]}]
Use
Hi,
How do I get rid of the additional line inserted at the end of a TEX or XML
environment?
Minimal working example:
\starttext
\setuptyping[TEX][before=,after=] % - trailing interline space
\hrule
\startTEX
\TeX
\stopTEX
\hrule
\medskip
\setuptyping[XML][before=,after=] % - trailing
Dear list
I experience weird results with latest beta (2014.05.30 23:26).
Here is the sample:
\setuppapersize[A6]
\setuptagging[state=start]
\setuptyping[margin=yes,align={right,broad}]
\starttext
\starttyping
\setuptyping[margin=yes, align={right,broad}]
\stoptyping
with the minimal sample:
\setuppapersize[A6]
\setuptagging[state=start]
\setuptyping[margin=yes,align={right,broad}]
\appendtoks
\unexpanded\def\obeyedspace{\hskip\zeropoint\char32\hskip%
\zeropoint}%
\to \everyenableelements
\starttext
\starttyping
for your reply, Hans.
I’m afraid I cannot make it work even with the minimal sample:
\setuppapersize[A6]
\setuptagging[state=start]
\setuptyping[margin=yes,align={right,broad}]
\appendtoks
\unexpanded\def\obeyedspace{\hskip\zeropoint\char32\hskip%
\zeropoint
70 \gdef\setupprettyBREAKtype%
71 {\def\prettyidentifier{BREAK}%
72\BREAKsetcounters
73\BREAKsethandlers
74\BREAKsetspecials}
75
76 \installprettytype[BREAK][BREAK]
77
78
\setuptyping[location=inmargin,option=color,numbering=line,bodyfont=small
1 - 100 of 391 matches
Mail list logo
