Gerben Wierda via ntg-context schrieb am 29.05.2023 um 16:19:
If I do something like:
\startbuffer[version]20230529a\stopbuffer
Version: \getbuffer[version]-en
I get whitespace between the content of the buffer and “-en”
What is the proper LMTX way to do this?
You need the \inlinebuffer
If I do something like:
\startbuffer[version]20230529a\stopbuffer
Version: \getbuffer[version]-en
I get whitespace between the content of the buffer and “-en”
What is the proper LMTX way to do this?
Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>)
R&A Enterprise Ar
> On 11 Feb 2018, at 14:17, Aditya Mahajan wrote:
>
> On Sun, 11 Feb 2018, Hans Hagen wrote:
> […]
>
> I prefer starting with XML and converting it to a lua table using helper
> functions. The advantage of XML is that you can verify the data using an RNC
> schema.
Hi Aditya,
Thanks for you
On 2/11/2018 2:17 PM, Aditya Mahajan wrote:
On Sun, 11 Feb 2018, Hans Hagen wrote:
Think different ... see end.
\startluacode
document.speakerdata = {
{
speakername = "Gauss",
title = "Remarks on Number Theory",
time = "8am",
On Sun, 11 Feb 2018, Hans Hagen wrote:
Think different ... see end.
\startluacode
document.speakerdata = {
{
speakername = "Gauss",
title = "Remarks on Number Theory",
time= "8am",
room= "B",
day
{talk}{day}, at
\getvariable{talk}{time} \NC\NR
\HL
\stoptabulate
}
}
\starttext
\starttitle[title={Monday talks}]
\setvariable{talk}{set}{\talksofday{Monday}}
\getbuffer[talkdata]
\stoptitle
\page
\starttitle[title={Tuesday talks}]
\setvariable
\getbuffer command for each of the different uses
in my global document.
For now, unfortunately, I cannot come up with a minimal example because the
question I am asking is about a real situation where nothing is minimal. That
is why I am asking a general abstract question to understand the general
On 3/28/2015 1:50 AM, Rik Kabel wrote:
The behavior of \getbuffer has changed with the new beta. With the
following sample code, one line of text is produced with the 2015-03-25
beta. Two lines of text are produced with the more recent betas.
\startbuffer
A
\stopbuffer
On Fri, 27 Mar 2015 20:50:52 -0400
Rik Kabel wrote:
> The behavior of \getbuffer has changed with the new beta. With the
> following sample code, one line of text is produced with the
> 2015-03-25 beta. Two lines of text are produced with the more recent
> betas.
>
> \s
The behavior of \getbuffer has changed with the new beta. With the
following sample code, one line of text is produced with the 2015-03-25
beta. Two lines of text are produced with the more recent betas.
\startbuffer
A
\stopbuffer
\starttext
A \getbuffer
\stoptext
--
rik
tbuffer[my:xtable]
>> \startxtable[option=stretch]
>> \startxrow
>> \startxcell alpha \stopxcell
>> \startxcell beta \stopxcell
>> \startxcell gamma \stopxcell
>> \stopxrow
>> \stopxtable
>> \stopbuffer
>>
>> \getbuffer[my:
\stopxcell
\startxcell gamma \stopxcell
\stopxrow
\stopxtable
\stopbuffer
\getbuffer[my:xtable]\blank
\processxtablebuffer[my:xtable]
\stoptext
fixed in next beta but no nesting of xtables ... too much coding and it
would nil the advantage (if there is any) anyway
Hans
\stopxrow
\stopxtable
\stopbuffer
\getbuffer[my:xtable]\blank
\processxtablebuffer[my:xtable]
\stoptext
Regards
Andreas
___
If your question is of interest to others as well, please add an entry to the
Wiki
l.20 \setlayer[FOO]{\getbuffer[FOO]}
?
! Emergency stop.
\endgroup
\vskip
\stopblankhandling ...ional \someblankdone \vskip
\blankskip \fi
\endgroup
l.3 \stopblankhan
\someblankdone \vskip
\blankskip \fi \endgroup
l.3 \stopblankhandling
\dovspacing ...argument #1\else \s!default \fi ")}
\leavevmode
l.20 \setlayer[FOO]{\getb
\blankskip \fi \endgroup
l.3 \stopblankhandling
\dovspacing ...argument #1\else \s!default \fi ")}
\leavevmode
...
l.20 \setlayer[FOO]{\getbuffe
Wolfgang Schuster wrote:
> Hi Hans,
>
> The definition for \getBUFFER need to be changed because it use the undefined
> command \dodoprocessTEXbuffer.
>
> \def\dodefinebuffer[#1][#2]%
> {\iffirstargument % else problems
> \doglobal\increment\nofdefinedbuffers
&g
Hi Hans,
The definition for \getBUFFER need to be changed because it use the undefined
command \dodoprocessTEXbuffer.
\def\dodefinebuffer[#1][#2]%
{\iffirstargument % else problems
\doglobal\increment\nofdefinedbuffers
\letvalue{\??bu#1\c!number }\nofdefinedbuffers
\letvalue
was in an article I submitted for NTG-MAPS
> a while ago, july 2007). Now this same code gives an error on getbuffer.
> What happened to getbuffer? Is it possible a \fi has disappeared in
> the getbuffer code between now and last july? Is there a quick patch
> because now I get stuck o
I had this code working (it was in an article I submitted for NTG-MAPS
a while ago, july 2007). Now this same code gives an error on getbuffer.
What happened to getbuffer? Is it possible a \fi has disappeared in
the getbuffer code between now and last july? Is there a quick patch
because now
On Wed, 11 Apr 2007, Wolfgang Schuster wrote:
> 2007/4/11, Aditya Mahajan <[EMAIL PROTECTED]>:
>>
>> On Thu, 22 Mar 2007, Taco Hoekwater wrote:
>>
>> > Wolfgang Werners-Lucchini wrote:
>> >> Hallo!
>> >>
>> >> The following simple example doesn't compile
>> >> (ConTeXt ver. 2007.01.02 and Live C
>> On Thu, 22 Mar 2007, Taco Hoekwater wrote:
>>
>> > Diagnostics:
>> >
>> > The problem is not caused by the \framed, but by the (lack of)
>> > parsing done by the buffering routines.
>> > Because the \startformula is not expanded, TeX does not realise
>> > you are in math mode, so it objects to t
th=5cm,height=4cm]
{\startformula
x^2 = x\cdot x
\stopformula}
This solution works also in combination with a buffer
\startbuffer
\startformula
x^2 = x\cdot x
\stopformula
\stopbuffer
\framed[width=6cm,height=4cm]{\getbuffer}
Wolfgang
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
> This is a serious bug. Even a simple example fails with the same
> error.
>
> \starttext
> \framed{
> \startformula
> x^2 = x\cdot x
> \stopformula}
> \stoptext
>
> A quick workaround is to use frametext instead of framed, but I am
> pretty sure that the above example used to work at some stage.
On Thu, 22 Mar 2007, Taco Hoekwater wrote:
> Wolfgang Werners-Lucchini wrote:
>> Hallo!
>>
>> The following simple example doesn't compile
>> (ConTeXt ver. 2007.01.02 and Live ConTeXt).
>>
>> What am I doing wrong?
>
> Diagnostics:
>
> The problem is not caused by the \framed, but by the (lack of)
Wolfgang Werners-Lucchini wrote:
> Hallo!
>
> The following simple example doesn't compile
> (ConTeXt ver. 2007.01.02 and Live ConTeXt).
>
> What am I doing wrong?
Diagnostics:
The problem is not caused by the \framed, but by the (lack of)
parsing done by the buffering routines.
Because the \st
Hallo!
The following simple example doesn't compile
(ConTeXt ver. 2007.01.02 and Live ConTeXt).
What am I doing wrong?
\starttext
\startbuffer
\startformula
x^2 = x\cdot x
\stopformula
\stopbuffer
\framed{\getbuffer}
\stoptext
Wolfgang
__
David Arnold wrote:
Then you do:
\getbuffer
will the setup be in a group, and only pertain to the stuff set with
\getbuffer?
No, normally they will live on (buffers often contain definitions).
But you can use
\setupbuffer[before=\begingroup,after=\endgroup]
Cheers, taco
All,
If you do something like:
\startbuffer
\setupYadaYada
.
.
.
.
\stopbuffer
Then you do:
\getbuffer
will the setup be in a group, and only pertain to the stuff set with
\getbuffer?
___
ntg-context mailing list
ntg-context@ntg.nl
http
; \bTR
>\bTD data1 \eTD
>\bTD data2 \eTD
> \eTR
> \eTABLE
> \stopbuffer
>
> \typebuffer
>
> \getbuffer
>
> \stoptext
>
Oh, works well.
Thank you a lot,
Regards,
Q.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
VnPenguin wrote:
Hi all,
I have a following code:
--
\startbuffer
\bTABLE
\bTR
\bTH title1 \eTH
\bTH title2 \eTH
\eTR
\bTR
\bTD data1 \eTD
\bTD data2 \eTD
\eTR
\eTABLE
\stopbuffer
\startTEX
\getbuffer
\stopTEX
\getbuffer
Hi all,
I have a following code:
--
\startbuffer
\bTABLE
\bTR
\bTH title1 \eTH
\bTH title2 \eTH
\eTR
\bTR
\bTD data1 \eTD
\bTD data2 \eTD
\eTR
\eTABLE
\stopbuffer
\startTEX
\getbuffer
\stopTEX
\getbuffer
32 matches
Mail list logo
