[email protected] writes:
>> On Wednesday, May 14, 2014 6:00:12 PM UTC-5, Olaf Meeuwissen wrote:
>> [email protected] writes:
>>
>> > Hello all,
>> >
>> > I have a message at "/Users/kms/Mail/[email protected]/[Gmail].All
>> >
> Mail/cur/1390956834_1.10938.highlander,U=2,FMD5=844bb96d088d057aa1b32ac1fbc67b56:2,S"
>> >
>> > Note the space in "All Mail". --exec doesn't like this:
>> >
>> > $ mu find date:20040823 --exec "cat"
>> > cat: /Users/kms/Mail/[email protected]/[Gmail].All: No such file or
>> > directory
>> > cat:
>> >
> Mail/cur/1390956834_1.10938.highlander,U=2,FMD5=844bb96d088d057aa1b32ac1fbc67b56:2,S:
>> > No such file or directory
>> >
>> > Should I file an issue on GitHub, or is this a configuration issue? I'm
> on
>> > Mac OS X, so it may also be a standards compliance issue.
>>
>> It's the `cat` command that doesn't like the space. To fix this, `mu
>> find` should quote path names or escape characters with special meaning.
>> You can probably work around it with something like
>>
>> mu find date:20040823 --fields="l" | while read filename; do
>> cat
>> done
>
> I wasn't even using cat initially:
>
> $ mu find date:20040823
> Mon Aug 23 07:41:27 2004 .......
>
> $ mu find date:20040823 --exec "mu view"
>
> but nothing was printed out.
The exact command doesn't matter, really. It the command line parsing
that sees the file name as two separate arguments. For the exact same
reason you are using double quotes around the "mu view" above. Saying
mu find date:20040823 --exec mu view
will treat the "view" bit as part of the search expression instead of
the command.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
--
You received this message because you are subscribed to the Google Groups
"mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
