Regression: shell patterns in copy dialog do not work

[vda]

I have two directories selected:
busybox.2 and busybox.t2

I press F5 and ask mc to copy *2 to *3:

┌─────────────────────────── Copy ───────────────────────────┐
│ Copy 2 directories with source mask:                       │
│ *2                                                     [ ] │
│                                   [x] Using shell patterns │
│ to:                                                        │
│ *3                                                     [ ] │
│ [ ] follow Links            [ ] Dive into subdir if exists │
│ [x] preserve Attributes                [ ] Stable Symlinks │
│           [< OK >]   [ Background ]   [ Cancel ]           │
└────────────────────────────────────────────────────────────┘

It creates directory named "*3", copies busybox.2 to it, then tries to copy busybox.t2 to it and complains when it sees existing files.

Looks like despite "[x] Using shell patterns" option being selected, it does not handle it right.

mc-2.6.1 worked as expected in this situation: it was creating copies named busybox.3 and busybox.t3

[slavazanko]

Try to use next test case:

source mask: *2
to: \13

chars '*' and '?' mean implicit replacement groups. For example,

File abscdefgh

source mask: ???*
to: \1 \2 \4 - \3

Result: a b defgh - c

}}

I think, in your test case usage of asterisk in 'to:' field not intuitive...

[slavazanko]

I think, behavior with asterisk in 'to:' field is deprecated (like as scanf search type).

Is this ticket actual?

[vda]

I think, in your test case usage of asterisk in 'to:' field not intuitive...

Press F5, then F1. It is still documented there in the help. And it was working in previous versions.

In programs like editors and mc, users tend to memorize things by keystrokes. Gratuitous changes in interface force people to relearn.

You were understandably pissed off by bad maintainership of old MC by Pavel. I was too. But if you want to fare better, pay attention to your user's needs. Don't make their experience with new versions of MC painful unless you have to.

Since I installed latest git, I have a number of things which work differently, or do not work at all:

File search dialog is no more at F9, right, right, down, down, enter. It is one point lower. Argh. I try to use M-? now.

_In_ file search dialog, travelling between filename field and search string field takes FOUR up/down arrows. In 2.6.1, it was taking just one. Also, search defaults have changed (regex was on by default in older version, for example).

In editor, F7 search does not remember last search string across editing sessions. As soon as one exits editor and enters it again, F7 will show empty string.

In editor, blue arrows and dots for whitespace appear to be non-configurable. How to turn it off? (A keyboard toggle would be ideal).

I will try to address each of these things with bug reports and hopefully even patches.

[slyfox]

Replying to vda:

I think, in your test case usage of asterisk in 'to:' field not intuitive...

Press F5, then F1. It is still documented there in the help. And it was working in previous versions.

It's clearly an easily fixable regression (I find useful to copy file '*' to '*.back' time to time too). Will be fixed it this ticket.

In programs like editors and mc, users tend to memorize things by keystrokes. Gratuitous changes in interface force people to relearn.

You were understandably pissed off by bad maintainership of old MC by Pavel. I was too. But if you want to fare better, pay attention to your user's needs. Don't make their experience with new versions of MC painful unless you have to.

Since I installed latest git, I have a number of things which work differently, or do not work at all:

File search dialog is no more at F9, right, right, down, down, enter. It is one point lower. Argh. I try to use M-? now.

_In_ file search dialog, travelling between filename field and search string field takes FOUR up/down arrows. In 2.6.1, it was taking just one. Also, search defaults have changed (regex was on by default in older version, for example).

In editor, F7 search does not remember last search string across editing sessions. As soon as one exits editor and enters it again, F7 will show empty string.

In editor, blue arrows and dots for whitespace appear to be non-configurable. How to turn it off? (A keyboard toggle would be ideal).

I will try to address each of these things with bug reports and hopefully even patches.

Separate bugs would be ideal. Some of them might already present as tickets.

Thanks!

[vda]

Updated fix