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 noticed a potential issue in the Standalone Binary installation section of the documentation where it suggests creating a symlink to make borgfs an alias for borg mount
Quote:
Optionally you can create a symlink to have borgfs available, which is an alias for borg mount:
ln -s /usr/local/bin/borg /usr/local/bin/borgfs
A symlink to borg will just replicate the borg command under a new name, borgfs, but does not restrict or modify its behavior to only execute borg mount.
The documentation might consider suggesting the use of a shell alias or a wrapper script instead.
For example:
alias borgfs='borg mount'
The text was updated successfully, but these errors were encountered:
Thanks for the clarification! I've tested it and you're right, it works as expected. I suggest adding a note to the documentation explaining that Borg internally detects the name by which it was invoked and adjusts its behavior accordingly. This isn't immediately apparent, and such a note would help clarify why creating a symlink serves as a functional alias.
I noticed a potential issue in the Standalone Binary installation section of the documentation where it suggests creating a symlink to make
borgfs
an alias forborg mount
Quote:
A symlink to
borg
will just replicate theborg
command under a new name,borgfs
, but does not restrict or modify its behavior to only executeborg mount
.The documentation might consider suggesting the use of a shell alias or a wrapper script instead.
For example:
The text was updated successfully, but these errors were encountered: