On 2/15/20 9:16 PM, Henning Hraban Ramm wrote:
> I guess I’m stupid.
> I’d like to have my chapter title in the header on right pages, but
> not on the first page of a chapter, that always is a right page.
> Since I’d like to keep the page number in the header on these pages,
> I can’t use header=
On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
best use \smallcaps or somethign equivalent
---
On 2/15/2020 12:25 PM, Fabrice Couvreur wrote:
Hi Henri,
Why does the blue path not rotate 90 with the draw command but rotate
with the fill command?
compare
draw origin -- (0,0.2cm) -- (4cm,0.2cm) -- (4cm,0) --
(4.1cm,-0.05cm) -- (0.1cm,-0.05cm) -- cycle rotated alpha withcolor red;
I guess I’m stupid.
I’d like to have my chapter title in the header on right pages, but not on the
first page of a chapter, that always is a right page.
Since I’d like to keep the page number in the header on these pages, I can’t
use header=empty.
What’s the right setup for me?
(In the MWE there
Hi,
One can easily enable small caps when using lucida, see the old mail
https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
Could this be added to the type script file?
/Mikael
___
If your question is of
On Sat, 15 Feb 2020, Floris van Manen wrote:
On 15-02-2020 06:40, Rudolf Bahr wrote:
I hope this helps you! At least in the case you're using linux.
it appears as that many of the files in the two path are sort of identical:
~/data/context
$ md5sum bin/mtxrun tex/texmf-linux-64/bin/luametat
> Hi Luca,
>
> > 1) always writing the full path of the correct executable,
>
> I don't know which operating system you're using. On linux instead of
> writing
> the full path I'm using the command "alias" in my ".bashrc" file. So,
> Adityas
> proposal on mtxrun (Date: Wed, 12 Feb 2020 00:24:21 -05
Thank you Aditya,
> My question is then how
> > do you usually run mtxrun:
> > 1) always writing the full path of the correct executable,
> > 2) avoid putting [lmtx path]/bin in PATH,
> > 3) putting [lmtx path]/bin _after_ [lmtx path]/tex/texmf-linux-64/bin in
> > the PATH
> >
>
> I always follow
\structureuservariable – this is really cool.
Thanks a lot Wolfgang.
juh
Am 14.02.20 um 19:53 schrieb Wolfgang Schuster:
> \setupexternalfigures[location=default]
>
> \defineoverlay
> [SlideBackground]
> [\doifsomething
> {\structureuservariable{background}}
> {\externalfigure[\str
On 15-02-2020 12:25, Fabrice Couvreur wrote:
> Hi Henri,
> Why does the blue path not rotate 90 with the draw command but rotate
> with the fill command?
>
Why not draw the match as a picture first, then rotate and shift that
picture?
Also, if you use a local scale unit, it will be easier to st
On 15-02-2020 06:40, Rudolf Bahr wrote:
> I hope this helps you! At least in the case you're using linux.
it appears as that many of the files in the two path are sort of identical:
~/data/context
$ md5sum bin/mtxrun tex/texmf-linux-64/bin/luametatex
b95ca64fabcb3f09edd861c4b87671cc bin/mtxru
Hi Henri,
Why does the blue path not rotate 90 with the draw command but rotate with
the fill command ?
\startMPcode
def match (expr alpha, pos) =
fill unitsquare xscaled 4cm yscaled 0.2cm rotated alpha shifted pos
withcolor yellow ;
fill origin -- (4cm,0) -- (4.1cm,-0.05cm) -- (0
12 matches
Mail list logo