ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matthew Huggett <mhuggett@zam.att.ne.jp>
Subject: Re: scite
Date: Tue, 30 Sep 2003 20:13:22 +0900	[thread overview]
Message-ID: <3F796552.1080904@zam.att.ne.jp> (raw)
In-Reply-To: <003701c3873d$b1efbf60$0100a8c0@vademecum>

Willi Egger wrote:

>  
>
>>At 01:12 30/09/2003 +0900, you wrote:
>>
>>    
>>
>>>I have the same trouble as Willi.  My SciTEUser.properties is definitely
>>>not being loaded.  If I put the import statements in my
>>>SciTEGlobal.properties, I get the ConTeXt menu items plus replacement of
>>>commands while I type.  However, there is no colouring and "compile"
>>>      
>>>
>calls
>  
>
>>>LaTeX.   Two questions:
>>>1) Can we use the ConTeXt stuff with the SciTE distribution from the main
>>>SciTE website, or must we use the one from Pragma?
>>>2) The standard SciTE distribution's SciTEGlobal.properties imports the
>>>main latex.properties.  Should we delete this?
>>>      
>>>
>>I wonder why the user props are not loaded, this file should be in you
>>Document And Setting \ SomeUserName path. If you open the file (options
>>menu) you can see in the heading where it is located
>>
>>Hans
>>    
>>
>
>I tried in the meantime again. The SciTEUser.properties file resides in the
>by Hans mentioned place.There are no other copies of this file in other
>directories. I have set the environment variable so that I am able to start
>sciTE from a cmd-window. The context.properties and the
>cont*-scite.properties files reside in the directory where sciTE.exe lives.
>The strange thing is, that after starting sciTE form the commandline I get
>the list of cont-"country"-scite.properties in the options dialog but there
>is no context.properties and also no metafun-scite.properties. Hence there
>are also no commands available as defined in context.properties.
>
>I am a bit puzzled.
>
>Willi
>  
>
Have you tried setting a "SciTE_HOME" environment variable.  I set it to 
the path of SciTE.exe, which is where I'm keeping all the properties 
files.  After setting this, my SciTEUser.properties was loaded (it 
contains only "import context" and "import metafun-scite").   I only had 
to edit the path to texexec and texutil in context.properties.  My only 
problem now is that I have no syntax highlighting.

  reply	other threads:[~2003-09-30 11:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 12:49 scite Hans Hagen
2003-09-29 15:40 ` scite Willi Egger
2003-09-29 16:12   ` scite Matthew Huggett
2003-09-30  8:07     ` scite Hans Hagen
2003-09-30 10:15       ` scite Willi Egger
2003-09-30 11:13         ` Matthew Huggett [this message]
2003-09-30 12:53           ` scite Willi Egger
2003-09-30 12:57           ` scite Hans Hagen
2003-09-30  9:55 ` scite Jules Colding
2003-09-30 10:20   ` scite Matthew Huggett
2003-09-30 10:30   ` scite Patrick Gundlach
2003-09-30 10:48     ` scite Jules Colding
2003-09-30 12:59       ` Hans Hagen
2003-09-30 14:46         ` context documentation Patrick Gundlach
2003-09-30 15:22           ` Hans Hagen
2003-09-30 15:51             ` Patrick Gundlach
2003-09-30 15:54             ` Patrick Gundlach
2003-09-30 16:13               ` Michael Hallgren
2003-09-30 20:14         ` Re: scite Jules Colding
2003-09-30 21:26           ` ConTeXt/Emacs Patrick Gundlach
2003-09-30  9:00 scite Matthew Huggett
2003-09-30  9:37 ` scite Hans Hagen
2003-09-30  9:52   ` scite Matthew Huggett
2003-09-30 13:01     ` scite Hans Hagen
2003-09-30 14:37       ` scite Willi Egger
2003-09-30 15:16         ` scite Matthew Huggett
2003-09-30 20:09         ` scite Willi Egger
2005-07-24 22:13 scite Hans Hagen
2005-07-25  5:11 ` scite Lutz Haseloff
2005-07-25 17:19 ` scite David Munger
2005-07-25 19:05   ` scite Hans Hagen
2005-07-25 20:38 ` scite Willi Egger
2007-08-16 12:21 Scite Wolfgang Werners-Lucchini
2011-11-17 18:28 scite Hans Hagen
2013-08-30 11:54 scite Hans Hagen
2018-08-21 15:24 scite Hans Hagen
2018-08-21 16:43 ` scite cryo shock
2018-08-21 16:51   ` scite cryo shock

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=3F796552.1080904@zam.att.ne.jp \
    --to=mhuggett@zam.att.ne.jp \
    --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).