Comment by rossvor | Hacker News Reader

Comment by rossvor | Hacker News Reader

Parent Full thread

No project I'm aware of, but I did cobble together a script to do something similar. In my I case also wanted it to work with copyq so there's some noise related to it.

  tmp=/tmp/out
  maim -s -u | tesseract - "$tmp"
  
  # Remove empty lines
  sed -ir '/^\s*$/d' "$tmp".txt

  copyq add "$(cat "$tmp".txt)"
  rm "$tmp".txt
  rm "$tmp".txtr

tesseract insists on adding on txt extension and what I assume is some intermediary file txtr, making it awkward to use with mktemp. Probably explained in the manual which I skipped.

But like others have said tesseract is not very reliable, at least with default settings -- it's common for it to add extra spaces or various single quotes, or omit spaces.

I wasn't familiar with that "-r", but FWIW the gsed man page says "(for portability use POSIX -E)"

Abutting that "r" option against the "i" option is likely why you ended up with a file named .txtr and therefore implies that it did not actually hear the "-r" you intended

I've had the best luck picking an actual backup suffix such as "-i.bak" or "-i~" to keep BSD sed and GNU sed on the same page, although I've also seen scripts that go as far as "--version" sniffing and changing the actual invocation as "${SED_I} -E" type stuff

You are absolutely correct! I wasn't aware that "-i" takes an optional suffix, so it didn't even occur to me to look at the sed line as possible cause for this extension weirdness.

Yeah, but "optional" in the _worst possible way_ since, due to the getopt library difference, the GNU version wants any empty suffix value abutted, and the BSD version wants it separated away from the "-i", burning thousands of hours of humanity over the years :-(

Woe unto those who write scripts as "sed -i -e /whatever/" since for half(?) of their users they'll end up with "somefile-e"

Reply on news.ycombinator.com