Neil Hodgson | 2 Jul 02:35 2004
Picon

Re: Re: use monospaced still there

   I have removed the use.monospaced property. The Frequently Asked Question
section of the SciTE documentation is now a separate document
http://scintilla.sourceforge.net/SciTEFAQ.html
   Each question is an anchor so now can be easily referenced like
http://scintilla.sourceforge.net/SciTEFAQ.html#Monospaced

   A minor fix on GTK+ 2.4 SciTE allows the Enter key to accept the file
chooser dialog. Users pining for keyboard control in the new chooser should
be aware that Alt+Home selects their home directory and Ctrl+L displays a
text entry box with autocompletion to allow typed entry of file names.

   The changes are present in CVS and also available from
http://scintilla.sourceforge.net/scite.zip Source
http://scintilla.sourceforge.net/wscite.zip Windows executable

   Neil
Bruce Dodson | 3 Jul 18:46 2004
Picon

Re: Re: use monospaced still there

I see that the "Use Monospaced Font" menu option remains.  I
had already removed it from my copy, based on an
understanding that it was going to be removed.
Nevertheless, I'm not going to restore it to my copy.

The "Use Monospaced Font" option is useless to me, since I
want to start in that mode, and I no longer have a way to do
that, other than my "properties and script" implementation.
Worse, the two options are incompatible: if "Use Monospaced
Font" is on, then nothing happens when you click "Toggle
Override Font", and likewise if "Toggle Override" is on,
nothing happens when you click "Use Monospaced".  Both have
to be off to see proportional fonts.  I can't publish
software with that kind of "combination lock" user
interface.

Obviously, it would have been much easier to just keep the
use.monospaced property setting in my copy of the codebase
so that a new implementation was not required.  However, I
hope the other changes I made to support this (e.g. the
ability to override and reset properties from script) were
useful enough to justify this effort.

Bruce
Neil Hodgson | 3 Jul 23:57 2004
Picon

Re: Re: Re: use monospaced still there

Bruce Dodson:

> I see that the "Use Monospaced Font" menu option remains.

   That is what I meant by """What I want is the original intent of the
monospaced option: a menu item that allows you to choose to temporarily see
text as monospaced."""

> I had already removed it from my copy, based on an
> understanding that it was going to be removed.
> Nevertheless, I'm not going to restore it to my copy.

   OK. Would you like to add a #ifndef to SciTERes.rc and SciTEGTK.cxx so
you don't have to patch updated versions?

> The "Use Monospaced Font" option is useless to me, since I
> want to start in that mode, and I no longer have a way to do
> that, other than my "properties and script" implementation.

   Yes, some options in SciTE will be useless to you. Unless / until user
definable menus are implemented this is going to be the case for everyone.

   Neil
Bruce Dodson | 4 Jul 15:37 2004
Picon

Re: Re: Re: use monospaced still there

>    That is what I meant by """What I want is the original
intent of the

And what I though you meant is that I had done that.

>    Yes, some options in SciTE will be useless to you.
Unless / until user

I don't mind options that are useless to me.  It wasn't so
much that, but the problem with this one is the
incompatibility.

How about an alternative in which I treat my "Toggle
Override Font" as a prototype and change the "Use Monospaced
Font" to work the same as my script, except per-buffer?
Bruce Dodson | 4 Jul 18:57 2004
Picon

Use Monospaced / Use Override reconciled?

In my snapshot,
http://gisdeveloper.tripod.com/scite_lua.html, I've taken
out the "Toggle Override Font" command, and ported it to C++
so it can replace the current implementation of "Use
Monospaced Font".

Note that you need to add ,$(font.override) to your font
properties that need to be monospaceable.  My distribution
would have this, and I assume that if Neil took this
implementation, he would add that to his properties too, so
most users won't notice or care that anything has changed
under the hood.

To have monospaced by default, set font.override explicitly
in the properties.  Otherwise it takes the value of
font.monospaced when you toggle it on.  I don't think this
has the same opportunities for confusion as the old
use.monospaced property.

I'm going to be away for a week.  Whether this goes into
core or not doesn't matter much to me.  The main thing is
that I didn't want my distro to have two "Monospaced"
toggles that can break each other.  Also, if I can help it,
I don't want my monospaced toggle to be in a different place
than the standard version.  Beyond that, the changes are
isolated to only a few places and will be easy to maintain
separately if need be.

Bruce
(Continue reading)

Martin D. McLauchlan | 3 Jul 12:11 2004
Picon

SciTE - Environmental Variables

SciTE is looking for the SciTEUser.property file in the C:\WINNT\Profiles\Admistrator directory/folder. I think the directory is based on the setting of some environment variable. I've searched the registry and don't find anything similar to this. Moreover, there is no corresponding variable in the Systme Property panel.
 
Question: Where are the SciTE variables stored and how are they set/changed?
 
Any assistance will be greatly appreciated.
_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Daniel | 5 Jul 10:45 2004

Re: SciTE - Environmental Variables

Hello Martin,

Saturday, July 3, 2004, 12:11:11 PM, you wrote:

> SciTE is looking for the SciTEUser.property file in the
> C:\WINNT\Profiles\Admistrator directory/folder. I think the
> directory is based on the setting of some environment variable. I've
> searched the registry and don't find anything similar to this.
> Moreover, there is no corresponding variable in the Systme Property
> panel.

> Question: Where are the SciTE variables stored and how are they set/changed?

The   folder   you   cited  is  stored  in  the  environment  variable
%USERPROFILE% which on Win2k/XP is set with the value C:\Documents and
Settings\<UseerName> or better %HOMEDRIVE%%HOMEPATH%
These  variables  should  be  available  in the Control Panel's System
applet, I don't remeber the exact position in WinNT4 but look for them
in the last tab.

Hope this helps.
Steve Donovan | 6 Jul 08:33 2004
Picon

Experimental GDB extension

Hi guys,

I've ben experimenting with a SciTE extension to run GDB.  It does
the basics, like jumping to a line when a breakpoint or a runtime
error occurs, and provides a console for entering other commands.

Some observations: 
- it would be nice if 'goto' could be enhanced to bring the selected
line to the centre of the buffer, perhaps by using an 'adverb'
command that precedes and modifies any goto: or find: that
follows it.
- One needs to put a distinct marker to show current 
execution position (changing colour to indicate whether it's
a break or an error would be cool)

Now it's written entirely in Lua, using my GTK bindings, and that
got me thinking about how one could integrate this directly
into SciTE.  The philosophy is always the _mininum_ extra
functionality needed to get Lua to do the actual work, and
it appears that one would only need a hundred or so lines, mostly
the pseudo-terminal stuff to capture processes as slaves.

Of course, to do this properly one needs a way for Lua scripts
to access defined markers in all buffers for breakpoint support.

 Any ideas about that?

steve d.

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Jan Hendrik | 6 Jul 09:12 2004
Picon

Re: Re: Re: use monospaced still there

Concerning [scite] Re: Re: use monospaced still there
Bruce Dodson wrote on 30 Jun 2004, 17:45, at least in part:

> I don't mean to keep repeating myself, but... in what way is this
> problem not solved by the script I posted to the list yesterday?

... by the fact that scripts are for programemrs, not for users. ;)  
*nix folks may see this differently, but IMHO configuring basic 
options should not be a programming task.

Bruce, I saw your posting and I noticed you had a script, but 
anything that just sounds Luaish is skipped here immediately ... I 
do a lot of HTML stuff, mostly with Homesite, but quick edits in 
SciTE, and out of necessity I scratch the surface of Javascript, 
Python and, most recently, PHP using SciTE, but getting into even 
one more programming or scripting language just to configure the 
editor is something I really do not need ... For me and my needs 
an editor is a tool like a hammer that should work without first 
needing another degree (usual learning curve aside).  IOW my aim 
is producing content, not becoming or being a programmer.  
However, I fully understand that SciTE aims at professional 
developers knowing several languages and writing editors and 
database frontends just to relax (and scripts while sleeping). <G>  
In so far our mileages differ a lot.

Now I have written a long useless sermon instead of scratching 
PHP or writing someone else ... sorry.

Best regards

Jan Hendrik

---------------------------------------
In memoriam Ronald Reagan:

     Let us build cathedrals of peace,
     where the people are free.
                -- Ronald Reagan
Philippe Lhoste | 6 Jul 12:49 2004
Picon
Picon

Re: Re: Re: use monospaced still there

> ... by the fact that scripts are for programemrs, not for users. ;)  
> *nix folks may see this differently, but IMHO configuring basic 
> options should not be a programming task.
> 
> Bruce, I saw your posting and I noticed you had a script, but 
> anything that just sounds Luaish is skipped here immediately ... I 
> do a lot of HTML stuff, mostly with Homesite, but quick edits in 
> SciTE, and out of necessity I scratch the surface of Javascript, 
> Python and, most recently, PHP using SciTE, but getting into even 
> one more programming or scripting language just to configure the 
> editor is something I really do not need ... For me and my needs 
> an editor is a tool like a hammer that should work without first 
> needing another degree (usual learning curve aside).  IOW my aim 
> is producing content, not becoming or being a programmer.  

I fully understand your point of view, as I keep repeating I wish to 
learn some other languages, like Python, but just don't have the time to 
do so (and perhaps the motivation? I started to learn PHP, but it can be 
useful in my future job, and I currently spend quite some time on SVG, 
but I like vector graphics...).

Well, my arguments aren't the same as your, but it reduces down to one 
point: one has only limited time.

That said, Lua is nice and simple, and Lua use in SciTE is probably even 
more simple. If you ever have the slightest wish/need to take a look, 
don't hesitate, it is very easy to learn.
But of course, you have to spend some hours for that, nothing is really 
free, if you don't pay with money, you pay with time...
That said, sometime using a simple script can save quite some time in 
hand editing. For example, to reduce floating point precision of 
coordinates pairs in a SVG file, I just wrote some lines (I added 
formating and comments for you :-) It was smaller and faster to type!):

function ReduceFPP()
   -- Read current selection
   local text, len = editor:GetSelText()
   -- Search FP number pairs separated by comas
   -- and provide them to a function that round them
   -- and spit them out to replace orignal values
   text = string.gsub(text, "([.%d]+),([.%d]+)",
     function (n1, n2)
       return math.floor(n1*10 + 0.5)/10 .. ',' ..
              math.floor(n2*10 + 0.5)/10
     end)
   -- Replace current selection with modified text
   editor:ReplaceSel(text)
end

I also used this to translate coordinates, etc.
You can use similar code to renumber a series of numbers, reformat HTML 
code, convert high Ascii to entities, etc.

And even if you are not a programmer, you can easily use scripts 
provided by others, you just have to set up some bindings to call them.

I don't try to evangelize you :-) of course. Just to say that scripting 
is good, even for non-programmers (and you already have programming 
basics anyway...).

Regards.

--

-- 
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://Phi.Lho.free.fr
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--

Gmane