Disregard spaces, aquire full paths [bash]

So, like, guise, I have this bash script that `find`s all of the images in a directory and performs a task on them, but shit goes down when the path has spaces in it.

Like, say I have a path ~/blah.jpg, it performs the task on ~/blah.jpg, but if I have shit like ~/blah 2.jpg, it tries to do it to ~/blah and 2.jpg, which sucks total ass.

How can I fix dat shit, my /prog/ niggas?

Inb4 "Herp derp spaces in unix".

use Perl;

Back to /b/, please

path="\"$path\""

THIS IS WHY I USE XARGS

Also, Herp derp spaces in unix

>>1
This is why I always use _'s

>>6
This is why I always use superfluous apostrophe's.

Shit, I'm fucking stupid.

It's this fucking for loop I've got that's fucking with the spaces.

I've got like


for i in `find -name ".jpg" -o -name "*.png"`

And it's reiterating for the spaces. Can I make it only do it for the newlines instead of just any whitespace? The whole thing is I'm not good at bash and its a nigger when it comes to strings anyways.

>>8
Whose a nigger?

>>7
Yeah, I have no idea why I did that
>>8
I don't think it can check for names like that, but you could use -print0 and a pipe or something I don't actually know or care

XARGS

Fixed it with the $IFS variable.

Kthxbye.

And of course, if you've been following along for a week or two, you know that this (BING!) is a Useless and Dangerous Use of Backticks!
Remember, most cases where you have:
    for f in `command ...`; do
        ...
    done
you should rewrite it as:
    command ... |
    while read f; do
        ...
    done
and in some cases, such as this one, you can use xargs as in:
    find ... -print0 | xargs -0 foo

Just another Useless Use of /prog/,

perl

>>13
>and in some cases, such as this one, you can use xargs as in:

Lolno. If you knew what I was doing that'd be like trying to swallow thumbtacks. Go shove a dildo down your throat, you fucking tool.

>>14
Useless Use Of Perl, bro. Fight the power.

XARGS == CORRECT