-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to edit symlink destination #1690
Comments
@elfmz After 65e1870 change symlink has strange behavior:
But I cann't explain situation 1. |
Improvements after elfmz#1690 & 65e1870 & 93a50b2 * SA_TXTBTN_INFO & SA_EDIT_INFO fields now never hidden (when seleceted >1 it shows the number of selected files + directories) * SA_EDIT_INFO not readonly only if symlink * If symlink then let's first focus not on the editable SA_EDIT_INFO, but on the button SA_TXTBTN_INFO
The issue has not been perfectly completed yet :) But If I'm trying to "edit" broken symlink using the F4 shortcut (symlink which points to non-existent file/folder) - far2l shows me red message box with text "No such file or directory (2) Cannot open the file" and nothing else happens further. That's a bit unexpected, because the main goal there - is to be able to fix broken symlink in place. From other hand the Ctrl+A works fine with the broken symlinks, as I said before. |
@alexandrustinov This is the common F4 behavior: on file try open it for edit; on directory show attribute dialog. Additional in #1744 I add confirmation for case when new symlink target not exist. |
The Midnight Commander has pretty nice feature File->Edit symlink , once you select the symlink you can change the destination that way
For far2l there are F4 or Ctrl+A keystrokes, Attributes dialog shows destination link path but input box is disabled (read/only).
I can change practically any attribute there but not the symlink destination path.
Is it possible to allow to change the symlinks destination by the Attributes dialog box?
The text was updated successfully, but these errors were encountered: