Show HN: Eyeball: Detect and understand changes in a program's output

#1

Post by martinpllu » Tue, Aug 29, 2017, 6:45 PM UTC

Show HN: Eyeball: Detect and understand changes in a program's output
github.com

Re: Show HN: Eyeball: Detect and understand changes in a program's output

#2

Post by yorwba » Tue, Aug 29, 2017, 8:01 PM UTC

Have you tested your script with files like " this has spaces .out"? I think you are missing some quotes around your variable expansions.

Re: Show HN: Eyeball: Detect and understand changes in a program's output

#3

Post by martinpllu » Wed, Aug 30, 2017, 10:30 PM UTC

yorwba wrote: post #2

Have you tested your script with files like " this has spaces .out"? I think you are missing some quotes around your variable expansions.

Wow, eagle eyes. Thank you. Any tips on how to deal with quotes around variable expansions in general? Should I quote each usage of a variable or does it depend on context?

Re: Show HN: Eyeball: Detect and understand changes in a program's output

#4

Post by yorwba » Thu, Aug 31, 2017, 7:35 AM UTC

martinpllu wrote: post #3

yorwba wrote: post #2

Have you tested your script with files like " this has spaces .out"? I think you are missing some quotes around your variable expansions.

Wow, eagle eyes. Thank you. Any tips on how to deal with quotes around variable expansions in general? Should I quote each usage of a variable or does it depend on context?

Quoting each usage of a variable is almost always correct.

The only context where it isn't correct is when you need word-splitting to occur, which is almost never.

Even "$@" is special-cased to do the right thing and quote each individual parameter, instead of the whole list.