zsh-users
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Oğuz <oguzismailuysal@gmail.com>
Cc: dana <dana@dana.is>, Zsh Users <zsh-users@zsh.org>
Subject: Re: variable expanding to `*` matches a literal `*` in case cond. construct
Date: Mon, 16 Dec 2019 01:28:27 +0100	[thread overview]
Message-ID: <CAHYJk3QuMU6E3nQZkdieTcy+646XjXdigRNcUpEzhbz-nzN7=w@mail.gmail.com> (raw)
In-Reply-To: <CAH7i3Lp8GkJw1uuLOQXoodAoYP3A7zS=VrgLYXSst4oe-bJwjw@mail.gmail.com>

On 12/16/19, Oğuz <oguzismailuysal@gmail.com> wrote:
> 16 Aralık 2019 Pazartesi tarihinde dana <dana@dana.is> yazdı:
>>
>> Apple have changed their default *log-in shell* to zsh. /bin/sh is still
>> /bin/bash (though it seems like they might switch to dash in the
>> future?),
>> and
>> both of those still work exactly the way they did before. You still need
>> to go
>> out of your way to write scripts that run under zsh. Even if you use zsh
>> to
>> run a shell script without an interpreter directive, it will run it with
>> /bin/sh.
>>
>
> Thanks, this is something I didn't know. So the conclusion is;
> 1. One should never, ever expect zsh to be compatible with other shells
> since it has to suck, just as its users,
> 2. Apple doesn't force zsh, and a proper shell is still available, so no
> need to worry.
>
> This is my last post to this mailing list, thanks.

If all shells worked exactly the same, what would be the purpose of
having more than one to choose from? Zsh doesn't fall into the same
traps of traditional sh like bash did, and it is possible to write
working scripts without using horribly convoluted constructs. If you
think that "sucks", that is your loss. Looking forward to not getting
a reply to this since you've already sent your last post to this
mailing list, you're welcome.

-- 
Mikael Magnusson

  reply	other threads:[~2019-12-16  0:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  8:41 Oğuz
2019-12-15 10:05 ` Andreas Kusalananda Kähäri
2019-12-15 11:04   ` Oğuz
2019-12-15 12:02     ` Andreas Kusalananda Kähäri
2019-12-15 12:50       ` Oğuz
2019-12-15 22:49         ` Eric Cook
2019-12-15 23:27         ` Dominik Vogt
2019-12-16  0:02           ` Perry Smith
2019-12-16  0:03         ` dana
2019-12-16  0:23           ` Oğuz
2019-12-16  0:28             ` Mikael Magnusson [this message]
2019-12-16  5:25             ` Lewis Butler

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='CAHYJk3QuMU6E3nQZkdieTcy+646XjXdigRNcUpEzhbz-nzN7=w@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=dana@dana.is \
    --cc=oguzismailuysal@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).