Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.
0 votes
in vifm by

al resolves the symlinks in the path to get the real path.

rl makes the path through the symlinks as if they were real directories.

What if I want a relative link, but with the symlinks resolved?

1 Answer

0 votes
by

al resolves the symlinks in the path to get the real path.
rl makes the path through the symlinks as if they were real directories.

I believe it's the other way around.

What if I want a relative link, but with the symlinks resolved?

rl resolves symlinks, because otherwise relative symlink can end up pointing to a wrong path (#411 on GitHub). This won't happen with absolute links.

by

Oh, indeed. I guess I wanted rl without resolution. I was also confused by the treatment of overwriting an existing link based on whether or not it's broken.

by

I was also confused by the treatment of overwriting an existing link based on whether or not it's broken.

This must be a bug. On what operation do you see the difference?

by

This must be a bug. On what operation do you see the difference?

Putting a symlink with the same name as an existing one. If the existing link is broken, Vifm changes the target; otherwise it shows the File Conflict window.

by

See it now, especially with set nosyscalls. Thanks!

by

Fixed on master.

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.
...