From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Lars <axteffekt@gmail.com>
Subject: Re: Textadept with ConTeXt
Date: Tue, 21 Aug 2018 09:06:33 +0200 [thread overview]
Message-ID: <2fde2de9-3318-dcaf-7ee8-3c1089d1d7a3@xs4all.nl> (raw)
In-Reply-To: <e152be80-4afd-f497-2ee1-aa1182437e1f@gmail.com>
On 8/21/2018 1:59 AM, Lars wrote:
> Hi there, thanks for your interest in Textadept. It's a great editor and
> I am sure that you won't regret testing it and using it in the future.
> Just have some patience.
i played with it a few times but its biggest drawback is the lack of a
fast and realtime console pane like scite has so i keep coming back to
scite (on the contrary scite has the lpeg lexer extern and its lua is
not shared with scites lua which is a drawback there) .. so currently i
see ta as a fallback
in the context distrubution there are actually files for textadept but
because its (still?) a moving target with a changing interface i'm not
sure if it works with the latest (it's btw one reason why the files that
ship with context basically reset a lot of the fetaures because as usual
with editors, they tend to add lots of key bindings and stuff not needed
for tex and friends)
anyway,
../context/data/textadept/context/textadept-context.cmd
../context/data/textadept/context/textadept-context.sh
still work on my machine so ... it's kind of providing the same
functionality as we use in scite.
> *Fifth, is your context lexer loaded when you compile the file?* Check
> the status bar in the lower right corner. If it doesn't say "context"
> but "latex" or "text" or anything like that, then choose the context
> lexer via "Buffer" -> "Select lexer...".
the lexer that we use in scite and textadept both use the textadept
lexer dll (which plugs into scintilla) but because the lua code that
came with it kept changing and i needed way better performance (for
large files like char-def) than was possible at that time i also rewrote
that code for our purpose (also because i wanted spell checking, utf
and such) ...
at some point the ta lexing method changed a bit so it became faster ...
all such such lexers sort of follow the same approach, mark regions and
associate them and we already had similar stuff on board in context so i
could combine things a bit
i think that the scite/ta lexers that we ship are quite ok (i've now
used them for years) and they are probably better than the context lexer
that comes with textadept, i.e. the context one supports a mix of tex,
mp, lua etc, knows primitives, commands, helpers, and follows up on the
way we have had syntax highlighting for decades which in turn closely
relates to the way the context user interface evolved
notepad++ does use the same scintilla editing framework but cannot load
the lexer dll; it does bidi a bit better
anyway, with both scite and ta i can gamble on two horses
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-08-21 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 22:55 Fabrice Couvreur
2018-08-20 23:59 ` Lars
2018-08-21 7:06 ` Hans Hagen [this message]
2018-08-21 7:36 ` cryo shock
2018-08-21 8:33 ` cryo shock
2018-08-21 8:58 ` Hans Hagen
2018-08-21 9:32 ` Fabrice Couvreur
2018-08-21 13:55 ` Jan U. Hasecke
2018-08-21 14:14 ` 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=2fde2de9-3318-dcaf-7ee8-3c1089d1d7a3@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=axteffekt@gmail.com \
--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).