Hm... I think I know what code you're talking about.
Though, I have to ask you to elaborate a bit. Technically, all you need to compare a keypress to a list is to type "getkey→K:K=<insert a list here>".

So, because of that, I need to know something like what you'll use this for then I can probably give you example code for that and explain it, if need be.

Well, for that, it'd just be...

Repeat sum(getKey={24,25,26,34
End

For example, if getKey was 25 the "getkey={24,25,26,34" part would output "{0,1,0,0}" then the "sum(" would add the elements together to equal "1" or "TRUE".

If it was cumSum then it'd output "{0,1,1,1}" in the end, which isn't a boolean as required by the Repeat function.

Haha, no problem!

I'm pretty rusty myself.
Had to actually test it on my calc first just to make sure I gave you the right information. ^^

(And I'm not sure that it's the fastest... but it's a hell of a lot faster and smaller than typing out "getKey=#" for each on you want to check. =P )

Remember that if you want to use the keypress you'd need to do this:

Repeat max(Ans={24,25,26,34
getKey->K //You don't need to store it to K, but I usually do.
End

@Ztrumpet, well yea that should go without saying. Funfact: The convention of using K for getkey started because that was what the example in TI's manual used. The same goes for using the variable I as the default variable in For loops. 

@Silver Shadow:Great! It's a quick and simple way to do it. =D

Funfact: The convention of using K for getkey started because that was what the example in TI's manual used.

Really? I just used it because to me K = Keypress. I do that with variables a lot. Like Position in a menu = M or any temporary variable = X.
In fact... I never even read the TI manual. =D

Though, you're probably right for the most part. I'm always a weird exception it seems. =P

Alot of us (way back in the day) used the thick paperback manuals that TI used to include with their products as a stating point for programming and as a reference. Many people learned from looking at others code, and as time passed people wrote their own tutorials and used what they were familiar with as reference. Thus certain conventions were established regardless of them having any relevance. Although, I suppose "K" for key does actually make sense. I just find it interesting that some of these things have largely stayed the same since about 98/99.