Help batch file to move files in list to created subdirectory

​Hi Beazleybub, and welcome to SevenForums,

Well I have just the batch file for you. Recently, another member asked for something similar: a batch script that would find a bunch of files given their filenames, in the form of a new-line separated text file list, and do something with those files.

The script can be found here, post #2, and I'll give you a hint regarding what sort of options you should use:

Code:

set "output_folder=.\NewSub"
set "default_mode=MOVE"
set "include_folders=FALSE"
set "silence_errors=FALSE"
set "adapt_current_directory=TRUE"

The rest should be self explanatory. One thing to note though, each filename entry in your text file list must have an extension, unlike in your example 'list.txt'.

Good luck, Beazleybub.

beazleybub said:

I have one small issue though. Some of my filenames have spaces in them. Could you modify the script to allow this?

The script already fully supports parsing filenames and manipulating files that have spaces in their name. Did you happen to find an issue relating to this? If so, please provide details.

In my file list I have a filename called "foo bar.txt" and the first time I tried to run it the screen just blinked. I added a pause to your script to see what was going on. The message displayed was...

Item 'foo' could not be located

0 items were copied to directory '.\NewSub'
Press any key to continue . . .

It was missing the "bar"


Thanks

​I was able to replicate and fix the issue you found, which was only a display issue with that particular error message. The script would still be unable to locate your file "foo bar.txt".

Make certain the filenames listed in your text file list have extensions, for instance, specify "foo bar.txt" and not just "foo bar", or you may use wildcards, e.g. "foo bar.*".

I'm sorry your response is a little confusing. You said you fixed the issue but, then say there can be no spaces in the filenames. I see no reason your script couldn't be edited to parse the list file with filenames that contain spaces. Anyhow, I still appreciate your input and script, they both were very useful.

beazleybub said:

You said [...] there can be no spaces in the filenames. I see no reason your script couldn't be edited to parse the list file with filenames that contain spaces.

Nowhere in any post did I ever say or even come close to implying that my script doesn't support filenames containing space characters. I do recall, however, saying the exact opposite. In my post #4, I mention that filenames with spaces are fully supported by the script. Zero strings attached there, I assure you.

To be crystal clear, in my previous post I had merely pointed out that there was a minor display error with one of the error messages, to which I've now fixed. This correction did not effect the algorithm of the script whatsoever.

In your example where the script failed to find the file "foo bar.txt", the script genuinely could not locate a file named "foo bar.txt" on your filesystem, despite what the error message said about not being able to find "foo". The function that outputs the error message got passed the full name "foo bar.txt", but the function was instructed to only print the first argument (arguments delimited by space character). This is the 'issue' I have fixed.

​

beazleybub said:

That is exactly what you said!

What is? Please be coherent.

beazleybub said:

Do you not think the filename "foo bar" has a space in it?

You've got to be kidding, right? This shouldn't need to be questioned. There is a single, empty, well defined space between "foo" and "bar.txt", and as obvious as this appears, I can, if you wish, manage the effort to ask others to confirm this for you if you are truly unsure.

Filenames and files with names containing spaces work just as flawlessly now with the script as files lacking space characters. What is with your disagreement in post #7?

beazleybub said:

Stop ranting like a contestant from Project Runway and breathe.

I take all my works and projects seriously. I would not allow for anyone to experience an error caused by my mistake without a subsequent, apt explanation. If you are unsatisfied with practical solutions or other aid given to you, you should spend time gathering details and propose at least a constructive, meaningful response instead of insulting the person giving you assistance and wasting time engineering hypothetical similes to help your intentionally provoking endeavour. It wasn't 'rant' it was making a point clear, which clearly failed.

beazleybub said:

(wipes hands)

Uber act of rudeness. I hope you enjoy your 100% free help.