Nickolai Dobrynin <[email protected]> writes: > SOLVED! The "M-&" was the culprit. Merely setting the process mark and > running B c (or B m, respectively) afterwards worked as expected.
Ah! I had missed that (important) part of your question. Yes, it looks like the way M-& is implemented, this will behave as if you invoked a command repeatedly for every single process marked file. This explains the behavior you see. But the moving etc. commands already honor process marks so M-& is not useful here at all. Michael.
