AutoHotkey Community

---C:\Autohotkey\Autohotkey.ini


---- C:\Autohotkey\Script\test.ahk


I also want the method of acquiring the information on the Include script.
If it is possible to get to know one's Path (C:\Autohotkey\Script) and FileName (test.ahk) in test.ahk, it is in the same place as itself. It becomes easy to create test.ini.
Is it difficult to add these to Built-in Variables?

Moreover, it is still gladder if the Include state of a script can be known. It is because it becomes unnecessary to adopt the following ways of writing.

Is it this, what you want?

---C:\Autohotkey\Script\test.ahk




---C:\Autohotkey\Autohotkey.ini

_________________
Ciao
toralf

Thank you for a reply. Your reply differed from that for which I was asking. When it was made, it thought that it was glad and tried.

---C:\Autohotkey\Autohotkey.ini


---C:\Autohotkey\Script\test.ahk


Error
#include file　"%A_ScriptDir%\%IncludeScript%" cannot be opend.
(The file name and syntax error it was reverse errorless were corrected.)
while regrettable "#include" -- "%A_ScriptDir%" -- and -- It cannot use "%IncludeScript%".


To the next test.ahk was deleted and tried.

---C:\Autohotkey\Autohotkey.ini


Error
#include file　"C:\Autohotkey\Script\test.ahk" cannot be opend.
Although it is regrettable "#include" It cannot skip dynamically, either.

Can you give a specific example of what this would be used for?

Does anyone think that #Include should be changed to allow switching directories? Example:
#Include C:\My Scripts ; Change working directory for #Include.
#Include StringRoutines.ahk

It could be used multiple times and would change the script's working directory for the purpose of #Include and maybe FileInstall commands, but probably not for the execution of the script (which would still use SetWorkingDir).

C:\Autohotkey\Autohotkey.ini
C:\Autohotkey\Script\hoge.ahk
C:\Autohotkey\Script\sub\sub1.ahk
C:\Autohotkey\Script\sub\sub2.ahk
C:\Autohotkey\Script\sub\sub3.ahk

--- C:\Autohotkey\Autohotkey.ini ---

--- C:\Autohotkey\Script\hoge.ahk ---

I want to carry out the packaging of the hoge.ahk and to Include it from a higher rank simply.
I do not want to be influenced of my home. I want the specification method which can be completed only by hoge.
Moreover, as for hoge.ahk, in addition, to operate, even if it performs alone is good.
Current directory which hoge.ahk uses at least for itself if it is impossible I want the structure the hoge.ahk itself is decided to be in the name of .ini.


I am sorry. Since it is idle, how to use FileInstal is not known well. I do not consider compile of a script.

I don't yet see a significant benefit to discovering the directory from which an #Include file was loaded. It seems to me that you must know the directory to include it in the first place. Since you must know it, there is no large benefit to having a way to discover it.

#Include is intended to be a simple mechanism for including other files. For now, I think elaborate improvements to it would be seldom used, and thus a low priority.

Isn't it so in demand? Although I thought that I was regrettable, I understood.
Thank you

Finding out the file name of an include-file is now possible via A_LineFile. Also, #Include has been improved in v1.0.35.11 to be able to set a new working directory for subsequent uses of #Include and FileInstall (it can also resolve %A_ScriptDir%).

Thanks for the suggestions.