ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Gavin <gavinpublic@icloud.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Seeking advice for module that draws globes
Date: Mon, 18 Dec 2023 18:27:06 +0100	[thread overview]
Message-ID: <a73aecbf-fdcb-430c-b8ec-e17e6dc8dee2@freedom.nl> (raw)
In-Reply-To: <61DD6183-DD34-4A3A-A04A-7E327EF84972@icloud.com>

On 12/18/2023 5:22 PM, Gavin wrote:
> Hi Hans,
> 
>> On Dec 18, 2023, at 3:12 AM, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
>>
>> about names:
>>
>> how about
>>
>> t-luageo.lmt
>> t-luageo.mpxl
>>
>> so that one knows what comes with the module (we do the same with s-* modules)
> 
> "t-luageo.lmt" is fine, but "t-luageo.mpxl" breaks the module. I think the line
> 
> \startMPdefinitions
>     loadmodule "luageo" ;
> \stopMPdefinitions
> 
> finds “mp-luageo” but not “t-luageo”. Changing the line to "loadmodule “t-luageo” does not work either.

so how about  mp-t-luageo

>> and you can add the example to the end of the module
> 
> Done.
> 
>> On Dec 18, 2023, at 3:08 AM, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
>>
>>> Also, we do have a strange artifact, at least when I run this code. There is a line running across Brazil:
>>>
>> i'm not sure where that comes from (you can try &&&)
> 
> 
> I will use &&& in my upcoming module, t-discoworld.
> 
> 
> 
> (Drawn with eofill, for maximum grooviness.)
> 
> Is there a place I can read about disconnected paths, &&&&, and &&&? These are totally unfamiliar to me.
at some point in the luametafun manual and they are probabaly mentioned 
in some docs that describe development

it's anyway something introduced last year, so kind of new

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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2023-12-18 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 22:22 [NTG-context] " Gavin via ntg-context
2023-12-17 23:58 ` [NTG-context] " Hans Hagen via ntg-context
2023-12-18  7:12   ` Henning Hraban Ramm
2023-12-19 14:27     ` Gavin via ntg-context
2023-12-19 17:42       ` Henning Hraban Ramm
2023-12-18  0:55 ` Hans Hagen via ntg-context
2023-12-18  3:49   ` Gavin via ntg-context
2023-12-18 10:08     ` Hans Hagen via ntg-context
2023-12-18 10:12 ` Hans Hagen via ntg-context
2023-12-18 16:22   ` Gavin via ntg-context
2023-12-18 17:27     ` Hans Hagen via ntg-context [this message]

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=a73aecbf-fdcb-430c-b8ec-e17e6dc8dee2@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=gavinpublic@icloud.com \
    --cc=j.hagen@freedom.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).