From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Dominik Reichardt <domiman@gmail.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Apple bash to zsh script problems with error control and bash emulation
Date: Mon, 16 Nov 2020 19:10:06 +0100 [thread overview]
Message-ID: <CAN=4vMq_mA8EDiBuyGLJBS99Y3PgP8ahykVoSn79LA6ce4uYzg@mail.gmail.com> (raw)
In-Reply-To: <20201116180129.4f6a851f@tarpaulin.shahaf.local2>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Mon, Nov 16, 2020 at 7:02 PM Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
> Dominik Reichardt wrote on Mon, 16 Nov 2020 16:00 +0100:
> > I’ve recently moved to zsh as Apple is pressuring us :)
>
Apple is only encouraging users to change their login shell to zsh. You can
still run scripts written in bash, perl, python or what have you.
The easiest solution is to keep the script as «#!/usr/bin/env bash»:
>
This is solid advice. The chance that Apple will make it impossible to run
bash scripts on macOS within the next decade is extremely low. If that
happens (it really won't), then you can decide whether to rewrite the
scripts or to change the OS.
Roman.
[-- Attachment #2: Type: text/html, Size: 1167 bytes --]
next prev parent reply other threads:[~2020-11-16 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:00 Dominik Reichardt
2020-11-16 18:01 ` Daniel Shahaf
2020-11-16 18:10 ` Roman Perepelitsa [this message]
2020-11-16 19:45 ` Dominik Reichardt
2020-11-16 20:11 ` Roman Perepelitsa
2020-11-16 23:15 ` Lewis Butler
2020-11-17 7:08 ` Roman Perepelitsa
2020-11-17 13:03 ` Dominik Reichardt
2020-11-17 15:54 ` Lewis Butler
2020-11-17 16:13 ` Dominik Reichardt
2020-11-17 21:29 ` Roman Perepelitsa
2020-11-17 21:47 ` Bart Schaefer
2020-11-17 22:25 ` Dominik Reichardt
2020-11-18 10:01 ` Roman Perepelitsa
2020-11-19 13:31 ` Lewis Butler
2020-11-19 13:55 ` Dominik Reichardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN=4vMq_mA8EDiBuyGLJBS99Y3PgP8ahykVoSn79LA6ce4uYzg@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=domiman@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).