Re: SciTE Python autocompletion add on syntax error

fogus:

> The folks at #python (irc.freenode.net) have confirmed a syntax error
> in: http://scintilla.sourceforge.net/gen_python_api.zip (found on
> http://wiki.python.org/moin/PythonEditors ).  I get a syntax error
> while running it under python 2.6, but others confirmed that it is not
> compliant with 3.0 or 1.x.

   The way that this program works is somewhat dangerous as it tries
to import (and thus run) anything it can find. It crashes for me but
does produce some output if you just avoid trying to examine 'print'
as a function since for Python 2.6 'print' is a keyword as well as a
builtin function. One way to do this is to add a check
        if builtin != 'print':
in the add_builtins branch.

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

Re: SciTE Python autocompletion add on syntax error

Are you saying that doing:

>         if builtin != 'print':
> in the add_builtins branch.

will fix the problem and give me the python API?

On Jul 31, 8:46 pm, Neil Hodgson <nyamaton...@gmail.com> wrote:
> fogus:
>
> > The folks at #python (irc.freenode.net) have confirmed a syntax error
> > in:http://scintilla.sourceforge.net/gen_python_api.zip(found on
> >http://wiki.python.org/moin/PythonEditors).  I get a syntax error
> > while running it under python 2.6, but others confirmed that it is not
> > compliant with 3.0 or 1.x.
>
>    The way that this program works is somewhat dangerous as it tries
> to import (and thus run) anything it can find. It crashes for me but
> does produce some output if you just avoid trying to examine 'print'
> as a function since for Python 2.6 'print' is a keyword as well as a
> builtin function. One way to do this is to add a check
>         if builtin != 'print':
> in the add_builtins branch.
>
>    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

Folding plaintext like python

Hello.
I would like to fold plain text documents (and possibly others) just
like python is folded.  How can this be configured?
Note: I do not want to fold like this: http://lua-users.org/wiki/SciteTextFolding
(see also http://writing.hed854.net/2007/11/text-folding-in-scite.html
)

How can I do this?

Also, my Python file has the following:
---
statement.indent.$(file.patterns.py)=5 shdghgjghjkSFGHCFGH \
hjfghjghjkghkljhlhddwwgbnn

statement.lookback.$(file.patterns.py)=0
block.start.$(file.patterns.py)=
block.end.$(file.patterns.py)=
---

Can someone explain that to me?  What does shdghgjghjkSFGHCFGH
hjfghjghjkghkljhlhddwwgbnn do specifically?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Re: Folding plaintext like python

fogus:

> Can someone explain that to me?  What does shdghgjghjkSFGHCFGH
> hjfghjghjkghkljhlhddwwgbnn do specifically?

   It makes no sense to me.

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

Re: SciTE Python autocompletion add on syntax error

fogus:

> Are you saying that doing:
>
>>         if builtin != 'print':
>> in the add_builtins branch.
>
> will fix the problem and give me the python API?

   I am saying it may help but may not be the whole answer.

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

Re: full featured lexer template

You know, that sounds similar to what I want.  I also want a lexer
template with, say 10 different keyword categories, customizable
folding, customizable function/class name definitions, etc.  A fully
functional template.  I would like to be able to just copy and name
the lexer something else, say "foo", grab *.foo files and interpret
them with my new foo lexer.

How can SciTE be "fully customizable" unless it can support new lexers
being added without source code modification?

On Jul 23, 3:30 pm, xtian <xtian.stra...@gmail.com> wrote:
> Ouch, where ever I say python below, I really mean povRay.
>
> On Jul 23, 3:29 pm, xtian <xtian.stra...@gmail.com> wrote:
>
> > I've been hacking at existing lexers for a long time now and would
> > love to see one of the full featured lexers such as python get opened
> > up a little.
>
> > python has a bunch of nice features but many of them are baked into
> > the python api.  It would be really cool if the python-specific stuff
> > that's baked in the api (comments and such) were exposed in the
> > properties file instead.  thus making something like:
>
> > template.properties
>
> > That combined with comments in the template properties file would be
> > really cool.  I already have a custom properties with many of the
> > comments in place - would be happy to clean it up and donate it if the

Re: Folding plaintext like python

On Saturday 01 August 2009 07:03:00 pm Neil Hodgson wrote:
> fogus:
> > Can someone explain that to me?  What does shdghgjghjkSFGHCFGH
> > hjfghjghjkghkljhlhddwwgbnn do specifically?

I think it is just dummy text--he doesn't want to show the real text 
here because it is confidential, so he's just saying something 
like "blah blah blah" or foo, bar, baz.

Randy Kramer
--

-- 
I didn't have time to write a short letter, so I created a video 
instead.--with apologies to Cicero, et.al.

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

Re: full featured lexer template

fogus wrote:
> You know, that sounds similar to what I want.  I also want a lexer
> template with, say 10 different keyword categories, customizable
> folding, customizable function/class name definitions, etc.  A fully
> functional template.  I would like to be able to just copy and name
> the lexer something else, say "foo", grab *.foo files and interpret
> them with my new foo lexer.

You can already do this using property files if language XYZ is 
quite similar to language ABC. On keyword categories, you can 
offer your extended keyword list support as patches to improve 
Scintilla.

> How can SciTE be "fully customizable" unless it can support new lexers
> being added without source code modification?

You're being pedantic with words.

Send in a patch. Show us the code. Make that magical lexer and 
show it to us, and we will treat you like a code God. 

Seriously, most F/LOSS software are very resource-constrained. 
When a user suggests something, the community can't jump up, drop 
everything, and implement it. Everyone is busy with other things. 
Those of us who are on many mailing lists won't even reply to most 
e-mails.

So the surest way of effecting change is to make it happen 
yourself. I realize this is hard for non-developers, but lack of 

Re: Folding plaintext like python

fogus wrote:
> Hello.
> I would like to fold plain text documents (and possibly others) just
> like python is folded.  How can this be configured?
> Note: I do not want to fold like this: http://lua-users.org/wiki/SciteTextFolding
> (see also http://writing.hed854.net/2007/11/text-folding-in-scite.html
> )

The trouble with your request is that if other people insist on 
folding text files exactly the way they want, but differently, 
then we might end up with fistfights.  

Someone is doing a lexer for reStructured text, which is very 
close to wiki source. This might be more to your taste.

Yes, a script-customizable thingy can solve all of this. But 
someone has to write it first...

> [snip snip]

--

-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia

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

MediaWiki wiki markup language properties file