AutoHotkey Community

I run my script at startup used a Registry record:

The script .ahk file is located in following directory:
C:\Documents and Settings\Dmitry Lyudmirsky\My Documents\AutoHotkey
However when runnig the script shows following:
A_WorkingDir = C:\Documents and Settings\Dmitry Lyudmirsky
A bug?

Try to add the path where the AHK installed on your machine

Not tested.!

MYYM,
I've tested your suggestion. It doesn't work.

I don't think it's a bug because the script's working directory doesn't have any code behind it. It just accepts whatever it was given. Thus, this working directory seems to be caused by the OS when it launches things in the Run subkey.

To work around this, change the working directory at the top of the script:
SetWorkingDir C:\Documents and Settings\Dmitry Lyudmirsky\My Documents\AutoHotkey

IMO you're better off using A_ScriptDir to refer to a file in the script's directory than depending on Windows to set the proper working directory...

Chris,
but why A_WorkingDir and A_ScriptDir might be different at the startup moment?
For example I create Test.ahk consisting of two lines only:

run it and then restart my computer. Immediately after restart I see MsgBox with following:
A_WorkingDir = C:\Documents and Settings\Dmitry Lyudmirsky
A_ScriptDir = C:\Documents and Settings\Dmitry Lyudmirsky\My Documents\AutoHotkey

You suggest to apply

at the top of my script.
This is a good idea, but my problem rise at the compiling time. The compiler does not able to find an IncludingFile located in the %A_ScriptDir% directory to process a line like this:

Unfortunately SetWorkingDir does not effect during the compilation.

Because A_WorkingDir depends solely on the working directory specified by the process that launched the script. To retain flexibility, the program does not try to override this.

There is a plan to provide a means to change the working directory for #Include files. In the meantime -- assuming there's no way you can have the program launch in the working directory you really want -- you will probably have to specify the full path with each #Include in the script.

I don't need to use a special directory for #Include files. All my #Include files are located in the SAME working directory as script files.

It means every time when I want to move or rename my working directory or bring my scripts on another computer I must rewrite all my scripts! Not nice, isn't it?

The fault here lies with the process that launches the script. It is specifying the wrong working directory. You could try having the registry launch a helper script that launches the main script by specifying the correct working directory:

Run C:\Scripts\Main Script.ahk, %A_ScriptDir%

I've made a note to see if A_ScriptDir can be directly supported by #Include. That would make this easier. Thanks for the idea.

In case you weren't aware, if you have compiled the script the directory name with the Include files won't matter as the data from the Include files is added to the compiled script.

corrupt,
thank you, i know this.
The surprise is that the compiler sometimes can not find "#Include FileNameWithoutPath.ahk" files stored in the SAME directory as the script file processed.

Chris,
please,
bring the compiler to search #Include files in %A_ScriptDir% as well as in %A_WorkingDir%!

I checked the code for ahk2exe and it does set the working directory to the script's own directory. Has anyone else had problem with ahk2exe not being able to find include files in the script's own folder?

Oh, I'm sorry, I've regard the "compiler" word incorrectly. I meant the interpreter, not the compiler. My problem relates to the AutoHotkey.exe, not to the Ahk2Exe.exe.
I run a set of MyScript.ahk as documents on Windows startup. In fact I launch the AutoHotkey.exe to run theese scripts. When they contain some #Include instructions, then AutoHotkey.exe searches IncludingFiles.ahk only in "working directory" -- DOS-like "current directory". This directory may be not the same as "MyScript with IncludingFiles" directory.
All is Ok when MyScript.ahk is running from Windows Explorer window or through a shortcut having explicit "Start in" data.
But AutoHotkey.exe does NOT find including files when a "current directory" is not the MyScript directory. It happens, for example, on Windows startup.
Of course I can avoid this problem by writing something like this:

in MyScript.ahk.
But instead, it would be better do without #Include at all, simply transfer some lines required from Including.ahk into MyScript.ahk directly.
That is why I ask to teach AutoHotkey.exe inspecting A_ScriptDir too.

Thanks for clarifying.

I'll try to make #Include support for A_ScriptDir. For example:
#Include %A_ScriptDir%\My Include.ahk

The reason for doing it this way rather than searching automatically in A_ScriptDir is that it might break existing scripts that rely on #Include files not being found depending on the working directory. This was a requested feature and is the reason for #Include's "ignore" option (*i).