SciTE4AutoHotkey v3.0.06.01 [Updated October 12 2014]

[Joe Glines]

I've had this happen before but, sadly, I don't recall waht the cure was. I'd look for SciTE in your registry and consider deleting it there, then re-installing

[gonzax]

I did, still the same problem and it's driving me nuts!!

I remember years ago I had this same problem or something similar, it always said there was an update when there wasnt. The problem is I don't remember what I did back then to solve it and nothing I do now makes any difference. I've uninstalled ahk and scite and nothing works.

Maybe some W10 update did something, I don't know, but the other computers are running W10 too and are working fine.

I tried copying over my user properties file from another pc but it does nothing, I get the same error.

PS: I also realised that I used to have Scite's settings in a folder inside MyDocuments\autohotkey, at least that's how it is on my other pc but I don't have that folder anymore here and reinstalling Scite won't create one.

W10 64bits
Scite Version 3.0.06.01 - Based on SciTE 3.5.1
Built on Oct 12 2014 13:40:05
AutoHotkey_1.1.30.01 32bits

[joedf]

what happens when running the "portable" zip version?

[gonzax]

what happens when running the "portable" zip version?

I just tried and that one works as it should, no errors or anything.
Should I unzip the portable version where the normal version is?

Edit: I unzipped the contents, now Scite opens without errors and scripts run fine, which is already much better than what I had. The only problem I see is I can't change any options if I go to Tools (zoom, style, etc won't update). If I run the portable version on its own from another folder it works but not from AHK's installation folder.

[gonzax]

Ok, I solved the problem, it was all to do with windows permissions, I guess some stupid W10 update reverted the permissions and that's why it wasn't working, I gave the USER folder inside Scite full control and now Tools works agagin.

I still don't know why Scite does not work correctly without unzipping the portable version's contents first. If anybody knows please let me know, just out of curiosity.

By the way, thanks a lot Joedf, I couldn't have made it work without your suggestion.

[joedf]

Glad it worked out

[JnLlnd]

Hi,

I would like to see #warn All, StdOut send its output to the SciTE4Autohotkey output pane. Is there a way to configure it?

The #warn doc says:

StdOut [v1.1.04+]: Send a description of the warning to stdout (the program's standard output stream), along with the filename and line number. This allows fancy editors such as SciTE to capture warnings without disrupting the script - the user can later jump to each offending line via the editor's output pane.

Thanks,

Jean

[joedf]

I've managed to get this working in the past, but it involved changing the subsystem code in AutoHotkey.exe
Maybe try this?
https://github.com/joedf/LibCon.ahk/blo ... hk2CLI.ahk

[JnLlnd]

I've managed to get this working in the past, but it involved changing the subsystem code in AutoHotkey.exe
Maybe try this?
https://github.com/joedf/LibCon.ahk/blo ... hk2CLI.ahk

Thank you for the suggestion, JoeDF, but I will look at that.

On another topic, I see that some new functions in AHK (like StrReplace) are not supported by the color highlighting in SciTE4Autohotkey. Is there a config file that need to be updated for these changes?

[joedf]

Assuming there no major updates needed to the lexer, I think you can modify ahk.keywords.properties
https://github.com/fincs/SciTE4AutoHotk ... properties

[JnLlnd]

Assuming there no major updates needed to the lexer, I think you can modify ahk.keywords.properties
https://github.com/fincs/SciTE4AutoHotk ... properties

Done that. I added strreplace and strsplit. There are probably other new functions but those are the one I use reguralery (since StringSplit and StringReplace are now deprecated.

[newbieforever]

Hi!
How can I tell SciTE4AutoHotkey to do syntax highlighting not only in .ahk files but also in .lib files?
Thank you very much in advance!

[TravisQ]

Options > Open User properties
add these lines

Code: Select all

file.patterns.ahk=$(ahk.file.extension);$(ahkscriptlet.file.extension);*.lib
lexer.$(file.patterns.ahk)=ahk1

[newbieforever]

Thank you, TravisQ, it works!!!

[SunAndSuch]

I am using SciTE in Linux. It's not SciTE4AutoHotkey, obviously, but it is very similar. In SciTE4AutoHotkey Ctrl+Tab cycles through open files in recently displayed order (and Ctrl+Tab+Tab goes to the next most recent and so on), while in SciTE it always switches to the next file to the right. I'd like it to behave the same as SciTE4AutoHotkey. What should I do?

[TravisQ]

Code: Select all

buffers.zorder.switching=1

# This setting chooses the ordering of buffer switching when Ctrl+Tab pressed.
# Set to 1, the buffers are selected in the order of their previous selection
# otherwise they are chosen based on the buffer number.

[mike091020]

BTW- I learned a lot of SciTE features by watching this Broken Link for safety video. The column manipulation stuff (about 1/2 way through the video) was AMAZING! I am learning Python which uses column indention to signify things so it comes in very helpful.

I found the video from this Broken Link for safety page which has some other helpful tweaks to apply to your setup file.

Thanks for the links. That was a helpful video.

My problem is that I can't get a good working version of the editor. Can you offer any help? So far as I can see, most of the links are broken and others are marked as spam and my security software won't let me get to them. The ones I've obtained seem to be not ready for prime time. For example: no help files or help files that have no content. The autocomplete that was mentioned (suggestions for parameters after an open paren) does not work. I can only wonder what else is going to be broken.

I'm still searching but many of the posts here date back to 2013. I'm wondering if this has been abandoned.


Any help is appreciated.
Thanks

[DrReflex]

Any chance SciTE4AutoHotkey will be upgraded to the current version of SciTE/Scintilla?

The last official release of SciTE4AutoHotkey was version v3.0.06.01. It is almost 5 years old. It was released in October of 2014 and is based on SciTE/Scintilla 3.5.1.
https://www.autohotkey.com/boards/viewtopic.php?f=61&t=62
https://github.com/fincs/SciTE4AutoHotkey
Lexikos provided an upgrade patch to SciTE/Scintilla 3.6.0 in 2015.
https://github.com/Lexikos/SciTE4AutoHotkey/tree/master/scipatches
I am not aware of any subsequent patches.

There have been substantial feature improvements to SciTE/Scintilla between versions 3.6.0 and the current version 4.2.0.

Version 3.6.0 was released in August of 2015. Scintilla 3 was designed for older systems and was based upon C++ 11 code.

Scintilla 4.2.0 was released in July of this year. It includes more user interface options, improved lexer support, symbolic user shortcut definitions, additional and improved syntax styling, call tips, and better code compilation. Scintilla 4 was designed for newer systems and is based upon C++ 14 code. It includes features through C++ 20.

[lexikos]

Why cross your fingers and wait for someone else to do it?

I use LPEG-based lexers, and generally only edit AutoHotkey scripts in SciTE, so lexer improvements or additions aren't any use to me. I looked through the release history but didn't see anything compelling. I'm sure I don't understand some of the improvements you listed, or how they would relate to AutoHotkey-editing.

Lexikos provided an upgrade patch to SciTE/Scintilla 3.6.0 in 2015.

fincs authored that commit, as GitHub shows. I just pulled it from one of his other branches, I guess, since it seems to be ahead of fincs:master. I seem to be using 3.5.1 locally.

Scintilla 4 was designed for newer systems and is based upon C++ 14 code. It includes features through C++ 20.

I don't see why that's a good thing, if it even matters. Also, Visual C++ 2019 (not Scintilla) includes C++20 features; I'm fairly certain the /std:c++17 switch is intended to prevent their use within the project:

For Visual C++ 2019, /std:c++latest now includes some C++20 features so switch to /std:c++17.

[joedf]

I still use the same old version. It works great and it's pretty stable.