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
I use yadm to manage my dotfiles across many different systems. The current
mechanism they have for managing files that are different are symlinks, so for
example
.sdirs## <- default
.sdirs##classA <- special one-off system (i.e. different and/or extra bashmarks)
A yadm alt command will link .sdirs --> .sdirs##classA or .sdirs --> .sdirs## based on
configuration.
The current bashmarks will stop on the symlink during a "s" and my guess "d"
Possible solution, to see if SDIRS is a link, if so follow it to the real file
change:
if [ ! -n "$SDIRS" ]; then
SDIRS=~/.sdirs
fi
touch $SDIRS
to
if [ ! -n "$SDIRS" ]; then
SDIRS=~/.sdirs
fi
tmp=$(readlink $SDIRS)
if [ -n "$tmp" ]; then
# echo "Updating sdirs: $tmp"
SDIRS=$tmp
fi
touch $SDIRS
The text was updated successfully, but these errors were encountered:
I use yadm to manage my dotfiles across many different systems. The current
mechanism they have for managing files that are different are symlinks, so for
example
.sdirs## <- default
.sdirs##classA <- special one-off system (i.e. different and/or extra bashmarks)
A yadm alt command will link .sdirs --> .sdirs##classA or .sdirs --> .sdirs## based on
configuration.
The current bashmarks will stop on the symlink during a "s" and my guess "d"
Possible solution, to see if SDIRS is a link, if so follow it to the real file
change:
to
The text was updated successfully, but these errors were encountered: