zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: var=$( typeset "$1" ) ... not within a function.
Date: Thu, 20 Oct 2022 18:58:31 -0700	[thread overview]
Message-ID: <530b18d0-5e72-6afd-7448-cdff9c119bda@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7auK9J5y=Eag1k5rOz=zys6n4GnfM_+mYpYLmXWoMdNPQ@mail.gmail.com>


On 2022-10-20 17:54, Bart Schaefer wrote:
> Yes, it's unfortunate that typeset (without options) was ever given
> the function you describe as "passive reporter".  Worse that it's
> synonym "declare" behaves the same.

Prowling around in the parameters there's lots of little mysteries,

  $ typeset -mp CDPATH
typeset -T CDPATH cdpath=(  )

... but the same command from within a script or function gives:

typeset -g -T CDPATH cdpath=(  )

... and if I scan the entire output of "$ typeset -p" and look for 
'CDPATH' I get:

typeset -T CDPATH cdpath=(  )
typeset -aT CDPATH cdpath=(  )

... and from within a function the '-g' is added.

typeset -g -T CDPATH cdpath=(  )
typeset -g -aT CDPATH cdpath=(  )

... what's the truth of the matter with CDPATH?  And how in hell can 
there be two of them?

I get the feeling that this whole neck of the woods hasn't been given a 
housecleaning since ENIAC, it's just always been this way and probably 
has to stay this way due to the ancientness of the tradition.  Probably 
goes back to sh 0.1

... and while I'm whining I notice that 'set' never does anything like: 
"CDPATH cdpath", it puts them on separate lines.  Dunno, couldn't they 
have separate values?






  reply	other threads:[~2022-10-21  1:59 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 17:21 Ray Andrews
2022-10-20 17:25 ` Roman Perepelitsa
2022-10-20 17:51   ` Ray Andrews
2022-10-20 17:54     ` Roman Perepelitsa
2022-10-20 18:38       ` Ray Andrews
2022-10-20 18:44         ` Roman Perepelitsa
2022-10-20 19:15           ` Ray Andrews
2022-10-20 19:35             ` Roman Perepelitsa
2022-10-20 20:48               ` Ray Andrews
2022-10-21  0:54                 ` Bart Schaefer
2022-10-21  1:58                   ` Ray Andrews [this message]
2022-10-21  2:25                     ` Bart Schaefer
2022-10-21 14:24                       ` Ray Andrews
2022-10-21 14:37                         ` Ray Andrews
2022-10-21 17:34                         ` Roman Perepelitsa
2022-11-01  5:00                       ` "typeset -p" inconsistency Bart Schaefer
2022-11-01 12:07                         ` Peter Stephenson
2022-11-01 12:40                         ` Ray Andrews
2022-11-01 19:08                           ` Bart Schaefer
2022-11-01 21:25                             ` Ray Andrews
2022-11-01 21:40                               ` Bart Schaefer
2022-11-01 22:46                                 ` Ray Andrews
2022-11-02  1:13                                   ` Lawrence Velázquez
2022-11-02  2:42                                     ` Ray Andrews
2022-11-02  3:11                                       ` Lawrence Velázquez
2022-11-02 12:56                                         ` Ray Andrews
2022-11-02 17:04                                           ` Bart Schaefer
2022-11-02 17:19                                             ` Ray Andrews
2022-11-02 18:21                                               ` Bart Schaefer
2022-11-02  3:10                                   ` Bart Schaefer
2022-11-02 17:09                                     ` Ray Andrews
2022-10-20 17:29 ` var=$( typeset "$1" ) ... not within a function Mikael Magnusson
2022-10-20 17:43   ` Ray Andrews
2022-10-21 17:33 ` Ray Andrews
2022-10-21 18:25   ` Bart Schaefer
2022-10-21 18:57     ` Ray Andrews
2022-10-21 19:02       ` Roman Perepelitsa
2022-10-21 19:06         ` Ray Andrews
2022-10-21 19:04     ` Ray Andrews

Reply instructions:

You may reply publicly 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 \
    --in-reply-to=530b18d0-5e72-6afd-7448-cdff9c119bda@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).