You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I specify a link in "./sidekick/setup/make_these_links.txt" as follows:
../some_path ./local_link_name
and ../some_path is itself a softlink, I get some weird results.
The target of the link created by ./sidekick setup is expanded to its full filepath rather than just using a path relative to the position of the linkname.
I'm worried that if the resulting links get pushed into version control they won't be portable.
My example at present is when setting up a link to ../int_data/some_dir from ./data/int/; but such links are not included in version control (since ./data is not included in version control).
The text was updated successfully, but these errors were encountered:
If I specify a link in "./sidekick/setup/make_these_links.txt" as follows:
and
../some_path
is itself a softlink, I get some weird results.The target of the link created by
./sidekick setup
is expanded to its full filepath rather than just using a path relative to the position of the linkname.I'm worried that if the resulting links get pushed into version control they won't be portable.
My example at present is when setting up a link to
../int_data/some_dir
from./data/int/
; but such links are not included in version control (since ./data is not included in version control).The text was updated successfully, but these errors were encountered: