From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=BODY_URI_ONLY, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 3a27d514 for ; Wed, 18 Sep 2019 16:07:22 +0000 (UTC) Received: (qmail 1440 invoked by alias); 18 Sep 2019 16:07:11 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24251 Received: (qmail 21853 invoked by uid 1010); 18 Sep 2019 16:07:11 -0000 X-Qmail-Scanner-Diagnostics: from mta01.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25573. spamassassin: 3.4.2. Clear:RC:0(24.224.136.30):SA:0(-2.6/5.0):. Processed in 2.481811 secs); 18 Sep 2019 16:07:11 -0000 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.eastlink.ca designates 24.224.136.30 as permitted sender) X-Authority-Analysis: v=2.3 cv=CfF2G4jl c=1 sm=1 tr=0 a=zv49KfEsxEDzuN5AGO7r0Q==:117 a=zv49KfEsxEDzuN5AGO7r0Q==:17 a=Nz0KCS2TAAAA:8 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=AnB_g7jWAAAA:8 a=hvzVGeBNHT_JHDFcUOIA:9 a=QEXdDO2ut3YA:10 a=ZerVIEu0q4xqpvNG3HNs:22 a=881ixuEySykgOP1Ki4DQ:22 X-Vade-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgdeljecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfgtefuvffnkffpmfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeftrgihucetnhgurhgvfihsuceorhgrhigrnhgurhgvfihssegvrghsthhlihhnkhdrtggrqeenucffohhmrghinhepshgtrhhiphhtihhnghhoshigrdgtohhmpdhophgvnhhsohhurhgtvgdrtghomhenucfkphepvdegrddvtdejrdeltddrudelgeenucfrrghrrghmpehinhgvthepvdegrddvtdejrdeltddrudelgedphhgvlhhopegludelvddrudeikedrtddrvdgnpdhmrghilhhfrhhomheprhgrhigrnhgurhgvfihssegvrghsthhlihhnkhdrtggrpdhrtghpthhtohepiihshhdquhhsvghrshesiihshhdrohhrghenucevlhhushhtvghrufhiiigvpedt X-Vade-Score: 0 X-Vade-State: 0 X-EL-IP-NOAUTH: 24.207.90.194 Subject: Re: Opensource.com Zsh article To: zsh-users@zsh.org References: From: Ray Andrews Message-id: Date: Wed, 18 Sep 2019 09:06:32 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-version: 1.0 In-reply-to: Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 8bit Content-language: en-CA On 2019-09-17 5:39 p.m., TJ Luoma wrote: > https://scriptingosx.com/moving-to-zsh/ > > TjL > It astonishes me that the reason for the switch is claimed to be a licensing version detail.  I understand that there's no one left in the cockpit at bash, would that not be a better reason?  Even now I can't quite accept that something as essential to computing as the shell should be treated so casually.  So it's zsh from now on, but even then all this will rest on the shoulders of our few intrepid volunteers?   Dunno, if that's the way the world works then that's the way the world works but it is very strange.  Sorta like going to the local nuclear power plant and finding that there's no  one there but a few volunteers and one day no one will even know how the place works but the city will still be expecting safe, reliable electricity.