From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6248 invoked by alias); 14 May 2017 01:17:07 -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: X-Seq: 22696 Received: (qmail 26512 invoked from network); 14 May 2017 01:17: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.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.28):SA:0(-0.7/5.0):. Processed in 3.891367 secs); 14 May 2017 01:17:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=wXnMPcNMpAKvUyznNo Xxf2934SU4w1vsxZShxbQNOd8=; b=nSpednUC8ZYMQ3pc1SorEECHeu+WRAwnJd 3htPUvQCUchujKGRk+Jdv0uZ758oq0NmmGYYxxa6H7rc+0zv+992EI8Bx65qR0eo Kao0ybaaGqFagyosuYyR4b7teSOCocpD1+PoH8dvSe+CPZbfzTU//7rADtc0TGKJ LR7P5idfTAlF68kz8x0lOCohjCXve4W9GJk+EtPQKH/v1586ELSiWY6LXpusxirJ +HlRfC+EK+SPWfryKAHUoTdXgLuDGDOaBxbvvd+Kq1Di8bMHlssn1kOjnCzCdWkV 1ZAQOKQI7TXeRwySbUD3ToTWb98GkBktLjJPxC0bBkg6ISrHJDDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=wXnMPcNMpAKvUyznNo Xxf2934SU4w1vsxZShxbQNOd8=; b=ebPhWc/9wxhS6fUCI2DBEfFbeWO5wR+Ty2 jyPEzfxP/MzYfG1wAGCGvAzWnt3vyDCJ1iuNNYlwMvkuKm2LC+U1smKUKWH/xDJJ EiSMR/Ok2LFloJLTgRtoux2o/n7gcw7+aF7iYgwHwiMOWkiEqsf8SzfGVFlAUPib Mrvs5ThPVcQ2rvRWLVmZgD8Ho/CvZu0KgWiYFZkP3c0oZwl7VlzU/5s4Rmvu7pro Umrkv2c3LKGThogMFGrkDiO8LxZcganOozEQY1+nvHeLs+4WCBXb3YEGsCY7unTH tVCB7IBE60GRdJ5TT/BdyjWyDyI5Ewo+Lm/hmUV0GxEAUE5OawFA== X-ME-Sender: X-Sasl-enc: IbSuV1qXHL+3yAu7cp9LacC+hsTiXTojhpHpCTYInpcc 1494723886 Date: Sun, 14 May 2017 01:04:44 +0000 From: Daniel Shahaf To: zsh-users@zsh.org Subject: Re: declare -p and -H (hideval) Message-ID: <20170514010444.GA4046@fujitsu.shahaf.local2> References: <170512150302.ZM9904@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <170512150302.ZM9904@torch.brasslantern.com> User-Agent: Mutt/1.5.23 (2014-03-12) Bart Schaefer wrote on Fri, May 12, 2017 at 15:03:02 -0700: > On May 12, 6:21pm, Sebastian Gniazdowski wrote: > } > } I use "declare -p" there, when user selects a parameter. No value is > } being shown for -H parameters. Is this correct? > > Yes. Manual for -p option says: > > If the -p option is given, parameters and values are printed > in the form of a typeset command with an assignment, > regardless of other flags and options. Note that the -H flag > on parameters is respected; no value will be shown for these > parameters. > > This takes precedence over the -m flag, etc. The fact remains that the "does not apply" clause that Sebastian quoted does not match the implementation. The question is just which of them should be fixed to match the other. (Code archeology may answer this, but I'm not going to do it tonight.) > } Any way to avoid -H effects with typeset -p? > > It would appear not.