-
Notifications
You must be signed in to change notification settings - Fork 3
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
patch vfs becoming permanently stale #3045
Comments
...I've obviously meant "by Right Arrow". |
Replying to mnk (#3045):
How? Using internal editor or not?
What do after this step?
Yes, this is #62.
You just cannot release vfs forced if you make this within that vfs. You must leave vfs and then you can release it.
"Right" key is an equivalent to "Enter" one, it moves you into selected vfs. Btw, this behavior exists more than 15 years. |
Replying to andrew_b:
Usually using internal editor.
Notice it's stale (or not and mess up the patch then). If notice, leave vfs and try to release it.
Well, I thought it was obvious (from the context) I leave the vfs before releasing it.
I've been using mc for a little over 10 years and this never became any less confusing and annoying. |
I cannot reproduce this bug with recent master snapshot (4.8.9-4-g5fdd102) or I'm doing something wrong.
Would you try reproduce this bug with 4.8.9-4-g5fdd102 yourself? |
Well, I've just took [8cb80dc] and [4f1801c]
Regardless of that, is the change of the inconsistent vfs dialog behavior open for discussion ? |
Replying to mnk:
OK, this behavior is changed to be consistent with other dialogs.
Branch: 3045_hotlist_right_key. |
|
|
|
Important
This issue was migrated from Trac:
mnk
(galtgendo@….pl)I'm not 100% sure (as I haven't downgraded yet), but there has been a major regression between 4.8.8 and 4.8.9 with patch vfs (at least I've only found it in this vfs, but I haven't used others in such way).
The workflow:
Not only vfs doesn't get updated (as this had happened before too), but now vfs can't be force-released from vfs dialog.
On a related note: I might be wrong here, but that dialog seems to be only one, that getting closed by Down Arrow - that's counter-intuitive and inconsistent.
The text was updated successfully, but these errors were encountered: