Closed ArkadiuszMichalski closed 2 months ago
No.
Instead, how about making a .Lua script that loads other scripts from whenever you want?
Use the loadfile() function in Lua.
For the fzf path, I'm double checking something, before I make a suggestion...
The fzf.exe_location
DOES expand environment variables.
I think one of the following must have happened:
Ahh right, for fzf.exe_location
it works, sorry for the confusion.
Instead, how about making a .Lua script that loads other scripts from whenever you want? Use the loadfile() function in Lua.
I guess I have no other option and I have to do it (except that I don't know Lua at all). I tried with the CLINK_PATH
variable (as suggested here https://chrisant996.github.io/clink/clink.html#lua-scripts-location), but apparently it didn't work with the default Cmder call:
"%CMDER_ROOT%\vendor\clink\clink_%clink_architecture%.exe" inject --quiet --profile "%CMDER_CONFIG_DIR%" --scripts "%CMDER_ROOT%\vendor"
In general, it would be useful to have a quick way to indicate additional Lua script folders, without having to modify the current code (so as not to overwrite it when updating).
Edit: finally setting CLINK_PATH
works, I must have written something wrong before.
If support for variables in clink.path
is not planned, the topic can be closed.
Yes, setting CLINK_PATH
is an even better way.
It is possible to use environment variables in the
clink_settings
file? I need to set up some additional folders for Lua scripts and .exe files, but I want to make it portable (without using absolute paths). Currently I use Cmder+Clink and variables like%CMDER_ROOT%
or%CMDER_CONFIG_DIR%
are not expanded.More specifically, I'm trying to set values for: