On 7/7/2022 6:19 PM, Pablo Rodriguez via ntg-context wrote:
Hi Hans,
many thanks for the new release.
I experience two issues with scite buffers:
\usemodule[scite]
\setuptyping[margin=yes]
\starttext
\startbuffer[b]b\stopbuffer
\startTEXpage[offset=1em]
no margin
Hi Hans,
many thanks for the new release.
I experience two issues with scite buffers:
\usemodule[scite]
\setuptyping[margin=yes]
\starttext
\startbuffer[b]b\stopbuffer
\startTEXpage[offset=1em]
no margin
a \sciteinlinebuffer[none][b] a
a \typeinlinebuffer[b][option
Dear list,
I have the following sample:
\showframe
\setuppapersize[A8]
\setuptyping
[align={right,broad},
strip=yes,
lines=yes,
blank=halfline]
\starttext
\startXML
content content content content
content content
content content
:
>
> \usemodule[scite]
> \setuptyping[margin=yes]
> \starttext
> \startbuffer[b]b\stopbuffer
> \startTEXpage[offset=1em]
> a \sciteinlinebuffer[none][b] a\par
> a \typeinlinebuffer[b][option] a
> \stopTEXpage
> \stoptext
>
> I’m on Linux64 and using curre
Dear list,
I have my third sample with scite:
\usemodule[scite]
\setuptyping[margin=yes]
\starttext
\startbuffer[b]b\stopbuffer
\startTEXpage[offset=1em]
a \sciteinlinebuffer[none][b] a\par
a \typeinlinebuffer[b][option] a
\stopTEXpage
\stoptext
I’m on Linux64 and using
On Sat, 1 Jan 2022 11:04:03 +0100
Hans Hagen wrote:
> quick and dirty
>
> \setuptyping[style={\definedfont[Mono*malayalam-two]}]
>
> \starttyping
> മലയാളലിപികളുടെ ആവൃത്തി നിർണ്ണയം
> \stoptyping
That was a quick fix. Yes, it is working.
> If the need for features i
the command pair \starttyping \stoptyping,
conjuncts are not formed as outside the command pair. Is it possible to
enforce [features=malayalam-two] even inside \starttyping \stoptyping
command pair?
quick and dirty
\setuptyping[style={\definedfont[Mono*malayalam-two]}]
\starttyping
മലയാളലിപികളുടെ
[mainface][mono][courier]
\definefontfamily [mainface][math][stix]
\setupbodyfont[mainface,10pt]
\setmathfontalternate{upright}
\setupmathematics[integral=nolimits, lcgreek=normal, default=normal]
\setupformulae[location=left, indentnext=auto]
\setuptyping[indentnext=auto]
% Might use
ce][serif][stix]
\definefontfamily [mainface][mono][courier]
\definefontfamily [mainface][math][stix]
\setupbodyfont[mainface,10pt]
\setmathfontalternate{upright}
\setupmathematics[integral=nolimits, lcgreek=normal, default=normal]
\setupformulae[location=left, indentnext=au
Note the presence of double-spaced blank lines in the following document
and in the attached source file:
\setuptyping[numbering=line]
\starttext
\startbuffer[javacode]
try {
final var num = stack.pop();
if( num != null ) {
stack.push( blah );
}
return true;
}
\stopbuffer
\type
Sylvain Hubert via ntg-context schrieb am 07.09.2021 um 11:49:
Dear List,
How should we remove the vertical space above and below the following typing?
\starttext
Remove space below
\starttyping
some
code
\stoptyping
\stoptext
\setuptyping [before=,after=]
Wolfgang
in on the new page.
>> It doesn’t happen with \start/stoplinenumbering.
>> MWE:
>> \setuptyping[
>> numbering=file,
>> ]
>
> \setuptyping[numbering=line]
Ah, thank you! (Wolfgang too!)
I can’t remember why I chose "file", and looking at the source als
Henning Hraban Ramm via ntg-context schrieb am 01.09.2021 um 18:01:
Hi again,
if a "typing" environment with line numbering goes over a page break, the line
numbers start at 1 again on the new page.
It doesn’t happen with \start/stoplinenumbering.
MWE:
\setuptyping[
numb
On 9/1/2021 6:01 PM, Henning Hraban Ramm via ntg-context wrote:
Hi again,
if a "typing" environment with line numbering goes over a page break, the line
numbers start at 1 again on the new page.
It doesn’t happen with \start/stoplinenumbering.
MWE:
\setuptyping[
numb
Hi again,
if a "typing" environment with line numbering goes over a page break, the line
numbers start at 1 again on the new page.
It doesn’t happen with \start/stoplinenumbering.
MWE:
\setuptyping[
numbering=file,
]
\setuppaper[A5]
\setupbodyfont[18pt]
\starttext
\startbuffer
tion]
[page={yes}]
\usetypescript[pagella]
\setupbodyfont[pagella,18pt]
\setupbodyfontenvironment[
28pt][ % For body
d=36pt, % For title
a=12pt, % For author & date
]
\setuptype[style=medium]
\setuptyping[typing][bodyfont=16pt]
\setupwhitespace[medium]
\setbreakpoints[compound]
\se
dium]
\setuptyping[typing][bodyfont=16pt]
\setupwhitespace[medium]
\setbreakpoints[compound]
\setuphead[chapter][style=\bfd]
\setuphead[section][style=\bfc]
\setuphead[subsection][style=\bfb]
\setuphead[subsubsection][style=\bf]
\setupitemize[autointro] % prevent orphan list intro
\setupitemize[indent
not seem to work
\setupcolors[state=start]
\setupcolor[xwi]
\definetextbackground
[Code]
[frame=on,
framecolor=black,
%corner=0,
%offset=10pt,
background=color,
backgroundcolor=gray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code
]
\definetextbackground
[Code]
[frame=on,
framecolor=black,
%corner=0,
%offset=10pt,
background=color,
backgroundcolor=gray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
=on,
framecolor=black,
%corner=0,
%offset=10pt,
background=color,
backgroundcolor=gray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
example
\stoptyping
\stoptext
> On 28 Jul 2021, at 13:13, Jeroen via ntg-context wrote:
>
> Is there a way to have two different styles of typing. I tried the following,
> but it does not seem to work.
>
> \setuptyping[abc][style=\ttx]
> \setuptyping[def][style=\ttxx]
>
> \starttext
>
> Am 28.07.2021 um 14:14 schrieb Jeroen via ntg-context :
>
> Is there a way to have two different types of typing. I tried the following,
> but it does not seem to work.
>
> \setuptyping[abc][style=\ttx]
> \setuptyping[def][style=\ttxx]
>
> \starttext
>
>
On 7/28/2021 2:14 PM, Jeroen via ntg-context wrote:
Is there a way to have two different types of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
text
text
\stoptyping
\starttyping[def
Is there a way to have two different types of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
text
text
\stoptyping
\starttyping[def]
text
text
\stoptyping
\stoptext
Is there a way to have two different styles of typing. I tried the
following, but it does not seem to work.
\setuptyping[abc][style=\ttx]
\setuptyping[def][style=\ttxx]
\starttext
\starttyping[abc]
example
example
\stoptyping
\starttyping[def]
example
example
\stoptyping
\stoptext
Thanks
ound=color,
> > backgroundcolor=lightgray,
> > location=paragraph,
> > before=\blank,
> > after=\blank]
> >
> > \setuptyping
> > [CPP]
> > [before=\startCodeBackground,
> > after=\stopCodeBackgr
26 15:41).
>
> \usemodule[scite]
>
> \definetextbackground
> [CodeBackground]
> [ frame=off,
> background=color,
> backgroundcolor=lightgray,
> location=paragraph,
> before=\blank,
> after=\blank]
>
> \setuptyp
=paragraph,
before=\blank,
after=\blank]
\setuptyping
[CPP]
[before=\startCodeBackground,
after=\stopCodeBackground]
\starttext
\samplefile{ward}
\startCPP
#include
int main(void)
{
printf("hello, world\n");
}
\stopCPP
\samplefile{weisman}
\stoptext
t; >
> > Why do pass a option for the typing environment to \starttext?
> >
> > > \definetextbackground[code][background=color, backgroundcolor=lightgray,
> > > frame=off, location=paragraph]
> > >
> > > \setuptyping[before={\startbackground[code]}
gt; > \definetextbackground[code][background=color, backgroundcolor=lightgray,
> > frame=off, location=paragraph]
> >
> > \setuptyping[before={\startbackground[code]}, after={\stopbackground}]
> >
> > \starttext[option=XML]
> > \starttyping
> > This is s
=paragraph]
\setuptyping[before={\startbackground[code]}, after={\stopbackground}]
\starttext[option=XML]
\starttyping
This is some code
a second line
\stoptyping
\stoptext
When I use \definetyping[Mytyping][option=XML] and then use \startMytyping ...
\stopMytyping nothing changes
; > > > > \starttextbackground[code]
> > > > > \starttyping
> > > > > This is some code
> > > > > a second line
> > > > > \stoptyping
> > > > > \stoptextbackground
> > > > You missed the W (working) in
ckground[code][background=color, backgroundcolor=lightgray,
> > > > frame=off, location=paragraph]
> > > >
> > > > \starttextbackground[code]
> > > > \starttyping
> > > > This is some code
> > > > a second line
> > > > \stoptyping
a second line
\stoptyping
\stoptextbackground
You missed the W (working) in MWE.
\definetextbackground
[Code]
[ frame=off,
background=color,
backgroundcolor=lightgray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code
optextbackground
>
> You missed the W (working) in MWE.
>
> \definetextbackground
> [Code]
> [ frame=off,
> background=color,
> backgroundcolor=lightgray,
> location=paragraph]
>
> \setuptyping
> [before={\blank\starttextbackground[Cod
[Code]
[ frame=off,
background=color,
backgroundcolor=lightgray,
location=paragraph]
\setuptyping
[before={\blank\starttextbackground[Code]},
after={\stoptextbackground\blank}]
\starttext
\starttyping
This is some code
a second line
\stoptyping
\stoptext
> \starttextbackground[code]
> \starttyping
> This is some code
> a second line
> \stoptyping
> \stoptextbackground
\definetextbackground[code][background=color, backgroundcolor=lightgray,
frame=off, location=paragraph]
\setuptyping[before={\startbackground[code]},
> whatever
> >
> > LMTX output:
> > whatever
> >
> > Is there a way to get the old MKIV behavior back?
>
> \setuptyping[LUA][strip=yes]
Thank you, Wolfgang!
___
If your question is of inte
processing the verbatim text:
MKIV output:
whatever
LMTX output:
whatever
Is there a way to get the old MKIV behavior back?
\setuptyping[LUA][strip=yes]
Wolfgang
___
If your question is of interest to othe
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
1 - 100 of 423 matches
Mail list logo
