Jump to content

BETA: SciTE v5x & lua Dynamic_include and "Smart" AutoComplete for Vars/UDFs/Abbrevs


Jos
 Share

Recommended Posts

just for the heck of it, I've got autoit-v3.2.12.1-sfx.exe, extracted it and used the SciTE that comes with it.
It runs in place and am sure does not have VC dependencies. You can run it at the same level folder as it should go but named to something else.

Might as well pack it up and put it here ( temporarily ) for you to download and use for testing scripts while you fix your setup

 

Edited by argumentum
removed ZIP

Follow the link to my code contribution ( and other things too ).
FAQ - Please Read Before Posting.
autoit_scripter_blue_userbar.png

Link to comment
Share on other sites

40 minutes ago, argumentum said:

just for the heck of it, I've got autoit-v3.2.12.1-sfx.exe, extracted it and used the SciTE that comes with it.
It runs in place and am sure does not have VC dependencies. You can run it at the same level folder as it should go but named to something else.

Might as well pack it up and put it here ( temporarily ) for you to download and use for testing scripts while you fix your setup

  SciTe_from_3.2.12.x.zip 365.93 kB · 1 download

That works great.  It's been a while since I could see a SciTE editor on this machine.

I don't know what the limitations are with this version.  But it is running.

Thank you very much.

You have been very helpfull!!!

Link to comment
Share on other sites

when you type set in a console, what do you get for path ?
This is mine:

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Users\Tester\AppData\Local\Microsoft\WindowsApps;

..because 0.0.0.0 is not found ( I guess )

Follow the link to my code contribution ( and other things too ).
FAQ - Please Read Before Posting.
autoit_scripter_blue_userbar.png

Link to comment
Share on other sites

Path=C:\Programs\Python312\Scripts\;C:\Programs\Python312\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Programs\LetsEncrypt\bin;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\dotnet\;C:\Programs\PHP\;C:\Programs\OpenSSL\bin\;C:\Users\Gary\AppData\Local\Microsoft\WindowsApps;C:\Programs\Microsoft VS Code\bin;C:\Users\Gary\.dotnet\tools;C:\Programs\Nmap

Link to comment
Share on other sites

wow, you've got a lot going on that PC :lol:
The path works on first found and your path should be

C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Programs\LetsEncrypt\bin;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\dotnet\;C:\Programs\PHP\;C:\Programs\OpenSSL\bin\;C:\Users\Gary\AppData\Local\Microsoft\WindowsApps;C:\Programs\Microsoft VS Code\bin;C:\Users\Gary\.dotnet\tools;C:\Programs\Nmap;C:\Programs\Python312\Scripts\;C:\Programs\Python312\

because otherwise, whatever is in python321 will be used first. Do replace it with the one I changed around above. Maybe that does it.
Else, put it back as it was I guess. But all the "C:\Windows\*" should be first regardless.

Edited by argumentum

Follow the link to my code contribution ( and other things too ).
FAQ - Please Read Before Posting.
autoit_scripter_blue_userbar.png

Link to comment
Share on other sites

I changed the path to match your suggestion.

I rebooted

I tried it.

I'm getting the same error.

Thanks for trying.  It was a good suggestion.

My Python scripts weren't running.  I found I had to move Python and Python scripts above Letsencrypt.  Letsencrypt has it's own Python.

Software should run more reliable now.

Edited by Docfxit
Link to comment
Share on other sites

  

@argumentumis far more experienced in this, and I have far exceeded my knowledge limitation, but I was curious, do you see any msvcp's listed in the registry in

Quote

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs

And if not, is it advisable to add the necessary mscvp140 paths to here? -- Probably not? (Don't try it on my suggestion).

Edit: never mind, I think that would be a bad idea. Unless you used CMD to register it (if it hasn't been for some reason?)

Edited by donnyh13

LibreOffice UDF  ; Scite4AutoIt Spell-Checker Using LibreOffice

Spoiler

"Life is chiefly made up, not of great sacrifices and wonderful achievements, but of little things. It is oftenest through the little things which seem so unworthy of notice that great good or evil is brought into our lives. It is through our failure to endure the tests that come to us in little things, that the habits are molded, the character misshaped; and when the greater tests come, they find us unready. Only by acting upon principle in the tests of daily life can we acquire power to stand firm and faithful in the most dangerous and most difficult positions."

 

Link to comment
Share on other sites

15 minutes ago, donnyh13 said:

@argumentumis far more experienced in this

Actually, no.
What I do is to have a virtual machine for each function. Say I need a web server. That goes into a VM. pfsense, another VM. Code in PHP, that goes in my WEB virtual PC.
So my attitude is: have a plain hardware PC and run specialized stuff in a VM. Anything goes wrong, load another VM and try there.
Win10 pro comes with Hyper-V and does not take many more resources to have VMs running.

The thing is that each time I work with something, it's got it's "gotchas" and I don't want to become a specialist of each niche situation each environment/function entails, therefore each goes in it's own VM. Say I code something for an client and it has a setup/environment and two years down the road I need to fix/change/add something, I'll load the VM I used to code that and makes it a whole lot easier

The OS goes on the C drive, data on a D drive. Anything goes wrong, reinstall the C drive

All that explained above solves most of the "it worked on my machine, don't know why it won't work here" situations.

In the case of @Docfxit, I would reinstall that PC.

 

Follow the link to my code contribution ( and other things too ).
FAQ - Please Read Before Posting.
autoit_scripter_blue_userbar.png

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...