Not knowing anything about SCiTE's api files, or anything much really,
but weird things happening with question marks is usually because
there's a regex somewhere where a questionmark isn't escaped.
I'm also guessing that when SCiTE references the api files, it uses the
same matching rules that it uses when doing the syntax highlighting. The
syntax highlighting of ruby in SCiTE is less than perfect... including
the fact that a question mark at the end of a method definition is not
highlighted as part of the method name.
ยทยทยท
-----Original Message-----
From: Matt Smith [mailto:matthewgarysmith@gmail.com]
Sent: Thursday, 6 October 2005 6:37 AM
To: ruby-talk ML
Subject: question marks in ruby.api for SCiTE
I created a ruby.api for SCiTE, so I can have autocomplete and calltips,
but I'm having a little problem.
The autocomplete and calltips don't work for any of the methods that end
with a question mark (like Array.include?). The autocomplete truncates
everything after the '?' and the calltips are non-existant.
Anyone have any insight/fixes for this problem?
- matt
#####################################################################################
This email has been scanned by MailMarshal, an email content filter.
#####################################################################################