ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Zillig <wolfgang.zillig@student.kuleuven.be>
Subject: Re: Scite problems after update of Scite
Date: Thu, 01 Dec 2005 10:27:09 +0100	[thread overview]
Message-ID: <438EC1ED.7060905@student.kuleuven.be> (raw)
In-Reply-To: <438E2379.8080107@wxs.nl>

Hans Hagen schrieb:

> Wolfgang Zillig wrote:
>
>> 1. when starting scite i get an error: attempt to call a string value
>>  
>>
>>> Lua: error occurred while loading startup script
>>>   
>>
>>
>> I assume this is due to "import scite-ctx" and in that file there is
>> "ext.lua.startup.script=$(SciteDefaultHome)/scite-ctx.lua" which I don't
>> have.
>>
>> My solution: I commended "import scite-ctx" out
>>  
>>
> ah, i see, i forget to copy the lua script into the zip; attached
>
> watch the lof pane for some info at startup
>
> (spell checking in tex and xml files only works when you have at the 
> top of the file something
>
> % language=uk
>
> as well as a spell check list defined in the properties files [one 
> word per line in such a file])
>
thanks, that is solved

>> 2. When I try to compile a file then I get the message: ">texmfstart
>> newtexexec.rb --autopdf --pdf to_do.tex
>>  
>>
>>> The system cannot find the file specified."   
>>
>> When I try the command:"texmfstart newtexexec.rb --autopdf --pdf
>> to_do.tex" in the command line I get the file compiled without any
>> problems. I absolutely don't have an idea whats going wrong here.
>>
>>  
>>
> looks like some file association problem; the is a zip with a binary 
> of texmfstart at the web site
>
> did you set up a file association?
>
> FTYPE LuaScript=c:\data\system\lua\bin\lua.exe %%1 %%*
> ASSOC .lua=LuaScript
>
do I need Lua installed on my computer?

>> 3. all text and context commands are in black and white. Is there a
>> chance to get color back?
>>  
>>
> looks like some messed up properties file ... are you sure that there 
> is no conflicting local prop file?
>
That was probably the case, but I couldn't locate my error completely, 
after some time and some changes it worked again!

Hans, thank you very much!

Wolfgang

  reply	other threads:[~2005-12-01  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 16:56 update Hans Hagen
2005-11-30 21:03 ` Scite problems after update of Scite Wolfgang Zillig
2005-11-30 22:11   ` Hans Hagen
2005-12-01  9:27     ` Wolfgang Zillig [this message]
2005-12-01 10:56       ` Hans Hagen
2005-12-01 12:22         ` Wolfgang Zillig
2005-12-05 10:55           ` Hans Hagen
2005-12-05 12:36             ` Wolfgang Zillig
2005-12-02  8:43     ` ConTeXt 2005.12.01 (Scite problems) 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=438EC1ED.7060905@student.kuleuven.be \
    --to=wolfgang.zillig@student.kuleuven.be \
    --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).