On 4/8/2018 12:11 AM, Pablo Rodriguez wrote:

On 04/07/2018 11:25 PM, Hans Hagen wrote:

...

On 4/7/2018 11:04 PM, Pablo Rodriguez wrote:

...

Dear list,

I have the following sample:

\useMPlibrary[txt]

\starttext

\startuseMPgraphic{followtokens} path RotPath ; RotPath := reverse halfcircle ; % path RotPath ; RotPath := halfcircle rotatedaround (origin, 180) ; \stopuseMPgraphic

\followtokens{Just follow the tokens} \stoptext

How can I get both paths (in diverse directions)?

I would like to repeat the same text twice, separating both sentences with a character.

I have to ask this, beause MetaPost is all Greek to me. i have no clue what you mean but this will change the direction

Many thanks for your reply, Hans.

I attach an image of what I mean.

I want a full circle in two halves with the same duplicated sentence. The first one written clockwise and the second one written counterclockwise (as in the commented path above).

I hope it is clearer now.

path p ; p := reverse halfcircle scaled 5cm ; path q ; q := reverse halfcircle scaled 5cm rotated 180 ; path q ; q := reverse halfcircle scaled 5cm rotated 180 ; \followtokens{~this way~} \followtokens{\reversedtext{~this way~}} we will have this in metafun: followtext("this way",p) ; so that one can do it all in mp ... a nice gimmick for the ctx meeting 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 -----------------------------------------------------------------

Dear Brian, On 8 April 2018 at 16:56, Brian Hunt wrote:

Hello everyone,

Per this question on tex.StackOverflow, I am having trouble getting ConTeXt (LuaTeX specifically) to run on Alpine Linux:

https://tex.stackexchange.com/questions/425463

Specifically, the build from ConTeXt standalone has a LuaTeX that seems not to run against the musl libc6 library.

We have a "nearly working" one. At least all the binaries should be there, see for example: http://distribution.contextgarden.net/setup/linuxmusl-64/ There are two to three remaining problems: 1.) I disabled automatic musl recognition (short after enabling it) after this bug report: https://mailman.ntg.nl/pipermail/ntg-context/2018/091094.html I need to finish "parsing" https://mailman.ntg.nl/pipermail/ntg-context/2018/091123.html and a few other posts in that thread and maybe make some additional testing. There was some "oh no, it has to be the other way around" discussion where I no longer followed and I need some more time to read everything more carefully (no time for that right now). 2.) Most likely a patch in mtxrun is still needed (but I admit that I didn't check) for proper platform recognition. The fact that we are struggling in shell doesn't really help doing this part either :) 3.) Ideally we need to set up some automated LuaTeX builds to be able to get the latest LuaTeX binaries in the future.

Has anyone run ConTeXt on Alpine?

At the moment it should work if you install TeX Live 2018 pretest with the ConTeXt scheme or if you fiddle a bit with the installation (you need to hardcode the platform name in first-setup.sh and then still some minor things might still go wrong, not sure). But in fact very little is required to fix the remaining issues. Can you please remind us to pick this up again in a couple of days? In the meantime, if you are willing to do some more extensive testing of patches (see full thread linked above) on both musl & non-musl linuxes, in various shells etc., as well as perhaps come up with a patch for mtxrun, that might help. Mojca

On Sun, 2018-04-08 at 22:50 +0200, Mojca Miklavec wrote:

Dear Brian,

On 8 April 2018 at 16:56, Brian Hunt wrote:

...

Hello everyone,

Per this question on tex.StackOverflow, I am having trouble getting ConTeXt (LuaTeX specifically) to run on Alpine Linux:

https://tex.stackexchange.com/questions/425463

Specifically, the build from ConTeXt standalone has a LuaTeX that seems not to run against the musl libc6 library.

We have a "nearly working" one. At least all the binaries should be there, see for example:     http://distribution.contextgarden.net/setup/linuxmusl-64/

There are two to three remaining problems:

1.) I disabled automatic musl recognition (short after enabling it) after this bug report:     https://mailman.ntg.nl/pipermail/ntg-context/2018/091094.html I need to finish "parsing"     https://mailman.ntg.nl/pipermail/ntg-context/2018/091123.html and a few other posts in that thread and maybe make some additional testing. There was some "oh no, it has to be the other way around" discussion where I no longer followed and I need some more time to read everything more carefully (no time for that right now).

This only blows up on Zsh.  I will contact the "config.guess" maintainer (from where I stole that snippet).

2.) Most likely a patch in mtxrun is still needed (but I admit that I didn't check) for proper platform recognition. The fact that we are struggling in shell doesn't really help doing this part either :)

3.) Ideally we need to set up some automated LuaTeX builds to be able to get the latest LuaTeX binaries in the future.

...

Has anyone run ConTeXt on Alpine?

At the moment it should work if you install TeX Live 2018 pretest with the ConTeXt scheme or if you fiddle a bit with the installation (you need to hardcode the platform name in first-setup.sh and then still some minor things might still go wrong, not sure). But in fact very little is required to fix the remaining issues.

Can you please remind us to pick this up again in a couple of days?

In the meantime, if you are willing to do some more extensive testing of patches (see full thread linked above) on both musl & non-musl linuxes, in various shells etc., as well as perhaps come up with a patch for mtxrun, that might help.

Mojca

On Sun, 2018-04-08 at 22:50 +0200, Mojca Miklavec wrote:

Dear Brian,

On 8 April 2018 at 16:56, Brian Hunt wrote:

...

Hello everyone,

Per this question on tex.StackOverflow, I am having trouble getting ConTeXt (LuaTeX specifically) to run on Alpine Linux:

https://tex.stackexchange.com/questions/425463

Specifically, the build from ConTeXt standalone has a LuaTeX that seems not to run against the musl libc6 library.

We have a "nearly working" one. At least all the binaries should be there, see for example:     http://distribution.contextgarden.net/setup/linuxmusl-64/

There are two to three remaining problems:

1.) I disabled automatic musl recognition (short after enabling it) after this bug report:     https://mailman.ntg.nl/pipermail/ntg-context/2018/091094.html I need to finish "parsing"     https://mailman.ntg.nl/pipermail/ntg-context/2018/091123.html and a few other posts in that thread and maybe make some additional testing. There was some "oh no, it has to be the other way around" discussion where I no longer followed and I need some more time to read everything more carefully (no time for that right now).

2.) Most likely a patch in mtxrun is still needed (but I admit that I didn't check) for proper platform recognition. The fact that we are struggling in shell doesn't really help doing this part either :)

3.) Ideally we need to set up some automated LuaTeX builds to be able to get the latest LuaTeX binaries in the future.

Similar to TeX live I have set up an automated Travis CI build, which can deploy binaries to GitHub releases. https://github.com/hmenke/luatex/blob/master/.travis.yml However, I just forked Adam's mirror and I am not planning to keep mine updated. It would be nice to have some sort of “official” LuaTeX mirror on GitHub for that.  Nevertheless, it might be worthwhile to check the '.travis.yml' I posted above into the LuaTeX SVN.

...

Has anyone run ConTeXt on Alpine?

At the moment it should work if you install TeX Live 2018 pretest with the ConTeXt scheme or if you fiddle a bit with the installation (you need to hardcode the platform name in first-setup.sh and then still some minor things might still go wrong, not sure). But in fact very little is required to fix the remaining issues.

Can you please remind us to pick this up again in a couple of days?

In the meantime, if you are willing to do some more extensive testing of patches (see full thread linked above) on both musl & non-musl linuxes, in various shells etc., as well as perhaps come up with a patch for mtxrun, that might help.

Mojca

A few notes: a.) On some platforms fgrep has been deprecated (in favour of `grep -F`) so it's not future-proof

I don’t think the aliases fgrep and egrep have ever been supposed to be portable. POSIX has grep -F and grep -E, and that’s what we should use.

b.) The caret (^) passed to `grep -F` will not be interpreted as a regex, since -F forces non-regexp, meaning the '^' will be interpreted literally (and the string "^musl" is not in the ldd output).

The caret in itself was not the problem, only that it was not escaped for the shell. Testing a regexp, with -E of course, is just as robust, and allows us to be more specific about what we test.

if command -v ldd >/dev/null && ldd --version 2>&1 | grep -Fq 'musl' > /dev/null

grep -E '^musl' works just as well; and as I explained, -q may return 0 even if there are errors, so should be avoided. Best, Arthur

A few more notes: 1. Missing texlua - found The missing `texlua` from `bin/` and `tex/texmf-linuxmusl-64/bin` appears to be a problem originating at the rsync source, notably it appears that `texlua` is missing from these paths: http://standalone.contextgarden.net/setup/linuxmusl-64/ http://standalone.contextgarden.net/current/bin/luatex/linuxmusl-64/bin/ The `texluac` also appears to be missing from these paths (but I have not experienced errors that appear relating to its absence). 2. mtxrun not finding paths Running `context` results in an error because it cannot find `mtx-context.lua`. I can confirm that mtx-context.lua is in an expected path with: $ /context # find . -name mtx-context.lua ./tex/texmf-context/scripts/context/lua/mtx-context.lua I noted mtxrun checks and sets the `platform` (`os.platform`) variable, and will use `linux-64` by default. When musl is being used this ought to be `linuxmusl-64`. Two potential solutions are: a. have mtxrun detect musl with a call to `ldd --version` when setting `platform`; or b. symlink texmf-linux-64 -> texmf-linuxmusl-64 I tried both but `context` still cannot find `mtx-context.lua`. The path resolution is complex and challenging to debug, and I expect the issue may be immediately apparent to some. I've attached a log of a call to `context` with a number of the traces turned on, that hopefully sheds some light on the problem. I'm happy to delve or investigate further as may be helpful, and any assistance is appreciated. Cheers, Brian -- *from the personal account of:* *Brian M Hunt * Direct: +1-289-684-4677 LinkedIn: https://linkedin.com/in/brianmhunt *This e-mail may contain information that is private, privileged, confidential and/or exempt from disclosure. Except as per this notice no waiver of any kind is intended by sending this e-mail, and this email is intended only for the named recipient(s) or the subscribers of a forwarding service the email is sent directly to and to which service you are an authorized recipient. Use, dissemination or copying without authorization is prohibited. Please notify the sender and destroy all copies of this e-mail if you have received this email in error.*

On Tue, Apr 10, 2018 at 11:05:12AM +0000, Brian Hunt wrote:

...

The caret in itself was not the problem, only that it was not escaped for the shell. Testing a regexp, with -E of course, is just as robust, and allows us to be more specific about what we test.

Either is fine I am sure

That’s what I was saying. But you seemed to imply that grep -F 'musl' was preferable to grep -E '^musl' from a portability and robustness point of view.

...

grep -E '^musl' works just as well; and as I explained, -q may return 0 even if there are errors, so should be avoided.

The -q is superfluous with the >/dev/null, and should be removed; incidentally though, is it not harmless in this case?

It is not. In Thomas’ case, using grep >/dev/null would have avoided a 0 exit status and thus prevented his system from being erroneously detected as supporting musl. Best, Arthur

So here's what I've got for a TODO so far to get ConTeXt working on Alpine Linux with musl (subject to item #6, mtx-context.lua not being found): 1. Add the musl test to first-setup.sh 2. Add the same musl test to tex/setuptex 3. Add texlua (and texluac?) to a. the setup rsync bin/ directories b. the tex/texmf-linuxmusl(|-ppc|-64) 4. Update mtxrun Here's code that ought to work for detecting musl in mtxrun. Around line 3721 of the mtxrun add: if find(architecture,"x86_64",1,true) then platform="linux-64" elseif find(architecture,"ppc",1,true) then platform="linux-ppc" else platform="linux" end + if resultof("ldd --version 2>&1"):find("musl") ~= nil then + platform = platform:gsub("linux", "linuxmusl") + end 5. Note that in tex/setuptex, there's evidently no way to get the current script so one has to explicitly provide the TeX directory (appears to be a BusyBox bug). 6. `context` is unable to locate `mtx-context.lua`. Some tracker output sheds some light: i. context --trackers=resolvers.expansions is identical ii. context --trackers=resolvers.details,resolvers.details differs, with the output attached. Note that to keep the comparison short I removed lines that differed only because `linux` had been changed to `linuxmusl`. Will keep plugging away to see if I can determine why `mtx-context.lua` cannot be found on Alpine Linux. Thanks for reading. Brian -- *from the personal account of:* *Brian M Hunt * Direct: +1-289-684-4677 LinkedIn: https://linkedin.com/in/brianmhunt *This e-mail may contain information that is private, privileged, confidential and/or exempt from disclosure. Except as per this notice no waiver of any kind is intended by sending this e-mail, and this email is intended only for the named recipient(s) or the subscribers of a forwarding service the email is sent directly to and to which service you are an authorized recipient. Use, dissemination or copying without authorization is prohibited. Please notify the sender and destroy all copies of this e-mail if you have received this email in error.*

On 4/11/2018 10:08 PM, Brian Hunt wrote:

So here's what I've got for a TODO so far to get ConTeXt working on Alpine Linux with musl (subject to item #6, mtx-context.lua not being found):

1. Add the musl test to first-setup.sh 2. Add the same musl test to tex/setuptex

no problem adding a robust test there

3. Add texlua (and texluac?) to   a. the setup rsync bin/ directories   b. the tex/texmf-linuxmusl(|-ppc|-64)

we don't use texluac, don't need texlua on windows and on linux texlua is just a symlink if musl needs different bin then there should be a different initial download i think because basically we're now talking of: windows, osx, linux, linuxmusl (a different species)

4. Update mtxrun

Here's code that ought to work for detecting musl in mtxrun.  Around line 3721 of the mtxrun add:

    if find(architecture,"x86_64",1,true) then       platform="linux-64"     elseif find(architecture,"ppc",1,true) then       platform="linux-ppc"     else       platform="linux"     end +   if resultof("ldd --version 2>&1"):find("musl") ~= nil then +     platform = platform:gsub("linux", "linuxmusl") +   end

that's not going to happen, some system call 9each run) in order to determine what linux species we run ... (there are a few calls but these are never used becasue we use HOSTTYPE (if needed we can set one ourselves on these platforms) isn't there some magic env var that tels if musl is used? do programs and scripts really have to jumpo through such loops

5. Note that in tex/setuptex, there's evidently no way to get the current script so one has to explicitly provide the TeX directory (appears to be a BusyBox bug). 6. `context` is unable to locate `mtx-context.lua`.  Some tracker output sheds some light:   i. context --trackers=resolvers.expansions is identical   ii. context --trackers=resolvers.details,resolvers.details differs, with the output attached.  Note that to keep the comparison short I removed lines that differed only because `linux` had been changed to `linuxmusl`.

Will keep plugging away to see if I can determine why `mtx-context.lua` cannot be found on Alpine Linux. hm, so musl is far from a drop=in for glib or do i get it wrong

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 -----------------------------------------------------------------

On 11 April 2018 at 22:37, Hans Hagen wrote:

On 4/11/2018 10:08 PM, Brian Hunt wrote:

...

3. Add texlua (and texluac?) to a. the setup rsync bin/ directories b. the tex/texmf-linuxmusl(|-ppc|-64)

we don't use texluac, don't need texlua on windows and on linux texlua is just a symlink

This was entirely my fault which has been fixed in the meantime.

if musl needs different bin then there should be a different initial download i think because basically we're now talking of: windows, osx, linux, linuxmusl (a different species)

Exactly. We have that. And most bits and pieces are in place to allow that, except for the problem with mtxrun not being able to determine the platform correctly.

...

4. Update mtxrun

Here's code that ought to work for detecting musl in mtxrun. Around line 3721 of the mtxrun add:

if find(architecture,"x86_64",1,true) then platform="linux-64" elseif find(architecture,"ppc",1,true) then platform="linux-ppc" else platform="linux" end + if resultof("ldd --version 2>&1"):find("musl") ~= nil then + platform = platform:gsub("linux", "linuxmusl") + end

that's not going to happen, some system call 9each run) in order to determine what linux species we run ... (there are a few calls but these are never used becasue we use HOSTTYPE (if needed we can set one ourselves on these platforms)

isn't there some magic env var that tels if musl is used? do programs and scripts really have to jumpo through such loops

Hans, we don't really need this code for the sake of minimals themselves, it is part of ConTeXt code that needs it and fails. The problem is that even if I properly detect the platform upfront, your code (mtx-update) will refuse to respect the setting. When calling ./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make --context=beta --platform=linuxmusl-64 --texroot="/some/path" from musl linux, the mtx-update will insist in always installing and using linux-64 binaries even if they don't work, no matter what else we try. I still believe that a string like "x86_64-linuxmusl" is something that luatex itself should be able to return when asked about what platform it is running on (what platform it has been compiled for). We've discussed this with Taco many years ago, but this has never been implemented. Mojca

Am 2018-04-13 um 13:42 schrieb Henri Menke :

...

Exactly. We have that. And most bits and pieces are in place to allow that, except for the problem with mtxrun not being able to determine the platform correctly.

Actually, the musl detection only has to be peformed for downloading binaries. Once those binaries are installed, they behave exactly like the linux-64 binaries. I would suggest to simply drop musl binaries in the texmf-linux-64 folder as well. (Who has ConTeXt for multiple platforms on their computer anyway?) That would render all the funny business of calling ldd in mtxrun superfluous.

Probably only a few people need different binaries, but think of e.g. - universities etc. that provide a (SMB/DAV) shared installation on a server - dual-boot computers (Windows/Linux or OSX/Windows) that use a shared installation Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net GPG Key ID 1C9B22FD

On 4/13/2018 1:14 PM, Mojca Miklavec wrote:

On 11 April 2018 at 22:37, Hans Hagen wrote:

...

On 4/11/2018 10:08 PM, Brian Hunt wrote:

...

3. Add texlua (and texluac?) to a. the setup rsync bin/ directories b. the tex/texmf-linuxmusl(|-ppc|-64)

we don't use texluac, don't need texlua on windows and on linux texlua is just a symlink

This was entirely my fault which has been fixed in the meantime.

...

if musl needs different bin then there should be a different initial download i think because basically we're now talking of: windows, osx, linux, linuxmusl (a different species)

Exactly. We have that. And most bits and pieces are in place to allow that, except for the problem with mtxrun not being able to determine the platform correctly.

...

...

4. Update mtxrun

Here's code that ought to work for detecting musl in mtxrun. Around line 3721 of the mtxrun add:

if find(architecture,"x86_64",1,true) then platform="linux-64" elseif find(architecture,"ppc",1,true) then platform="linux-ppc" else platform="linux" end + if resultof("ldd --version 2>&1"):find("musl") ~= nil then + platform = platform:gsub("linux", "linuxmusl") + end how about this one

function resolvers.platform(t,k) local architecture = os.getenv("HOSTTYPE") or resultof("uname -m") or "" local platform = os.getenv("MTX_PLATFORM") local musl = find(os.selfdir or "","linuxmusl") if platform ~= "" then -- we're done elseif find(architecture,"x86_64",1,true) then platform = musl and "linuxmusl" or "linux-64" elseif find(architecture,"ppc",1,true) then platform = "linux-ppc" else platform = musl and "linuxmusl" or "linux" end os.setenv("MTX_PLATFORM",platform) os.platform = platform return platform end assuming that the user or setuptex sets the path right this will cover runtime that still leaves an issue for the initial mtx-update but that one can set MTX_PLATFORM=linuxmusl 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 -----------------------------------------------------------------

For those interested in reproducing the issues experienced on Alpine, I've published an image that you should be able to start with: $ docker run -ti brianmhunt/context-alpine:demo (You can see the Dockerfile etc here: https://hub.docker.com/r/brianmhunt/context-alpine/) That image applies the TODO/workarounds previously posted (sometimes inelegantly) and brings it to the point where I got stuck, namely luatools and context erroring with "unknown script base.lua" and "unknown script context.lua", respectively. On Wed, 11 Apr 2018 at 19:14 Henri Menke wrote:

...

So here's what I've got for a TODO so far to get ConTeXt working on Alpine Linux with musl (subject to item #6, mtx-context.lua not being found):

1. Add the musl test to first-setup.sh 2. Add the same musl test to tex/setuptex 3. Add texlua (and texluac?) to a. the setup rsync bin/ directories b. the tex/texmf-linuxmusl(|-ppc|-64) 4. Update mtxrun

Here's code that ought to work for detecting musl in mtxrun. Around

On Wed, 2018-04-11 at 20:08 +0000, Brian Hunt wrote: line 3721

...

of the mtxrun add:

if find(architecture,"x86_64",1,true) then platform="linux-64" elseif find(architecture,"ppc",1,true) then platform="linux-ppc" else platform="linux" end + if resultof("ldd --version 2>&1"):find("musl") ~= nil then + platform = platform:gsub("linux", "linuxmusl") + end

5. Note that in tex/setuptex, there's evidently no way to get the current script so one has to explicitly provide the TeX directory (appears to be a BusyBox bug).

Standard POSIX sh has no way to reliably detect sourced invocation of a script. BusyBox uses POSIX sh underneath and thus suffers from the same limitation. See StackOverflow for detail: https://stackoverflow.com/questions/29832037

...

6. `context` is unable to locate `mtx-context.lua`. Some tracker output sheds some light: i. context --trackers=resolvers.expansions is identical ii. context --trackers=resolvers.details,resolvers.details differs, with the output attached. Note that to keep the comparison short I removed lines that differed only because `linux` had been changed to `linuxmusl`.

Will keep plugging away to see if I can determine why `mtx-context.lua` cannot be found on Alpine Linux.

Thanks for reading.

Brian

-- from the personal account of: Brian M Hunt Direct: +1-289-684-4677 <(289)%20684-4677> LinkedIn: https://linkedin.com/in/brianmhunt This e-mail may contain information that is private, privileged, confidential and/or exempt from disclosure. Except as per this notice no waiver of any kind is intended by sending this e-mail, and this email is intended only for the named recipient(s) or the subscribers of a forwarding service the email is sent directly to and to which service you are an authorized recipient. Use, dissemination or copying without authorization is prohibited. Please notify the sender and destroy all copies of this e-mail if you have received this email in error.

______________________________________________________________________________

...

_____ 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

______________________________________________________________________________

...

_____

___________________________________________________________________________________ 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

___________________________________________________________________________________

-- *from the personal account of:* *Brian M Hunt * Direct: +1-289-684-4677 LinkedIn: https://linkedin.com/in/brianmhunt *This e-mail may contain information that is private, privileged, confidential and/or exempt from disclosure. Except as per this notice no waiver of any kind is intended by sending this e-mail, and this email is intended only for the named recipient(s) or the subscribers of a forwarding service the email is sent directly to and to which service you are an authorized recipient. Use, dissemination or copying without authorization is prohibited. Please notify the sender and destroy all copies of this e-mail if you have received this email in error.*

On 4/8/2018 8:10 PM, Pablo Rodriguez wrote:

On 04/08/2018 04:41 PM, Hans Hagen wrote:

...

On 4/8/2018 12:11 AM, Pablo Rodriguez wrote:

...

[...] I want a full circle in two halves with the same duplicated sentence. The first one written clockwise and the second one written counterclockwise (as in the commented path above).

I hope it is clearer now.

path p ; p := reverse halfcircle scaled 5cm ; path q ; q := reverse halfcircle scaled 5cm rotated 180 ;

path q ; q := reverse halfcircle scaled 5cm rotated 180 ;

\followtokens{~this way~} \followtokens{\reversedtext{~this way~}}

Many thanks for the reply, Hans.

I don’t know what I’m missing here, but I cannot get your code working. Here you have the full sample:

\useMPlibrary[txt]

\starttext \startuseMPgraphic{followtokens} path p ; p := reverse halfcircle scaled 5cm ; path q ; q := reverse halfcircle scaled 5cm rotated 180 ;

path q ; q := reverse halfcircle scaled 5cm rotated 180 ; \stopuseMPgraphic

\followtokens{~this way~} \followtokens{\reversedtext{~this way~}} \stoptext

\reversedtext is undefined (I’m using beta from 2018.04.04 00:51).

of course it it ... it's basically the lua snippet i sent a few mails ago

But even commenting that second command, \followtokens seems to require that path is named RotPath to be used the text. I get the standard line.

sure, that's how it works (at least with that module ... that trickery dates from mkii)

What am I doing wrong here?

probably using a mechanism in away that is a bit ovet the top (so you can wait till the embedded variant shows up)

...

we will have this in metafun:

followtext("this way",p) ;

so that one can do it all in mp ... a nice gimmick for the ctx meeting

This will be incredibly handy.

i wonder, not many users run into this feature (kind of coincidence that we have two reports this month) .. it's mostly that i was curious if it could be integrated that i looked into it

Many thanks for your help,

Pablo

-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

Is followtext(“string”,path) not yet implemented? Because I get an error when running: \startMPcode path p; p:=reverse halfcircle xyscaled 25mm; draw p; followtext("some text but not that long",p); % <- causes error \stopMPcode Or do I need to call followtext in some other way that is not clear to me. dr. Hans van der Meer

On 8 Apr 2018, at 16:41, Hans Hagen wrote:

On 4/8/2018 12:11 AM, Pablo Rodriguez wrote:

...

On 04/07/2018 11:25 PM, Hans Hagen wrote:

...

On 4/7/2018 11:04 PM, Pablo Rodriguez wrote:

...

Dear list,

I have the following sample:

\useMPlibrary[txt]

\starttext

\startuseMPgraphic{followtokens} path RotPath ; RotPath := reverse halfcircle ; % path RotPath ; RotPath := halfcircle rotatedaround (origin, 180) ; \stopuseMPgraphic

\followtokens{Just follow the tokens} \stoptext

How can I get both paths (in diverse directions)?

I would like to repeat the same text twice, separating both sentences with a character.

I have to ask this, beause MetaPost is all Greek to me. i have no clue what you mean but this will change the direction Many thanks for your reply, Hans. I attach an image of what I mean. I want a full circle in two halves with the same duplicated sentence. The first one written clockwise and the second one written counterclockwise (as in the commented path above). I hope it is clearer now.

path p ; p := reverse halfcircle scaled 5cm ; path q ; q := reverse halfcircle scaled 5cm rotated 180 ;

path q ; q := reverse halfcircle scaled 5cm rotated 180 ;

\followtokens{~this way~} \followtokens{\reversedtext{~this way~}}

we will have this in metafun:

followtext("this way",p) ;

so that one can do it all in mp ... a nice gimmick for the ctx meeting

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 ----------------------------------------------------------------- ___________________________________________________________________________________ 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 ___________________________________________________________________________________