From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Ray Andrews" <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: uninvited members of associative array
Date: Thu, 15 Dec 2022 19:05:12 -0500 [thread overview]
Message-ID: <b63cd138-fc96-4c4b-b6dd-49205652363a@app.fastmail.com> (raw)
In-Reply-To: <e2358c69-b70f-8ed7-ce91-218e65a0189f@eastlink.ca>
On Thu, Dec 15, 2022, at 6:48 PM, Ray Andrews wrote:
> I just noticed something. My big array has ten named elements but if I
> print it:
>
> printf "%-20s %s\n" ${(kv)main} > /dev/pts/2
>
> width 90
> window main
> offset 0
> topE 1
> active 1
> 90 main
> bottomE 48
> lastE 196
> hight 48
> 196 48
> List 1
> 0 1
> list List
> 1 48
> currentE 1
>
> ... it all works, however 'elements' 90, 196, 0 and 1 seem to have
> created themselves, I didn't make them.
How are you creating and populating "main"? Can you provide a test
case that the rest of us can actually use? If I just guess the
contents of "main" then I don't see a problem.
% cat foo.zsh
typeset -A main
main=(
active 1
bottomE 48
currentE 1
height 48
lastE 196
list 1
offset 0
topE 1
width 90
window main
)
typeset -p main
printf '%-20s %s\n' ${(kv)main}
% zsh -f foo.zsh
typeset -A main=( [active]=1 [bottomE]=48 [currentE]=1 [height]=48 [lastE]=196 [list]=1 [offset]=0 [topE]=1 [width]=90 [window]=main )
window main
width 90
offset 0
topE 1
height 48
active 1
lastE 196
bottomE 48
list 1
currentE 1
--
vq
next prev parent reply other threads:[~2022-12-16 0:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 23:48 Ray Andrews
2022-12-16 0:05 ` Lawrence Velázquez [this message]
2022-12-16 0:48 ` Ray Andrews
2022-12-16 1:29 ` Lawrence Velázquez
2022-12-16 2:09 ` Dominik Vogt
2022-12-16 2:56 ` Ray Andrews
2022-12-16 3:21 ` Lawrence Velázquez
2022-12-16 4:16 ` Ray Andrews
2022-12-16 10:05 ` Dominik Vogt
2022-12-16 14:13 ` Ray Andrews
2022-12-16 15:19 ` Dominik Vogt
2022-12-16 19:14 ` Ray Andrews
2022-12-16 16:30 ` Daniel Shahaf
2022-12-16 18:21 ` Ray Andrews
2022-12-16 19:04 ` Dominik Vogt
2022-12-16 20:10 ` Ray Andrews
2022-12-16 21:15 ` Dominik Vogt
2022-12-16 21:33 ` Bart Schaefer
2022-12-16 21:59 ` Dominik Vogt
2022-12-16 22:15 ` Bart Schaefer
2022-12-16 23:33 ` Ray Andrews
2022-12-17 12:47 ` Pier Paolo Grassi
2022-12-17 17:32 ` Ray Andrews
2022-12-17 18:10 ` Ray Andrews
2022-12-17 18:19 ` Roman Perepelitsa
2022-12-17 20:31 ` Ray Andrews
2022-12-17 20:49 ` Bart Schaefer
2022-12-17 21:07 ` Lawrence Velázquez
2022-12-17 21:52 ` Ray Andrews
2022-12-17 22:10 ` Bart Schaefer
2022-12-17 23:41 ` Daniel Shahaf
2022-12-18 0:15 ` Ray Andrews
2022-12-18 0:25 ` Daniel Shahaf
2022-12-18 2:13 ` Ray Andrews
2022-12-18 20:12 ` Daniel Shahaf
2022-12-18 20:26 ` Bart Schaefer
2022-12-18 20:41 ` Ray Andrews
2022-12-18 3:44 ` Lawrence Velázquez
2022-12-17 23:25 ` Daniel Shahaf
2022-12-16 21:33 ` Ray Andrews
2022-12-16 20:25 ` Daniel Shahaf
2022-12-16 21:43 ` Dominik Vogt
2022-12-16 3:20 ` Bart Schaefer
2022-12-16 4:15 ` Ray Andrews
2022-12-16 8:12 ` Roman Perepelitsa
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=b63cd138-fc96-4c4b-b6dd-49205652363a@app.fastmail.com \
--to=larryv@zsh.org \
--cc=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).