AutoHotkey Community

TAC109

I wrote: The Updater does the actual updating using a long DOS command line, mainly to avoid any file contention. For each file to be updated it deletes the file from the target, copies the new file from a temp location to the target, then if the copy succeeds deletes the file from the temp location...

TAC109

I will remove the attempts at preserving virtualization in the next version, so your code should work unchanged then. However, keep in mind that if you launch Ahk2Exe through RunWait comspec, then virtualization will be disabled which means that registry read-writes won't work among other things. T...

TAC109

Thanks for your reply. I guess I should have stated that I'm running Windows 10 (my system is too old for Win 11). I'm not sure the problem is in execution permissions. I did my testings in a Win 11 standard user environment, and compiling a v1 script with both AHK v1 U64 .bin and .exe created an ex...

TAC109

Descolada Thanks for your new store edition of AutoHotkey v2. I’ve been checking it out with regards to the Ahk2Exe compiler and have some comments regarding this: I see that you have included the compiler that was issued with AutoHotkey v1.1.37.01. Unfortunately this is not the latest version, whi...

TAC109

It seems that the consultant stopped updating the AHK Store Edition (last update March 2020). … The Microsoft Store version you are referencing indicates that it contains AutoHotkey v1.1.37.01, which is the latest version, so the date you quoted is probably when this item first appeared in the Stor...

TAC109

The Run command seems needlessly complicated. Try replacing it with:

Code: Select all

 Run, *RunAs %ComSpec% /c "tscon.exe 1 /dest:console"

Cheers

TAC109

Note that the documentation states that the contents of an INI file must either be ANSI or UTF-16. UTF-8 is not permitted.

Cheers

TAC109

Seems to be an AutoHotkey bug. Also happens with v2.0.10. @boiler Could you please move this thread to the 'bug reports' section of the forum. Thanks.

TAC109

In addition to the reply from @mikeyww, you should also update your version of Ahk2Exe to v1.1.37.01c. (See here.)

Cheers

TAC109

Try:

Code: Select all

NumpadUp::
Run %comspec% /c "D:\Batch Fles\File Explorer Restart.bat"
Return

TAC109

See this thread for up-to-date tricks.

Cheers

TAC109

It is not clear from your code that it is necessary to run your program using either cmd.exe or %comspec% in the first instance. Have you tried this? In this case you would instead need to code the RunWait command like this: Runwait, "%A_ScriptDir%\DATA 123\qpdf.exe" --empty --pages "%outtemp1%" -- ...

TAC109

Descolada It seems a bit extreme to set up a separate extension for AutoHotkey v1 just to handle the Windows Explorer 'New' option. As the code for a new v2 is just '#Requires AutoHotkey 2.0' could you perhaps add a comment to that line to change the 2.0 to 1.1 for v1.1. Alternatively you could als...

TAC109

You should always endeavour to use correct syntax, even if it appears to work otherwise, as a later update may tighten the syntax checking and cause an error message. In this case I expect either 'cmd.exe' or 'qpdf.exe' tolerate the mistake and make a silent correction.

Cheers

TAC109

@neogna2
I enjoyed reading many of the 'Joel on Software' articles too.

Cheers

TAC109

Thanks @Ragnar

Cheers

TAC109

The thread you quoted: This 2020 thread is relevant to this topic and has the opposite wish: remove a BOM recommendation. https://www.autohotkey.com/boards/viewtopic.php?t=79309 resulted in no changes to the documentation : Be sure to save the file as UTF-8 with BOM if it will contain non-ASCII char...

TAC109

My suggested alteration to the faq is to help users having possible problems when editing/processing scripts. If you find that your editor handles UTF-8 files correctly, then that is good, however the editor will still process files correctly when saved as UTF-8 with BOM but with more certainty. Thi...

TAC109

Having a BOM (Byte Order Mark) written to the start of a UTF-8 file ensures that any modern utility (including editors) that can understand UTF-8, can determine with certainty that the file is actually UTF-8. Without a BOM at the start of the file the program has to make a guess as to the file encod...

TAC109

Ragnar If you agree, could you change the v2 faq, item Why are the non-ASCII characters in my script displaying or sending incorrectly? replacing Short answer: Save the script as UTF-8. with Short answer: Save the script as UTF-8, or for complete compatibility with utilities such as editors, UTF-8 ...

Search found 1125 matches

Re: Autohotkey within the Microsoft Store

Re: Autohotkey within the Microsoft Store

Re: Autohotkey within the Microsoft Store

Re: Autohotkey within the Microsoft Store

Re: Autohotkey within the Microsoft Store

Re: run compiled script issue Topic is solved

Re: Unicode characters in INI files

Re: [BUG] Compiled script: Run/RunWait launch the wrong executable Topic is solved

Re: problem running script after compiling

Re: Bat Files

Re: single-line way to write if??

Re: quote and double-quote " " "

Re: Autohotkey within the Microsoft Store

Re: quote and double-quote " " "

Re: V2 faq UTF8 recommendation Topic is solved

Re: V2 faq UTF8 recommendation Topic is solved

Re: V2 faq UTF8 recommendation Topic is solved

Re: V2 faq UTF8 recommendation Topic is solved

Re: V2 faq UTF8 recommendation Topic is solved

V2 faq UTF8 recommendation Topic is solved