From: Tom Hale <tom@hale.ee>
Date: Thu, 04 May 2017 09:35:31 GMT
Subject: Re: [PATCH] __git_ps1: Don't kill shell if user types `set -e`
Message-ID: <60ea6f0e-aa27-9a2c-54fd-9c14db9f028c@hale.ee>
In-Reply-To: <CACBZZX6XdwND2-7cY0zp8+K_uh60tn-i_r9V7HAe2X-a-RJeQA@mail.gmail.com>

On 04/05/17 16:16, Ævar Arnfjörð Bjarmason wrote:

> What's the real use-case here? If you do "set -e" in your shell you
> also get e.g.:
> 
>     $ ls -l blah
>     ls: cannot access blah: No such file or directory
>     === Command terminated with exit status 2 (Thu May  4 11:16:03 2017) ===
> 
> I.e. any little failure will terminate your shell, are you actually
> running a shell like this? For what purpose?

If I want to copy and paste a list of commands and have the execution
stop at a failure, I type "bash" then "set -e", then paste the commands.

It saves me creating a script file and then removing it later.

-- 
Tom Hale