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=-1.0 required=5.0 tests=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 493dcc5d for ; Sat, 6 Jul 2019 14:23:50 +0000 (UTC) Received: (qmail 24744 invoked by alias); 6 Jul 2019 14:23:42 -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: 24022 Received: (qmail 3573 invoked by uid 1010); 6 Jul 2019 14:23:42 -0000 X-Qmail-Scanner-Diagnostics: from mta02.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25496. spamassassin: 3.4.2. Clear:RC:0(24.224.136.13):SA:0(-2.6/5.0):. Processed in 1.947033 secs); 06 Jul 2019 14:23:42 -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.13 as permitted sender) X-Authority-Analysis: v=2.3 cv=ApaQI91P c=1 sm=1 tr=0 a=cnjiLCurb0vjRq4CKMedvw==:117 a=cnjiLCurb0vjRq4CKMedvw==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=lNUqkwdUsYVSR9i-d2AA:9 a=QEXdDO2ut3YA:10 X-Vade-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfeeigdejiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfgtefuvffnkffpmfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeftrgihucetnhgurhgvfihsuceorhgrhigrnhgurhgvfihssegvrghsthhlihhnkhdrtggrqeenucfkphepvdegrddvtdejrdduiedrudejgeenucfrrghrrghmpehinhgvthepvdegrddvtdejrdduiedrudejgedphhgvlhhopegludelvddrudeikedrtddrvdgnpdhmrghilhhfrhhomheprhgrhigrnhgurhgvfihssegvrghsthhlihhnkhdrtggrpdhrtghpthhtohepiihshhdquhhsvghrshesiihshhdrohhrghenucevlhhushhtvghrufhiiigvpedt X-Vade-Score: 0 X-Vade-State: 0 X-EL-IP-NOAUTH: 24.207.16.174 Subject: Re: Comprehensive comparison between zsh and bash To: zsh-users@zsh.org References: <7aeeabc8-0375-1793-c8a0-1b3af235f1d0@eastlink.ca> <20190706023105.GA2314@spodhuis.org> From: Ray Andrews Message-id: <469e414f-b728-9cee-91a9-41cae31ac63c@eastlink.ca> Date: Sat, 6 Jul 2019 07:23:03 -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: <20190706023105.GA2314@spodhuis.org> Content-type: text/plain; charset=utf-8; format=flowed Content-transfer-encoding: 8bit Content-language: en-CA On 2019-07-05 7:31 p.m., Phil Pennock wrote: > On 2019-07-05 at 13:29 -0700, Ray Andrews wrote: >> Just curious:  Is there some way of dumping the state of all variables at >> all lines with both bash and zsh to some file or other such that one could >> quickly spot exactly when and where something might change between them? >> Not a proactive, analytic study of the code, but just a pragmatic finding of >> differences after the fact. > `typeset -p` dumps all variables; the format differs slightly between > shells but that's light text-munging to normalize. > > This is probably a good start: > > trap 'typeset -p' DEBUG Thanks Phil and Sebastian.  I have no need for it myself since I've never done a thing in bash, but I was wondering what might be available to converts.  I'll play with your suggestions anyway tho just for fun.  But since all the other shells are moribund it seems to me that zsh should make an effort to draw all shellers to itself and to make room around the fire for them.  It would add to critical mass and maybe spark some innovation.  Maybe there could be some purpose build conversion utilities.