Re: Find the path of a shell command [POSTPONED]

On Wed, Oct 12, 2022 at 9:57 PM Cameron Simpson wrote: > On 13Oct2022 03:25, Paulo da Silva > wrote: > >There is another problem involved. The script, works fine except when > >launched by cron! Why? > > Record the script output: > > # record all output > exec >/tmp/script.$$.out 2>&1

RE: for -- else: what was the motivation?

This has been discussed so often precisely because I swear NO CHOICE of keyword would satisfy everybody! Most languages start with designated keywords and some reserve a few for later use. But then things can get frozen in place to avoid breaking existing programs or break older compilers/interp

Re: for -- else: what was the motivation?

On 2022-10-12, Rob Cliffe via Python-list wrote: > I too have occasionally used for ... else.  It does have its uses. But > oh, how I wish it had been called something else more meaningful, > whether 'nobreak' or whatever. I use it a few times year. I have to look it up in the documentation eve