[SOLVED] Bash Random Keys

PTrenholme · 08-19-2013, 10:14 PM

Did you read my post #7, above?

I thought I'd explained (and shown you an example - and function) that did what I think your Python code accomplishes.

At the risk of the pun police calling, "The key is in the indirection operator!"

grail · 08-20-2013, 12:29 AM

I am with PT ... I do follow the python example but believe his solution provided the same result.

Are you having issues when using that example?

Lucien Lachance · 08-20-2013, 09:07 AM

I've got it, I had to adjust it without using shuf because I don't have that command, after reading a post I realized it wasn't too much to rework. Thanks for the help. How did you come up with that logic?

grail · 08-20-2013, 10:19 AM

Quote:

I had to adjust it without using shuf because I don't have that command

Well that is a little weird as it is a part of the coreutils package, which is pretty standard on most distros, at least that I have used (which is a few

)

Quote:

How did you come up with that logic?

Can't obviously speak for PT as the author, but essentially you told us the logic with your python example.

As an alternative to shuf you could combine min86's suggestion with PT's script to get:

Code:

#!/bin/bash

declare -A moves
moves=(['r']="rock" ['p']="paper" ['s']="scissors")
tmp=(${!moves[*]})

for ((i=0;i<10;++i))
do
	key=${tmp[RANDOM % ${#tmp[*]}]}
	echo key=${key}
	echo "move ${i} = ${moves[${key}]}"
done

PTrenholme · 08-20-2013, 04:12 PM

Quote:

Originally Posted by Lucien Lachance

[...]How did you come up with that logic?

Well, the usual way: I read the info file.

The function was written because I thought you would, perhaps, be using it for several different arrays.

Lucien Lachance · 08-20-2013, 04:51 PM

I wish the man pages weren't always so terse, I have to get the hang of that still. Most of the time I know, or have an idea of how it needs to be solved and go from there. Do you usually know where to begin looking in the docs, or does it usually take you awhile to figure things out? I hope this makes sense..

PTrenholme · 08-21-2013, 09:31 AM

The man pages are intentionally terse. They are supposed to be used to "remind" command users about things they seldom use. The info files are (usually) more complete, often with examples. (If you have the pinfo command installed, it makes using the info system much easier and intuitive.)

Lucien Lachance · 08-21-2013, 07:40 PM

I see, I found this helpful link as well concerning lower case and upper case submissions: http://mintaka.sdsu.edu/GF/bibliog/l...bian/bash.html
Really puts things into perspective, I had always thought using tr, awk, or perl were the only ways of achieving this. Thank you pointing out that bash could handle this problem natively @grail.