[ edit: this apparently does not get the annexes ] For those who want to grep it...

anc84 · on Nov 5, 2015

    for file in *.pdf; do pdftotext "${file}"; done

Less HN clutter ;)

tosseraccount · on Nov 5, 2015

It gets rid of the goldarn blanks in the filenames.

anc84 · on Nov 5, 2015

    for file in *.txt; do mv "${file}" "${file// /}"; done

jaytaylor · on Nov 5, 2015

Off-topic:

Wow thanks, I didn't know about that form of bash variable substitution!

It's documented under the heading:

    ${var/Pattern/Replacement}

at http://www.tldp.org/LDP/abs/html/parameter-substitution.html

tosseraccount · on Nov 5, 2015

WellIdidnotknowthat.thanks!

mahouse · on Nov 5, 2015

Blanks in the filenames are a problem? Is this MS DOS 6?

pdkl95 · on Nov 5, 2015

Blanks are only a problem for people that haven't read bash(1). Once you learn to simply use "$@" everywhere, you never worry about blanks again.

scbrg · on Nov 5, 2015

Since space is the standard argument separator in most shells, yes, obviously. The problem can be worked around/handled in various ways, but it's still a problem, of course.

fnordfnordfnord · on Nov 5, 2015

They're at least annoying for some people to deal with.