Get Files Whose Displayed Name Contains Even/Odd Numerals

[Shane_Stanley]

@Yvan Koenig

More than 10 times faster than faster one of the scripts tested yesterdays.
We got here a new example of the efficiency of ASObjC.

Thanks for doing the test; sorry about leaving copy instead of move in there.

For sure, the used syntax may appear as a bit esoteric but, with the samples which you posted several times here or in the list applescript-users@lists.apple.com, we have a lot of starting points which may be edited to fit specific needs.

Which is sort of how many of us learned to script in the first place.

[Shane_Stanley]

@Nigel Garvey

I’d be inclined to wait for an “Oh by the way I forgot to mention .” response from the OP before worrying about that. One would need to know which number was relevant in such a case.

Yes, although I was thinking more in terms of how some of the example scripts would behave when a file is found by both regexes (none of your regicide here, thank you ;)), and it’s already been moved by the time the second lot of moving is attempted.

[Yvan_Koenig]

@Shane Stanley

@Yvan Koenig

More than 10 times faster than faster one of the scripts tested yesterdays.
We got here a new example of the efficiency of ASObjC.

Thanks for doing the test; sorry about leaving copy instead of move in there.

Not a problem. It was a good way to push me to search in Xcode’s help.
Often, the names given to features - probably clear for those whose English is the main language - are a bit complicated for me but in this case my old scholar English was sufficient.

Yvan KOENIG running Yosemite 10.10.5 in French (VALLAURIS, France) lundi 28 septembre 2015 14:21:39

[DonL]

Wow guys. Thanks for the responses. I’ll just be over here picking up my brain which just oozed out me ear.

Here’s the background for the script. I have bunch of PDF’s created from scans of a book that I want to recombine to re-create the book. However, they were all scanned in using a copy machine that didn’t have any sorting or collating functions. As a result, the original was scanned twice; once in a regular position and the second time upside down. The first scan yielded the correct orientation of the binding on the even pages. The second scan yielded the correct orientation of the binding on the odd pages. If you combine the even pages of the first scan and the odd pages of the second scan into one PDF file, you can then print 2 sided and have a book you just need to run through a 3 hole punch and put in a binder.

I thought there might be an easy way to use a list of numbers up to 200 (since I knew there wasn’t more than 200 pages in the original) to separate the files.

[Yvan_Koenig]

To resume the problem, according to my understanding,

(1) There was no risk to have two numbers embedded in a file name which is fine because we have no way to decide which one would be significant if they were two or more.
(2) There was no real need to drop numbers greater than 200.
This time you have less than 200 files but on day the original document may have more than 200 pages.
(3) It seems that the availability of zeros in front of numerical value was not a problem.

Yvan KOENIG running Yosemite 10.10.5 in French (VALLAURIS, France) mardi 29 septembre 2015 10:27:06