gmane.editors.scite.general

Re: Startup issue

sdaau — 2012-05-22T14:01:00

And was wrong again - this earlier snippet is *not* the fix:


Once you were in tab A, and switch to sciteLuaFuntions.lua - even
`pwd` (in shell) will read the directory of file in tab A! So the
right thing to do, is ask the shell for the absolute path to your home
directory; so under linux we can use `readlink` to return location of
home directory `~` (which lua couldn't understand directly)... The fix
is thus this:

Re: Startup issue

sdaau — 2012-05-22T13:43:11

Hi Neil,

Many thanks for your reply!!


Indeed - what I experienced just now (and what I always forget, mixing
from Python and such): `print myvar` generates an error;
`print(myvar)` doesn't :)



Indeed it isn't - sorry for that, I wasn't clear about it myself; just
before you posted, I had found and written a correction: "if you turn
to a different tab AND execute one of your own lua scripts ..." ; ...
and then switch back to the sciteLuaFunction.lua tab, I may add - then
the current directory seems to remain the one from the last visited
tab document.

However, I think now I have a fix for this on a lua-script-for-Scite
level, also  posted in that reply - so all looks good now :)

Cheers!

Re: Startup issue

sdaau — 2012-05-22T13:35:22

Ehm, I was wrong:


Nope, correction: it turns out to be more specific than that - if you
turn to a different tab AND execute one of your own lua scripts
(stored in luaSciteFunctions.lua); THEN the problem with changing the
"current directory" of lua occurs (otherwise not by simply changing
tabs).

The most straightforward way to fix that is to simply add the home
directory to lua's package.path; however, since lua is in Scite's case
running as a module, it doesn't have a reference to argv[0]. So this
is what worked for me, as a sort of a "preamble" for
luaSciteFunctions.lua:

---------

Re: Startup issue

Neil Hodgson — 2012-05-22T13:24:35

sdaau:


   Lua shows "attempt to call a string value" for many different failures.


   This shouldn't be the case. There have been problems caused by switching current directories so I've been trying to eliminate chdir calls. There are still some on GTK+ when showing file open and save dialogs - it may now be possible to eliminate those. There are also some when running a command and it would also be better for the forked process to do that so SciTE's directory remains constant.

   Neil

Re: Startup issue

sdaau — 2012-05-22T12:01:25

Just wanted to post back, in response to this thread:

Re: [scite] Startup issue -
http://www.mail-archive.com/scite-interest< at >lyra.org/msg03855.html

(from Jul 2007 - while archive on google groups goes back only to Oct
2007).

The problem was:


I got the same error, but my use case was slightly different - if I
changed sciteLuaFunctions.lua from within Scite, and tried to save it,
I sometimes got that error, due to a `require("SciTEHexEdit")`.

Namely, it seems that each time you switch a tab to a document in
Scite, it seems that Scite's "current directory" is also changed to
the directory of the document in the tab. However, this somehow
doesn't work when you switch back to the tab for
sciteLuaFunctions.lua; which is why I got those errors. I noticed,
however, that if - after switching to sciteLuaFunctions.lua tab - I
try to type "pwd" in the Output Pane; it gets correctly read as `/home/
username` - and *after* this, saving sciteLuaFunctions.lua after a
change goes fine (unless there are lua compilation

Re: Basic SciTe Help

Philippe Lhoste — 2012-05-21T09:43:14

Yes.
Note: software's name is SciTE (TE = Text Editor, Sci = Scintilla, the component 
displaying the source code).


Not really.
You include t2t (in SciTEUser.properties), and this file should define the extensions 
associated to the t2t lexer (or another, close of the syntax you need).


Yes, it is not automatic. Most language property files doesn't have an abbreviation file, 
these are generally more user-specific. Some languages property files have an API file, 
though.
For example, I have a api.$(file.patterns.lua)=$(SciteDefaultHome)/lua5.api
But again, these should go to SciTEUser.properties, unless you always require the API or 
abbreviation file to be shipped with your t2t.properties.


An import is always imported, regardless of the current file / buffer. Beware of conflicts 
with other properties files!
So, your t2t.properties should define only properties for this kind of file.
Don't use
tabsize=4
but
tab.size.*.t2t=4
or
tab.size.$(file.patterns.t2t)=4
if you defined this property (useful if you

Basic SciTe Help

Homme, James — 2012-05-18T14:21:36

Hi,
I apologize in advance for not always making connections unless they are explained in many words. The version of SciTe I have is the one from AutoItscript.com/. AutoIt runs on Windows, in case what I'm talking about has anything to do with this. But I don't know if what I'm asking has to do with this fact.

I was trying to set up abbreviations that would help me write t2t files. As I was looking through the various properties files and trying to trace what would happen when I worked on a t2t file, I saw that the global properties file has a lot of import lines in it for various languages, and none of them end with ".properties." I'm assuming from this that SciTe somehow knows that it should add this extension. Is this right?

Next Question. When I save or open a file and give it a t2t extension, is that when SciTe understands that it should use my t2t.properties file?

Next question. Should I create an import line in my t2t.properties file for t2t.abbreviations.properties?

Next question. Does all of thi

Re: Mac App Store reviews

Neil Hodgson — 2012-05-13T23:31:13

Philippe:


   Preview downloads are normally broken in some way and that's not something I like doing. Its also extra work.


   I saw current SciTE users as the main initial market and the screenshots were to reassure them that its real SciTE with full functionality.

   Neil

Re: Mac App Store reviews

Philippe — 2012-05-13T14:16:19

The price is probably realistic for a Mac text editor, but you could offer 
a preview download on scintilla.org.

However, with all due respect to the effort, screenshots on App Store 
"makes me want to poke my eyes out with a fork". Only die-hard, 
design-blind, SciTE fans who switched to MacOS will buy that.

On Sunday, May 6, 2012 12:45:29 PM UTC+2, Neil Hodgson wrote:

Re: Mac App Store reviews

Jingcheng Zhang — 2012-05-12T17:11:35

It's glad to see SciTE under Mac, but it's a bit expensive... Anyway, it's
free under Windows and Linux.

On Sun, May 6, 2012 at 6:45 PM, Neil Hodgson <nyamatongwe< at >gmail.com> wrote:

Re: fatal error C1083: Cannot open include file: 'd2d1.h'

Neil Hodgson — 2012-05-07T23:10:18

zetah:


   Direct2D and DirectWrite are recent so require a recent version of the Windows SDK or a recent version of Visual Studio which includes the SDK.

   Neil

Re: fatal error C1083: Cannot open include file: 'd2d1.h'

zetah — 2012-05-07T14:24:32

I know it's D2D header: 
http://msdn.microsoft.com/en-us/library/windows/desktop/dd317121 but I hope 
I don't need to download additional xxx MB SDK, or?

fatal error C1083: Cannot open include file: 'd2d1.h'

zetah — 2012-05-07T14:20:24

I'm trying to compile current hg version of Scintilla on a XP SP3 PC with 
VS 2008 Pro and Windows SDK for VS 2008

I used suggested command:
  nmake -f scintilla.mak

which after a while prompted this error:
  fatal error C1083: Cannot open include file: 'd2d1.h'

What rerequirement am I missing?

Mac App Store reviews

Neil Hodgson — 2012-05-06T10:45:29

   I'd like to encourage those who have purchased the OS X version of SciTE to post ratings and reviews on the App Store. That includes negative reviews and low ratings if you have been disappointed. Its important that potential customers get a realistic view of the application before paying for it.

   If the App Store provided support for preview downloads than that would help a lot. I've been expecting such a feature but it hasn't arrived yet.

   Neil

Re: Shbang not detected after loading session and switching tab

Neil Hodgson — 2012-05-06T00:49:30

Martin Panter:



   Yes, it is complex. ReadProperties is a fairly heavy call so is avoided when possible. However, this change moves the call so should be OK. Committed.

   Neil

Re: Turn off hidden files from open dialog SciTE 3.1 Mac OS X

Neil Hodgson — 2012-05-04T10:15:12

   fileselector.show.hidden will be in the next OS X release with the default being to show hidden files.

   Neil

MS Visual Studio 2010 projects for Scintilla and SciTE 3.1.0

Ferdinand Prantl — 2012-05-03T08:22:33

Hi,

You may find them useful for compiling and debugging Scintilla with SciTE.

http://prantl.host.sk/scite/scite-3.1.0-vs2010.zip
  - adds MSVS 2010 projects to sources unpacked from scite310.zip.

http://prantl.host.sk/scite/scite-3.1.0-vs2010-scintillua-3.0.4.zip
  - adds MSVS 2010 projects to sources unpacked from scite310.zip and
scintillua3.0.4-1.zip. Lua is shared from the scite project.

Enjoy,

   --- Ferda

Re: SciTE Mac OS X 3.1.0 and Spotlight

Neil Hodgson — 2012-05-03T02:52:35

Christopher David Desjardins:


   I'd expect it to show up too. There haven't been any changes in SciTE aimed at Spotlight. Its possible the sandbox changes affect whether SciTE gets indexed.

   Neil

Re: SciTE Mac OS X 3.1.0 and Spotlight

Christopher David Desjardins — 2012-05-03T02:02:34

So this isn't a bug? It seems like SciTE should show up when searched for in Spotlight. If I search for Safari, Chrome, Mail, etc., that are in Applications folder they show up. SciTE is also in the Applications folder. It just seems strange.
Chris

On May 1, 2012, at 10:57 PM, Neil Hodgson wrote:

Shbang not detected after loading session and switching tab

Martin Panter — 2012-05-02T13:18:42

Hi

This issue has been bugging me for a while. It was happening in 3.0.2
and 3.0.3 Arch Linux packages and still in a 3.1.0 package I compiled
myself, but I think it may be a regression because I’m pretty sure it
used to work better.

I have Scite set up to automatically load the previous tabs (session)
when it starts. When it has loaded the tabs, the initial selected tab
is a file with an extension that selects the syntax highlighting (e.g.
SciTEIO.cxx). When I change to a tab that is meant to be using a
shebang to select the syntax highlighting language (e.g. filename
"filefs" beginning with "#! /usr/bin/env python2"; I have set up
shbang.python2=py), there is no highlighting. However opening the file
manually rather than via session loading automatically selects Python
highlighting, and it also works if the shebang file is initially
selected when Scite loads (rather than switching tabs).

I did a bit of digging and came up with the attached stab-in-the-dark
change which seems to fix the issue for me. T

Re: SciTE Mac OS X 3.1.0 and Spotlight

Neil Hodgson — 2012-05-02T03:57:32

Christopher David Desjardins:


    Spotlight doesn't search some of the places it used to. Files in ~/Library don't seem to show up.

   Neil