Re: Version 1.79 soon

   A couple more minor updates to the Perl and CAML lexers.

   The Perl change fixes bug #2809168 where making some particular
changes would get the styling in a state where it would not be
automatically fixed when the change was undone.

   The CAML lexer now also supports the SML language (determined by
the presence of 'andalso' in the set of keywords) and fixes some bugs.

   If no new problems are found, this will be released as 1.79 tomorrow 2/July.

http://www.scintilla.org/scite.zip Source
http://www.scintilla.org/wscite.zip Windows executable

   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: Request about the documentation

Christophe (and all),

(Intentionally top posting, and leaving old information below in case 
you need to refer to it.)

Just wondered if you had a chance to look at the link, maybe even try 
it, and your reaction?

As I mentioned, it doesn't seem to be the "put this line of code here in 
this file, this line of code there in that file", kind of clear 
instructions that would help me, and I guess that's what hung me up.  I 
suspect it may be the same for you?

Maybe there is somebody out there who could carry the example a little 
further by going that far?  (And confirming that the example still 
works?)

Randy Kramer

On Monday 29 June 2009 01:19:17 pm Randy Kramer wrote:
> On Monday 29 June 2009 12:13:15 pm Christophe wrote:
> > Randy Kramer a écrit :
> > > I've actually seen a simple example somewhere--and when I have
> > > time, hopefully later today, I'll dig it out and send you the
> > > link. (There is a chance that the example is old enough that it
> > > no longer works--I haven't got as far as trying it so far.)
> >
> > That would be great to have a complet but simple example. I'm
> > impatient to see your link....

1.79 downloads

   I created a 1.79 release for both Scintilla and SciTE 1.79 on
SourceForge but they aren't visible to users. Possibly this is just a
temporary synchronization delay or it could be that SourceForge's new
design has problems.

   For now, the files can be downloaded from

Scintilla source
http://www.scintilla.org/scintilla179.tgz
http://www.scintilla.org/scintilla179.zip

SciTE
http://www.scintilla.org/scite179.tgz source
http://www.scintilla.org/scite179.zip source
http://www.scintilla.org/Sc179.exe Windows single executable file
http://www.scintilla.org/wscite179.zip Windows executable with support files
http://www.scintilla.org/gscite179.tgz GTK+ Linux executable with support files

   If the files still aren't accessible from SourceForge tomorrow,
I'll update all the download links.

   Neil

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

Scintilla 1.79 released

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

     The most important change in this release is that Scintilla may no
longer crash the process when memory is exhausted. However, if memory is
exhausted while performing an operation within Scintilla, the internal
data structures may be left in an inconsistent state which may cause a
crash later. Scintilla reports memory exhaustion and other exceptions
through the SCI_GETSTATUS API. Application developers should decide on a
strategy to deal with a non-OK status. The safest thing to do is
probably to save modified buffers to a recovery directory since saving
them to their original file could cause loss if the buffer has been
corrupted. Scintilla must now be compiled with exception handling turned on.

     A platform layer for Cocoa on Mac OS X is included.

     Deprecated APIs have been removed. These have not been included by
default for years and required explicit enabling so this change should
not cause problems. The symbols removed are

	SCI_SETCARETPOLICY
	CARET_CENTER
	CARET_XEVEN
	CARET_XJUMPS
	SC_FOLDFLAG_BOX
	SC_FOLDLEVELBOXHEADERFLAG
	SC_FOLDLEVELBOXFOOTERFLAG
	SC_FOLDLEVELCONTRACTED
	SC_FOLDLEVELUNINDENT
	SCN_POSCHANGED

Font quality

    The wxWidgets implementation of Scintilla wxStyledTextCtrl has an
additional parameter 'extraFontFlag' which appears to be used to
determine whether to enable font anti-aliasing. A request
(https://sourceforge.net/tracker/?func=detail&atid=352439&aid=2812250&group_id=2439)
has recently been made to add some way to force ClearType font
anti-aliasing mode on Windows. Other platforms may have similar
settings.

   It would help interoperability and minimize code if a single
mechanism was defined for these settings. The Windows feature used to
control this is called quality (see LOGFONT:
http://msdn.microsoft.com/en-us/library/dd145037%28VS.85%29.aspx) and
takes a value from an enumerated set. Scintilla could expose a similar
concept, replacing extraFontFlag and allowing a set of
platform-independent values (default, no-anti-alias, anti-alias,
lcd-specific) which would be passed through to the closest platform
equivalent along with any needed platform-specific values.

   Neil

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

Re: Discontiguous selection and virtual space

    Committed the new selection code to CVS. Made work on GTK+. Use
the position of the caret for features like the Input Method Editor
(input for languages like Japanese) even when the caret is in virtual
space.

   Available from CVS and from

http://www.scintilla.org/scite.zip Source
http://www.scintilla.org/wscite.zip Windows executable

   Neil

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

Scintilla and PyQt

Hello,
I'm trying to implement a very simple lexer but I don't know how to 
start. Ther is no Python example showing how to use 
Qsci.QsciLexerCustom. I would want to do a lexer which would ....

    1. ... put in red all line which begins with a  #

    2. ... put in blue only the word "blue"

    3. ... make a folding with something starting with  /*  and ending
    with  */

Best regards.
Christophe

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

# -*- coding: utf-8 -*-
#!/usr/bin/env python

import sys
from PyQt4 import QtCore, QtGui, Qsci
from window_LecteurCodePython_HTML import Ui_window_LecteurCodePython_HTML

Re: Discontiguous selection and virtual space

Re: Discontiguous selection and virtual space

haimag ren:

> Not take into account backspace operation at start of line.

   While the most commonly wanted behaviour is to not apply backspace
at line start, there are use cases for allowing it. Say I have a
directory listing and want to turn it into a list, the following set
of images show the sequence:

1) Initial listing
2) Select start of lines
3) Backspace removes line ends to make a single line
4) Type ", " to make a list

   Unsure what to do here as it its not really something I'd want to
be a global default, more a per-action choice.

   Neil

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

Re: Discontiguous selection and virtual space

On 04/07/2009 02:00, Neil Hodgson wrote:
> 1) Initial listing
> 2) Select start of lines
> 3) Backspace removes line ends to make a single line
> 4) Type ", " to make a list

Very interesting use case, original and useful.
Funnily, it would answer exactly the question asked at:
http://stackoverflow.com/questions/1062423/extend-notepad

--

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

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