I recently installed the new Autohotkey v2. I have an existing autohotkey script called test-v1.ahk
When I double-click on test-v1.ahk, autohotkey is smart enough to detect that the code conforms to v1 syntax and runs autohotkey v1 on it. How to force auto-hotkey v2 to run on test-v1.ahk?
Both Autohotkey v1 and v2 are installed on my PC running on Windows 10.
Someone smart and helpful gave me this answer.
The solution is this
https://www.autohotkey.com/docs/v2/lib/_Requires.htm
Related
I have both .net core 2.0 and .net 4.7.2 installed.
I have installed Azure Function Apps Extension in VScode and a have verified that azure-functions-core-tools v2 is also installed.
I am able to create and debug V2 Function Apps using .netcore with no problems.
My question is how do I also install the tooling for V1 Function Apps side by side using VSCode and be able to debug as well?
thanks
Is this what you want?
1, Delete the global azure-functions-core-tools version.
Go to the cmd, use the command below:
npm uninstall -g azure-functions-core-tools
2, Then go to the VS Code, create a empty folder.
Press F1, click , then click the language.
Now you can see multiple version of function that you can choose:
Click what you want.
3, Create a folder named node_modules under your function app folder.
4, Click F1 to open the cmd terminal.
If you choose v2 just now, please use this command:
npm install azure-functions-core-tools#2
Now, It has been create successfully.
5, How to run test your azure function:
Use this command on local:
node_modules\.bin\func host start
How to create function v1 is similar.
I use the AutoHotKey script to map some the keys under Windows 10 OS . It works very well except that I started Powershell as administrator. All the key mappings does not work after that as if autohotkey has been shut down. However things are all fine when I run PowerShell without administrator. Anyone knows how to fix that?
As Bluecakes said, just running the AutoHotKey as administrator will fix my problem.
You can either set the AutoHotKey to run always as administrator by right-click on AutoHotKey.exe and select property, in the compatiblity Tab , check the run this programme as administrator, or you can add a 'run as administrator' entry in the right-click menu of ahk scripts by editting the registry. Following this link:
This goes out to anyone who is well versed in the Eclipse IDE and or PyDev perspective plug-in who is willing to offer some technical support.
I am trying to write a python module that must take in arguments from the command prompt with sys.argv function calls. Rather than printing out the correct output when I enter E:\ ... \src>program.py arg1 arg2, all that happens is a new command line (E:\ ... \src>) is output and the Eclipse IDE window flashes orange without any code in my python module actually being executed. Also, if I close the Eclipse IDE and try to run program.py, it will just open Eclipse again and open my program in a new tab.
I'm confused as to why it is not working now when just last week it was working perfectly while testing another program that took in arguments from the command prompt by sys.argv function calls. My question for everyone is whether or not you are aware of any settings that may have been altered by updates, etc. that could cause this problem; or has anybody out there ever run into this problem and figured out how to resolve it? I have already checked my PATH variable, so that is not the problem :-(. Any help you can provide would be greatly appreciated ... thank you.
OS: Windows 8.1 Pro / Eclipse ver.: Kepler (4.3) / Python ver.: 3.3.2
I answered my own question in the comment above. I just had to wait to post an answer due to the fact that I just created a stackoverflow account yesterday.
OS: Windows 7 Ultimate SP1 x64.
At some point I figured I can no longer update my IDE for Powershell - PowerGUI Script Editor (latest is v3.7.0.92 at the moment of writing). I am getting this error when inside the script editor -> check for updates, as well as in a standalone installation, in both cases the installation is rolled back.
In my Programs and Features I have the following relevant entries:
(A) Quest PowerGUI 3.6 --- Version 3.6.0.21
(B) Quest PowerGUI 3.6 --- Version 3.6.0.8
When I attempt to uninstall (A), I am getting this error:
Although the current version inside the script editor is shown as 3.6.0.21.
And when trying to uninstall (B), I get a standard Modify/Repair/Remove dialog, but when I do Remove, it ends up with the first error again (#1722 above). Doing Repair works, but does not solve the problem, i.e. still unable to Update.
Is there any way I can make it work again?
P.S. One may point out this to be part of superuser, yet I think it's an inherent part of Powershell development and so deserves a place on SO.
It seems the uninstall function either doesn't complete correctly or misses some important registry settings. I had the same problem, and this resolved it for me:
download and run the microsoft uninstall utility
in the utility do the following:
select the install or upgrade software or hardware category.
find and run the fix problems with programs that can't be installed or uninstalled.
give answers to the prompts regarding the powergui instance that will not uninstall.
exit the utility.
install the powergui version of your choice.
get pint from pub
I have Windows 7 at home with Powershell 2 and I really like the free version of the PowerGUI Powershell editor.
I'd like to start using Powershell at work but we are on version 1.o on XP with SP2. I was going to install PowerGui but
it looks like it requires some Core components or maybe even Powershell 2.0. I expect that our XP production servers may not have this version and I think it is safe to stay with 1.0 for now to avoid pushback from the keys with the keys to the production box.
My question is this:
Is there an editor like powerGui that I can use with version 1 where I do not have to install additional Powershell components that may not be present in production?
You can use all of the free and commercial editors on XP:
PowerShell Integrated Scripting Environment (ISE) ships with PowerShell V2
PowerGUI (www.powergui.org) is a great free editor with support for code folding and intellisense, and PowerPacks to make it easy to work with PowerShell by point and click
Idera makes another great editor (PowerShell Plus - www.powershellplus.com) with a strong collection of scripts that ship with it.
DevFarm makes PowerWF and PowerSE (www.powerwf.com), and editor and workflow tool for working with PowerShell
PrimalForms is an editor and tool to make UI in PowerShell, built by Sapien (www.sapien.com)
Hope this Helps
If your question is actual PowerGUI script editor (version 2.4.0) works with PowerShell V1.0. My answer is that I don't think it works. In my understanding you need a version before 2.0 . I'am using PowerGUI 1.9.5.966 which works perfectly with PowerShel V1.0.