My list of programming/scripting languages to learn is getting longer
and longer faster than I can cross them off... Are you aware of any
particular reason of using Lua for extending the IDE? Is SciTE perhaps
implemented in Lua itself?
Anyway, I'm afraid I'm one of those guys who never got around to using
Emacs beyond X-c and a couple of others (which I've gracefully
forgotten already a number of years ago) so I'm not that keen on
extending an IDE with macros etc.
Thanks for mentioning it, though. I wouldn't want my rather blunt
comparison between SciTE and notepad to stand between me and learning
about other IDE's...
-Lasse-
···
On Tue, 29 Mar 2005 22:17:23 +0900, Michel Martens <blaumag@gmail.com> wrote:
> > Lasse Koskela:
> > SciTE feels like coding with notepad
I'm yet another SciTE user, but what I have to say might be of your interest.
SciTE comes with an embedded Lua interpreter that allows the user to
create customized extensions. The API is good but slightly
undocumented. I managed to adapt the editor to my needs.
I asked about this on IRC, and now use the colour coding for regexes
out of the perl.xml file. There are some problems with ' and " in the
regex though. Also when putting #{} sections in the regex. But as a
basis, it is good.
<!-- jEdit 4.1 adds regular expression syntax rules so we can
highlight this sort of crap. -->
<SEQ_REGEXP TYPE="MARKUP"
HASH_CHAR="/"
AT_WORD_START="TRUE"
>/[^[:blank:]]*?[^\\]/</SEQ_REGEXP>
There is other good stuff in there too.
Douglas
···
On Thu, 31 Mar 2005 08:19:44 +0900, Florian Gross <flgr@ccan.de> wrote:
Rob . wrote:
> Florian, to fix the syntax highlighting problem in jEdit try
> installing this Ruby edit mode file (ruby.xml) into
> {install-dir}/jedit/modes/
> href="http://community.jedit.org/?q=filestore/download/2124
The Regexp rule still seems to be commented out:
> <!-- /regexp?/i -->
> <!-- This doesn't really work well, because it can't distinguish a regexp
> from multiple instances of the "/" division operator on the same line. -->
> <!-- <SEQ_REGEXP HASH_CHAR="/" AT_WORD_START="TRUE"
> TYPE="LITERAL3">/[^/]+/[iomx]*</SEQ_REGEXP> -->
Lothar Scholz wrote:
Hello Curt,
> The refactoring stuff is clearly labelled as "experimental" -- it is not
> production ready.
This raises the question if this project (RRB) is dead ?
I didn't see any progress in the last year.
Yeah, I was just thinking the same thing. Its pretty useless in its current state, and if it not being actively developed, then it should be removed from FreeRIDE.
Curt
Kind of: all the user configuration is handled by Lua.
Lua was first developed to be a language tailored to extend other
applications. The configuration files in SciTE are described in Lua.
The text editor has an embedded interpreter that handles user
configuration and provides an API (with several hooks) for writing
extensions. Writing an extension is as easy as it is to declare a
function in JavaScript, but without curly braces. More detail would be
slightly off topic, but if you want more just insist 
Michel.
···
On Wed, 30 Mar 2005 01:24:22 +0900, Lasse Koskela <lasse.koskela@gmail.com> wrote:
On Tue, 29 Mar 2005 22:17:23 +0900, Michel Martens <blaumag@gmail.com> wrote:
> > > Lasse Koskela:
> > > SciTE feels like coding with notepad
>
> I'm yet another SciTE user, but what I have to say might be of your interest.
>
> SciTE comes with an embedded Lua interpreter that allows the user to
> create customized extensions. The API is good but slightly
> undocumented. I managed to adapt the editor to my needs.
My list of programming/scripting languages to learn is getting longer
and longer faster than I can cross them off... Are you aware of any
particular reason of using Lua for extending the IDE? Is SciTE perhaps
implemented in Lua itself?
gabriele renzi wrote:
I can say I agree with the tooltip thing.
OTOH,"it crashes for me" is not very useful from a developer standpoint.
Well, it's better than nothing. Now the developer knows it's not just one person having problems, so it's less likely to be a site-specific issue, and also that it has happened with multiple versions, so it's more likely to be a fundamental bug, and also that it took me very little time to crash it, so they have a pretty good chance of duplicating it on their own.
Unfortunately, FreeRIDE is so unstable for me and so unenjoyable to use that I don't find it worth any extra time to dig into it. By contrast, I actually spent a fair amount of time on issues with the Eclipse RDT plugin authors because (1) it doesn't crash right away, and (2) it provides novel and interesting features in a pleasant-to-use environment.
···
--
Glenn Parker | glenn.parker-AT-comcast.net | <http://www.tetrafoil.com/>
Douglas Livingstone wrote:
I asked about this on IRC, and now use the colour coding for regexes
out of the perl.xml file. There are some problems with ' and " in the
regex though. Also when putting #{} sections in the regex. But as a
basis, it is good.
<!-- jEdit 4.1 adds regular expression syntax rules so we can
highlight this sort of crap. -->
<SEQ_REGEXP TYPE="MARKUP"
HASH_CHAR="/"
AT_WORD_START="TRUE"
>/[^[:blank:]]*?[^\\]/</SEQ_REGEXP>
There is other good stuff in there too.
Thanks, I added this. Still seems to fail with this Regexp, though:
/^(.+?):(\d+)(?::in `(.*?)')?/
As you said this is probably related to the space and the back tick.