Neil Hodgson wrote:
> Alphax:
>
>
>>Not sure if this is related to the makefiles or my system config, but
>>after compiling Scintilla (using mingw32-make under MSYS),
>
>
>To me MSYS is a strange environment. Possibly you are seeing
> effects from the different shell (copy vs cp?) or simil
You will not be able to achieve this in the way you want. Implement
the SciTE director interface by providing a window that can exchange
WM_COPYDATA messages with active SciTE instances.
http://scintilla.sourceforge.net/SciTEDirector.html
Neil
___
Hi
I've found the following typo in scite/gtk/SciTEGTK.cxx
--- SciTEGTK.cxx.ORG2005-09-16 09:32:34.48333 +0200
+++ SciTEGTK.cxx2005-09-16 10:01:15.353319000 +0200
@@ -330,7 +330,7 @@
virtual SString GetRangeInUIEncoding(Window &wCurrent, int selStart,
int selEnd);
>how about implementing dialog window, filled with list of filename (no
>full path) of the buffers, just like in Visual Studio .NET\'s Alt-W-W
>(Window-Windows). It\'s pretty handy when you had this 50+ buffers opened
>at a time,
I don't think anyone needs 50+ files open at the same time.
I hav
Well I dont think that I would ever need it either. But vs.net wouldnt
have had that feature for nothing. Ask any vc.net studio coders whether
they use Alt-W-w.
This has the relationship to an important limitation of then ability of
a person when dealing with increasingly big software: limited
> Ask any vc.net studio coders whether they use Alt-W-w.
They may use it for selecting files to be tiled on screen,
or they open that many files just because opening a file
in VS is slw.
If there are not that many files, switching with Ctrl+Tab
or Tab Bar is obviously faster.
>z-order buffer
In older versions, the New command would set the file name
information to use the current directory at that time with an empty
file name. Now a new file has a completely empty path and the open
dialog opens on the current directory at open time. I can't see strong
reasons for preferring any par
Roman Hubacek:
> Typically I work on a project (i.e. a few files in one directory), so it
> is useful to open files from there - it works great. When I wanted to
> add new file, the same applied. I can't see why not hold current directory.
Which directory do you mean *exactly*? The directory o
Helmut Jarausch:
> I've found the following typo in scite/gtk/SciTEGTK.cxx
>
> --- SciTEGTK.cxx.ORG2005-09-16 09:32:34.48333 +0200
> +++ SciTEGTK.cxx2005-09-16 10:01:15.353319000 +0200
> @@ -330,7 +330,7 @@
> virtual SString GetRangeInUIEncoding(Window &wCurrent, int selSt
Dody Suria Wijaya:
> how about implementing dialog window, filled with list of filename (no
> full path) of the buffers, just like in Visual Studio .NET's Alt-W-W
> (Window-Windows).
This dialog is almost completely useless. It only contains 6 more
files than the Window menu in a non-resizeab
Piotr Fusik:
> What's that z-order buffer switching thing?
> First time I saw it, I misread it as "z-buffer" (3D text editor?). :-)
Z-order means remembering the order in which buffers are activated
and switching between them in that order. This makes it easy to
switch to recently used buffer
Typically I work on a project (i.e. a few files in one directory), so it
is useful to open files from there - it works great. When I wanted to
add new file, the same applied. I can't see why not hold current directory.
Which directory do you mean *exactly*? The directory of the file
active b
Dody Suria Wijaya wrote:
how about implementing dialog window, filled with list of filename (no
full path) of the buffers, just like in Visual Studio .NET's Alt-W-W
(Window-Windows). It's pretty handy when you had this 50+ buffers opened
at a time, and you know the file's name, and you just wan
Neil Hodgson wrote:
recently I've upgraded to new Scite (1.66) and after some time I've
noticed some different behavior. I have some files in a directory and
editing some of them in Scite. When I create new file and try to save it
(SaveAs), I'm in "Documents" directory instead of last file dir
Neil Hodgson wrote:
Accident (Microsoft would say "It is an unintended feature"...) :-)
If a control keystroke isn't mapped to a SciTE or Scintilla command, it
is entered as a regular character.
Its not really accidental: I think it is useful to be able to enter
control characters although t
> my.own.color=#FF
> style.*.32=fore:$(my.own.color) <-- this working properly
> error.marker.fore=$(my.own.color) <-- this change color by RED (#FF),>
GREEN (#00FF00) or BLUE (#FF) randomly > (working non-stable and never>
properly).
< This is incorrect syntax and will not work.
Pl
>This dialog is almost completely useless. It only contains 6 more
> files than the Window menu in a non-resizeable dialog. SciTE's Buffers
> menu can contain many more paths. In VS .Net, the Solution Explorer
> can, at least, be resized and organized with folders.
I don't think you understand
> They may use it for selecting files to be tiled on screen,
> or they open that many files just because opening a file
> in VS is slw.
> If there are not that many files, switching with Ctrl+Tab
> or Tab Bar is obviously faster.
On contrary, I have never seen vs developer actually "tile" the
Thanks, it's quite similar.
I'll work it up soon, maybe there are some codes that can be quickly
copied as a basis, so we can see for real whether putting buffer list
can be useful, or just become redundant.
On 9/17/05, Philippe Lhoste <[EMAIL PROTECTED]> wrote:
> Perhaps something like this sc
Alphax wrote:
Neil Hodgson wrote:
Alphax:
Not sure if this is related to the makefiles or my system config, but
after compiling Scintilla (using mingw32-make under MSYS),
To me MSYS is a strange environment. Possibly you are seeing
effects from the different shell (copy vs cp?) or similar.
Kein-Hong Man wrote:
Alphax wrote:
Neil Hodgson wrote:
Alphax:
Not sure if this is related to the makefiles or my system config, but
after compiling Scintilla (using mingw32-make under MSYS),
To me MSYS is a strange environment. Possibly you are seeing
effects from the different shell (c
Was my previous message (below) inappropriate for this list? If so,
apologies and could anyone suggest where I should ask this? If not, can
anyone throw me a bone? ;)
-geoff
Geoff Catlin wrote:
I'm using SciTE for PHP development and I'd like to be able to
syntax-check my code whenever the
Павел Кудинов wrote:
my.own.color=#FF
style.*.32=fore:$(my.own.color) <-- this working properly
error.marker.fore=$(my.own.color) <-- this change color by RED (#FF),>
GREEN (#00FF00) or BLUE (#FF) randomly > (working non-stable and never>
properly).
< This is incorrect syntax and
Geoff Catlin wrote:
Was my previous message (below) inappropriate for this list? If so,
apologies and could anyone suggest where I should ask this? If not, can
anyone throw me a bone? ;)
Well, not to be unhelpful (and speaking for myself), this just seemed
to be not only going pretty far in
Hi!
Another problem I couldn' t resolve since a long time:
my settings:
autocompleteword.automatic=1
autocomplete.php.start.characters=-_
autocomplete.php.fillups=$(SciteDefaultHome)\php.api
but on values like $_POST it does not work.
I found when I delete the $ in my php.api ( leaving only _P
Dody Suria Wijaya wrote:
how about implementing dialog window, filled with list of filename (no
full path) of the buffers, just like in Visual Studio .NET's Alt-W-W
(Window-Windows). It's pretty handy when you had this 50+ buffers opened
at a time, and you know the file's name, and you just wa
Robert, thanks for the reply.
I suppose my real question is this: is IDE-esque syntax checking, as
described below, do-able in SciTE via Lua scripting? Or is that a bit
outside its scope? (In which case I'll be relocating to the
wxPython-users list.)
-geoff
I'm using SciTE for PHP developm
Geoff Catlin wrote:
Robert, thanks for the reply.
I suppose my real question is this: is IDE-esque syntax checking, as
described below, do-able in SciTE via Lua scripting? Or is that a bit
outside its scope? (In which case I'll be relocating to the
wxPython-users list.)
Since I do not use
Robert Roessler:
> SString colour = props.Get(key);
>
> It seems to me that this could (should?) be:
>
> SString colour = props.GetExpanded(key);
OK, committed.
> So, without more information, I would guess that this is just
> historical... and the 7 [property-fetching] calls that deal with
Philippe Lhoste:
> That's why it is "accidental", because it is not consistent. A better
> way to enter such control chars may be to use good old two stroke
> command, like Ctrl+Y Ctrl+.
Scintilla has no abilities to handle multiple key sequences and
such a feature needs careful design to cope
Geoff Catlin:
Sometimes the reason for lack of reply is just that no one has
anything much to say. In your case, I doubt anyone has implemented
anything similar.
> I suppose my real question is this: is IDE-esque syntax checking, as
> described below, do-able in SciTE via Lua scripting? Or is
Kein-Hong Man:
> I encounter this when I use Msys, but was so far too lazy to fix
> it. Changing some backslashes in the Makefile fixes things:
>
> ../bin/Scintilla.dll: ../../scintilla/bin/Scintilla.dll
> $(COPY) ../../scintilla/bin/Scintilla.dll $@
> ...
Unfortunately that leads t
32 matches
Mail list logo
