headers
J. Baltasar Garcia Perez-Schofield | 4 May 13:07
Picon

scite reading configuration files


	Hi !

	I'm new at Scite, this is my first post. My question is regarding a
project of mine, which consists of a VM and a few compilers.

	http://trevinca.ei.uvigo.es/~jgarcia/TO/zero

	This is a non-profit project.

	There's still no IDE for Zero, and my plan was to create package (a zip
file) with scite and the configuration files modifed in order to be able
to manage those compilers for the VM.

	My questions are:

	a) Whether this is legal or not. I would add a side note in the link to
the package pointing to the Scite web page and thanking the
collaboration.

	b) While scite reading the configuration files in the same directory
works for windows, it does not work for linux. The linux scite expects
to find the configuration files in /usr/share/scite, while I would like
it to read them from the same directory, such as in Windows. I wonder
whether it would be possible to pass a command line option or something
similar, making scite to read the configuration files from the directory
it is.

	Thank you in advance,
(Continue reading)

Permalink | Reply | 6 comments |
headers
Neil Hodgson | 5 May 01:57
Picon

Re: scite reading configuration files

J. Baltasar Garcia Perez-Schofield:

>         My questions are:
>
>         a) Whether this is legal or not. I would add a side note in the link to
> the package pointing to the Scite web page and thanking the
> collaboration.

   Packaging SciTE is completely legal as described in the license
http://scintilla.sourceforge.net/License.txt

>         b) While scite reading the configuration files in the same directory
> works for windows, it does not work for linux. The linux scite expects
> to find the configuration files in /usr/share/scite, while I would like
> it to read them from the same directory, such as in Windows. I wonder
> whether it would be possible to pass a command line option or something
> similar, making scite to read the configuration files from the directory
> it is.

   Set SciTE_HOME:
""" On Windows, the global properties file is located in the directory
of the executable. The user properties file is looked for in the user
profile directory as set in the USERPROFILE environment variable, or
in the directory of the executable if USERPROFILE is not set. For GTK+
the user properties file is found in the user's home directory and the
global properties in a directory set at build time - normally
/usr/share/scite. If the "SciTE_HOME" environment variable is set on
either Windows or GTK+ then it is where both the global and user
properties files are found."""
(Continue reading)

Permalink | Reply | 5 comments |
headers
Scorpio | 5 May 08:33
Picon
Gravatar

Re: scite reading configuration files

When U double click a file configured to open by default in SciTE, how
to make it open in the new tab in the latest window? And can we have
options of whether to open in new instance or in a new tab by right
clicking? And how do we do it...?

On 5/5/07, Neil Hodgson <nyamatongwe <at> gmail.com> wrote:
> J. Baltasar Garcia Perez-Schofield:
>
> >         My questions are:
> >
> >         a) Whether this is legal or not. I would add a side note in the link to
> > the package pointing to the Scite web page and thanking the
> > collaboration.
>
>    Packaging SciTE is completely legal as described in the license
> http://scintilla.sourceforge.net/License.txt
>
> >         b) While scite reading the configuration files in the same directory
> > works for windows, it does not work for linux. The linux scite expects
> > to find the configuration files in /usr/share/scite, while I would like
> > it to read them from the same directory, such as in Windows. I wonder
> > whether it would be possible to pass a command line option or something
> > similar, making scite to read the configuration files from the directory
> > it is.
>
>    Set SciTE_HOME:
> """ On Windows, the global properties file is located in the directory
> of the executable. The user properties file is looked for in the user
> profile directory as set in the USERPROFILE environment variable, or
> in the directory of the executable if USERPROFILE is not set. For GTK+
(Continue reading)

Permalink | Reply | 3 comments |
headers
S. Sevki Dincer | 6 May 02:46
Picon
Favicon

some suggestions

Greetings,
Here are some small suggestions of my great experience with SciTE (very nice editor, i use it all the time) that i think may enhance it little bit. Changes are in the makefiles (little bit faster and connected build process, just "make prefix=/my/pref install" in scite builds -if needed- and installs everyhing, including scintilla) and some properties files (better -in my opinion- default values for, or enabling of, some options).
Thanks..

8:00? 8:25? 8:40? Find a flick in no time
with theYahoo! Search movie showtime shortcut.
Attachment (SciTE.173.suggestion.tgz): application/x-gtar, 94 KiB
_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Permalink | Reply | 4 comments |
headers
James Cuénod | 6 May 20:23
Picon

Just a thought

I was just thinking (while working on some annoying Javascript...)

Would it be possible to make SciTE highlight corresponding quotation marks (like it does with brackets) and also ignore the escaped ones?
hmm,


--
Now go, and may the [open] source be with you 

_______________________________________________
Scite-interest mailing list
Scite-interest <at> lyra.org
http://mailman.lyra.org/mailman/listinfo/scite-interest
Permalink | Reply | 2 comments |
headers
Robert Roessler | 6 May 21:11
Favicon

Re: Just a thought

James Cuénod wrote:
> I was just thinking (while working on some annoying Javascript...)
> 
> Would it be possible to make SciTE highlight corresponding quotation 
> marks (like it does with brackets) and also ignore the escaped ones?

It seems to me like they aren't really the same (or even that similar) 
case... with bracketing syntactic constructs, you often have no way 
within the SciTE environment of seeing where the limits/boundaries are.

With most implementations of string literals, OTOH, you can always 
check the lexical extent of a given string by removing/adding an 
endpoint, and then the syntax coloring will "explain" things. ;)

Robert Roessler
robertr <at> rftp.com
http://www.rftp.com
Permalink | Reply | 1 comment |
headers
mitchell | 6 May 23:49
Picon

Re: Just a thought

Hi,

> James Cuénod wrote:
>> I was just thinking (while working on some annoying Javascript...)
>>
>> Would it be possible to make SciTE highlight corresponding quotation 
>> marks (like it does with brackets) and also ignore the escaped ones?
> 
> It seems to me like they aren't really the same (or even that similar) 
> case... with bracketing syntactic constructs, you often have no way 
> within the SciTE environment of seeing where the limits/boundaries are.
> 
> With most implementations of string literals, OTOH, you can always check 
> the lexical extent of a given string by removing/adding an endpoint, and 
> then the syntax coloring will "explain" things. ;)

I agree syntax highlighting is a wonderful solution, however I would 
find it occasionally helpful to be able to use ctrl+m to jump to 
beginning and end quotes. I happen to get around this by having some lua 
commands to select the string and then arrow right or left depending on 
my needs.

All in all it would be nice, but I don't think its of the utmost importance.

-Mitchell;

> 
> Robert Roessler
> robertr <at> rftp.com
> http://www.rftp.com
Permalink | Reply | 0 comments |
headers
Neil Hodgson | 7 May 01:31
Picon

Re: scite reading configuration files

Scorpio:

> When U double click a file configured to open by default in SciTE, how
> to make it open in the new tab in the latest window?

   The check.if.already.open property can be set to allow files to
open into an existing instance of SciTE.

> And can we have
> options of whether to open in new instance or in a new tab by right
> clicking? And how do we do it...?

   You'll have to learn about setting up shell context menus from your
platform's documentation. check.if.already.open may work on a command
line to set the behaviour for that run but both the existing instance
and the instance being run to add the file must have the option set.

SciTE -check.if.already.open file.txt

   Neil
Permalink | Reply | 2 comments |
headers
Neil Hodgson | 7 May 11:43
Picon

Re: some suggestions

S. Sevki Dincer:

> Here are some small suggestions of my great experience with SciTE (very nice
> editor, i use it all the time) that i think may enhance it little bit.
> Changes are in the makefiles (little bit faster and connected build process,
> just "make prefix=/my/pref install" in scite builds -if needed- and installs
> everyhing, including scintilla) and some properties files (better -in my
> opinion- default values for, or enabling of, some options).

   Running pkg-config once at the start rather than on each compile is
probably a worthwhile win. I don't want to build architecture specific
executables by default since that will cause more support issues.
While SciTE is (mostly) used in ways where buffer overrun security is
not needed, Scintilla is a component that may be incorporated into
vulnerable applications such as browsers.

   The .inc extension is used by multiple languages so should not be
claimed by assembler by default. Your font sizes are enormous. Most
default values are chosen to avoid any automatic changes to files
since, for example, stripping trailing spaces by default will damage
some people's data. Others are my defaults so are most likely to have
been tested.

   Neil
Permalink | Reply | 0 comments |
headers
J. Baltasar Garcia Perez-Schofield | 7 May 11:45
Picon

Re: scite reading configuration files


	Hi, there !

>    Packaging SciTE is completely legal as described in the license
> http://scintilla.sourceforge.net/License.txt

	This is great news ! :-)

>    Set SciTE_HOME:
> """ On Windows, the global properties file is located in the directory
> of the executable. The user properties file is looked for in the user
> profile directory as set in the USERPROFILE environment variable, or
> in the directory of the executable if USERPROFILE is not set. For GTK+
> the user properties file is found in the user's home directory and the
> global properties in a directory set at build time - normally
> /usr/share/scite. If the "SciTE_HOME" environment variable is set on
> either Windows or GTK+ then it is where both the global and user
> properties files are found."""

	Thank you. I've read about SciTEGlobal and SciTEUser, but didn't get
the point about Scite_HOME.

	Salud !

		Baltasar

--

PBC -- J. Baltasar García Perez-Schofield
jbgarcia en uvigo de es  http://webs.uvigo.es/jbgarcia/
Dep. Informática, Universidad de Vigo, España (Spain)
Permalink | Reply | 0 comments |

Gmane