Neil Hodgson | 1 Jun 11:37 2012

SciTE 3.2.0 released

   SciTE 3.2.0 is now available from the scintilla.org web site.

   SciTE 3.2.0 is a minor bug fix release.

   Ctrl+Double Click and Ctrl+Triple Click add the word or line to the set of selections.

   Other changes were made and bugs fixed. A detailed list of changes is available on the history page.

   The commercial version on OS X will appear in the App Store when/if it is approved by Apple.

   SciTE uses Mercurial (Hg) for source code control. The repositories can be cloned with

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

   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.

s andf | 2 Jun 15:33 2012
Picon

dostring command does not work since version 3.1.0

Dear all,
   I use the following command to backup my file:
command.15.*=dostring os.execute("cmd /C copy $(FileNameExt) $(FileName)_"..os.date("%y%m%d%H%M%S")..".$(FileExt)")
   However, this command works for version 3.0.4 but not for both version 3.1.0 and 3.2.0
Is it a bug?
 
Best regards.
 
Youzhao Lan 
2012-06-02  20:18:17

--
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.
Neil Hodgson | 4 Jun 04:30 2012

Re: dostring command does not work since version 3.1.0

s andf wrote:

   I use the following command to backup my file:
command.15.*=dostring os.execute("cmd /C copy $(FileNameExt) $(FileName)_"..os.date("%y%m%d%H%M%S")..".$(FileExt)")
   However, this command works for version 3.0.4 but not for both version 3.1.0 and 3.2.0
Is it a bug?

   The current directory is no longer set before running Lua commands so you should include full paths in the command using $(FilePath) and $(FileDir).

   The reason that the current directory is no longer being set is that this has caused various problems on each platform in the past. On Windows, setting the current directory locks that directory so it can not be deleted.

   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.

Neil Hodgson | 4 Jun 14:03 2012

Background save failures on Linux

   There is a bug fix committed (change set 3839) that affects buffer lifetime that could be the cause of the problems with background saving although it is unlikely.

   To try to solve this, thread creation was switched from pthreads to glib and any problems reported to the console and also as a message box. To enable experimentation, background saving was turned on in global options. It would be help greatly in solving this if users would try the current version in Hg and report if they ever see any warning: "Failed to save file '^0' as thread could not be started.".

   If this warning should appear, all is not lost as it should be possible to save the contents into a new file after turning off background saving: Select All; Copy; New; Paste; Open User Options File; background.save.size=10000000; Save; Previous; Save As.

   While it would be possible to save the contents in the foreground if thread creation fails, that doesn't help fix the bug and it would only really help if thread creation was flakey. That would be a pity as it would increase responsiveness to make further use of threads in SciTE.

   Available from Hg:

   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.

vanyinet | 6 Jun 10:09 2012
Picon

Select word problem

Today I discovered that CTRL + mouse double click doesn't select the word.
I need to click 5 times to get the word selected.

I am using latest SciTE from HG on Ubuntu 11.10

Istvan

--

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

Neil Hodgson | 7 Jun 01:43 2012

Re: Select word problem


Today I discovered that CTRL + mouse double click doesn't select the word.
I need to click 5 times to get the word selected.

I am using latest SciTE from HG on Ubuntu 11.10

   Modifier keys are problematic on Linux since the window manager takes over some of the most useful key and mouse combinations. You probably still have rectangular selection set to use Ctrl so that interferes with multiple selection. See http://www.scintilla.org/SciTEDoc.html#property-rectangular.selection.modifier

   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.

vanyinet | 7 Jun 06:46 2012
Picon

Re: Select word problem

Yes the rectangular.selection.modifier was set to 2.

It worked before with this setting both word selection (CTRL+double 
click) and the rectangular selection too.
It stooped to work recently.

If this is the situation, I'll use Super key from now for rectangular 
selection.

Thanks.
Istvan

On 2012-06-07 02:43, Neil Hodgson wrote:
> vanyinet <at> gmail.com <mailto:vanyinet <at> gmail.com>:
>
>> Today I discovered that CTRL + mouse double click doesn't select the word.
>> I need to click 5 times to get the word selected.
>>
>> I am using latest SciTE from HG on Ubuntu 11.10
>
> Modifier keys are problematic on Linux since the window manager takes
> over some of the most useful key and mouse combinations. You probably
> still have rectangular selection set to use Ctrl so that interferes with
> multiple selection. See
> http://www.scintilla.org/SciTEDoc.html#property-rectangular.selection.modifier
>
> 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.

--

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

Neil Hodgson | 7 Jun 07:10 2012

Re: Select word problem

vanyinet <at> gmail.com:

> If this is the situation, I'll use Super key from now for rectangular selection.

   The current release of Ubuntu has taken over the Super key as well.

   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.

Frank Wunderlich | 8 Jun 12:09 2012
Picon

editor.WordChars not acessable in Scite 3.2 and error-bug

hi,
i have a script using editor.WordChars. i think its not a feature from 
Scite-RU and i tried it in GSciTE 3.2.
i get the following error:
..ome/frank/.scite/lua/highlighting_identical_text.lua:98: Pane function 
/ readable property / indexed writable property name expected
which points to this line:
word_pattern = '[^' .. editor.WordChars .. ']'
where word_pattern is a local var, so the error can only thrown by 
editor.WordChars

because of the dots in front of the path, i can't open the file directly 
by doubleclick. changing it to /home/frank works.

Regards Frank

--

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

Philippe Lhoste | 8 Jun 13:16 2012
Picon
Picon

Re: editor.WordChars not acessable in Scite 3.2 and error-bug

On 08/06/2012 12:09, Frank Wunderlich wrote:
> i have a script using editor.WordChars. i think its not a feature from Scite-RU and i
> tried it in GSciTE 3.2.
> i get the following error:
> ..ome/frank/.scite/lua/highlighting_identical_text.lua:98: Pane function / readable
> property / indexed writable property name expected
> which points to this line:
> word_pattern = '[^' .. editor.WordChars .. ']'
> where word_pattern is a local var, so the error can only thrown by editor.WordChars

WordChars is a write-only property, a setter.
You can see that in the iFaceTable.cxx file, among others.

Possible workaround: read directly the property from SciTE. For example:

-- The property set specifically in lua.properties
print('lua', props['word.chars.lua'])
-- The more generic property,
-- but doesn't work for multiple extensions (eg. $(file.patterns.cpp))
local ext = string.lower(props["FileExt"])
print(ext, props['word.characters.*.' .. ext])

--

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


Gmane