On Sunday 29 May 2005 10:43 pm, Brett Parker wrote:

...

      for number in $(seq 1156 1183); do               cp dcp_11$number.jpg dest

                       ^^ this was a deliberate error, honest...                        obviously this *will not* work unless you strip                        that 11, either from the seq or here.

Ok that is a whole lot neater than my option (even with the mistake) Wasn't it Babbage that used to put deliberate errors in his plans to foil those who tried to copy him ? Hardly in the sprit of the ALUG, Brett :-)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brett Parker <iDunno@sommitrealweird.co.uk> wrote:

Chris Glover <chris@glovercc.plus.com> wrote:

...

Hi,

Here's one for you...

If I have a range of files named dcp_1100.jpg - dcp_1189.jpg and I only want to copy 1156-1183, how do I do it.

cp dcp_11[56-83].jpg <dest> does not work, but cp dcp_115[6-9].jpg <dest> does.

OK, how about this...

cp dcp_11{5[6-9],[67][0-9],8[0-3]}.jpg dest

Yeah, it's not pretty, but it should work. The alternative is something like... (in bash):

for number in $(seq 1156 1183); do cp dcp_11$number.jpg dest done

And then, just because we can, and we like using as few processes as possible... for number in $(seq 1156 1183); do echo dcp_$number.jpg done | xargs cp --target-directory=dest Right - I wonder if anyone has anything more clean than that ;) (NOTE TO DAVE: No, you can not do: cp dcp_`seq 1156 1183`.jpg dest And here's why... the arguments to cp will expand to: dcp_1156 1157 ... 1183.jpg ) Cheers, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCmjjEEh8oWxevnjQRAjfrAJsGuaGpdxcPP+PxWSiX6RneihwYIwCfdq/t WZAWEc8hxbRMR01aApTNPzI= =5lHT -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 MJ Ray <mjr@phonecoop.coop> wrote:

Brett Parker <iDunno@sommitrealweird.co.uk> wrote:

...

No, you can not do: cp dcp_`seq 1156 1183`.jpg dest And here's why... the arguments to cp will expand to: dcp_1156 1157 ... 1183.jpg

Actually, if you use the rc shell, you can do exactly that: cp dcp_^`{seq 1156 1183}^.jpg dest The `{} expands to a list, which then has the endings added associatively to produce dcp_1156.jpg dcp_1157.jpg and so on.

Hmm, useful. Sortof. Though, other than you, dear Mark, who else is running the rc shell? I'd make an assumption that most people are using bash, or some derivitive of sh. If they're using tcsh on a modern *nix operating system, they probably want shooting... I haven't tested in zsh yet, but I'm fairly sure my solutions would work in that too ;)

Unfortunately, bash just turns the output of backticks into a string and pastes it into the command. It then reads the next command in from that, which causes problems in this and other situations, instead of doing what you usually want.

Well, no, it wouldn't because I'm very very used to how bash expands things ;) Cheers, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCnDqUEh8oWxevnjQRAtl6AJ9+gA0l+dVYAjvyjwRzO7yGCLcMKwCeK2dL xL3H02aa3Xn/i2XZUnEHYBg= =/fMK -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 MJ Ray <mjr@phonecoop.coop> wrote:

Brett Parker <iDunno@sommitrealweird.co.uk> wrote:

...

Hmm, useful. Sortof. Though, other than you, dear Mark, who else is running the rc shell? I'd make an assumption that most people are using bash, or some derivitive of sh. [...]

In bash, you could do "cp $(seq -fdcp_11%g.jpg 58 83) dest" for the same effect, but it's not as general.

...

...

[...] which causes problems in this and other situations, instead of doing what you usually want. Well, no, it wouldn't because I'm very very used to how bash expands things ;)

So why did you use for and xargs to bring that into the problem? ;-)

For and xargs was the second example, and not as neat as the first, the first using pure shell globbing foo, the second being an easy ish way to do it if you don't know globbing. Oh, and of course, I used xargs foo to reduce the number of processes required on a large data set :P The for and xargs foo maybe required on stupidly large data sets.

Anyway, the point was that Dave was expecting the obvious thing and bash doesn't do the obvious thing: a bug in bash not Dave.

I'd say it's non-obvious to a shell that you want that bit in the middle of these things to be {pre,app}ended to the data. Maybe I'm not really human though :P Cheers, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCnETMEh8oWxevnjQRAnUwAJ9aaYFrQn8VjRoSltIZrJ34Jw6BfgCgg4lq OWEVo85D1dD0R8P39QGT9DE= =PsLK -----END PGP SIGNATURE-----