need syntax highlighting
My problem is solved using manual zero width spaces at the moment but
I'd be interested to find a more structural solution.
Checking at the Context source code I would have thought that
breakpoints were possible withing typing env. See
https://source.contextgarden.net
Hello,
is there a way to preserve empty lines in typing env?
By default it is removing them.
Thanks
* * *
\definetyping[custom]
\setuptyping[custom][
space=normal,
lines=yes,
tab=4,
]
\starttext
\startcustom
Foo
Bar
Baz
\stopcustom
\stoptext
That works Hans, thank you.
line 802 in core-env should be:
>
> \permanent\tolerant\protected\def\setupenv
>{\syst_variables_set\getrawparameters[\s!environment]}
>
> (seems i forgot that one when doing some cl
ror on line 13 in file : Use of \getrawparameters
doesn't match its definition
mtx-context | fatal error: return code: 1
This was working with the previous release.
line 802 in core-env should be:
\permanent\tolerant\protected\def\setupenv
{\syst_variables_set\getrawparameters[\s!environm
I've used the following without any troubles for a few years now:
$ cat ~/bin/fontcache
#!/usr/bin/env bash
fc-cache -fv
mtxrun --generate
mtxrun --script fonts --reload
___
If your question is of interest to others
On Tue, Apr 11, 2023 at 05:57:30PM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 3:13 PM, Carlos via ntg-context wrote:
>
> > But where is actually luametatex under the standalone sources
> just in the bin path
thanks Hans.
Didn't have the time to look at et . Looking at a small
On 4/11/2023 3:13 PM, Carlos via ntg-context wrote:
But where is actually luametatex under the standalone sources
just in the bin path
Hans
-
Hans Hagen | PRAGMA ADE
On Tue, Apr 11, 2023 at 12:20:32PM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 12:00 PM, Carlos via ntg-context wrote:
>
> > and belongs to TeX Live?
>
> well, i suppose there is a non-empty copy in texlive but an empty one can go
> indeed
>
> > > > Here we go! Back to point A where
On Tue, Apr 11, 2023 at 12:20:32PM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 12:00 PM, Carlos via ntg-context wrote:
>
> > and belongs to TeX Live?
>
> well, i suppose there is a non-empty copy in texlive but an empty one can go
> indeed
>
> > > > Here we go! Back to point A where
On 4/11/2023 12:00 PM, Carlos via ntg-context wrote:
and belongs to TeX Live?
well, i suppose there is a non-empty copy in texlive but an empty one
can go indeed
Here we go! Back to point A where we were at before
as alan pointed out: just install with the lmtx installer in a path
On Tue, Apr 11, 2023 at 11:23:45AM +0200, Hans Hagen via ntg-context wrote:
> On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
>
> > Hello Alan, my PATH is set to:
> >
> >
On 4/11/2023 11:11 AM, Carlos via ntg-context wrote:
Hello Alan, my PATH is set to:
PATH=/home/ce/context-install/bin:/home/ce/context-install/tex/texmf-linux-64/bin:/opt/texlive/2023/bin/x86_64-linux:$PATH;
export PATH
what is that first path doing there
Do we actually need to list all
On Mon, Apr 10, 2023 at 10:01:55PM -0600, Alan Braslau via ntg-context wrote:
> On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
> Aditya Mahajan via ntg-context wrote:
>
> > Did you source the `setuptex` script, which sets the correct path.
>
> My PATH is set to
>
--generate it returned
/usr/bin/env texlua no such file or directory
So I thought heck, perhaps by creating a symbolic link we'll call it
a day, but that wasn't enough, nope.
That # line will go away or change because per 2023 we assume that the
script is run by luametatex and we're in a sort
Hi Carlos,
I think that you may be installing the old ConTeXt MkIV distribution
instead of the new ConTeXt LMTX. ConTeXt LMTX doesn't distribute
"texlua" at all, and running
"./install --modules=all" doesn't make sense with LMTX (since the
installer can't install modules).
From what link did
On Mon, 10 Apr 2023 20:51:58 -0400 (EDT)
Aditya Mahajan via ntg-context wrote:
> Did you source the `setuptex` script, which sets the correct path.
My PATH is set to
PATH=./context/tex/texmf-freebsd-amd64/bin:/home/MyAccount/context/tex/texmf-freebsd-amd64/bin:...
If my current working
e a
> > few things that don't add up or I can't seem to add them up :).
> >
> > first, while I was trying to mtxrun --generate it returned
> >
> > /usr/bin/env texlua no such file or directory
> >
> > So I thought heck, perhaps by creating a symboli
e a
> > few things that don't add up or I can't seem to add them up :).
> >
> > first, while I was trying to mtxrun --generate it returned
> >
> > /usr/bin/env texlua no such file or directory
> >
> > So I thought heck, perhaps by creating a symboli
e a
> > few things that don't add up or I can't seem to add them up :).
> >
> > first, while I was trying to mtxrun --generate it returned
> >
> > /usr/bin/env texlua no such file or directory
> >
> > So I thought heck, perhaps by creating a symboli
le I was trying to mtxrun --generate it returned
>
> /usr/bin/env texlua no such file or directory
>
> So I thought heck, perhaps by creating a symbolic link we'll call it
> a day, but that wasn't enough, nope.
>
> This is is circa 21st century ladies and gentlemen!
>
> s
I'm just following some of the standalone installation instructions
as per the wiki alongside a TeX Live installation, but there are a
few things that don't add up or I can't seem to add them up :).
first, while I was trying to mtxrun --generate it returned
/usr/bin/env texlua no such file
macro
4/ gui_v04.ods
LibreOffice Calc as interface for user
=====
examples of output env files are attached.
\setuplayout
[
backspace=37mm,
width=136mm,
topspace=12mm,
height=27
n
:) depending how one looks at it.
> > Is LuaLaTeX behaving the same way?
> >
> > Answer: no.
>
> no surprise because it doesn't use the same setup
>
> what cache path does
>
> mtxrun --variables
>
> report
mtxrun --variables
resolvers
correctly. I figured
> this by running `mtxrun --variables`. Here is a little excerpt:
>
> resolvers | lists | TEXMF
> resolvers | lists | env:
> {$TEXMFCONFIG,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFPROJECT,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFDI
yway, selfautoparent seems not to be resolved correctly. I figured
this by running `mtxrun --variables`. Here is a little excerpt:
resolvers | lists | TEXMF
resolvers | lists | env:
{$TEXMFCONFIG,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFPROJECT,!!$TEXM
nce this from the command line? Does it
> work the other way around, so with “—mode=en”?
Hi Gerben,
I think this may do the trick:
\doiftext{\env{ml}}
{\mainlanguage[\env{ml}]}
\starttext
Document main language:
\startmodeset
[**en] {English}
[**es] {Spanish}
uot;OpenSansEmoji.ttf" is the one to be installed.
> $ context --version
> mtx-context | current version: 2022.04.01 09:37
>
> $ cat ~/bin/fontcache
> #!/usr/bin/env bash
>
> fc-cache -fv
> mtxrun --generate
> mtxrun --script fonts --reload
I had problems in the past w
Appreciated, Pablo.
The output remains unjustified:
https://i.ibb.co/dM9LFWZ/future-human.png
$ find /usr/share/fonts/ -name "*Emoj*"
/usr/share/fonts/emoji/OpenSansEmoji.otf
$ context --version
mtx-context | current version: 2022.04.01 09:37
$ cat ~/bin/fontcache
#!/usr/bin/en
lready provides a blockquote-environment which can be
> configured to have the same style as your custom environment.
Hi Wolfgang,
I have a related question:
I noticed that the font settings were wrong in the original MWE of Michael. I
am also aware that ConTeXt has a blockquote env (having used it be
colors, fonts, page sizes to more specific things like doubleside-
> headers-footers, singleside-headers-footers to product specific things like
> env-
> factsheet for things that are special to factsheets only.
>
> Here are some of my environment files:
>
> hs.env-2-seiter-din
ink that all this will end up in 20-30 environment files going from
general things like colors, fonts, page sizes to more specific things
like doubleside-headers-footers, singleside-headers-footers to product
specific things like env-factsheet for things that are special to
factsheets only.
Here are some of my
gt; > > > > The TeXlive documentation says that ConTeXt uses TEXMFCACHE,
> > > > > which uses the default $TEXMFSYSVAR;$TEXMFVAR in my texmf.cnf.
> > > > > My TEXMFSYSVAR is /var/opt/texlive, but ConTeXt doesn't use it.
> > >
> > hm, my
> > $&
EXMFSYSVAR;$TEXMFVAR in my texmf.cnf.
> > > > My TEXMFSYSVAR is /var/opt/texlive, but ConTeXt doesn't use it.
> >
> hm, my
> $> mtxrun --variables
> says
> resolvers | lists | TEXMFCACHE
> resolvers | lists | env: unset
> resolvers | lists
Live
> installer. I built the binaries from their sources and then installed
> the rest from the texmf archive file. I use other engines on a daily basis,
> mostly pdflatex, and they work flawlessly.
>
> Thanks, Rainer
>
>
hm, my
$> mtxrun --variables
,small]\setupinterlinespace},
before={\blank[white,small]\startcodebkg}, % a bit of extra space
after={\stopcodebkg},
directory=vimout/, % note: you must create this folder yourself!
]
\starttext
\startvimR
#!/usr/bin/env R
included_aa <- list(
`6d1t` = 2
"
in order to
- help the reader to tidy up concepts / ideas
- deal with the markup (part 2) in as few as possible pages
- <60 pages
- one topic = 1 or 2 pages
- no
- prepare user to use env files
- limit digression as much as possible
2/ clearly split "main f
"
in order to
- help the reader to tidy up concepts / ideas
- deal with the markup (part 2) in as few as possible pages
- <60 pages
- one topic = 1 or 2 pages
- no
- prepare user to use env files
- limit digression as much as possible
2/ clearly split "main f
On Thu, 24 Jun 2021 23:30:00 +0200
Hans Hagen wrote:
> -- on freebsd always (does anyone know an env var?)
On FreeBSD, there is `uname -m` but also `hostname`.
I find the environment variable $HOST to be set, but I am not sure that
this is done by default (for standard installations).
A
> > > uname -m rb
> > > > hm, that is a real last resort attempt to determine
> what
> > > system it is
> > > > running on (we try to avoid such calls)
> > > >
> > > > -- on l
sort attempt to determine what
> system it is
> > running on (we try to avoid such calls)
> >
> > -- on linux if HOSTNAME is not known (did that change?)
> > -- on sunos always (does anyone know an env var?)
>
ort attempt to determine what
> > system it is
> > > running on (we try to avoid such calls)
> > >
> > > -- on linux if HOSTNAME is not known (did that change?)
> > > -- on sunos always (does anyone know an env var?)
> &
> > -- on linux if HOSTNAME is not known (did that change?)
> > -- on sunos always (does anyone know an env var?)
> > -- on freebsd always (does anyone know an env var?)
> >
> >
> > Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any important
such calls)
>
> -- on linux if HOSTNAME is not known (did that change?)
> -- on sunos always (does anyone know an env var?)
> -- on freebsd always (does anyone know an env var?)
>
>
Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any important
changes on the OS. In
On 6/24/2021 11:20 PM, Jairo A. del Rio wrote:
It prints:
uname -m rb
hm, that is a real last resort attempt to determine what system it is
running on (we try to avoid such calls)
-- on linux if HOSTNAME is not known (did that change?)
-- on sunos always (does anyone know an env var
Hi all,
in my document I have to set a long path to my environment files:
\environment ../../../hs.pub.context/env-fonts
I wonder if I can use the option --path to set hs.pub.context as input
folder to look for environment files.
But I have no idea how to pass a "list" to this option
Hi, Wolgang—
The mwe files in a product/component structure are attached.
Everything works as desired with the current env file.
If one comments out the startsetups...\stopsetups, the guillemets are not
properly spaced in the body text, while those in the footnote are fine.
If one comments out
][setups=test] is in the
component file.
Is this expected behavior?
(Before I just \setcharacterspacing[test] in the env file but now it
only works when in the component file)
Can you make a simple example, it's possible there is a reset somewhere
which disables the feature at the end
.
Is this expected behavior?
(Before I just \setcharacterspacing[test] in the env file but now it only
works when in the component file)
Alan
On Mon, May 17, 2021 at 3:11 PM Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:
> Alan Bowen schrieb am 17.05.2021 um 20:57:
> > Wol
t;https://github.com/DaveJarvis/keenwrite;
url
"https://github.com/DaveJarvis/keenwrite/releases/download/2.0.0/keenwrite.jar;
version "2.0.0"
sha256 "259743af0728502e89abac043973ef5c213573183ba71ba93accb2a330f0e7a8"
head "https://github.com/DaveJarvis/keenwrite.git;
def i
builder.directory( mDirectory.toFile() );
final var cacheDir = getCacheDir();
final var env = builder.environment();
env.put( "TEXMFCACHE", cacheDir.toString() );
builder.redirectOutput( DISCARD );
builder.redirectError( DISCARD );
final var proces
]
[3mm]
\stopmode\startenvironment env-colors
%% Hostsharing corporate colors
%% Für RGB-Medien wie zum Beispiel Präsentationen
%% definieren wir RGB-Farben.
%% Wenn context ohne mode=fogra39 und ohne mode=isocoated aufgerufen wird,
%% werden diese RGB-Farben benutzt.
\startnotmode[fogra39,is
ds more consistent.
OTOH I can understand you don’t want to bloat your module.
> Another option is to write the external files as valid tex file (i.e., with a
> \startTEXpage .. \stopTEXpage wrapper), and when defining the filtercommand,
> use something like `context --environment=env fi
nd after filters while processing
external files. Another option is to write the external files as valid tex file
(i.e., with a \startTEXpage .. \stopTEXpage wrapper), and when defining the
filtercommand, use something like `context --environment=env filename`, where
env is the environment file
\operatingsystem \NC\NR
>>> \stoptabulate
>>> \stoptext
>> On MacOS 10.13 the result of \operatingsystem is „osx-ppc“.
>> That was a surprise:-)
> maybe apples are no longer apples
They lost the Power when they became Intelligent, and now they get ARMed.
&
\outputfilename\NC\NR
\NC \type{\operatingsystem} \NC \operatingsystem \NC\NR
\stoptabulate
\stoptext
On MacOS 10.13 the result of \operatingsystem is „osx-ppc“.
That was a surprise:-)
maybe apples are no longer apples
because we cannot check for some env variable directly (at least we
could
On 07/11/2020 13:11, Pablo Rodriguez wrote:
echo "" && curl -Ihttp://pragma-ade.com/context/latest/cont-tmf.zip
2>&1 | grep Last-Modified && echo ""
So you don’t mix access time with last modification.
this seems to work:
#!/usr/bin/env bash
cd
this is my script for a daily update check which seems to do the job
#!/usr/bin/env bash
cd ~/context
context --version | grep "current version"
echo ""
mtxrun --script cache --erase >ctx.log
rm tex/*.tma
sh ./install.sh >ctx.log
context --versi
Dear list,
I have this sample:
\setupinteraction[state=start]
\starttext
\def\cB{file.pdf}
\def\cC{file with spaces.pdf}
%~ \def\PathName{\cldcontext{[[\env{completepath}]]}}
\def\PathName{%
\cldcontext{string.gsub([[\env{completepath
ata.numbersfname([==[#1]==])}}
I’m afraid it doesn’t work.
\startluacode
userdata = userdata or {}
function userdata.numbersfname(name)
return string.match(name, "%d+")
end
\stopluacode
\defineexpandable[1]\numbersfname
{\cldcontext{userdata.numbersfname([=
On 10/13/20 5:33 PM, Pablo Rodriguez wrote:
> [...]
> \starttext
> \ctxlua{ d = [[\env{fname}]] }
>
> d: \cldcontext{d}\\
> \doifelse{\cldcontext{d:match("\letterpercent d+")}}
> {123}{yes}{no}
> \stoptext
> [...]
> 3. I’m trying this on
ion userdata.numbersfname(name)
return string.match(name, "%d+")
end
\stopluacode
\define[1]\numbersfname
{\cldcontext{userdata.numbersfname([==[#1]==])}}
\starttext
\numbersfname{abc123}
\numbersfname{\env{fname}}
\doifelse{\numbersfname{\env{fname}}}{123}{yes}{no}
Pablo Rodriguez schrieb am 13.10.2020 um 17:33:
Dear list,
I have the following sample:
\starttext
\def\numbersfname
{\cldcontext{string.match([[\env{fname}]], "\letterpercent d+")}}
\ctxlua{ c = context.getvariable("environment", "fname") or &quo
On Tue, 13 Oct 2020, Pablo Rodriguez wrote:
> Dear list,
>
> I have the following sample:
>
> \starttext
> \def\numbersfname
> {\cldcontext{string.match([[\env{fname}]], "\letterpercent d+")}}
> \ctxlua{ c = context.getvariable("environment"
Dear list,
I have the following sample:
\starttext
\def\numbersfname
{\cldcontext{string.match([[\env{fname}]], "\letterpercent d+")}}
\ctxlua{ c = context.getvariable("environment", "fname") or "a" }
\ctxlua{ d = [[\env{fname}]] }
tex:
Dear list,
I have the following sample:
\starttext
\ctxlua{ context.setvariable("environment", "filename", "abc123") }
\ctxlua{ c = context.getvariable("environment", "filename") or "a" }
\ctxlua{ d = [[\env{filename}]]
any thanks for your reply, Lukas.
I found another workaround at the ConTeXt file (b.tex).
\cldcontext{string.gsub([[\env{PDFdocument}]], "", "/")}
I don’t know why I needed to add "" instead of "\\". (otherwise, I
I guess that's as Ctx translates &qu
ot;
Best regards,
Lukas
On 2020-10-06 16:18, Pablo Rodriguez wrote:
Dear list,
I have a minimal sample file:
\starttext
\insertpages[\env{PDFdocument}]
\stoptext
I invoke it in Windows, using the following batch file:
@echo off
REM ~ context --purgeall --arguments="PDFdoc
:18, Pablo Rodriguez wrote:
Dear list,
I have a minimal sample file:
\starttext
\insertpages[\env{PDFdocument}]
\stoptext
I invoke it in Windows, using the following batch file:
@echo off
REM ~ context --purgeall --arguments="PDFdocument=%1" b.tex
I’m afraid it only wor
Lukas.
I found another workaround at the ConTeXt file (b.tex).
\cldcontext{string.gsub([[\env{PDFdocument}]], "", "/")}
I don’t know why I needed to add "" instead of "\\". (otherwise, I
kept getting "C://Users//username//Desktop//document.pdf
> Am 06.10.2020 um 16:18 schrieb Pablo Rodriguez :
>
> Dear list,
>
> I have a minimal sample file:
>
> \starttext
>\insertpages[\env{PDFdocument}]
> \stoptext
>
> I invoke it in Windows, using the following batch file:
>
> @echo off
Dear list,
I have a minimal sample file:
\starttext
\insertpages[\env{PDFdocument}]
\stoptext
I invoke it in Windows, using the following batch file:
@echo off
REM ~ context --purgeall --arguments="PDFdocument=%1" b.tex
I’m afraid it only works if the batch file a
es (\copypages use the figure mechanism) with \setupexternalfigure[location=...]. Below is a modified (but untested) version of your sample document. Wolfgang begin product\startproduct product \environment env-WA % \setvariables% [document]% [ manual={Course Manual},% tit
of your sample document.
Wolfgang
begin product
\startproduct product
\environment env-WA
% \setvariables
% [document]
% [ manual={Course Manual},
% title={Title},
%subtitleone={Subtitle 1},
%subtitletwo={Subtitle 2},
% revnumber={Revision number
Flamma The main product file==\environment env-WA \startproduct currentproduct % Document definitions\define\MyManual{Course Manual}\define\MyTitle{Title}\define\MySubtitleOne{Subtitle 1}\define\MySubtitleTwo{Subtitle 2}\define\MyRevnumber{Revision number} % Load frontmatter files\startfront
be able to copy and adapt to your needs.
Kind regards,
Jan Willem Flamma
*The main product file*
==
\environment env-WA
\startproduct currentproduct
% Document definitions
\define\MyManual{Course Manual}
\define\MyTitle{Title}
\define\MySubtitleOne{Subtitle 1}
\define
) Once the bodymatter starts the pagenumber is set to the arabic 1 (see below in the main product file) You should be able to copy and adapt to your needs. Kind regards,Jan Willem Flamma The main product file==\environment env-WA \startproduct currentproduct % Document definitions\define
Hi,
It is possible that the Mint upgrade changed something in your environment that
affects ConTeXt.
Check for (new) env settings that start with TEXMF.
Best wishes,
Taco
> On 11 Jul 2020, at 03:07, jbf wrote:
>
> Hi,
>
> After upgrading from Linux Mint 19.3 to 20, when at
s(os.env) do logs.report('ENV', a .. '=' ..v)end\stopluacode\stoptextinstead of just context ? in the terminal24 juni 2020 kl. 21:05 skrev Jan-Erik Hägglöf <janerik.hagg...@bahnhof.se>:lua error > lua error on line 70 in file ./labels3.tex:function call [801]: ...-64/tex/texmf-context/
Hi,
> On 24 Jun 2020, at 23:13, Jan-Erik Hägglöf wrote:
>
> Is the difference when I’m running mtxrun … inside macvim
I would suspect PATH problems. Try running this bit of code both ways,
and compare the differences:
\starttext
\startluacode
for a,v in pairs(os.env) do
logs.re
Alan Bowen schrieb am 10.06.2020 um 17:04:
Thanks, Taco! That works in my mwe. I added way=bytext in my env file
and the output is just what I need.
Why don't you use sub pages?
\starttext
%\setupsubpagenumber[start=5]\resetsubpagenumber
\setcounter[subpage][5]
\startTEXpage
\samplefile
Thanks, Taco! That works in my mwe. I added way=bytext in my env file and
the output is just what I need.
Best, Alan
On Wed, Jun 10, 2020 at 9:44 AM Taco Hoekwater wrote:
> Hi Alan,
>
> Sorry, I should have actually tried your MWE. You do *not* want
> way=bypage here, as
As a work around, rename /usr/bin/inkscape to new-inkscape, such as:
# mv /usr/bin/inkscape /usr/bin/new-inkscape
Then change /usr/bin/inkscape to intercept and replace the command
line argument:
#!/usr/bin/env bash
/usr/bin/new-inkscape \
$(echo "$@" | sed 's/--export-pdf/--expor
s as default:
>>> https://github.com/fiee/tools/blob/master/contextproject.py
>
>> Is there a running example ? I’m not sure how to fill in the commandline
>
>
> 1) Have a look at https://wiki.contextgarden.net/Project_structure
>
> 2) To avoid the whole name, I s
/Project_structure
2) To avoid the whole name, I set:
alias mkprj='python3 ~/workspace/tools/contextproject.py'
3)
$ mkprj --help
Usage: contextproject.py [options]
(env > prj > prd > cmp)
Provide all names without prefix and suffix!
ConTeXt project management (c) 2009-2019 by Henning Hra
nts/:/usr/share/fonts/" (log
>> out and log in)
> I'm using fish shell, but here is my env:
Do you understand well how your shell work? If you do, it is Ok, but otherwise
why do you use such unusual shell? Why not bash or zsh?
> $ env | grep OSFONTDIR
> OSFONTDIR=/home/go
> Am 22.04.2020 um 07:43 schrieb Saša Janiška :
>
>> This works for me with LMTX in Fedora.
>>
>> Add to ~/.bashrc "export OSFONTDIR=~/.fonts/:/usr/share/fonts/" (log
>> out and log in)
>
> I'm using fish shell, but here is my env:
>
>
On Tue, 21 Apr 2020 23:07:48 +0200
Pablo Rodriguez wrote:
Hello Pablo,
thank you for your assistance!
> This works for me with LMTX in Fedora.
>
> Add to ~/.bashrc "export OSFONTDIR=~/.fonts/:/usr/share/fonts/" (log
> out and log in)
I'm using fish shell, but here is
On 2/19/2020 1:20 PM, Jan U. Hasecke wrote:
Dear all,
strange problem with my online print shop. I want to print 3 products.
1. Business Cards
2. Flyer
3. Poster
All definitions for fonts, colors, color profiles and pdf version come
from one an the same file (env-cd.tex).
All PDFs passed
Dear all,
strange problem with my online print shop. I want to print 3 products.
1. Business Cards
2. Flyer
3. Poster
All definitions for fonts, colors, color profiles and pdf version come
from one an the same file (env-cd.tex).
All PDFs passed the data check without problems, but
Business
ad:
\starttext
\enablemode[\env{OptionThis}]
\enablemode[\env{OptionThat}]
This: \doifmodeelse{ab}{enabled}{disabled}.\par
That: \doifmodeelse{ábc}{enabled}{disabled}.
\stoptext
I use --arguments to pass modes to documents compiled via
\executesystemcommand.
Everything worked
d.tex read:
\starttext
\enablemode[\env{OptionThis}]
\enablemode[\env{OptionThat}]
This: \doifmodeelse{ab}{enabled}{disabled}.\par
That: \doifmodeelse{ábc}{enabled}{disabled}.
\stoptext
I use --arguments to pass modes to documents compiled via
\executesystemcommand.
Everyth
- 8< -
I don't see any core dump but on other examples being fine with
context I see this "fatal error" but with the same return code.
Or I missed something? Is luatex-cache (as in log above) a cache?
P.S. I have the following *tex* env. variables set in the se
on any computer with a working TeX Live, without them having to
install any fonts or dependencies.
I tried setting the RUNTIMEFONTS env variable, and it does exactly what
I want. The fact that it leaves garbage in the cache that can influence
other, unrelated projects, is a bit unsettling, I guess
having to install any
fonts or dependencies.
I tried setting the RUNTIMEFONTS env variable, and it does exactly what I
want. The fact that it leaves garbage in the cache that can influence
other, unrelated projects, is a bit unsettling, I guess I'll just have to
remember to tell people to clean
as AR is; many functions included, restore last
view, tabbed env, page thumbs navigator/bookmarks navigator, attachment
list, comment list; OCR included; handy designed; (many command line
options, e.g.) /open and /close options to be used by 3rd party
programs; /printto for batch printing; printing
9 of bin/mtxrun to
local platform="openbsd6.5-amd64"
but I obviously did not understand what to do next:
calling
env PATH="$PWD/bin:$CONTEXTROOT/texmf-$platform/bin:$PATH"
MTX_PLATFORM="$platform" \
./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make
Hi all,
I did a quick standalone install of Mark IV:
```shell
mkdir ~/context
cd ~/context
wget http://minimals.contextgarden.net/setup/first-setup.sh
sh first-setup.sh --modules=all --context=current --engine=luatex’)
```
Set the correct paths and env in `~/.bashrc':
```shell
# Add ConTeXt
the xml files? I know that
I can process a file with \xmlprocessfile or call it from the command
line with --env=, and in a normal tex-file I could obviously use
\environment for this, but how does this work with xml?
with "somefile.ctx" being:
My very special style
ling what styel
> to load and you can run individual files or assemblies ... all the stuff
> needed to do that is there (and probably also documented someplace)
>
Ok. Sounds good. How can I call the style in the xml files? I know that I
can process a file with \xmlprocessfile or call it from the comma
now in
/Library/TeX/texbin
which is ultimately a symlink to
/usr/local/texlive/2018/bin/x86_64-darwin
(which you could also use if needed).
> And this last part is where I think the context binary seems to be
> /usr/local/texlive/2018/texmf-dist/scripts/context/stubs/unix
>
> But
1 - 100 of 593 matches
Mail list logo
