ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt and SciTE
Date: Tue, 19 Jun 2012 10:58:40 +0200	[thread overview]
Message-ID: <4FE03F40.10909@wxs.nl> (raw)
In-Reply-To: <4FE005F1.1010602@gmail.com>

On 19-6-2012 06:54, Bill Meahan wrote:
> I'm trying to get the SciTE lexers that come with the ConTeXt
> distribution working but I'm not having much luck. SciTE certainly
> processes the ConTeXt start-up script but never does any highlighting.
>
> I always get the warning that lpeg is not loaded but I cannot find any
> separate lpeg.properties file or lpeg.lua file so I don't know how to
> get it imported and active to run the lexers. Any suggestions?
>
> Interestingly, the lexers work just fine in Textadept but I haven't
> quite figured out how to get them to load automatically. I have to
> manually select the lexer but it works fine once I do.
>
> I'm inclined to go the Textadept route and build a nice snippets file
> and Adeptsense support but I'd like to see things running in SciTE, too.

You have to change some configuration files but as that situation seems 
to change every now and then I wait with providing extra files for 
textadept till it's more stable.

(Textadept has no realtime log pane so I cannot use it here without 
sacrificing too much convenience.)

> Right now I'm using Emacs to do my editing but AUCTeX does a poor job of
> supporting ConTeXt and when I asked about future plans on the AUCTeX
> mailing list, I got a snarky, sarcastic reply that "code doesn't change
> itself." Typical FSF attitude, I see. If I'm going to have to write my
> own support, Lua is much closer to the languages I've used before than
> elisp so it should be considerably easier.
>
> Of course, I'll pass on anything I come up with to the ConTeXt community.

concerning scite ... on windows it boils down to

- installing scite
- copying the scintillua lexer dir to the wscite path
- copying the context/data/scite directory to teh wscite dir

on linux it's a bit more complex as you need to figure out where scite 
keeps its properties files and that's sort of hard coded in the binary

(but it does work on linux)

on osx it's not working as there is no lpeg support provided there 
(unfortunately)

Hans


-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------


___________________________________________________________________________________
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:[~2012-06-19  8:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  4:54 Bill Meahan
2012-06-19  8:58 ` Hans Hagen [this message]
2012-06-19 16:48   ` Bill Meahan
2012-06-19 17:28     ` Hans Hagen
2012-06-19 20:17       ` Bill Meahan
2012-06-19 20:43         ` Hans Hagen
2012-06-19 21:27           ` Bill Meahan
2012-06-19 21:57             ` Hans Hagen
2012-06-20 16:37               ` Bill Meahan
2012-06-20 18:02                 ` Hans Hagen
2012-06-20 18:44                   ` Hans Hagen
2012-06-20 18:59                     ` Bill Meahan
2012-06-20 19:05                   ` Bill Meahan
2012-06-20 19:32                     ` Hans Hagen
2012-06-20  3:04   ` Bill Meahan
2012-06-20 14:24     ` Hans Hagen
2012-06-20 14:46       ` luigi scarso
2012-06-20 15:24       ` Aditya Mahajan
2012-06-20 16:11         ` Bill Meahan
2016-04-19  7:10 uppercase, small caps, numerals and German capital sharp s Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-20 14:03   ` Thomas Fehige
2016-04-20 14:25     ` Wolfgang Schuster
2016-04-22 11:35       ` glyph substitution Thomas Fehige
2016-04-22 20:28         ` Hans Hagen
2016-04-25 12:48           ` Thomas Fehige
2016-04-25 18:12             ` Thomas Fehige
2016-04-25 20:44               ` Wolfgang Schuster
2016-04-27 14:27                 ` Thomas Fehige
2016-04-27 15:10                   ` Hans Hagen
2016-04-29  8:38                     ` Test Suite Fonts "extensions-001" Thomas Fehige
2016-04-29  9:05                       ` Wolfgang Schuster
2016-05-03  9:22                         ` Setting up TeXworks Thomas Fehige
2016-05-06  8:04                           ` Mojca Miklavec
2016-05-07 10:49                             ` Thomas Fehige
2016-05-09 11:02                               ` Thomas Fehige
2016-05-15 19:29                                 ` Thomas Fehige
2016-05-16 14:34                                   ` ConTeXt and Scite Thomas Fehige

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=4FE03F40.10909@wxs.nl \
    --to=pragma@wxs.nl \
    --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).