patch vfs becoming permanently stale

[mnk]

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:

• create a patch
• enter vfs, delete a few files, leave vfs
• modify the patch externally (i.e. delete a single chunk from a file)
• reenter vfs

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.

[mnk]

...I've obviously meant "by Right Arrow".

[andrew_b]

Replying to mnk:

The workflow:

• create a patch
• enter vfs, delete a few files, leave vfs
• modify the patch externally (i.e. delete a single chunk from a file)

How? Using internal editor or not?

• reenter vfs

What do after this step?

Not only vfs doesn't get updated (as this had happened before too),

Yes, this is #62.

but now vfs can't be force-released from vfs dialog.

You just cannot release vfs forced if you make this within that vfs. You must leave vfs and then you can release it.

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.

"Right" key is an equivalent to "Enter" one, it moves you into selected vfs. Btw, this behavior exists more than 15 years.

[mnk]

Replying to andrew_b:

Replying to mnk:

The workflow:

• create a patch
• enter vfs, delete a few files, leave vfs
• modify the patch externally (i.e. delete a single chunk from a file)

How? Using internal editor or not?

Usually using internal editor.

• reenter vfs

What do after this step?

Notice it's stale (or not and mess up the patch then). If notice, leave vfs and try to release it.

Not only vfs doesn't get updated (as this had happened before too),

Yes, this is #62.

but now vfs can't be force-released from vfs dialog.

You just cannot release vfs forced if you make this within that vfs. You must leave vfs and then you can release it.

Well, I thought it was obvious (from the context) I leave the vfs before releasing it.

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.

"Right" key is an equivalent to "Enter" one, it moves you into selected vfs. Btw, this behavior exists more than 15 years.

I've been using mc for a little over 10 years and this never became any less confusing and annoying.
What would be expected is something more alike to "Search Results" dialog, where Right Arrow moves the cursor to dialog's buttons.

[andrew_b]

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?

[mnk]

Well, I've just took 8cb80dcc9c0c2f36111dd439f3e415cec58f7ffa and 4f1801ca11a50187b51916813a3a331e4e3190ba
and the problem seems fixed (though links like changeset/8cb80dcc9c0c2f36111dd439f3e415cec58f7ffa?format=diff&new=8cb80dcc9c0c2f36111dd439f3e415cec58f7ffa save with \r\n endings - bit quirky).

Regardless of that, is the change of the inconsistent vfs dialog behavior open for discussion ?

[andrew_b]

Replying to mnk:

Regardless of that, is the change of the inconsistent vfs dialog behavior open for discussion ?

OK, this behavior is changed to be consistent with other dialogs.

Branch: 3045_hotlist_right_key.
changeset:7d28512890a94e36b3e444d85bee0c4c542050f0

[andrew_b]

Merged to master: [0eb1f6fcae0710b25f9a11181238cd061a25121c].