From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Empty element elision and associative arrays (was Re: Slurping a file)
Date: Fri, 19 Jan 2024 09:15:19 -0800 [thread overview]
Message-ID: <6b957d12-4306-4988-83fd-d7b67e42bbea@eastlink.ca> (raw)
In-Reply-To: <CAHYJk3S7VO29br+_2vj5oxankKmOpcFoX6dtB2LDTQENGSO=fA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
On 2024-01-19 08:01, Mikael Magnusson wrote:
> Keys are unique but values aren't, so it's sort of a nonsensical
> request; that said, you can do it ;).
I dunno, you might have some sort of efficiency test and store the
results in an array keyed to the names of the various tests and you want
to see them in the order of best to worst.
I think that for the time being this works for me:
typeset -A array=( [1test_one]=123 [2test_two]=345 [3test_three]=111
[4test_four]=5 )
echo "\nraw"
printf "\n%-20s %s" ${(kv)array}
echo "\n\nsorted on key"
printf "\n%-20s %s" ${(kv)array} | sort
echo "\nsorted on value"
printf "\n%-20s %s" ${(kv)array} | sort -k2
echo "\nsorted on value numerically"
printf "\n%-20s %s" ${(kv)array} | sort -k2g
output:
5 /aWorking/Zsh/Source/Wk 0 % . test2
raw # No recognizable order
1test_one 123
2test_two 345
4test_four 5
3test_three 111
sorted on key # If the array itself won't do it, then make 'sort' do it:
1test_one 123
2test_two 345
3test_three 111
4test_four 5
sorted on value # dictionary sort
3test_three 111
1test_one 123
2test_two 345
4test_four 5
sorted on value numerically # numeric sort
4test_four 5 # This isn't going anywhere.
3test_three 111
1test_one 123
2test_two 345 # Here's the winner, congratulations test_two
team.
... so however much I think there should be a defined order to the way
the arrays print, it seems easy enough to use other tools to do it.
[-- Attachment #2: Type: text/html, Size: 2891 bytes --]
next prev parent reply other threads:[~2024-01-19 17:16 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 19:05 more splitting travails Ray Andrews
2024-01-12 19:19 ` Bart Schaefer
2024-01-12 19:56 ` Ray Andrews
2024-01-12 20:07 ` Mark J. Reed
[not found] ` <CAA=-s3zc5a+PA7draaA=FmXtwU9K8RrHbb70HbQN8MhmuXTYrQ@mail.gmail.com>
2024-01-12 20:03 ` Fwd: " Bart Schaefer
2024-01-12 20:32 ` Ray Andrews
2024-01-12 20:50 ` Roman Perepelitsa
2024-01-13 2:12 ` Ray Andrews
2024-01-12 20:51 ` Bart Schaefer
2024-01-12 21:57 ` Mark J. Reed
2024-01-12 22:09 ` Bart Schaefer
2024-01-13 3:06 ` Ray Andrews
2024-01-13 3:36 ` Ray Andrews
2024-01-13 4:07 ` Bart Schaefer
2024-01-13 5:39 ` Roman Perepelitsa
2024-01-13 20:02 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-13 20:07 ` Slurping a file Ray Andrews
2024-01-14 5:03 ` zcurses mouse delay (not Re: Slurping a file) Bart Schaefer
2024-01-14 5:35 ` Ray Andrews
2024-01-14 10:34 ` Slurping a file (was: more spllitting travails) Roman Perepelitsa
2024-01-14 10:57 ` Roman Perepelitsa
2024-01-14 15:36 ` Slurping a file Ray Andrews
2024-01-14 15:41 ` Roman Perepelitsa
2024-01-14 20:13 ` Lawrence Velázquez
2024-01-15 0:03 ` Ray Andrews
2024-01-15 0:55 ` Empty element elision and associative arrays (was Re: Slurping a file) Bart Schaefer
2024-01-15 4:09 ` Ray Andrews
2024-01-15 7:01 ` Lawrence Velázquez
2024-01-15 14:47 ` Ray Andrews
2024-01-18 16:20 ` Mark J. Reed
2024-01-18 17:22 ` Ray Andrews
2024-01-18 17:36 ` Mark J. Reed
2024-01-18 17:55 ` Ray Andrews
2024-01-18 22:34 ` Bart Schaefer
2024-01-18 23:08 ` Ray Andrews
2024-01-19 2:46 ` Bart Schaefer
2024-01-19 2:58 ` Ray Andrews
2024-01-19 10:27 ` Stephane Chazelas
2024-01-19 13:45 ` Mikael Magnusson
2024-01-19 14:37 ` Mark J. Reed
2024-01-19 14:57 ` Ray Andrews
2024-01-19 15:46 ` Mark J. Reed
2024-01-19 16:01 ` Mikael Magnusson
2024-01-19 17:15 ` Ray Andrews [this message]
2024-01-19 17:42 ` Bart Schaefer
2024-01-19 18:45 ` Ray Andrews
2024-01-14 22:09 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-15 8:53 ` Roman Perepelitsa
2024-01-16 19:57 ` Bart Schaefer
2024-01-16 20:07 ` Slurping a file Ray Andrews
2024-01-16 20:14 ` Roman Perepelitsa
2024-01-16 20:38 ` Ray Andrews
2024-01-16 20:43 ` Roman Perepelitsa
2024-01-16 22:27 ` Ray Andrews
2024-01-15 2:00 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-15 4:24 ` Slurping a file Ray Andrews
2024-01-15 6:56 ` Lawrence Velázquez
2024-01-15 14:37 ` Ray Andrews
2024-01-15 15:10 ` Marc Chantreux
2024-01-15 15:29 ` Mark J. Reed
2024-01-15 16:16 ` Marc Chantreux
2024-01-15 16:33 ` MUAs (was: Re: Slurping a file) zeurkous
2024-01-16 7:23 ` Slurping a file Lawrence Velázquez
2024-01-16 14:37 ` Ray Andrews
2024-01-17 3:50 ` Lawrence Velázquez
2024-01-17 5:10 ` Ray Andrews
2024-01-15 7:26 ` Slurping a file (was: more spllitting travails) Lawrence Velázquez
2024-01-15 14:48 ` Slurping a file Ray Andrews
2024-01-15 13:13 ` Slurping a file (was: more spllitting travails) Marc Chantreux
2024-02-10 20:48 ` Stephane Chazelas
2024-02-11 0:59 ` Mikael Magnusson
2024-02-11 4:49 ` Bart Schaefer
2024-02-11 5:04 ` Mikael Magnusson
2024-02-11 4:46 ` Bart Schaefer
2024-02-11 5:06 ` Mikael Magnusson
2024-02-11 7:09 ` Stephane Chazelas
2024-01-13 2:19 ` Fwd: more splitting travails Ray Andrews
2024-01-13 3:59 ` Bart Schaefer
2024-01-13 4:54 ` Ray Andrews
2024-01-13 5:51 ` Roman Perepelitsa
2024-01-13 16:40 ` Ray Andrews
2024-01-13 18:22 ` Bart Schaefer
2024-01-13 19:08 ` 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=6b957d12-4306-4988-83fd-d7b67e42bbea@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).