How to use /nyagos.d under nyagos.exe as before?

[emisjerry]

v4.4.18_0 made the following changes:

Note

The scripts in nyagos.d/ are no longer loaded automatically. Use %APPDATA%/NYAOS_ORG/nyagos.d instead.

This modification seems to affect portability: when I want to run the same Nyagos environment on multiple computers, I have to manually synchronize.

I placed Nyagos in a Dropbox folder, so multiple computers synchronize the same Nyagos files through Dropbox.

I tried using mklink /D to point %APPDATA%/NYAOS_ORG/nyagos.d to the folder inside my Dropbox, but Nyagos does not use the Lua files in nyagos.d.

Is there another way to make Nyagos also use the nyagos.d inside the nyagos.exe directory?

[hymkor]

I tried using mklink /D to point %APPDATA%/NYAOS_ORG/nyagos.d to the folder inside my Dropbox, but Nyagos does not use the Lua files in nyagos.d.

(1) Verification on my environment

In my environment, Lua scripts inside a directory linked with mklink /D are loaded correctly.
So it may be that something other than Nyagos itself is preventing access to the linked directory.

[1] hymko@IROIKKAIZTSU:C:\Users\hymko\AppData\Roaming\NYAOS_ORG
> dir
 Volume in drive C is Windows
 Volume Serial Number is 6E1A-374E

 Directory of C:\Users\hymko\AppData\Roaming\NYAOS_ORG

2025/11/20  20:15    <DIR>          .
2025/07/14  17:27    <DIR>          ..
2025/11/20  20:15    <SYMLINKD>     nyagos.d [C:\Users\hymko\Dropbox\nyagos.d]
2025/11/20  20:18            63,715 nyagos.history
               1 File(s)         63,715 bytes
               3 Dir(s)  767,924,097,024 bytes free

[1] hymko@IROIKKAIZTSU:C:\Users\hymko\AppData\Roaming\NYAOS_ORG
> type nyagos.d\469.lua
print("load %APPDATA%/NYAOS_ORG/nyagos.d/469.lua")

[1] hymko@IROIKKAIZTSU:C:\Users\hymko\AppData\Roaming\NYAOS_ORG
> nyagos
Nihongo Yet Another GOing Shell 4.4.18_0-52-g7aaf4650-windows-amd64
(c) 2014-2025 NYAOS.ORG <https://nyaos.org/nyagos>
load %APPDATA%/NYAOS_ORG/nyagos.d/469.lua
loadfile C:\Users\hymko\share\bin\.nyagos
start ~\share\bin\.nyagos
done amd64/.nyagos
start ~/.nyagos
[2] hymko@IROIKKAIZTSU:~/AppData/Roaming/NYAOS_ORG
>

(2) An alternative way to load scripts

As an alternative way to load scripts, you can put the following code in either (directory of nyagos.exe)\.nyagos or %USERPROFILE%\.nyagos.
This will load all Lua scripts under nyagos.d at startup.

local directory = string.gsub(nyagos.exe,"%.exe$",".d\\*.lua")
local scripts = nyagos.glob(directory)
if scripts then
    for i = 1, #scripts do
        loadfile(scripts[i])()
    end
end

(3) About the removal of automatic loading

Regarding the removal of automatic loading for nyagos.d:
the main reason was to reduce the number of files that must be bundled with nyagos.exe.
At the same time, I had not yet finalized how nyagos.d should ideally be used going forward.

For example, if a file inside nyagos.d has the same name as a standard script now embedded in the executable, perhaps the user’s customized version should override the built-in one.
Ideas like this require careful consideration, and implementing everything at once would be risky.
So I decided to make changes step by step, checking actual user needs as we go.

Therefore, if loading nyagos.d\*.lua without any special configuration is something you really need, I am open to revisiting the specification and adding that behavior back.

[emisjerry]

1. symbolic link was incorrect

At first, my command was wrong, i have to make the link to %APPDATA%/NYAOS_ORG/nyagos.d. i missed the /nyagos.d

2. Portable version

Although handling it through a .nyagos file is a feasible solution, a portable version can provide users with an additional option. Perhaps specifying a personal directory via an environment variable is also a workable approach? For example:

NYAGOS_PERSONAL_DIRECTORY="C:\Dropbox\nyagos\my_nyagos.d"

If the variable is set, use its value; if not, default to %APPDATA%\NYAGOS_ORG\nyagos.d.

[hymkor]

Thanks for the suggestion - I think it is a good idea.

Regarding environment variables: I used to be a bit hesitant about introducing more of them, but in practice they offer a clear advantage in terms of usability. So I am generally positive about adopting this approach, though there are several things I need to think through carefully:

• It might be useful to allow multiple directories, separated by semicolons.
• Even if the variable is set, I am not sure whether %APPDATA%\NYAOS_ORG\nyagos.d should be disabled. Using both the default directory and the user-specified one could be a reasonable option.
• If an environment variable is added, perhaps a command-line option should also be provided for the same purpose.
• At the same time, adding too many configuration mechanisms would risk making the overall behavior harder to fully grasp, even for me. This is one of the reasons I have recently been simplifying or removing some features.

As for the release schedule: Nyagos is currently updated twice a year, and the changes discussed here would likely be included in version 4.4.19, planned for the first half of 2026. Fortunately, there is plenty of time before that release, so we can still consider ideas. In particular, it can be difficult to judge which specifications are simple and easy to understand from a user perspective, so feedback from users is very helpful.