Re: [scite] How would you suggest I distribute my Scite Extension?
Hans Joseph Solbrig: My extension is titled The Pattern Repeater. It basically modifies the UI of scite, offering the user the option of repeating previous edits when it notices text that matches the patterns within previous edits. You should just distribute the whole of your modified SciTE. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] for your consideration, a patch to OpenSelected()
April White: The code for finding if the path is a directory should use FilePath::IsDirectory which is portable. I forgot, thank you. I'll upload a new version with this change and include the documentation change as well. I'll probably start a new message thread at that point. I forgot too and was about to say that you should break the code into a directory check in FilePath and the code that acts on that before I looked in FilePath and it was already there. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE window does not come into foreground on Gnome
Alexander Kriegisch: I run SciTE 1.74 on a Linux box on a Gnome Desktop. I am facing the problem of the SciTE window not being foregrounded automatically when I open a new file. I am running the editor in check.if.already.open=1 mode, by the way. There is some discussion about this area in this thread: http://mailman.lyra.org/pipermail/scite-interest/2007-June/009403.html Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE license question
Jonathan Wilson: Is it permissible to take SciTE code including Scintilla.dll and SciLexer.dll code and mix it with code released under the GPLv3 and then release the result as GPLv3? The license is at http://scintilla.sourceforge.net/License.txt . I am not aware of any conflicts with GPLv3. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
steve donovan: I think we're confident enough for this to be updated. I'll have a look at the needed changes. Is there a complete version of this patch? Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: 1.74 crashes under FC7 X86_64
Me: Scintilla should probably do something more sensible with invalid UTF-8 rather than relying on Pango to fail nicely. However its difficult to do anything sensible with invalid UTF-8 As a work-around, if I have time, I may map invalid bytes in supposedly UTF-8 text into Private Use Area characters (probably E000-E080) that should then be properly handled by the platform although will look a little weird. A better solution would be to have little hex blobs [C4][E3] like Scintilla's control character display but that is more work. Whatever is done, there's going to be some speed/complexity cost. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] for your consideration, a patch to OpenSelected()
April White: I am not sure where we stand on this change. I have altered SciTEDoc.html but have not uploaded it yet. On the basis of not being useful often enough I don't think this should go in. Of course other people like commands I never use but if this is seen as needed by others, they should say they want it, preferably explaining the circumstances in which it would help them. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan:
for (int param = 0; param maxParam; param++) {
SString paramText(param + 1);
SString paramTextVal = props.Get(paramText.c_str());
if (paramTextVal.length() 0) {
if (paramTextVal.contains( )) {
SString val;
val += \;
val += paramTextVal;
val += \;
paramTextVal = val;
}
parameters += paramTextVal;
parameters += ;
}
}
Needs documentation.
BTW, the existing line in lua.properties is problematic:
command.go.*.lua=Lua-5.0.exe $(FileNameExt)
The .exe shouldn't be needed on Windows either.
The Lua people are now just calling their executable 'lua', now that
the 5.0-5.1 transistion is over.
Someone that uses command line Lua on Windows should say whether this works
command.go.*.lua=lua $(FileNameExt)
Neil
___
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan:
if (props.GetInt(find.files.using.extension)) {
SString ext = *.;
ext += filePath.Extension().AsInternal();
memFiles.Insert(ext);
}
Since its fairly rare for a language to have a single extension
(C/C++ programmers will often have both .c/.h or similar) I was
expecting a second layer to this. If someone writes up a documentation
patch as well the above can go in.
Neil
___
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
The IDM_* constants are now exposed to Lua like all the SCI_* constants. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] [Feature Request] Edit behavior when rectangle selection
Peng Yi: Firstly, I know scintiall can support rectangle selection mode. But when I input some text when have rectanle seletion, all selections will be removed and my input is insert into postion that selection start. I know some editors (for example, jedit and textmate) have a feature can insert input into all selected columns. Have Scintilla/Scite this feature? Or this feature can be added in next release? Scintilla does not have this feature. It will not be in the next release. There is a proposed (and rejected) implementation here: https://sourceforge.net/tracker/index.php?func=detailaid=545068group_id=2439atid=352439 Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Compiling problem SciTE in MinGW
Hi Ulf, Looks like you are using CygWin or MSYS which are not properly supported by the Scintilla build files. There is some broken CygWin support in there which I intend to remove. You could try using a pure MingW environment, otherwise it is simpler to use the Microsoft compiler. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Compiling problem SciTE in MinGW
Ulf Nyman: NO I use a pure MinGW/MSYS enviorement MinGW v.3.4.5 MSYS v.1.0.10 Me (from previous mail): Looks like you are using CygWin or *** MSYS *** Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: 1.74 crashes under FC7 X86_64
Jan Boehme: (scite:4552): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() when I open SciTEGlobal.properties and scroll down to: ... chars.accented=ŠšŒœŸÿÀàÁáÂâÃãÄäÅåÆæÇçÈèÉéÊêËëÌìÍíÎîÏïÐðÑñÒòÓóÔôÕõÖØøÙùÚúÛûÜüÝýÞþßö This is a set of byte values and should not be interpreted as UTF-8. Scintilla should probably do something more sensible with invalid UTF-8 rather than relying on Pango to fail nicely. However its difficult to do anything sensible with invalid UTF-8 - I don't want to prohibit the display of files that contain invalid UTF-8 since you may be recovering a corrupted file. Stanislav Maslovski: # Try this: # # 1. convert properties files to utf-8 using iconv (or you can do it only # with your user properties file). Don't do this to SciTEGlobal.properties as it will make chars.accented useless. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: 1.74 crashes under FC7 X86_64
Stanislav Maslovski: Oops, I did not know. If they are byte values, then what encoding is assumed for them? None really. Its a set of bytes that have values between 128 and 255 and are often printable characters in various encodings. The first line is OK for ISO-8859-1 or -15 or Windows European and isn't too bad for other ISO-8859-*. The Russian line is for either CP1251 or KOI8-R - I can't recall which. For users of 8-bit encodings they should be modified to fit in with what they feel are word characters in their preferred encoding. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] for your consideration, a patch to OpenSelected()
April White: I am unsure whether to change SciTE.rc: MENUITEM Open Selected Filename\tCtrl+Shift+O,IDM_OPENSELECTED to MENUITEM Open Selected Filename or Folder\tCtrl+Shift+O, IDM_OPENSELECTED Its not really opening a folder: IIRC EMACS has sort of directory-editing mode and I wouldn't want this command to be confused with something like that. BTW I noticed that scite/scripts/commandsdoc.py has this line: !--Generated by scite/scripts/scommandsdoc.py -- notice the 's' preceding commandsdoc.py Fixed now. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] [PATCH] SciTE 1.74 GTK+: layout based on native GtkPaned widget
Stanislav Maslovski: - problem with cursors solved. Using cursorInvalid in this way is good. - focus issues fixed. Oops, not all of them. When the output window is opened to the maximum width the focus goes nowhere... Its OK to be a bit heavy-handed, forcing the focus into a visible window even if it doesn't seem to be currently associated with an editing pane. That's better than any situation where typing goes nowhere. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] for your consideration, a patch to OpenSelected()
April White: I've found it useful to be able to easily open the folder that the filename is in, without having to ... Is this seen by others as a commonly needed operation? Everyone works differently and this doesn't seem to me to be something that I'd use. Its not easily discoverable either although possibly some documentation would help. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] [PATCH] SciTE 1.74 GTK+: layout based on native GtkPaned widget
Hi Stanislav, - cursorLast and the related code was removed because it did not work with dynamically destroyed/created windows. This removal should not affect the win32 code. There are several other platforms (OS/X, wxWidgets, QT, ...) so published APIs like this should not change. It would also be better to get this code working on GTK+ to avoid unnecessary calls to gdk_window_set_cursor. This may now be optimized but I think there was flickering on old versions of GTK+. There are new focus issues when switching between horizontal and vertical layouts. The focus seems to go nowhere so typing has no effect. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Properties fixes
steve donovan: We have a few inconsistencies in cpp.properties: command.go.*.c=$(FileName) ... command.go.$(file.patterns.cplusplus)=./$(FileName) The first is appropriate for Windows, and those people on *nix who put . on the path. But generally . is not on the path. I think we need a if PLAT_WIN/if PLAT_GTK here This worked OK on Windows XP: command.go.*.c=./$(FileName) Anyone want to send in an updated cpp.properties? Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] [cpp.properities] please add *.ipp
Jan Boehme: Please add the *.ipp postfix to the cpp.properities file to handle ipp file content like regular C++. Added to file.patterns.cpp. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] multiple languages in one file support
CieNTi: Hi ... i want to ask if there is possible to see the language's layout in a mixed file. In example, i have a php file, and into it, i have php + html + css + javascript ... how can i see each language's layout/autocomplete/etc together without manually switching in the Language menu? This is not supported by SciTE. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Annoying match case
steve donovan: It's possible that the 'find files' dialog is reseting the 'match case' set by the 'find stuff' dialog, which would be irritating and inconsistent. Since there is no way to specify case-insensitive to the search command, it is treated as a matching case search. This is shown by the Match Case option being selective and inactive. The Match Case option is shared between Find and Find in Files (and Replace). It would be possible to separate the two but quite often you are working with similar documents for Find and Find in Files so sharing the state helps. It makes more sense when using the internal Find in Files as it allows choosing case-insensitive searches. The global setting files should not have the properties shown by Istvan if using current SciTE. If you want a custom Find in Files command then it should be in user properties. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] IDM_PREVFILE, IDM_NEXTFILE broken in GTK CVS?
Geoff Catlin: Recently, though I'm not sure exactly when, navigating between tabs using Ctrl+PageUp/PageDown (which use IDM_PREVFILE and IDM_NEXTFILE) stopped working in my build of the GTK SciTE CVS code. I have this in my user options file: user.shortcuts=\ Ctrl+PageUp|IDM_PREVFILE|\ Ctrl+PageDown|IDM_NEXTFILE| I've tried mapping other keys to IDM_PREVFILE and IDM_NEXTFILE but to no avail. Works for me using current download with normal bindings or with Shift+Ctrl+C, Shift+Ctrl+V mapped to IDM_PREVFILE and IDM_NEXTFILE. My checkout has some differences in gtk/SciTEGTK.cxx to alter the menu items and accelerator keys, but is otherwise identical to CVS. I also recently update to Ubuntu Feisty Fawn (from Edgy Eft) which may be related, but I figured I'd try here first. My tests were on Fedora 7 so there may be some global assignment to those keys or your changes could be at fault. Also, I just noticed that a single column block selection starting at the beginning of a line shows no selection highlighting. Works for me although there is a current problem with foreground selection highlighting. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Re: Re: Compiler error
Roger Sondermann: When I set CYGWIN = 0 or comment out the ifdef TERM in .../scite/win32/makefile I do get: with make: make: *** No rule to make target `..\..\scintilla\bin \Scintilla.dll', needed by `..\bin\Scintilla.dll'. Stop with mingw32-make.exe: cp ..\..\scintilla\bin\SciLexer.dll ..\bin\SciLexer.dll cp: cannot stat `..\\..\\scintilla\\bin\\SciLexer.dll': No such file or directory Its still running cp rather than copy so CYGWIN is still being defined (to 0), so remove the four lines: ifdef TERM # Assume that any defined TERM implies cygwin. CYGWIN = 1 endif Now mingw32-make clean in both directories and then mingw32-make in both directories. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] For your consideration, my SciTE Job Queue implementation
April White: Can anyone confirm whether InterlockedExchange() exists in GTK? I think the closest is g_atomic_int_compare_and_exchange but it will be simpler to just implement the functionality using a mutex. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Compiler error
Roger Sondermann: Don't know if the missing export definition file is a real problem. No its just an uninteresting warning. I do get SciLexer.dll and Scintilla.dll ...\scintilla\bin, but they will not be found when building SciTE.exe because of the backslashes instead of slashes in /scite/win32/makefile: DLLS=..\bin\Scintilla.dll ..\bin\SciLexer.dll Works for me. Sure you are using the mingw version of make: mingw32-make? BTW: Is it correct to have -mno-cygwin in the above comands? Yes, this is using mingw not cygwin. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Re: Compiler error
Roger Sondermann: cp ..\..\scintilla\bin\Scintilla.dll ..\bin\Scintilla.dll cp: cannot stat `..\\..\\scintilla\\bin\\Scintilla.dll': No such file or directory G:\Programs\System\MSys\bin\mingw32-make.exe: *** [..\bin \Scintilla.dll] Error 1 ... and Scintilla.dll is in ...\scintilla\bin\ I'd forgotten that some cygwin compatibility was added to the makefile. Remove the definition of TERM from your environment (or edit the makefile to stop defining CYGWIN) and run make. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Regex search/replace: ? does not work
Alexander Kriegisch: Talking about REs, I would like to ask the developers if there is any chance for a more extensive RE library being implemented or adapted No. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Compiler error
Building with Borland 5.5 currently fails. I tried to use the current version of Borland's compiler to build and couldn't get that to work. Unless someone wants to contribute a fix to get 5.5 working, its time to say that Borland is no longer supported. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan: Ah, I see: one can't then do a Lua-free build; that's a bugger. I suppose IFaceTable doesn't have to be considered part of Lua support - I can't see any calls to real Lua in IFaceTable.cxx or .h but am unsure whether there are indirect links. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Flash in Linux
izak marais: Ok, i see what happend threre, but I tried echo $(api.*.mx;*.as;*.asc) echo And nothing happend. Obviously I'm writing the variable name wrong, but what is the correct syntax? Looking at that, there isn't really a syntax for it since the file searching feature is handled differently to variable expansion. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: Trying to figure out what you are trying to tell ...error in relacement string, things where changed that where not intendet to be changed ...as I understand it. In this case the first occurrence should be as good as the last. Pretty low chance that the last is an unintentional one. Most of the time if one is wrong all are wrong. I think the last is better to show than the first since it confirms extent of change. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Folding of second-level blocks
Ivan Kolev: Is there a way to toggle all second-level blocks? http://mailman.lyra.org/pipermail/scite-interest/2007-June/009240.html Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] For your consideration, my SciTE Job Queue implementation
I have uploaded to: ... long cancelFlag; /* only one job can be executing at a time, this should be safe as a public variable of the class */ The cancelFlag is used in both the UI thread and the execution thread so should be protected. That is why InterlockedExchange is used in the current code. The same effect should be possible by using the JobQueue mutex in an int SetCancelFlag(int value) method. The IDM_FINISHEDEXECUTE and IDM_JOBS cases are too complex to contain within SciTEWin::Command so should be moved out into methods. I've included Changelog-AprilW.txt in which I've tried to list all of the changes I made. There are one or three changes outside of the command system I did which I hope will also be accepted. Including multiple changes in a patch makes it much harder to review. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: That is what the noise is usually taken for. Maybe most people have a few lines of code they'd like to replace something in. But as as soon as there are a few hundred ringing a bell is a much easier on your eyes than getting jumped to an arbitrary location. Ringing a bell is much harder on your ears and concentration. Don't get you - why useless? 9 replaced out of 9 expected. Well done ...no typo. I don't count the number of replacements I'm expecting to be made so a report of 9 replacements is unlikely to give me useful information: how do I know that 9 is the correct number rather than 8 or 10? And yes, I find it very helpful to have an indicator. Replacing is the main purpose of the dialog so why not let everybody know what happend? Because it is detail that is uninteresting in the vast majority of cases. You do know that something was replaced because there is no message saying that the operation failed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan: The patch involves changing the signature of ExtensionAPI::DoMenuCommand; in Extender.h around line 30, we then have virtual void DoMenuCommand(const char *cmd)=0; The idea of a published extension interface is to give extension writers a solid basis to work. Changing method signatures will make existing extensions fail. I'd like people to think about this when proposing additions to the extension interface: once its published in a release we're stuck with it. in SciTEBase.h around 901 we have: void DoMenuCommand(const char* cmd); I didn't want to do it this way since its less useful than having the constants be available to Lua similar to the way that other constants (such as SCI_SETZOOM) are made available. Doing this in the same way as SCI_SETZOOM would add around 3K for strings (in IFaceTable.cxx) that are already in the executable so I'd prefer a way that avoids double storage of those strings. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Replace dialog feature request
Philippe Lhoste: On the other hand, I am starting to find this message (no occurrences found) more distracting and annoying than my system of screen flashing (and ring belling!), because I have to dismiss it before changing my typo... The No replacements alert could be dropped but new users would probably find it more difficult to understand what happened. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: Just to make my point clear - as I see it placing a little note in the dialog Replaced: 3 (a.k.a ring a bell in the users head) should be much easier on the user compared to sending him down an unknown number of lines just to give proof something happend. Bit of an overkill as I see it. Showing the change is more direct than telling the user about it. When I see the changed text in context I can more easily detect that an error was made in the choice of replacement string. Telling me that some number of replacements was made gives me no such feedback. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Replace dialog feature request
Holger Kohnen: I tried the setting: find.replacewith.focus=1 but at least on gtk i see no effect. This hasn't been implemented on GTK+. I have changed the documentation to reflect this. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan: So the IDM_ constants could be put into IFaceTable, and would then be automatically available. Then GetMenuCommandAsInt() could call IFaceTable::FindConstant(name). I know this is a little awkward, because then the script-generated tables in IFaceTable come from two sources, but it would avoid the double storage issue and provides a unified mechanism to look up significant constants. The modularity wasn't that great either as it made other features depend on the Lua subsystem. It also exposes a lot more symbols to features like user.shortcuts that may not be sensible although it would allow user.shortcuts=Alt+Home|SCI_RIGHTEND| Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Calltip question
CieNTi: Im sorry. I said calltip when i was trying to say Complete Symbol. Is annoying that you start writing image and press CTRL+I, a really good list appear, but you cannot remain writing Why can't you continue writing? Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
Does this need updated documentation on http://scintilla.sourceforge.net/SciTEDirector.html ? Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Properties fixes
Philippe Lhoste: style.lua.13=$(style.lua.5),back:#E0FFE0 style.lua.14=$(style.lua.5),back:#E0E0FF style.lua.15=$(style.lua.5),back:#E0 style.lua.16=$(style.lua.5),back:#FFE0FF style.lua.17=$(style.lua.5),back:#FFE0E0 style.lua.18=$(style.lua.5),back:#FFD0D0 style.lua.19=$(style.lua.5),back:#FFE0E0 which is a bit toned down. OK, committed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: Bit puzzeled about the replace dialog currently. When hitting the Replace All button in the replace dialog it jumps to the last occurence replaced. Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. People like to see that a command has had the expected effect and the current behaviour shows an example of the changed text. While its fairly arbitrary to show the last replacement it does reassure that the file has been processed. And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. I find it useless noise myself but its implemented on Windows. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Three proposed patches to SciTE
steve donovan: 1) Currently, Find-in-files is initialized with the property 'find.files, but it would be cool if there was an option for it to use the _current extension_ to build up a mask. If I am working in Python, then it should know that I am probably wanting to search Python files, etc. How are you going to arbitrate between the current extension's choice and the history? I commonly make a series of searches with one mask. 2) View|Parameters sets $(1)..$(4). It would be convenient if there was a new constructed property $(Parameters) which is built out of these properties, quoted if necessary to make a valid command line. It would then be quite safe to update all the command.go properties to use $(Parameters) out of the box. Don't really see the advantage over using quotes where needed when specifying commands. 3) On the scripting side, scite.MenuCommand() takes an integer id which has to be looked up in SciTE.h by a human. Now SciTE already maintains a map of 'IDM_...' constants, so it is possible to redefine Extender::MenuCommand() to take a string argument and use this table if necessary, so that one can use symbolic 'IDM_..' names. This only takes an extra 15 lines and doesn't otherwise affect the interfaces. This has been looked at before. If you have a good way of doing it I'll probably include it. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [SciTE] broken link
F.E. Karaoulanis: The TCL API file link at http://scintilla.sourceforge.net/SciTEExtras.html is broken and points to a parked domain. OK, removed. The extras page would probably be better as a wiki rather than being mediated by me if anyone is interested in setting that up. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] me, Linux, and SciTE/Scintilla
April White: Okay, only the 'Go' command, but it works. I'll try the change I made to the SciTE/Lua interface, where I added scite.Execute() Good! Shouldn't be much more work to add the other commands. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Calltip question
CieNTi: Sorry if this was asked ... i searched but i didnt found solution. I discovered a few days ago this wonderful editor, SciTE. But my question is ... can SciTE able to manage the calltip like VB style? (when the calltip appear, you can write more characters and the calltip list is shrinking). I think you mean autocompletion which is a list of symbols that match the typed text. In SciTE the list selection moves depending on your typing rather than excluding items from the list. There is no built in means for doing what you want although it may be possible to implement this as a script. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Property fixes and modeless incremental search on Windows
Changed property wild card code so that wild card suffixes like Make* work for file pattern based properties. Another bug fixed where filepattern properties were not picking up filepattern definitions from higher priority property sets. For example, users wanting to extend the definition of XML files by setting file.patterns.xml in their user properties were unsuccessful. The incremental search dialog on Windows is now non-modal. This was mostly done because users were unable to work out how to exit incremental search. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Flash in Linux
izak marais: Thanks for the informative reply. How do I check where the api... property is pointing? You should be able to display it in the output pane using the echo command: echo $(file.patterns.flash) then use that to find the value of api... You could just write the expression rather than call echo but you'll probably see a command not found message then. I simplified the api line to api.$(file.patterns.flash)=$(SciteDefaultHome)\flash.api; \ is not a directory separator on Linux. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Startup issue
James Cuénod: Sorry, it doesn't matter what version you're running - I don't think. SciTE is looking for something eg: ext.lua.startup.script=$(SciteDefaultHome)\scite-gdb\extman.lua Maybe it would be simpler if SciTE had a preferred script name and ext.lua.startup.script was just a way to override the default. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTe on Windows: how to set UTF-8 with BOM as default?
empError: There is no setting that will default new files to having a BOM. You could look into writing a Lua script for OnOpen that detects a new file (I expect it gets an empty filename) and calls scite.MenuCommand(153) where 153 is IDM_ENCODING_UTF8. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Flash in Linux
izak marais: The first thing I'm unsure about is the extent of built in flash support in the Linux version. Falsh(actionscript) is listed as a supported language for scite. When I open a .as file I get correct syntax highlighting and code folding, but there is no properties file and no language selection option (even amongst the commented ones in the global properties file). I would like to edit the compile and build commands to use a makefile, but since there is no properties file, I don't know how to proceed. Flash is treated as JavaScript which is handled by the cpp lexer so properties are in cpp.properties. You should always add your compile and build commands to your user properties file rather than to the language-specific file distributed with SciTE. That way you can install new versions while retaining your customizations. lexer.$(file.patterns.flash)=flash in flash.properties and that there is no lexer named flash outside of scite|flash. If I change this to I expect this lexer has been modified for scite|flash. However, code I cant get auto completion and call tips working properly. If I add autocompleteword.automatic=1 to my sciteuser.properties I get auto completion on keywords and functions the second time I use them in a file. Is this normal? Yes. Also call tips are not functioning at all, in spite of the inclusion of flash.api and the following lines in flash.properties ### #Load the Flash API ### api.$(file.patterns.flash)=$(SciteDefaultHome)\flash.api;$(SciteDefaultHome)\API.custom;API.flashcommClient;API.flashcommServer; autocomplete.flash.ignorecase=1 The ignorecase line will be ignored because its using 'flash' rather than cpp and for calltips it should say 'calltip' rather than 'autocomplete'. Check that the API file is working with Edit | Complete Symbol. If not simplify your api setting to a single file and check where SciTE thinks the api... property is pointing. You might want to unindent the whole file as well - I don't know if everything works indented. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Problem to add new keywords to php
cokinou: I would like add another keyword (like into lua.properties) with added on php.properties : keywords2.$(file.patterns.php)=function1 function2 function3 style.php.13=fore:#FF,bold But no effect on PHP code :(, i try to change the number style.php.xxx but no effect :,( The php lexer isn't supported any more although it is still present. It was always mostly just another way to access the hypertext lexer which is set up in html.properties. The hypertext lexer handles HTML and XML, including embedded PHP. Because it is handling HTML, PHP, ASP, and client-side JavaScript, it has to cooperate with these languages in assigning keyword lists. Keyword list 2 is used for JavaScript keywords. Only one keyword list is allocated to PHP (and there is only one keyword style) so you should append your keywords to the list of PHP keywords in your php.properties. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Folding for Kixtart
Smudley: Is there a way for a noob like me to implement folding for Kixtart? I like ScITE and use it for AutoIT but I have tons of scripts done in Kixtart. It would help to have the folding feature working. Best way to write lexers and folders is to examine current code. You can find these for AutoIT in scintilla /src/LexAU3.cxx. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] me, Linux, and SciTE/Scintilla
April White: Thanks Mitchell. I did compile with DEBUG=1, and followed the steps above, but I did not get a segfault while executing a tool - nothing did happen - but I did get a double free or corruption when I exited SciTE. The results of 'back' were vague and useless, showing a few unidentified addresses and some with system names such as 'libc.so.6' There are various memory debuggers. I've found Valgrind useful on Linux. Is there an equivalent to win32 SendMessage()? There is no close equivalent to SendMessage. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: [scintilla] Moving some WordList and PropSet functionality from Scintilla to SciTE
steve donovan: replace line 166 (which is just #define LUA_API extern) That looks like line 164 to me. Committed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] me, Linux, and SciTE/Scintilla
April White: So the rhetorical question is, how do I debug this? My Linux experience is really limited, heck I cannot even find where aliases are set nor change one to suit my preferences. Well I can type in the command, but I want to put it into my start up script - which I did - but it does not 'take'. IIRC I used kdevelop for a while but like most IDEs, it really expects you to be using its project facility so you have to figure out how to run up an external executable. I've never found a Linux IDE that I actually like so most debugging is done using Visual Studio on Windows. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Support for CSS in the HTML Language
Kronuz: I was just wondering, when and how are decisions of moving code from SinkWorld to Scintilla done? When it looks like a good idea and it works. ...Also, is SinkWorld interface backward compatible with Sintilla? (i.e. can one compile, for instance, SciTE using SinkWorld instead of Scintilla as the main library?) No, the API is completely different. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Support for CSS in the HTML Language
Kronuz: it'd be nice if the JavaScript was a full copy of the stand alone CPP lexer. In some ways I've been thinking about possibly reusing CPP functionality inside HTML; HTML would depend on CPP, and CPP would have more a generalized version of its lexer available for HTML (or others) use. (This would make the source code and hence the binary much smaller too) Both client-side and server-side JavaScript are handled (separately) in the HTML lexer. Arbitrarily composable lexers would be good: see SinkWorld for an implementation: http://scintilla.sourceforge.net/SinkWorld.html Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Moving some WordList and PropSet functionality from Scintilla to SciTE
Bug #1749659 bought up again some modularity problems with Scintilla/SciTE. The WordList and PropSet classes are defined in Scintilla and used both in Scintilla and SciTE. SciTE requirements have led to some complex methods (such as GetNearestWords) being added even though they are not used in Scintilla. Some projects using Scintilla also use these classes which makes it hard to change them when SciTE needs a new feature. I want to separate Scintilla and SciTE more. A new StringList class in SciTE will be equivalent to the current WordList. WordList drops methods that are not used in Scintilla. Scintilla gets to keep the name because WordList is used in all lexers including those distributed by others. All of the code responsible for iteration through a property set and for wild card file matching is moved from PropSet to SciTE's PropSetFile class. It would have been good to move over the variable expansion feature but unfortunately this has been exposed as SCI_GETPROPERTYEXPANDED. Projects that have used PropSet and WordList in similar ways to SciTE could either copy the classes from Scintilla into their code or use the modified classes from SciTE. In the future, I expect that SciTE will start using the standard C++ library rather than its own container classes and diverge further from Scintilla. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Re: [scintilla] Moving some WordList and PropSet functionality from Scintilla to SciTE
Shane Caraveo: Would this change the functionality provided by setkeywords, and the set/get property methods? That is the basic level we use in Komodo. This does not change the main Scintilla SCI_* interface and will only be an issue for applications that link directly to Scintilla's PropSet and WordList classes. PropSet's Get and Set will be the same as will WordList::Set. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
There seems to be some unnecessary entities. Looking at the set of properties mentioned in the DirectorExtension, [ipc.director.name, current.pid, ipc.scite.name, PipeName] it appears that PipeName is just giving ipc.scite.name a default value so could go into ipc.scite.name (is there a property hierarchy issue here?). I don't see any use for current.pid. AddSendPipe should error out a little more nicely by ignoring calls after s_send_cnt has reached MAX_PIPES. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] implementing indentifier search into SciTE
Jonathan Wilson: What I want is for the end user to be able to select, say, ThingTemplate=ControlPoint and then select go to definition somehow How hard would it be to add what I want to SciTE? Its a simple matter of writing some Lua and attaching it to a command or menu item. There's plenty of example Lua code at http://lua-users.org/wiki/SciteScripts Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] New version of scite-gdb
gcc (4.1.2) started complaining about the conversion from a void * (result of dlsym) into a function pointer. So now its coerced into an int (!) first. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE 1.74 .49Ru-Board released
mozers: [*] You can move tab to another place in list by menu command, by shortcut or by mouse. I copied in the implementation of the menu commands but did not add them to menus. The mouse drag version doesn't show obvious enough feedback for me. Since this included more #ifdefs to choose between Windows and GTK+, I moved some of the tab bar functionality into virtual methods to remove some #ifdefs. [*] Completely adjustable toolbar. This is quite good with an setting that is similar to existing SciTE usage. Doesn't appear to be implemented on GTK+ and can't see how to use system images. [*] and more... I may copy having separate styles for the path and match for find in files. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: Re: Re: Re: Re: Re: [scite] Single instance and Director Extension in SciTEGTK
Chachereau Nicolas: Basically the only change since the last version sent to the mailing list is that you can now call register: with a correspondant field as well, that is, sending :filepath:register:, where filepath is a file you created and to which SciTE will write the name of the pipe you can listen to (instead of using /tmp/SciTE.register). Doesn't that remove the need for /tmp/SciTE.register? Third and last, my proposal for an implementation of the focus: message. http://nico.esoxprojects.net/scite/focus.zip On Windows, ActivateWindow(const char *timestamp) is less obviously useful (and the argument isn't) so I'm not sure whether this should go in SciTEBase. OTOH I'm not sure it shouldn't either and making PerformOne virtual so there could be special handling on each platform is approximately as messy. NO_FILER is now becoming quite complex. Its mainly there to just turn off the director extension if there are problems building it or its not wanted. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
steve donovan: use SciTE as a single instance even without the director. If you want, we could break backward compatibility and require SciTE to be compiled without NO_FILER to be able to use check.if.already.open. Can we imagine a situation where people can't or won't put in the director interface? People with weird almost-Posix environments (things like QNX or OpenVMS) may not be able to get all the wanted calls. Those concerned with security may not want an open command channel that goes through /tmp files. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE 1.74 .49Ru-Board released
me:
[*] and more...
I may copy having separate styles for the path and match for find in files.
This is now done. I thought that distinguishing file search results
by looking for Internal search... would be too expensive and fragile
('Internal search for x in y' should really be localized) so
errorlist now breaks location from matched text for all GCC-style
messages when lexer.errorlist.value.separate is 1. Defaulted this to
off so that it is compatible with previous versions. Using style
SCE_ERR_VALUE=21 as 21 is next in sequence and default to black on
white in others.properties.
Neil
___
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] selection.back in Sc1.exe
instanton: For Sc1.exe built with the latest CVS and MinGW it appears that selection. back is not working. Whatever value is asigned to selection.back the background of selected text in Sc1 is always the same very light blue, Works for me with MinGW with default being a grey background. Setting selection.back=#FF in user properties makes that pink. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: Re: Re: Re: Re: [scite] Single instance and Director Extension in SciTEGTK
steve donovan: There is a danger of overengineering. This is a slipperly slope which will end up with us using something like DBus...! I had a another look at DBus. It probably is too complex although since there is a per-user instance there will be less opportunity for interference on multi-user machines. Its also a 'standard' which could lead to easier integration with other tools but DCOP and Orbit were also standards. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: Re: Re: Re: Re: Re: [scite] Single instance and Director Extension in SciTEGTK
Chachereau Nicolas: That's not really the use case. Suppose the director, for some reason, takes a while before asking SciTE to be activated. You might then have switched to another application, e.g. might be reading something in your web browser. It would then be an annoyance if SciTE was suddenly risen above what you're reading. On Windows the 'rule' is that the application currently with focus can donate it to another application. That means that sending a focus: message to the SciTE that should have focus wouldn't work on Windows since the OS will refuse to heed the call. Instead the SciTE with focus must call SetForegroundWindow on the SciTE that it is asking to open the file. The x11.windowid is actually something else altogether. ScitePM needs it for its own bring-SciTE-to-front. But then that will be handled properly... Yup, send a focus: message :) Sending a focus: message is better than exposing implementation details like window IDs if possible. SciTE derivatives could have multiple top level windows. Its likely that SciTE for GTK+ only runs on X now (sometimes on top of another system like OS X) but its not the only possibility. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Invalid free() in src/SciTEBuffers.cxx
Chachereau Nicolas: This is the patch, we just need to initialise stack in the class BufferList in SciTEBuffers.cxx: OK, committed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE 1.74 €
Axel Huizinga: after updating to 1.74 on my linux 64 bit box Scite type EUR instead of €. Can I change this behaviour? What locale settings are you using? Often people use ISO-8859-1 which does not include € but it should be OK in UTF-8. You can try character.set=1000 for ISO-8859-15 but that hasn't been thoroughly tested or documented. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] File type patterns like Makefile* do not work
Alexander Kriegisch:
Could you point me to the place inthe source code where the globbing is
done and also to the place where it is called for 'file.patterns.foo'?
Maybe I can hack it for myself with my extremely limited C/C++
abilities. I would also provide a patch to the mailing list which
somebody more adept could then refine and possibly commit.
PropSet::GetWild in scintilla/src/PropSet.cxx starting from if
(*keyfile == '*') {.
Neil
___
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Embedding Python
Benjamin Fisher: I'm not sure of the scope of this project but I know it will be not be quick. I guess my question is how impossible this is :), and how to start. Is anyone else interested in this or willing to help? I doubt it would take much effort. SciTE communicates with each extension through a fairly narrow interface defined in scite/src/Extender.h. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] TeX (was: Re: Re: Re: [scintilla] styler.GetPropertyInt and keywordlists)
instanton: After carefully inspecting the ColouriseTeXDoc code I realized that the keywordlists are not used most of the time because most TeX files would not begin with a comment line like %interface=tex or interface=latex and the like. I don't use TeX so just assume the people that contribute code know what they are doing. This becomes difficult when there are multiple ways of using a language and communities built around particular libraries as I can't judge the benefits or drawbacks. In some cases (e.g. for users using UTF8 encoding), the first line of the document must be used for other purposes (e.g. putting %# -*- coding: utf-8 -*- there in order that SciTE recognize the document as being written in UTF8 encoding) The encoding cookie should work on line 2 as well. So I'm wondering if you would accept the idea of replacing ColouriseTeXDoc code in LexTeX.cxx with something similar to ColoriseLaTeXDoc from LexOthers.cxx. To preserve current usage, it would be safer to implement a second lexer in LexTeX.cxx and allow users to choose between the two. If there are other TeX users on this list or the scite-interest list then they should make their opinions known. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Help on using ListBoxx
Yan Feng: I need a new ListBoxx window in SCite IDE ,but I don't know how to instance the object like ListBoxX lbx the VC++ always told me no ListBoxX declared. You shouldn't use ListBoxX directly from SciTE as it is contained within Scintilla and exposed using the autocompletion APIs. Have a look at SCI_AUTOCSHOW. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
Chachereau Nicolas: I think we should decide in which way SciTE reacts when it is sent a message. I think SciTE should be raised above the other windows in some cases, like: find:, goto:, insert:, loadsession:, macrocommand:, macrolist:, menucommand:, open:, output:, replaceall: Fronting windows with insufficient reason became such a problem on Windows that recent versions of Windows try to stop applications fronting themselves except in particular cases. SciTE should not be fronted by default for most of these commands as they damage use cases where SciTE is being controlled by a foreground application that wants to retain focus over a sequence of actions. How strict should we be about the closing: message? If there are any unsaved files, and the user cancels the quit, should SciTE send a message to tell the director it didn't quit? Or should it be impossible for the user to cancel a quit when the director is closing? There should probably be an alternative command for one or the other since it depends on the controlling application. I don't really like the assumption that a process can only communicate with SciTE if it started it. I think a process should be able to become a director even after SciTE started. Say you have a director application along with SciTE instances attached to it. You don't want the director to interfere with SciTE instances that you (or another director) started independently. To achieve this, we may have to change the method we use for IPC. Most of my thinking about the director interface was on Windows where WM_COPYDATA can be broadcast to all windows or sent to one in particular. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE text selection and VMware tools copy paste
Alexander Kriegisch: I use a debian'ish Linux (Elive) from within VMware Player 2 on a WinXP host. VMware tools are installed and working, i.e. copy paste to/from the VM and the host system works as expected, with one notable exception: I cannot copy any selected text directly out of SciTE's window to my host system, while pasting something into SciTe from WinXP works. There have been reports of copying from Scintilla/SciTE to other applications (aterm IIRC) not working so there may be something that could be fixed if anyone is sufficiently interested in debugging this. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Minimal way to export Lua symbols from SciTE
steve donovan: Right - I made a linker version script by whacking the lua.symbols And building with -rdynamic -Wl,--version-script lua.map Still works! The executable is a bit larger ;) but not as big as -rdynamic on its own. Builds for me too. Are all the Lua users happy enough with this for it to be committed? Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] File type patterns like Makefile* do not work
Alexander Kriegisch: file.patterns.make=makefile*;Makefile*;*.mak;configure*;*.mk SciTE globs can only match '*' as a prefix, not as a suffix. I will remove configure* from others.properties. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Is a SciTEGTK.h possible?
mitchell: I notice in win32/, there is a SciTEWin.h so SciTEWin.cxx, SciTEWinDlg.cxx, and SciTEWinBar.cxx can be separated instead of creating one huge SciTEWin.cxx file. I don't think that this has actually been a good split as its not really obvious which file a piece of functionality is going to be in. Having a single .cxx file for a class would be easier to navigate. However SciTEGTK.cxx is one huge file. I don't have enough knowledge of SciTE/C++ to separate the class definitions for a SciTEGTK.h in order to create a new SciTEGTKPM.cxx, a project manager/file browser that could be potentially lengthy. It would be better to find a sensible way to break the classes up and then represent this structure in the headers. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Minimal way to export Lua symbols from SciTE
steve donovan: (BTW, I get a _smaller_ executable using this explicit retain-symbols-file technique!) Its smaller because it has removed most of the symbol information so is harder to debug. The --version-script linker option may be better. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Odd Behaviour when saving untitled buffers with GTK SciTE
steve donovan:
This gtk_file_chooser_set_filename() line should be replaced with:
if (savePath.IsUntitled()) { // saving 'untitled'
gtk_file_chooser_set_current_folder(GTK_FILE_CHOOSER(dlg),
savePath.Directory().AsInternal());
} else {
gtk_file_chooser_set_filename(GTK_FILE_CHOOSER(dlg), savePath.AsInternal());
}
OK, committed.
Neil
___
Scite-interest mailing list
Scite-interest@lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: Minimal way to export Lua symbols from SciTE
mitchell: I find it easier just to link to the Lua library on my system rather than building Lua into SciTE. I find it relatively straightforward in Linux :) The only-dependency-is-GTK policy is a bit of a reaction against some Linux applications which are a pain to install because of the need to install prerequisites. Oh more elegant, easier, etc, no doubt! But Neil likes a single executable under Linux, and he's the man that makes the decisions ;) Everyone else can release distributions of SciTE if they want. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTEDirectory.properties
Bambero: As I see SciTEDirectory.properties won't works under linux (gtk). I have: properties.directory.enable=1 But it won't works. Works for me: added properties.directory.enable=1 to user properties, opened directory properties and set caret.fore=#00FF00. Saved and the caret is green. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Making Scintilla a wide character window on NT
Bug #1732146 reports that SciTE does not allow keyboard input for the Armenian language on Windows. This is because Armenian, like Devanagari, Tamil, and Georgian do not have code pages so can only work through Unicode and only on NT and successors, not on Windows 9x. To fix this on NT, Scintilla is now registering as a wide character window class and SciTE is calling GetMessageW and DispatchMessageW in its event loop. On 9x, the current calls are still used. The WM_CHAR handler has been modified to treat the wParam as a Unicode character on NT. This seems to be the minimum set of changes needed. Applications that use Scintilla and would like to support these languages should use GetMessageW and DispatchMessageW either exclusively if Windows 9x is not supported or conditionally if it is. Since it is no longer easy for me to test on Windows 9x, this code has not yet been tested there so if you still run on Windows 9x you may want to try this. The changes are to pieces of code that are core to Scintilla's input handling and all of SciTE's behaviour on Windows so could affect other aspects. Changes available from CVS and from http://scintilla.sourceforge.net/scite.zip Source http://scintilla.sourceforge.net/wscite.zip Windows executable Bug: https://sourceforge.net/tracker/index.php?func=detailaid=1732146group_id=2439atid=102439 Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] compiling scite under Linux x86_64
hon fui lee: I've trying to compile scite under Linux x86_64 (RHEL 2) for both GTK1 and GTK2, but failed. scintilla compilation is OK. GTK+ 1.x is no longer supported by SciTE. At least GTK+ 2.4 is now required for the file chooser dialog. Some APIs may be used from later versions of GTK+ but they should be reasonably easy to #ifdef out if needed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Compiling in two phases
Baltasar: I suppose that the direct solution is to use compile for the compiler, build for the assembler, and then go for execution, but I'd like to have it done in just one step. It'd be cool if these steps (compile build) were called automatically when performing Go, but they are not. You can use command.go.needs.filepattern but I'd advise learning how to use a build program like make. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] An Idea For Menus
Hans Joseph Solbrig: I would like to create code to allow sub-menu and sub-sub-men off the tools menu to be created from properties. This is quite messy. The SciTE-Ru distribution includes a cascading tools menu but I did not include this code because I didn't think it was implemented well. http://scite.ruteam.ru/ Also, another very useful addition would be to allow a tools menu command to be added for any extension - recognize *.* as well as *.cpp. SciTE's wildcard code only handles a single '*' in each pattern. This works with '*': command.name.11.*=Where am I? command.11.*=cmd /c echo $(FilePath) Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] New version of scite-gdb
Steve Donovan: The Director interface under Unix remains a bit klunky. I think for my next project I'll review the code and see if we can work around the inflexibilities without breaking backward compatibility with ScitePM, etc. If there is a better communications technique that is more similar to the Windows version of the Director interface then it is probably worth a backwards incompatible change. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] 1.74: Pango Warning: Invalid UTF-8
Felix Kater: when I enable utf-8 and also the dynamic popups for already typed words (don't know how you call them) and if the popup tries to display an *existing/listed* word with the german umlaut u (with two dots) I get: (scite:8921): Pango-Warning **: Invalid UTF-8 string passed to pango_layout_set_text() The code that is finding the similar words in the text does not understand UTF-8, only byte value characters so stops when it finds a byte that is not in the list of word characters. This then presents half of a UTF-8 character to the list show code which then fails. Its unlikely I'll fix this. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Long path problem
Marcel x: should be char pipeData[PATH_MAX]; ? Committed except with MAX_PATH which is the internal version of PATH_MAX. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] SciTE 1.74 released
KHMan: * need to update list of lexers in SciTEDoc.html: cmake, gap, plm, progress * in the global properties, menu.language, the entry for Forth is missing, it can be commented out by default Committed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] caret.fore property
mitchell: I figure since generally the editor and output pane background colors will be the same, caret.fore should apply to both of them. OK, committed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Re: April White's ( PhiLho's) tool menu generator
mitchell: I suspect it has to do with OnClear. It now is called *before* the Lua global namespace is reinitialized, giving scripts a chance to clean up after themselves as in the documentation. I thinks its a scoping or lifetime issue. If toolList is initialised after udl_ListTools then its OK: local toolList = Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] 1.74 release candidate code
I would like to release Scintilla and SciTE 1.74 Monday morning (21 hours from now). The release candidate code is available from CVS or from http://scintilla.sourceforge.net/scite.zip Source http://scintilla.sourceforge.net/wscite.zip Windows executable These are the same as the last downloads except for changes to HTML. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] 1.74 test downloads
Chris Sutcliffe: Does this version have 'loadlib' disabled? When I try to start scite_gdb I get: C:\wscite\scite-gdb\scite_lua\gdb.lua:261: attempt to call global 'loadlib' (a nil value) Looks like it got renamed to package.loadlib for Lua 5.1. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
