ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Burak Emir" <burak.emir@gmail.com>
To: "Hans Hagen" <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context minimal install problem? luatex bug?
Date: Sat, 7 Jun 2008 23:50:52 +0200	[thread overview]
Message-ID: <ac0ce270806071450h5dbae3a5waa54abfcd5fc18d2@mail.gmail.com> (raw)
In-Reply-To: <484B010D.8040209@wxs.nl>


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

On Sat, Jun 7, 2008 at 11:43 PM, Hans Hagen <pragma@wxs.nl> wrote:

>
>>> ...ex/texmf-context/scripts/context/lua/mtx-context.lua:563: attempt to
>>> index local 'ctxdata' (a nil value)
>>>
>>>
>> So ctxdata is not there ('a nil value')... if you look at line 563, you
>> see
>> (this line is not indented like the others):
>>
>>    563 ctxdata.flags.inputfile = filename -- is this right
>>
>
> ah, i was unaware of that bug being in the formal beta
>
> just comment that line
>
> (ctxdata is only there when there is a ctx file and i happen to have them
> around -)
>

Yay ... commenting the line worked. I see the "PDF Producer
luaTeX-0.25.3" now in the generated pdf.

Thanks!

I have the feeling I will find out what ctx files are good for one day :)

Burak

-- 
Burak Emir
--
http://burak.emir.googlepages.com

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

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

  reply	other threads:[~2008-06-07 21:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 11:23 Burak Emir
2008-06-07 11:55 ` Burak Emir
2008-06-07 12:15   ` Taco Hoekwater
2008-06-07 12:37     ` Burak Emir
2008-06-07 12:45       ` Burak Emir
2008-06-07 12:55         ` Taco Hoekwater
2008-06-07 12:59           ` Burak Emir
2008-06-07 13:18             ` Taco Hoekwater
2008-06-07 13:54               ` Burak Emir
2008-06-07 14:05                 ` Taco Hoekwater
2008-06-07 14:13                   ` Burak Emir
2008-06-07 14:17                     ` Taco Hoekwater
2008-06-07 14:44                       ` Burak Emir
2008-06-07 14:50                         ` Burak Emir
2008-06-07 16:27                         ` Jean Magnan de Bornier
2008-06-07 20:56                           ` Burak Emir
2008-06-07 21:09                             ` Burak Emir
2008-06-07 21:43                               ` Hans Hagen
2008-06-07 21:50                                 ` Burak Emir [this message]
2008-06-08 21:34                                   ` Hans Hagen
2008-06-07 21:29                             ` Mojca Miklavec
2008-06-07 12:01 ` Taco Hoekwater

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=ac0ce270806071450h5dbae3a5waa54abfcd5fc18d2@mail.gmail.com \
    --to=burak.emir@gmail.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).