SCIENTIFIC-LINUX-USERS Archives

March 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chris Schanzle <[log in to unmask]>
Reply To:
Chris Schanzle <[log in to unmask]>
Date:
Sat, 7 Mar 2015 19:28:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On 03/07/2015 06:32 AM, David Sommerseth wrote:
>> From: "ToddAndMargo" <[log in to unmask]>
>> To: "SCIENTIFIC-LINUX-USERS" <[log in to unmask]>
>> Sent: 7. March 2015 05:40:43
>> Subject: Re: need rsync exclude help
>>
>>>      --exclude='{wine-*,wine-1.7.24}' /home/CDs/Linux /mnt/MyCDs/.
>>>
>> I am not real certain that the {} thingy works correctly.
>> Anyway, I only needed 'wine-*'
> That seems redundant in this case.  You can always test such expansions using 'echo'
>
>    $ echo {wine-*,wine-1.7.24}
>    wine-* wine-1.7.24
>    $ echo wine-{1.7.24,package-1.2.3}
>    wine-1.7.24 wine-package-1.2.3
>

But note no expansion occurs by the shell when surrounded by single quotes:

$ echo -exclude='{wine-*,wine-1.7.24}'
-exclude={wine-*,wine-1.7.24}

Rsync may do something with the braces, but not the shell, in this case.

ATOM RSS1 RSS2