headers
Neil Hodgson | 2 Jan 08:20
Picon

Re: Incremental SciTE autocompletion


Sergey Kishchenko:

> New version can be found here :
> http://groups.google.com/group/scite-interest/web/incremental_autocompletion_v3.tar.gz
> It consists of
> 1. Incremental word autocompletion(autocompleteword.automatic=1 and
> autocompleteword.automatic=2)
> 2. Incremental symbol autocompletion (autocomplete.automatic=1 and
> autocomplete.automatic=2)
> 3. Docs patch

   Looks like it still doesn't cope with scripted autocompletion lists.

   To test with scripted autocompletion you can add to your startup
script something like:

function ShowList()
	editor:AutoCShow(1, "abc bbb def")
end

   Then in user properties:

command.name.5.*=ShowList
command.5.*=ShowList()
command.subsystem.5.*=3

   Then restart SciTE.

> 4. gtk makefile patches (I use `make DEBUG=1 TRACE=1` for tracing)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Neil Hodgson | 3 Jan 01:12
Picon

Re: hypertext lexer folding bug?


Jingcheng Zhang:

> Maybe so, but when I'm editing on the first page, and I want to refer
> to codes on the last page with many page codes between them, this
> behavior brings me some trouble as I have to fold the codes between
> them again whenever I want to add a string or comment. As I mentioned
> above, Python lexer does allow inserting a quote character without
> expanding the folded codes.

   Python doesn't allow single quoted strings to go over the line end
so changes the style to StringEOL (an error state) and then goes back
to the default style for the next line. If single quoted strings can't
continue past a line end in PHP then you could change the lexer to
recognise this. The idea of StringEOL styles is not universally loved.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 3 Jan 01:19
Picon

Re: hypertext lexer folding bug?


Frank Wunderlich:

> but the following seems to be a bug (overlapping fold points):
> ...

   There are only fold levels - increments and decrements are not
tagged with any sort of type. If you want different behaviour then try
to describe just what you want.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
sek | 4 Jan 20:00
Picon

parrot.propeties


Hi,

I created a property file for parrot.
It allows you to use SciTE for developping programs written in PIR and
PASM.
Various compilation modes are supported as well as debugging.
I also added integration of the following High Level Languages :
Javascript, Lua, Perl, Python, Ruby.

For the moment it is Windows only and uses the Python lexer but I plan
to add GTK support and implement a real parrot lexer.

Give it a try and comments are welcome.

Sekou.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 1 comment |
headers
sek | 4 Jan 20:04
Picon

Re: parrot.propeties


You can downoad it here.
http://groups.google.com/group/scite-interest/web/parrot_properties.zip

Sekou

On Jan 4, 8:00 pm, sek <sekou.d...@gmail.com> wrote:
> Hi,
>
> I created a property file for parrot.
> It allows you to use SciTE for developping programs written in PIR and
> PASM.
> Various compilation modes are supported as well as debugging.
> I also added integration of the following High Level Languages :
> Javascript, Lua, Perl, Python, Ruby.
>
> For the moment it is Windows only and uses the Python lexer but I plan
> to add GTK support and implement a real parrot lexer.
>
> Give it a try and comments are welcome.
>
> Sekou.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Hobbs | 5 Jan 15:39

Forcing default to monospace font


I've changed SciTEGlobal.properties, html.properties to make
everything default to monospace font but it does not work.
Every time I load a text or html file it defaults to sans
serif but not monospace. I have to select "Use monospace font"
on the menu EVERY time to get monospace font.
How do I get it to ALWAYS default to monospace?

Mike

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 2 comments |
headers
Philippe Lhoste | 5 Jan 18:43
Picon

Re: Forcing default to monospace font


On 05/01/2009 15:39, Mike Hobbs wrote:
> I've changed SciTEGlobal.properties, html.properties to make
> everything default to monospace font but it does not work.

What have you changed, exactly?

> Every time I load a text or html file it defaults to sans
> serif but not monospace. I have to select "Use monospace font"
> on the menu EVERY time to get monospace font.
> How do I get it to ALWAYS default to monospace?

You have to change style.*.32 to change default (eg. no selected lexer), and the styles in 
the properties file of the lexers you use. Use variables to add flexibility, or just 
remove the font: declarations to use default.

--

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Hobbs | 7 Jan 10:52

Re: Forcing default to monospace font


In message <gjtgrq$uds$1 <at> ger.gmane.org>
          Philippe Lhoste <PhiLho <at> GMX.net> wrote:

> On 05/01/2009 15:39, Mike Hobbs wrote:
>> I've changed SciTEGlobal.properties, html.properties to make
>> everything default to monospace font but it does not work.

> What have you changed, exactly?
In SciTEGlobal.properties originally "font:!Bitstream Vera Sans" but
I added in "Mono" (copying the font.monospace assignment):
if PLAT_GTK
     font.base=font:!Bitstream Vera Sans Mono,size:9
     font.small=font:!Bitstream Vera Sans Mono,size:8
     font.comment=font:!Bitstream Vera Sans Mono,size:9
     font.text=font:!Bitstream Vera Sans Mono,size:9
     font.text.comment=font:!Bitstream Vera Sans Mono,size:9
     font.embedded.base=font:!Bitstream Vera Sans Mono,size:9
     font.embedded.comment=font:!Bitstream Vera Sans Mono,size:9

In html.properties wherever there was a line of the form
style.hypertext.0=fore:#000000,$(font.text)
I changed it to the form...
style.hypertext.0=fore:#000000,$(font.monospace)
(in 13 places)

I also tried the example in the FAQ by adding the following to
SciTE.properties:
font.base=$(font.monospace)
font.small=$(font.monospace)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sergey Kishchenko | 8 Jan 16:48
Picon
Gravatar

Re: Incremental SciTE autocompletion


On 2 янв, 09:20, "Neil Hodgson" <nyamaton...@gmail.com> wrote:
>    Looks like it still doesn't cope with scripted autocompletion lists.
>
>    To test with scripted autocompletion you can add to your startup
> script something like:
>
> function ShowList()
>         editor:AutoCShow(1, "abc bbb def")
> end
>
>    Then in user properties:
>
> command.name.5.*=ShowList
> command.5.*=ShowList()
> command.subsystem.5.*=3
>
>    Then restart SciTE.

I tried this feature and I didn't find any bugs related to the patch.
Patched SciTE acts the same as the original SciTE. What kind of
problems with scripted autocompletion do you have?

> > 4. gtk makefile patches (I use `make DEBUG=1 TRACE=1` for tracing)
>
>    Don't want this.
Ok.

> > 5. 'Annoying extra backspace to cancel autocompletion' fixed
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Neil Hodgson | 8 Jan 23:10
Picon

Re: Incremental SciTE autocompletion


Sergey Kishchenko:

> I tried this feature and I didn't find any bugs related to the patch.
> Patched SciTE acts the same as the original SciTE. What kind of
> problems with scripted autocompletion do you have?

   There is a bit of global state associated with the 'only one' mode.
If you cancel (with Esc) from an 'only one' popup, I think that state
persists so when you use backspace on the scripted autocompletion it
replaces the autocompletion with a list of similar words, just as if
it was invoked for that purpose rather than by the script. Any state
changed by entering an 'only one' popup should be cleared when it goes
away for any reason or else the code that responds to the backspace
needs to work out why the autocompletion was shown.

   Neil

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "scite-interest" group.
To post to this group, send email to scite-interest <at> googlegroups.com
To unsubscribe from this group, send email to scite-interest+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/scite-interest?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |

Gmane