Better error-message in case of "index out of range", mentioning the actual index which was out of range. Also, use the same error-code, because the underlying cause is all the same.

1 files changed, 5 insertions, 5 deletions

diff --git a/tests/lsearch.test b/tests/lsearch.test
index e401581..b188924 100644
--- a/tests/lsearch.test
+++ b/tests/lsearch.test
@@ -432,19 +432,19 @@ test lsearch-17.11 {lsearch -index option, empty argument} {
 } [lsearch [list \{] \{]
 test lsearch-17.12 {lsearch -index option, encoding aliasing} -body {
     lsearch -index -2 a a
-} -returnCodes error -result {index "-2" cannot select an element from any list}
+} -returnCodes error -result {index "-2" out of range}
 test lsearch-17.13 {lsearch -index option, encoding aliasing} -body {
     lsearch -index -1-1 a a
-} -returnCodes error -result {index "-1-1" cannot select an element from any list}
+} -returnCodes error -result {index "-1-1" out of range}
 test lsearch-17.14 {lsearch -index option, encoding aliasing} -body {
     lsearch -index end--1 a a
-} -returnCodes error -result {index "end--1" cannot select an element from any list}
+} -returnCodes error -result {index "end--1" out of range}
 test lsearch-17.15 {lsearch -index option, encoding aliasing} -body {
     lsearch -index end+1 a a
-} -returnCodes error -result {index "end+1" cannot select an element from any list}
+} -returnCodes error -result {index "end+1" out of range}
 test lsearch-17.16 {lsearch -index option, encoding aliasing} -body {
     lsearch -index end+2 a a
-} -returnCodes error -result {index "end+2" cannot select an element from any list}
+} -returnCodes error -result {index "end+2" out of range}
 
 
 test lsearch-18.1 {lsearch -index option, list as index basic functionality} {