From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: follow up
Date: Mon, 8 Apr 2019 10:32:00 +0200 [thread overview]
Message-ID: <F894514C-8E72-4743-B05D-B438EFE4F332@gmail.com> (raw)
In-Reply-To: <B0F808F6-7505-4481-8B10-BD1A2E2E53A2@me.com>
[-- Attachment #1.1: Type: text/plain, Size: 12129 bytes --]
Dear Dalyoung,
Actually when you have added
export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
either in your engine file (using TeXShop), or when typesetting from the Terminal, then you don't need to use mtxrun --autogenerate in order to typeset a file with LuaMetaTeX: you can just have
/context-osx-64/tex/texmf-osx-64/bin/context myfile.tex
in this way you can use any mode you wish.
Or have I misunderstood the issue you are asking about?
Best regards: OK
> On 5 Apr 2019, at 16:30, Jeong Dal <haksan@me.com> wrote:
>
>
> Dear Hans and Otared,
>
> Thank you for your help.
> It is OK to use ConTeXt-LMTX in TeXShop and in Atom.
>
> I’d like to compile it in LMTX mode or in MKIV mode without running "mtxrun —geneate” when I change mode.
> Set path to absolute path of mtxrun in the setting doesn’t help.
>
> Actually, it is not a problem of ConTeXt.
>
> I’ll try it once more.
>
> Thank you.
>
> Best regards,
>
> Dalyoung
>
>
>> 2019. 4. 5. 오후 7:00, ntg-context-request@ntg.nl 작성:
>>
>> Send ntg-context mailing list submissions to
>> ntg-context@ntg.nl
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mailman.ntg.nl/mailman/listinfo/ntg-context
>> or, via email, send a message with subject or body 'help' to
>> ntg-context-request@ntg.nl
>>
>> You can reach the person managing the list at
>> ntg-context-owner@ntg.nl
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ntg-context digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: How to update LMTX? (Hans Hagen)
>> 2. Re: follow up (Hans Hagen)
>> 3. Re: (no subject) (Hans Hagen)
>> 4. Re: follow up (Otared Kavian)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Fri, 5 Apr 2019 00:20:32 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] How to update LMTX?
>> Message-ID: <4ab6b1ec-62cd-90c8-0f54-b303f025c2b6@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> On 4/5/2019 12:09 AM, Alan Braslau wrote:
>>> On Thu, 4 Apr 2019 23:11:42 +0200
>>> Hans Hagen <j.hagen@xs4all.nl> wrote:
>>>
>>>> (we just don't use rsync)
>>>
>>> As rsync can be problematic for some locations
>>> (TCP port 873 blocked) without the ability to
>>> tunnel.
>>
>> indeed, especially in schools
>>
>>> http is most often open.
>> right and rsync is also very unix centric so on windows one has to use
>> cygwin (bah) or a mingw version (hard to get); also the rsync protocol
>> is sometimes updated so then you need matching versions
>>
>> Hans
>>
>> -----------------------------------------------------------------
>> Hans Hagen | PRAGMA ADE
>> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
>> -----------------------------------------------------------------
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Fri, 5 Apr 2019 00:28:19 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] follow up
>> Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> On 4/5/2019 12:17 AM, Jeong Dal wrote:
>>> Dear Hans,
>>>
>>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>>> But I have a problem to run it.
>>>
>>> If it is OK to run a file in LMTX environment, then I got a following
>>> error when I run it in MKIV environment.
>>> “I can’t fine a file …../defFonts.tex” even though it is there.
>>> To resolve it, I run “mtxrun —generate” in MKIV.
>>> But it invoke the same type error in LMTX.
>>> Here are the command in Atom editor which I use to run it.
>>>
>>> LMTX:
>>> source /Users/graph/ConTeXtLMTX/tex/setuptex;
>>> context {filePath}
>>> MKIV:
>>> source /Users/graph/ConTeXt/tex/setuptex;
>>> context {filePath}
>>>
>>> I may avoid it by adding “mtxrun —generate” before compiling it.
>>> But it isn’t a good solution.
>>> I think that there is a better way to do this.
>>> Would you please tell me how to fix it or what is a better way?
>> Does
>>
>> <path to>/mtxrun --autogenerate --script context --autopdf {filePath}
>>
>> work in your editor?
>>
>> Hans
>>
>> -----------------------------------------------------------------
>> Hans Hagen | PRAGMA ADE
>> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
>> -----------------------------------------------------------------
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Fri, 5 Apr 2019 00:37:27 +0200
>> From: Hans Hagen <j.hagen@xs4all.nl>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>, Dmitry
>> Starostin <starostin.dmitry@gmail.com>
>> Subject: Re: [NTG-context] (no subject)
>> Message-ID: <2a626d5a-4378-e1f9-2278-d1496f62f810@xs4all.nl>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> On 4/4/2019 9:30 PM, Dmitry Starostin wrote:
>>> In terminal:
>>>
>>> mtxrun --autogenerate --script context --autopdf Test.tex
>>>
>>> ->
>>>
>>> resolvers | initialization | fatal error: kpse library is accessed
>>> (key: default_texmfcnf)
>> this normally means that there is no file database ... context mkiv nor
>> lmtx doesn't use kpse
>>
>> Hans
>>
>>
>>
>> -----------------------------------------------------------------
>> Hans Hagen | PRAGMA ADE
>> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
>> -----------------------------------------------------------------
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Fri, 5 Apr 2019 08:49:00 +0200
>> From: Otared Kavian <otared@gmail.com>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] follow up
>> Message-ID: <84D8FE1D-E7F7-418F-B10F-A141DD6D8CEC@gmail.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> Hi Dalyoung,
>>
>> If this can be of any help, here is what I did in order to install LuaMetaTeX on MacOS in order to use it with TeXShop:
>>
>> 1) I downloaded from
>> http://www.pragma-ade.nl/install.htm
>> the version of the installer for MacOS and installed a folder named context-osx-64 at an appropriate place (actually at /context-osx-64)
>>
>> 2) Then I did
>> sh install.sh
>> in that folder, and once the download was finished I replaced the directory texmf-local with a symbolic link to my texmf-local directory (which sits somewhere else)
>>
>> 3) In the directory
>> ~/Library/TeXShop/Engines
>> I created a new file named LuaMetaTeX.engine containing the following three lines:
>>
>> #!/bin/bash
>>
>> export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
>>
>> /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf "$1" --purgeall
>>
>> 4) Then when opening TeXShop, I can choose from the scroll menu which shows up on the top left of each a tex file, the engine LuaMetaTeX (or I can set it as default in the Preferences) in order to typeset with LuaMetaTeX engine.
>>
>> 5) When I need to update the installation I just run again
>> sh install.sh
>> from within the directory /context-osx-64
>> (The symlink to my texmf-local is not destroyed).
>>
>> 6) If I need to typeset a file from a command line in Terminal, then I need to say
>>
>> export PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
>>
>> before typesetting myfile.tex by saying
>>
>> /context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script context --autopdf myfile.tex
>>
>> (Note that the above command should be issued when one is already in the directory containing myfile.tex, beacuse otherwise the corresponding pdf file will be created in the wrong place…).
>>
>> Best regards: OK
>>
>>> On 5 Apr 2019, at 00:17, Jeong Dal <haksan@me.com> wrote:
>>>
>>> Dear Hans,
>>>
>>> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
>>> But I have a problem to run it.
>>>
>>> If it is OK to run a file in LMTX environment, then I got a following error when I run it in MKIV environment.
>>> “I can’t fine a file …../defFonts.tex” even though it is there.
>>> To resolve it, I run “mtxrun —generate” in MKIV.
>>> But it invoke the same type error in LMTX.
>>> Here are the command in Atom editor which I use to run it.
>>>
>>> LMTX:
>>> source /Users/graph/ConTeXtLMTX/tex/setuptex;
>>> context {filePath}
>>> MKIV:
>>> source /Users/graph/ConTeXt/tex/setuptex;
>>> context {filePath}
>>>
>>> I may avoid it by adding “mtxrun —generate” before compiling it.
>>> But it isn’t a good solution.
>>> I think that there is a better way to do this.
>>> Would you please tell me how to fix it or what is a better way?
>>>
>>> Thank you for reading.
>>>
>>> Best regards,
>>>
>>> Dalyoung
>>>
>>>
>>>>
>>>> Hi,
>>>>
>>>> We have worked furiously all day kicking-out extra code, and are pleased
>>>> to present a lean-and-mean version of luatex with your favorite ConTeXt.
>>>> Same good taste but only half the calories and a new name: luametatex
>>>> and ConTeXt LMTX. No more Mk-whatever, no more dependencies for we can
>>>> now stand on our own. Of course, good-old luatex and MkIV (as well as
>>>> MkII) will continue to coexist and be maintained. However, now you will
>>>> be able to run ConTeXt lmtx on your smart thermostat or on your
>>>> refrigerator for the Internet of Things - the dawn of a new era!
>>>>
>>>> Stay tuned,
>>>>
>>>> Alan and Hans
>>>
>>> ___________________________________________________________________________________
>>> If your question is of interest to others as well, please add an entry to the Wiki!
>>>
>>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>>> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
>>> archive : https://bitbucket.org/phg/context-mirror/commits/
>>> wiki : http://contextgarden.net
>>> ___________________________________________________________________________________
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to the Wiki!
>>
>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>> archive : https://foundry.supelec.fr/projects/contextrev/
>> wiki : http://contextgarden.net
>> ___________________________________________________________________________________
>>
>>
>> ------------------------------
>>
>> End of ntg-context Digest, Vol 178, Issue 19
>> ********************************************
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 18860 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-04-08 8:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1554458401.26589.ntg-context@ntg.nl>
2019-04-05 14:30 ` Jeong Dal
2019-04-08 8:32 ` Otared Kavian [this message]
[not found] <mailman.769.1554712325.1194.ntg-context@ntg.nl>
2019-04-08 13:32 ` Jeong Dal
[not found] <mailman.557.1554137032.1194.ntg-context@ntg.nl>
2019-04-02 11:49 ` Jeong Dal
2019-04-02 12:25 ` Hans Hagen
2019-04-02 12:40 ` Floris van Manen
2019-04-02 12:50 ` Hans Hagen
2019-04-02 13:12 ` Floris van Manen
2019-04-02 13:23 ` Hans Hagen
2019-04-02 13:58 ` Floris van Manen
2019-04-02 14:18 ` Ulrike Fischer
2019-04-02 14:50 ` Hans Hagen
2019-04-02 15:11 ` Hans Hagen
2019-04-02 18:38 ` Taco Hoekwater
2019-04-02 19:29 ` Floris van Manen
2019-04-02 20:16 ` Hans Hagen
2019-04-03 5:58 ` Christoph Reller
2019-04-03 7:06 ` Hans Hagen
2019-04-02 14:42 ` Hans Hagen
2019-04-04 22:17 ` Jeong Dal
2019-04-04 22:28 ` Hans Hagen
2019-04-05 6:49 ` Otared Kavian
2019-04-01 12:56 Hans Hagen
2019-04-01 13:18 ` Floris van Manen
2019-04-01 13:31 ` Mojca Miklavec
2019-04-01 19:41 ` Henning Hraban Ramm
2019-04-02 15:56 ` Aditya Mahajan
2019-04-02 16:24 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F894514C-8E72-4743-B05D-B438EFE4F332@gmail.com \
--to=otared@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).