Re: Re: Show MRU files into menuItems defined by fileStackMax.

Jérôme LAFORGE:

> Originally, I didn't want modify the design of the code. That's reason
> why I implemented this code with explicit memory managment.
> So, I changed it, and as you told me I replaced all this code with
> containers from the C++ standard library (deque) and I removed all
> explicit memory managment.
> I hope that this new patch is acceptable for you in term of complexity

   Instead of being simpler, the patch has grown from 164 to 414
lines. I won't be applying it in its current form.

   Neil

--

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

Re: Save into session "Find what" and "Replace with"

Jérôme LAFORGE:

> I want to know if there is a way (script lua or something else) to save "Find what" and "Replace with"
> from search dialog into session (file .SciTE.session).
> In most case, I search (or replace) the same pattern, and it's quite annoying for me to retype it again.
> In the case, there is no way. I propose you this patch that works GTK+ and normally on Windows (but I didn't
test on Windows)
> http://pastebin.com/4xi61u0T

   The restoration of the find/replace memories is not integrated into
the session restore code so triggers unexpectedly.

   Properties use '.' between words, not capitalization like "findWhat".

   Neil

--

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

Re: GTK+ "Show hidden files" toggle removal from File Open

Me:

>   I think the best solution is to remove SciTE's features and rely on
> the platform standard behaviour.

   The fileselector.show.hidden property and "Show hidden files" check
box have now been removed.

   Neil

--

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

Re: Non ascii characters in black, howto?

Here is how I handled changing the non-ascii characters (below #32) to
non-black (i.e., non-reverse). The context was that I needed to mimic
the appearance and underlying control characters (i.e., hidden codes)
used by the Borland Sprint editor. That editor, dating from 1988, was/
is a fully programmable and customizable editor/formatter/printer
combination for which I have 20,000+ documents/programs in this
format. In moving to Windows 7, I needed a replacement editor - and
SciTE with Lua became the best option. These code changes below could
be abstracted to be customizable from properties and/or Lua, but I
needed the changes immediately so I just change the source and
recompile for each SciTE version. Here are the changes.

#1. The default control character is now a space (#32). In conjunction
with change #4 (below), an annoying flicker/change between states that
would otherwise happen when files are loaded and/or closed is avoided.

In Scintilla\Editor.cxx:

old:

	controlCharSymbol = 0; /* Draw the control characters */

new:

	controlCharSymbol = 32; /* Draw the control characters */

#2. The default control character text is replaced with a "^" version
(i.e., the hidden codes to be displayed) to mimic the Borland Sprint
edition (when revealing the underlying codes).

Re: Re: New Asm Syntax file for SciTE

On 9/29/2011 12:21 AM, Marat Dukhan wrote:
> Fixed typo in es.
> Also added LWP instructions from "AMD64 Technology Lightweight
> Profiling Specification", Publication No. 43724, Revision No. 3.08,
> August 2010

Sorry for the delay, here is the MASM stuff. I was sidetracked 
training my immune system on the latest strain of common cold.

The extra MASM-specific mnemonics are names with an added suffix 
for disambiguation purposes:

; F prevents epilogue code generation in a PROC block
iretf iretdf
; W and D is to disambiguate CX/ECX size
loopw loopd
loopew looped loopz loopzw loopzd
loopnew loopned loopnz loopnzw loopnzd
; W and D is to disambiguate operand size
pushw pushd
; N=near return, F=far return
retn retf

LOOPZ and LOOPNZ are very common alternate forms of LOOPE, LOOPNE. 
Some of these are also on the wiki page you listed as reference.

I think it's best to just put them into their respective 
instruction lists, enabled by default.

I can confirm that ESC is simply a section of the first 

Re: New Asm Syntax file for SciTE

Updated the file with MASM pseudoinstructions and loop(n)z forms.
Also corrected some errors in XOP and AVX2 instructions,
added AMD TBM instruction set, and rewrote NASM stuff according to
the NASM 2.10rc8 documentation.

I think now the the syntax file can be included to SciTE distrib.

Regards,
Marat Dukhan

On Oct 1, 10:32 pm, KHMan <keinh... <at> gmail.com> wrote:
> On 9/29/2011 12:21 AM, Marat Dukhan wrote:
>
> > Fixed typo in es.
> > Also added LWP instructions from "AMD64 Technology Lightweight
> > Profiling Specification", Publication No. 43724, Revision No. 3.08,
> > August 2010
>
> Sorry for the delay, here is the MASM stuff. I was sidetracked
> training my immune system on the latest strain of common cold.
>
> The extra MASM-specific mnemonics are names with an added suffix
> for disambiguation purposes:
>
> ; F prevents epilogue code generation in a PROC block
> iretf iretdf
> ; W and D is to disambiguate CX/ECX size
> loopw loopd
> loopew looped loopz loopzw loopzd
> loopnew loopned loopnz loopnzw loopnzd

Re: Re: New Asm Syntax file for SciTE

On 10/3/2011 12:51 AM, Marat Dukhan wrote:
> Updated the file with MASM pseudoinstructions and loop(n)z forms.
> Also corrected some errors in XOP and AVX2 instructions,
> added AMD TBM instruction set, and rewrote NASM stuff according to
> the NASM 2.10rc8 documentation.
>
> I think now the the syntax file can be included to SciTE distrib.

Patience. We're not going to push a broken file into SciTE, are 
we? 

I'm viewing the NASM 2.09.10 documentation as text in SciTE with 
your latest properties file, and I see...

CDQE
CQO
FUCOMI
FUCOMIP
16 CMPPS pseudo-ops

...up to section B.1.3.

At least one AVX typo, VBLENDPD...

Are you going to add all those AVX pseudo-mnemonics?

 

--

-- 
Cheers,

Test code with fractional positioning and changed session saving

   To allow testing of some new code, there are executable and source
code downloads available.

   This includes the Direct2D/DirectWrite support for Windows 7 and
Vista which includes fractional horizontal character positioning. It
is turned on with technology=1 and GDI is restored with technology=0.

   Session files are now saved without switching to each buffer so
should be faster. This required that the bookmarks for a buffer are
saved when switching away from that buffer if session.bookmarks=1. The
caret position is now saved instead of the start of the selection.

   Committed to Hg and available from
http://www.scintilla.org/scite.zip  Source
http://www.scintilla.org/wscite.zip Windows executable

  Neil

--

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

Re: Test code with fractional positioning and changed session saving

Re: Test code with fractional positioning and changed session saving

Remi Gillig:

> Nice ! What's the difference with GDI? What's the advantage of fractional
> positioning?

   Direct2D draws antialiased: see the smooth circular symbols in the
fold margin with fold.symbols=2. DirectWrite draws text with more
accurate shapes but a little less sharp. It allows fractional sizes so
you can specify
font.base=font:Verdana,size:9.7

   Fractional positioning is more consistent. Currently on some
platforms characters within a style run are positioned at fractional
positions but the ends are rounded off to the nearest pixel. Thus you
will see either more or less space than expected between runs. Another
effect is that if you change the style of some text then both it and
the text following will move a small amount.

   Neil

--

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