Skip to content
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

savannah: Issues with Batch Operations #112

Open
mc-butler opened this issue Jan 2, 2009 · 2 comments
Open

savannah: Issues with Batch Operations #112

mc-butler opened this issue Jan 2, 2009 · 2 comments
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.6.1 Reproducible in version 4.6.1

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/112
Reporter slavazanko (@slavaz)

Original: http://savannah.gnu.org/bugs/?12737

Submitted by:NoneSubmitted on:Tue 19 Apr 2005 04:47:28 PM UTC
Category:CoreSeverity:3 - Normal
Status:NonePrivacy:Public
Assigned to:NoneOpen/Closed:Open
Release:All versionsOperating System:All

Original submission:

One of the main reasons people use MC is because if its "Yes for all" or "No for all" features.

When doing batch moves/copies (of multiple directories) under Win32, the copy is often interrupted with "Permission denied" or "File cannot be stat-ed" and only options: "Skip, Retry, Abort".

Skipping a lot of sequetial files often by accident skips files being copied (if you hold S!) - What a user interface disaster is that!?

Another solution would be "Force" and "Force All" which would find the applications holding handles to files to be deleted, killing the handles, and deleting the file. I would most definitely add this feature, in the Linux version too.

There should at the very least be a "Skip All" option, most definitely.

Further, the neither the transfer rate nor ETA is displayed during most operations. Surely the code to do this for any operation is in place?

I submit this here due to lack of time/ability to find a more appropriate place. Please guide me in the right direction. I will even fix these issues myself when I find the time.

Thanks guys, everyone working on this project. We need this utility, everywhere!

Furthermore, I have discarded the mc.hlp file long ago and do not know what version I am using as there is no About anywhere that I can find. 

Comment 1 by Coenraad Loubser <tunasashimi> at Tue 19 Apr 2005 10:32:31 PM UTC:

Version 4.1.36

Comment 2 by Pavel Tsekov <ptsekov> at Wed 20 Apr 2005 08:40:07 AM UTC:

Do you speak of the native Win32 port of MC ? It has been deprecated for quite some time. If you want to use MC on Win32 you better get the Cygwin version of MC. Using setup.exe from:

http://www.cygwin.com/setup.exe

Btw you seem to use quite an old version of MC - the last released version is MC4.6.0 from 2 years ago, and also there there are the MC4.6.1-pre[1-4] pre-releases.

Comment 3 by Anonymous at Wed 20 Apr 2005 09:20:02 AM UTC:

Thanks, ive been out of the loop for a while.

I cringe when I thiink of installing cygwin, last time (about a year or
2 back it gave me such hassles)

Maybe things have changed....

Comment 4 by Pavel Tsekov <ptsekov> at Wed 20 Apr 2005 11:35:52 AM UTC:

If you have problems installing Cygwin or Cygwin packages you can ask for help on the Cygwin mailing list. If you want to only use MC you don't have to install the whole net distribution - just select 'mc' from the 'Utils' category.

If the problem that you are experiencing persists with the Cygwin version you can come back and open a new bugreport or maybe continue this one.

Comment 5 by Oswald Buddenhagen <ossi> at Mon 16 May 2005 05:25:30 PM UTC:

the same happens under *nix with a vfat mount when the mount option "quiet" (ignore perm set errors) is not set.
@mc-butler
Copy link
Author

Changed by styx (@styx) on May 25, 2009 at 8:21 UTC (comment 1)

  • Milestone set to future releases

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jan 11, 2014 at 23:14 UTC (comment 2)

  • Description edited
  • Branch state set to no branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.6.1 Reproducible in version 4.6.1
Development

No branches or pull requests

1 participant