Re: SciTE editor

Don't sweat it Philippe; I think our little corner of the
open source nusphere has just graduated: it has reached the
point where the discussion forums have begun to attract
trolls.  Ah, nirvana!

Nevertheless, perhaps the first few comments might have some
legitimacy?

Cheers,
Bruce

Re: gtk 2 unicode character input question

   Hi John,

   Here are some of the failure messages.

   Neil

----------------------------------------------------------------
Krzysiek:
----------------------------------------------------------------
After some time, I've finaly gave up. I can't force SciTE to NOT to use UTF.
I
want plain ISO-8859-2 text. Screen shot of the situation is available here:

http://fatcat.ftj.agh.edu.pl/~nelchael/scite_enc.png

The second editor is KWrite from KDE. My config:

code.page=0
character.set=238

If I got it right from docs: setting code.page to 0 disables Unicode, am I
correct? So how to tell SciTE not to use Unicde, but use one byte encoding?

----------------------------------------------------------------
One more thing: I've checked and the problem isn't present in 1.57, and I'm
almost sure it's due to the:

"International input enabled on GTK+ 2 although there is no way to choose an
input method." [ 1.58 Changelog ]

Scintilla 1.60 released

   Scintilla 1.60 is now available from the scintilla.org web site.

   Scintilla 1.60 can display continuation markers on wrapped lines. Lexers
were added for Gui4Cli, Kix, Specman E, AutoIt3, APDL, and Bash languages.
Input method preedit window on GTK+ 2 may support some Asian languages.
Scintilla can be built for GTK+ 2 on Windows.

   Minor features and bugs fixed including some crashing bugs with display
code, AMD64 processors, and long text on GTK+ with X fonts.

   A detailed list of changes is available on the history page.

   Thanks to the contributors of code and documentation and to the testers.

   Neil

Re: Scintilla 1.60 released

Am 1 May 2004 um 22:37 hat Neil Hodgson geschrieben:

> 
>    Scintilla 1.60 can display continuation markers on wrapped lines.
>

Hello Neil,

Thank you very much for the update. But how can I enable the 
continuation markers with my LaTeX files? I checked the docs but I 
did not find any hints.

Kind regards
Albert
--

-- 
Dr. Albert Kapune
Brunnenstrasse 1
D-59514 Welver-Nateln
TELEFON: (02384) 911012
TELEFAX: (02384) 911011

Re: Scintilla 1.60 released

Hi Albert,
Simply uncomment some/all of the entries in sciteglobal.properties or copy
them to your user properties file:

wrap.visual.flags=3
3 -> markers at both sides of wrapped lines

wrap.visual.flags.location=3
3 -> both markers near text (default near border)

wrap.visual.startindent=4
4 -> extra indent of 4 spaces on start continuation of wrapped lines
(default no extra indent)

This should be in the Scite doc.

Wrapping option must be enabled and you must have long lines which are
actually wrapped to see the markers.

--
Hans

----- Original Message -----
From: "Albert Kapune" <akapune <at> gmx.de>
To: "Discussion of the Scintilla editing component"
<scintilla-interest <at> lyra.org>
Sent: Saturday, May 01, 2004 7:21 PM
Subject: Re: [scintilla] Scintilla 1.60 released

>

Re: Scintilla 1.60 released

Am 1 May 2004 um 21:45 hat Hans geschrieben:

> Simply uncomment some/all of the entries in sciteglobal.properties or
> copy them to your user properties file:
> 
> wrap.visual.flags=3
> [...]

Hallo Hans, 

thank you very much for your hint. Now it works.

> 
> This should be in the Scite doc.

I always searched for "continuation" and not for "wrap".


Kind regards
Albert

--

-- 
Dr. Albert Kapune
Brunnenstrasse 1
D-59514 Welver-Nateln
TELEFON: (02384) 911012
TELEFAX: (02384) 911011

Re: Scintilla 1.60 released

On Sat, 2004-05-01 at 14:37, Neil Hodgson wrote:
> Scintilla can be built for GTK+ 2 on Windows.
Hmm! I'm doing it with 1.57, can I face any problem ??

Just to address the update as urgent or critical.

Thanks in advance for your response.
--

-- 
Iago Rubio   
- Home page    * http://www.iagorubio.com 
- Last project * http://cssed.sourceforge.net         
- GPG Keyserv  * pgp.rediris.es id=0x909BD4DD

_______________________________________________
Scintilla-interest mailing list
Scintilla-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scintilla-interest

Re: Scintilla 1.60 released

Iago Rubio:

> On Sat, 2004-05-01 at 14:37, Neil Hodgson wrote:
> > Scintilla can be built for GTK+ 2 on Windows.
> Hmm! I'm doing it with 1.57, can I face any problem ??
>
> Just to address the update as urgent or critical.

   AFAIK, no one worked on or tested Scintilla for GTK+ 2 on Windows until
John Ehresman for version 1.60. If you managed to get Scintilla 1.57 to
build and run then you were lucky. By GTK+ 2 on Windows, I mean the Windows
port of GTK+ 2, not running an X server on Windows.

   Neil

Re: SetWordChars in wxPython

Peter Parente:

> It appears that SetWordChars doesn't work in the latest version of the
> wxStyledTextControl in wxPython 2.5. After setting the word chars to
> just the letters (not _ and 0-9 like the default) the WordStartPosition
> and WordEndPosition functions still count the excluded characters as
> part of a word.
>
> Has any else seen this behavior or am I doing something wrong?

   This is a fairly serious regression first present in Scintilla 1.57 that
was caused by allowing changing the set of white space characters. The
SetWordChars method first resets the character classifications to a
reasonable default and then sets all the argument characters to ccWord.
There is no mechanism to change characters to ccPunctuation (or ccNewLine),
only ccWord or ccSpace.

   Could be solved by adding a way to set some characters to be punctuation.
Or by treating all characters not in the argument as punctuation. The latter
would preserve expected behaviour for more containers.

   Neil

Re: [ scintilla-Support Requests-945616 ] Can't execute command with SciTE

SourceForge.net wrote:
> Support Requests item #945616, was opened at 2004-04-30 14:25
> Summary: Can't execute command with SciTE
> 
> Using Windows 2000 - SciTE 1.59
> =========================
> Hi, I've used the config files to run a command for my 
> file types.
> 
> I've done some tests but I don't quite understand.
> 
> 1) I've tried to do any command just to execute it.
> 
>   command.go.*.asb=dir
>   command.go.subsystem.*.asb=1
> 
>    When I do "go", I get the following:
>   The system cannot find the file specified.

dir is an internal command of the command prompt program.
You must type something like:
command.go.*.asb=cmd /c dir
/c is "execute given command and quit".
On Win9x, it must be something like "command /c dir".

> 2) I've tried something else.
> 
>   command.go.*.asb=start /?
>   command.go.subsystem.*.asb=1
>