From: "David C. Rankin" <firstname.lastname@example.org> To: zsh users list <email@example.com> Subject: Re: help adapting bashism for zsh Date: Mon, 10 Jun 2019 16:55:05 -0500 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 06/10/2019 12:34 PM, Ray Andrews wrote: > On 2019-06-10 7:53 a.m., Roman Perepelitsa wrote: >> automatic translation of bash code to zsh. It's likely that your >> requirements are unique. Usually systems that can afford to have zsh >> can also afford to have bash, so no translation is necessary. >> > In my case I didn't want the bother of having to learn the idiosyncrasies of > two shells. I picked one and was hoping to never have to learn the other. If > I was planning to transition from bash to zsh, I'd be hoping to subsequently > avoid bash altogether and thus go through the conversion trouble once but then > forget about bash and do all further work in zsh. So space considerations > would be the least of my motives. Just me, but zsh syntax is so abstruse that > not only learning it, but also trying to remember the differences vis a vis > bash, would seem brain blowing. > > So it seems David will have to do it line by line. That's the interesting part. I have 2-decades of bash, which with the bashisms makes that somewhat of a daunting challenge. The "2566 POSIX and bash scripts" wasn't a guess, it was a 'find ~/scr -type f | wc -l' exercise. From the days of loading Linux from floppy disks from boxed sets, you didn't really have a lot of foresight as to the implications of shell choice, which is what makes the shell differences now more acute. So the path forward seems like leaving all shells installed the only solution and migrate the needed scripts one at a time. We shall see how it goes. -- David C. Rankin, J.D.,P.E.
next prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-10 0:33 David C. Rankin 2019-06-10 5:41 ` Roman Perepelitsa 2019-06-10 14:43 ` David C. Rankin 2019-06-10 14:53 ` Roman Perepelitsa 2019-06-10 17:34 ` Ray Andrews 2019-06-10 21:55 ` David C. Rankin [this message] 2019-06-10 20:22 ` Bart Schaefer 2019-06-10 22:31 ` David C. Rankin 2019-06-11 8:56 ` Peter Stephenson
Reply instructions: You may reply publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
zsh-users Archives are clonable: git clone --mirror http://inbox.vuxu.org/zsh-users Newsgroup available over NNTP: nntp://inbox.vuxu.org/vuxu.archive.zsh.users AGPL code for this site: git clone https://public-inbox.org/ public-inbox