> IMO, in the presence of -e, "false && false" should terminate > execution, just as "false && true" should. The entire compound > statement is false because the first one is. 2013 POSIX says: The -e setting shall be ignored when executing [...] any command of an AND-OR list other than the last.
(from http://pubs.opengroup.org/onlinepubs/9699919799/)
