ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mathieu Dupont <mathieudupont@hotmail.com>
To: Hans Hagen <pragma@wxs.nl>, ConTeXt <ntg-context@ntg.nl>
Subject: Re: Random selection of a word in a set with lua and mkiv
Date: Wed, 8 Jun 2011 17:19:15 +0000	[thread overview]
Message-ID: <COL107-W3512A758BB9332F3269DE5B2620@phx.gbl> (raw)
In-Reply-To: <4DEFAC66.9000002@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]



I see.So it can be fixed by simply adding the first line before the second :\CHOOSERANDOM{""}\CHOOSERANDOM{"Maths", "Physics", "Algebra", "Analysis", "Chemistry", "Geometry", "Wave equation", "Schrödinger equation"}Thanks, that fixes one of my problems !


Mathieu



> Date: Wed, 8 Jun 2011 19:07:50 +0200
> From: pragma@wxs.nl
> To: ntg-context@ntg.nl
> CC: mathieudupont@hotmail.com
> Subject: Re: [NTG-context] Random selection of a word in a set with lua and mkiv
> 
> On 8-6-2011 7:00, Mathieu Dupont wrote:
> >
> >
> > This following code works, except that the first random is always the same (Analysis) for some reason.
> > Anyone knows why ?
> > \enableregime[il1]\starttext\startluacode	userdata = userdata or {}	math.randomseed( os.time() )	function userdata.random(...)		context(arg[math.random(1, #arg)])	end\stopluacode\def\CHOOSERANDOM#1{\ctxlua{userdata.random(#1)}}\dorecurse{10}{\CHOOSERANDOM{"Maths", "Physics", "Algebra", "Analysis", "Chemistry", "Geometry", "Wave equation", "Schrödinger equation"}\par}\stoptext
> 
> Because context remembers the seed (is reported in the log). Delete the 
> tuc file and you will get another value. We could get oscillation 
> otherwise.
> 
> 
> -----------------------------------------------------------------
>                                            Hans Hagen | PRAGMA ADE
>                Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>      tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>                                               | www.pragma-pod.nl
> -----------------------------------------------------------------
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 2710 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2011-06-08 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 16:52 Otared Kavian
2011-06-08 17:00 ` Hans Hagen
2011-06-08 17:00 ` Mathieu Dupont
2011-06-08 17:07   ` Hans Hagen
2011-06-08 17:19     ` Mathieu Dupont [this message]
2011-06-08 20:12   ` Otared Kavian
2011-06-08 20:48     ` 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=COL107-W3512A758BB9332F3269DE5B2620@phx.gbl \
    --to=mathieudupont@hotmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).