From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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.4 Received: (qmail 22578 invoked from network); 30 Jul 2020 04:31:13 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 30 Jul 2020 04:31:13 -0000 Received: (qmail 16859 invoked by alias); 30 Jul 2020 04:31:07 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46287 Received: (qmail 20794 invoked by uid 1010); 30 Jul 2020 04:31:07 -0000 X-Qmail-Scanner-Diagnostics: from out4-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25884. spamassassin: 3.4.4. Clear:RC:0(66.111.4.28):SA:0(-2.6/5.0):. Processed in 6.418912 secs); 30 Jul 2020 04:31:07 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrieehgdejtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfffgrnhhivghlucfuhhgrhhgrfhdfuceougdrshesuggr nhhivghlrdhshhgrhhgrfhdrnhgrmhgvqeenucggtffrrghtthgvrhhnpeefhfekfeevie elleehiefftdekudejledvhfdtjedtgeegvdeuffefleehhfdvgfenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghnihgvlhdrsh hhrghhrghfrdhnrghmvg X-ME-Proxy: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-128-gd51a832-fm-20200728.001-gd51a8328 Mime-Version: 1.0 Message-Id: In-Reply-To: <1e250159-b06f-ad39-0cef-e27c5fefa89a@gmx.com> References: <271b648e-9c30-3333-cfca-dedf8df9e248@barella.org> <45badc15-202a-72f6-a87a-ee058283279e@gmx.com> <20200729230756.48e8c61d@tarpaulin.shahaf.local2> <1e250159-b06f-ad39-0cef-e27c5fefa89a@gmx.com> Date: Thu, 30 Jul 2020 04:30:03 +0000 From: "Daniel Shahaf" To: "Eric Cook" , zsh-workers@zsh.org Subject: Re: zsh: corrupt history file Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Eric Cook wrote on Thu, 30 Jul 2020 03:56 +00:00: > On 7/29/20 7:07 PM, Daniel Shahaf wrote: > > I guess you mean adding such warnings to zshparam(1)? In which case= , > > perhaps adding them to bin_typeset() would be more effective? As in= : > > > > % export HISTORY=3Dfoo > > zsh:1: warning: $HISTORY should not be exported; use 'typeset HISTOR= Y=3Dfoo' instead > > > > (and if someone actually needs to export $HISTORY for whatever reaso= n, > > we can make -h suppress the warning) > > That is indeed what i meant, but your solution has two problems in the= > example of PS1. if it is in the environment when zsh starts and the > user doesn't set it, you experience the issue of another shell's > escape sequences being used that typeset won't warn of since it isn't > being used. What I proposed would address the issue of zsh exporting $PS1 and some other shell then using zsh's value (e.g., =C2=ABexport PS1=3D'%# '; dash= =C2=BB). What you're describing is the converse problem and would need to be fixed separately. > the second issue being software like python's virtualenv > being written under the assumption that exporting PS1 won't cause an > warning message in the shells their activation script is written for, > would need to now account for that. Isn't that a bug in their code that they should fix? PS1 shouldn't be e= xported. Incidentally, if they do the equivalent of =C2=ABenv PS1=3Dfoo zsh=C2=BB= , then they won't be affected because that doesn't go through bin_typeset() in the first place. They'd only be affected if they somehow cause the 'export'= or 'typeset' builtins to be executed (e.g., by setting up their own $ZDOTDIR). > I know i have offered critiques yet no solutions, but i don't think > either of the suggestions is ideal personally.