gmane.editors.scite.general

SciTE4AutoIt v3.2.0 -- selection problem

2013-05-25T09:12:28


I've an unexpected behavior by selections  in SciTE.

The following script causes, the word under the cursor is selected. This 
can either apply to the Word character (by pressing Ctrl + Shift + E) or 
additionally with leading "$" for variables (by pressing Ctrl + E).

i.e. : *$variable*

with Ctrl+E:  *$variable*

with Ctrl+Shift+E:  *$variable*

This works perfectly - as long as the right of the term is a space. 


If this is not so, then ranges are selected that do not correspond to the 
markers. 

i.e.: *Global* *$arr|ay**[**$sizeA**][**$sizeB**]*    -- Pipe (|) marks the 
caret


Ctrl+Shift+E, expected:

*Global* *$array**|**[**$sizeA**][**$sizeB**]*

actually:

*Global* *$array**[**$sizeA**]**|**[**$sizeB**]*

*
*

and Ctrl+E, expected:

*Global* *$array**|**[**$sizeA**][**$sizeB**]*

actually:*
*

*Global* *$array**[**$sizeA**]**|**[**$sizeB**]*

*
*

Incidentally, it does not matter how I run the selection ( .SelectionStart 
/ Stop; :SetSel (); :CharRightExtend () ), always the same behavior. 



Here my Lua script:

 

-------------------------------------------------------------------------

EditKey = EventClass:new(Common)

-------------------------------------------------------------------------


-------------------------------------------------------------------------

SciTE 3.3.2 released

Neil Hodgson — 2013-05-22T00:14:46

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

   SciTE 3.3.2 is a minor bug fix release.

   Bugs fixed with multi-typing in virtual space.

   On Windows, a problem with Direct2D/DirectWrite (technology=1) was fixed and Asian DBCS encodings work with Direct2D.

   OnSave no longer called twice when files saved asynchronously.

   There are several fixes on OS X. Most importantly, the quarantine attribute should no longer be applied to files saved from SciTE or its subprocesses making it easier to compile and run programs. Input composition of accented and Asian characters improved. Release awaits Apple review which has been taking around a week.

   Other changes were made and bugs fixed. A detailed list of changes is available on the history page.
http://www.scintilla.org/ScintillaHistory.html

   SciTE uses Mercurial (Hg) for source code control. The repositories can be cloned with
hg clone http://hg.code.sf.net/p/scintilla/code scintilla
hg clone http://hg.code.sf.net/p/scintilla/scite

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

   Neil

SciTE search problems

Dmitry Konstantinov — 2013-05-21T12:55:10

Hi!

I have SciTE 3.3.1 on Ubuntu 12.10, KDE. I often have problem: SciTE
frezzes on text search, do not answer on any action and in top it get 100%
cpu. Prev versions i don't see such problem.

What information i need to get from my pc next time, to detect where is
problem: scite, scintilla or environment code and make bug report?

Thank you.

Search in selection?

tetsuo — 2013-05-14T22:01:27

Hello. I would like to be pointed to a Lua script to make a "search in selection". That functionality is present in the "Replace" function, but it only works for replacing. I would like to find stuff in a selection and wrap around the search while in it.

Thank you.

What is the default Character Set if character.set=0?

trismarck — 2013-05-14T13:04:15

Hello,

I have a question about the default Character Set that Scite uses when it 
opens a text file w/o the Unicode BOM (or w/o any other indication, what 
the character encoding of the text file is).
There is a setting in File: Encoding, that is called "Code Page Property". 
I've found out that this option maps to the code.page setting in the 
SciTEGlobal.Properties file (Options: Open Global Properties). What I have 
set there is: code.page=0, which means that, to display the contents of the 
text file, a _single_-byte code page will be used. 
On this newsgroup I've found the information that the code.page setting is 
actually only needed to determine, _how many bytes_ does each character in 
the text file translates to (I know there exist 'code pages' for which not 
every character maps to the same number of bytes), and not to set a 
particular character set. So, if code.page=0, then that means that each 
character in the text file is interpreted as a single byte.
The second setting is the character.set setting. This setting determines, 
what character set will be used to map the bytes (or byte sequences) in the 
file to the actual characters (characters that this character.set contains).
Now, the documentation tells me that the character.set=0 means the 
'Default' character set. This is the part where I get stuck - how does 
Scite determine, what is this 'default' character set? Does Scite use some 
Windows API call to i.e. determine the default code page of the OS? I've 
actually sifted through the source code and I've found out that, if Scite 
uses GTK+ or Qt, then the SC_CHARSET_DEFAULT preprocessor directive (see 
Scintilla.h) maps to 0, which maps to ISO-8859-1 (see CharacterSetID() 
function in PlatGTK.cxx and PlatQt.cxx). But, I'm not sure if the same 
happens on Windows - I couldn't find the function that would tell me, how 
the default character set is determined if Scite uses Windows controls. In 
ScintillaWin.cxx I've found the CodePageFromCharset() function that takes 
the VisualStyle object that has the Style subobject and this Style 
subobject has the .characterset property defined, but I can't figure out, 
how is this property set (or this property is actually relevant to my 
original question) if Scite uses Windows controls.

So the questions I have:
1. What is the default Character Set if character.set=0? (if Scite uses 
Windows controls)
2. What is the function is the Scite source code that determines, what is 
the default Character Set? (is this just a fixed setting or does Scite use 
Windows API calls? (and if it uses those calls, where can I find them in 
the code) )
3. How is the .characterset property of the Style subobject of the 
VisualStyle object set by default (and is this at all relevant to what I'm 
asking about).

What I want to do is to roughly understand, how does the text editor use a 
given character encoding to read a text file / display the characters that 
it has read from the text file. Especially, to test this, I need to know 
exactly, what character set Scite used to encode characters to the file 
(characters -> byte sequences).

Cheers and sorry for the long post.

Sass highlight syntax sass.properties

Huynh Cao Ky — 2013-05-11T05:53:33

Hi,

Does anyone have sass.properties or build it?
Please share if you have it. 
Thanks!

Project manager?

George — 2013-05-08T21:12:47

Is there a good "Project Manager" plugin for SciTE?
Google found me three potential candidates:
- sciteproj which requires GTK and direct work with X11. I understand the 
use of glib in such project and (maybe) GTK, but the need for X11 functions 
prevent this from work on Windows.
- Scite Project Manager. Requires AutoIT and probably will work on Windows 
(did not try myself), but will not work on Linux.
- filerx. Saw several topics about it, with a "unfortunately not supported 
anymore" conclusions.

Did I miss any other promising project managers? I do need something which 
can live on both systems.
How do you work with multi-file projects?

Caret invisible after toggling all folds twice

Ashwin Hirschi — 2013-05-08T16:24:04

Often when I use the "Toggle all folds" command (from the View menu) I find 
that the caret is not visible anymore after unfolding. I need to press 
something like the down key to have Scite adjust the view and continue 
working...

Is this the intended behaviour? I find it a bit unfriendly...

I'm not sure if others are experiencing this too, but it looks quite easy 
to replicate: just open a largish file, move the caret somewhere near the 
end, perform the Toggle all folds command twice, and the caret is nowhere 
to be seen.

Perhaps something like a scroll caret action at the end of the FoldAll 
function could improve things?

Ashwin.

Complete list of keyboard shortcuts

Ingemar — 2013-05-07T08:49:42

Hi,

I've been looking all over (I think :)) for a complete list of keyboard shortcuts that are available in SciTE. But I can't find any. The SciTEDoc.html file says "Keyboard commands in SciTE mostly follow common Windows and GTK+ conventions" and then there is a list of commands mapped to keyboard that aren't available in any SciTE menu.
Is there such a list available or - even better - a way to list all currently defined keyboard shortcuts?

Regards,
Ingemar

copy and paste inside Find-replace strip

Amir Sabbagh — 2013-04-29T08:28:34

Hi all,
I am creating a new thread to keep things cleaner.

I am using Scite Version 3.2.1 on Windows XP 64 bit
if I write something in the strip (either in the "Find" field or in the
"Replace Field") and then i try to copy it with Ctrl+C and paste it to
somewhere else, e.g. to the Scite window, the selection is not grabbed.
If I performed some copy and paste before, it is pasted that one instead
the selection in the strip.

To grab the text in the strip I have to right click on the selection and
choose Copy from the menu.

Amir

MRU mangling...?

Ashwin Hirschi — 2013-04-26T03:53:14

For quite a while Scite's MRU list has been bothering me. It seems to act 
erratically, with files I've closed first showing up in the list and then 
mysteriously disappearing later on. 

Oddly enough, each time new entries disappeared older entries would show up 
in their place. Often files I had worked on the day before... Weird (and 
quite annoying)!

Today, it finally annoyed me enough to drop my work and try and figure out 
what's going on. Fortunately, I think I've solved this little mystery:

It turns out the MRU list is *not* mangled if I simply open files using a 
File menu command. But, things *do* go wrong if I open a file by (directly 
or indirectly) starting a 2nd Scite instance.

My Scite setup has check.if.already.open=1 as well as save.recent=1. So, 
what happens is, the 2nd instance passes its commandline to the 1st 
(already running) instance and then stops. The original instance will 
process the commandline and open any files that are mentioned.

So far, so groovy, it seems. However, in ProcessCommandLine (in 
SciTEBase.cxx) there are 2 places where both InitialiseBuffers and 
RestoreRecentMenu are called...

The one close to the end of the function looks fine to me, since it's only 
called if the buffers aren't already initialised. But the first occurrance 
of RestoreRecentMenu seems odd. Is this the place that keeps resetting my 
MRU list to a previous state? I believe so.

So, my question is: should those 3 lines (4712-4714; version 3.3.1) really 
be there? Won't this logic be called during phase 1 (in the section below) 
anyway?

I'm not familiar enough with Scite's code base to say for certain. But it 
seems to me that if a running instance is processing new parameters passed 
to it, it should leave the MRU list alone...

What do you think?

Ashwin.

Clang address sanitizer on GTK+

Neil Hodgson — 2013-04-25T23:04:59

   AddressSanitizer is a tool for finding memory bugs, like writing beyond allocations, which is included in recent versions of Clang. 
http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer
   The main advantage of AddressSanitizer over other tools like Valgrind is that its faster so builds that include it can be used as normal.

   New Linux distributions like Ubuntu 13.04 include Clang 3.2 so allow use of AddressSanitizer. I've updated the make files for Scintilla and SciTE to use AddressSanitizer for Clang debug builds (make CLANG=1 DEBUG=1). No new bugs have been found yet but I suspect there may be bugs in lexers I don't use. 

   Neil

another suggestion

Odaylton Junior- BR — 2013-04-24T01:45:47

 

Hello Again ...

One point that I do not know if it's a limitation of autoit or SCITE but if 
possible would be very helpful ...

Imagine the situation:

After performing a listing, all was well when suddenly an error occurs.

Ok but if I knew the values of variables at the time of the error would 
be very useful for debugging.

1) Display the line that gave the error (OK)

2) Location of error (OK)

3) Values of Variables involved in Line (Tip)

4) Values in alphabetical order of the Local Variables in Function 
Location (Hint)

5) Amounts in alphabetical order of global variables (Tip)

PS when Matrix Display all data (Tip)

 

If so show me where I can post this suggestion

error in the vertical scroll bar

Odaylton Junior- BR — 2013-04-21T01:26:51


 error in the vertical scroll bar

When I'm rolling the bar with the mouse and my program does not occupy the 
entire horizontal line of the window is fine but (image 1)
 

<https://lh4.googleusercontent.com/-45uqscIPCHY/UXM_0BRccuI/AAAAAAAAAAk/7t2sDlY88fU/s1600/Falha+no+Editor1.JPG>
 
 
 
 if there is some pretty big line that spans the entire horizontal line horizontal 
scroll bar appears as you would expect .
  but keep clicking no longer works because I have to climb the mouse 
position to reach the scroll wheel ...
(image 2)

<https://lh3.googleusercontent.com/-nlic3nSAHFs/UXNAS5ds7rI/AAAAAAAAAAs/o06jBj2bu4o/s1600/Falha+no+Editor.JPG>
 

I suggest you lock the horizontal scroll bar disabled but existing for the vertical 
scroll button not be shifting all the time ....

Improvements SCITE

Odaylton Junior- BR — 2013-04-20T23:53:28

Text translated from Portuguese by google - please apologize for any errors

I would like to offer my congratulations for the excellent work and initiative in all "Autoit"
I'm starting to use and I love it all ...
I wish I could help and make a suggestion on a subject little thought to editors languages: Productivity
We can no longer think that a language editor has to be limited only in a notebook, but a development tool.
My suggestion to divide into 2 parts:
Part I
===========================
Going straight to the point.
And I think it would be very interesting that when you type a key word in SCITE for Ex: "If" the editor has inserisse the next lines "Then" and "EndIf" (as follows EX1) to save time in development and not waste time to use Tidy to find any typos
EX1: Enter the "If" + {space} is automatically inserted in the listing:
If $ {end} focal point of Then
{Tab}
Else
{Tab}
EndIf
{Enter}
Where the focus would already be in front of "$" which typically could be a new variable for comparison
In case you enter immediately after {BACKSPACE} + {Enter} whether to cancel the insertion and programmer could continue from "If"
This can extend to all functions:
EX2: When Type "is" + {space} is automatically inserted in the listing:
For $ {end} of focal point i = 1 To
{Tab}
Next
{Enter}
Where the focus would already be in front of the "$" that normally could be a new variable for comparison or already use "$ i" and with only {END} now able to define the end of the loop
And apply this to all functions, it would be a like a CodeWizard simplified language functions today.
Imagine the speed of development that would win because not waste time with obvious things and keep more standardized format.
Part II
==================================
I usually use a development methodology for functions with more than one field variables as in Ex3 and make it possible to think beyond standard useful, easy to read and debug:
Ex3:
Using MsgBox + {Space} is automatically inserted in the listing:
; ============================= MsgBox  ========================
, Displays a simple message box with optional timeout.
;
, Return Value:
, Success: Returns the ID of the button pressed.
, Failure: Returns -1 if the message box timed October
;
; =============================================================
MsgBox ( {Tab} 0, _ {Tab}      ;Flag -  {Tab}The flag  Indicates the type of message box
{Tab}    {Tab}      {Tab}      ;        {Tab}and the possible button combinations ....
{Tab}    {Tab}      {Tab}      ;Default {Tab}0 = OK button 
{Tab}    {Tab}      {Tab}      ; {Tab}       1 = OK and Cancel ... {Main options }
{Tab}    {Tab} "", _{Tab}      ;Title -{Tab}in XX Maximum characters
{Tab}    {Tab} "", _{Tab}      ;Text - {Tab} in XX Maximum characters
{Tab}    {Tab} Default, _ {Tab}; [Timeout] = 0 - {Tab} between 0 and XX min
{Tab}    {Tab}  Default _ {Tab}; [HWND] = The window handle to use the the parent for this dialog.
{Tab}    {Tab})           {Tab}; =====================================

This is a trivial example but imagine if this became a pattern there would be no need for HELP functions as this would already be on the list and an apprentice for example would be very helpful.

I would go even beyond:
When entering Func + {space} would open a window which fell within standard:
1) Function Name {functioname}
2) Brief description of any function {XXXX}
3) the name of the variable {$YYYYYY } 
4) a description of the variable for any Help Future, {WW ... WW}
5) Default Value {ZZZZ}
6) Possible variants or description Variable {MM .... MM}
7) and 2 box seen for [Const] and [ByRef] be active or not
8) Variable Return {$RRRRR} [optional]
9) Return Description {SSSSSSS} [Optional]
10) Fault Descriptions {FFFFFFF}
Or possibly all parameters for a pre-defined UDF
Generating something like a possible new UDF

; ====================== {functioname} ======================================
; {XXXX}
; Return Value
; Success: {SSSSSSSSS}
; Failure: {FFFFFFF}
; ===========================================================================
Func {functioname} ( {Tab} {$YYYYYY}, _ {Tab};[{YYYYYY}] - {Tab}    {WWWW ...
{Tab}   {Tab}        {Tab}              {Tab};{Tab}                 .... WWW}
{Tab}   {Tab}        {Tab}              {Tab};Default ={ZZZZZ}{Tab}{MM....
{Tab}   {Tab}        {Tab}              {Tab}; {Tab}                ....MMM}
...
{Tab}   {Tab}        {Tab} {$YYYYn} _   {Tab}; [YYYYn {}] - {Tab} {WWWW ...
{Tab}   {Tab}        {Tab}              {Tab};              {Tab}  .... WWW}
{Tab}   {Tab}        {Tab}              {Tab};Default(n)={ZZZZZn}{Tab}{M...
{Tab}   {Tab}        {Tab}              {Tab};                   {Tab} ...MMMn}
{Tab}   {Tab}        ) {Tab}            {Tab};================================= 
{Enter} 
Local ${RRRRRR}

{focal point}

{Tab} Return ${RRRRR}

EndFunc;==> {functioname}
; =============================================================================

I hope it was clear and I hope that at least the first part is regarded with affection
I see that this would allow a greater proficionalismo programmer and standardization.

paste text in a new tab

Amir Sabbagh — 2013-04-19T14:35:27

Hi all,
I am trying to write a script that takes some text from a buffer and paste
it to a new tab.
the text extraction part is fine, but I can not figure how to open a new
tab and paste the text there.

so far I am trying with:

#creating in advance a file
io.open ("Ciro.txt" ,"a+")

#opening it in Scite
scite.Open("Ciro.txt")

#for some reason the UndoAction does not work
editor:BeginUndoAction()
last_line=editor.LineCount
u = editor:PositionFromLine(last_line)
editor:GotoPos(u)

#finally paste
editor:Paste()
editor:EndUndoAction()

it works, but I'm almost sure there is a better way to open a new tab and
paste the text there.

Thank you
Amir

Adding properties for a Java like language

Ani — 2013-04-19T13:24:45

Hello,

I am trying to add support for a java like language in SciTE.
I am able to get some basic things working by modifying the cpp/java properties 
file. However, there is one big difference with this language, and that is :
the identifiers can have hyphens(-) and colons(:)

So, I was trying to see if there are options to control the lexer, 
(i.e, if I could find anything similar to but lexer.cpp.allow.dollar)

I tried setting 
word.characters.filetype to include ':' and '-'

but this didnt help either, I see some words highlighted 
within the identifier, like for e.g:

_range_ gets highlighted in a:allow-range-test

because 'range' is a keyword!

Any help/suggestions/workarounds really appreciate.

There are some other issues as well, that I am facing - like the strings
here, can run on multiple lines without a concat op (+ in java) or a
line continuation char (\) - if there are any ways to workaround this
please do let me know.

Thanks
--Ani

Changes to FirstVisibleLine?

Ashwin Hirschi — 2013-04-16T00:23:03

Several functions in my Scite setup use the following (simplified) code 
fragment:

    local line = editor:LineFromPosition(editor.CurrentPos)
    local top = editor.FirstVisibleLine
    editor:LineScroll(0, line - top - 1)

The fragment scrolls the current line to the top of the editor pane, and 
has worked well for many years. But it seems that recent versions of Scite 
have somehow broken it... 

It still works fine for smaller files. But files of several thousand lines 
seem to throw it off. In fact, the further down the file the current line 
is, the more wrong the end result is.

Simply printing the line and top variables shows that 
editor.FirstVisibleLine is now often not correct anymore. Also, the current 
API docs state that "Scroll so that a display line is at the top of the 
display", which seems odd for a property that still holds a number in Scite 
3.3.1.

In any case, am I doing something wrong and is there a new/better way to 
scroll a line to the top of the pane? Or is this simply a bug that has 
somehow crept into the code?

Ashwin.

Change in how the Lua editor:remove works

Robin — 2013-04-13T16:33:47

In going from SciTE 3.3.0 to 3.3.1 the Lua editor:remove semantics appears 
to have changed from all previous versions I have used in the last 2-1/2 
years.

Previously, if p is a valid position in the editor, a call to

editor:remove(p,p)

removed one character at the position p. In addition, a call to

editor:remove(p,p+1)

would also remove one character at the position p. Now it appears that only 
the latter works while the former now does nothing.

Was there a reason for this change? Was it always supposed to work the way 
it does now?

I am not complaining as SciTE is a great editor. I really like that I can 
use Lua to manage each and every keystroke and use the auto completion 
facility to hook-in an extensive menu system in addition to the traditional 
menu - providing hundreds of additional static and dynamic actions and menu 
items.

Thanks. Robin.

SciTE 3.3.1 released

Neil Hodgson — 2013-04-11T12:45:14

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

   SciTE 3.3.1 is a minor feature release.

   Support was improved for some languages.

   Other changes were made and bugs fixed. A detailed list of changes is available on the history page.
http://www.scintilla.org/ScintillaHistory.html

   SciTE uses Mercurial (Hg) for source code control. The repositories can be cloned with
hg clone http://hg.code.sf.net/p/scintilla/code scintilla
hg clone http://hg.code.sf.net/p/scintilla/scite

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

   Neil

Showing the end of the output after execution

Simon Arnu — 2013-04-11T12:09:40

I regularly use Scite for executing lengthy scripts (Batch files, python scripts). Per default, the current position in the output window is set back to the start. Is there some secret configuration option that instructs scite to just stop at the end of the output?
For my use case it would be more convenient that way, because I could see the end status right away without scrolling back.

Simon