Warp Autoname completion

[Former user]

So, you used to just be able to do for example /warp kur to warp to kuraicho, problems of course arose if there were two warps beginning with given string, however someone has clearly updated this functionality, so now it gives a nice little not saying Multiple warp matches found and then even shows which bit (apparently) intersect in red.

Unfortunately, said person has clearly missed a 1 for a 2 or something, because even when there is only one warp matching string, and it even only displays one, it thinks there are multiple.

Even so, when the are more matches (i.e. /warp new) it does seem to work well, so nice work whoever did it.

[Riot]

because even when there is only one warp matching string, and it even only displays one, it thinks there are multiple.

That's a wonderful essay you've written.

But do you want to try just telling me:

1. Exactly what you typed,
2. Exactly what you expected to see,
3. Exactly what you saw instead

This is the formula for all successful bug reports, and no matter how flowery your writeup is otherwise, without these three basic pieces of info, it's totally useless to me.

[Former user]

Ok, so for example, when I type /warp vizim , I hope to be warped to vizima, as it is obviously the only warp with vizim in the name. Instead, it tells me that there are more than one warp with that in the string, even though there's only one. Even so, if there ARE more than one with the string - i.e. /warp new , it gives the correct output, saying there are multiple warps with that in the name.

So basically it doesn't realise when there is only one warp possible with partial name completion.

[Riot]

So to rephrase this long-winded thing into my nice simple bullet points:

1. Type /warp vizim
2. Expect to find warp vizima
3. Instead see more than one result

Was that really so hard??

[Riot]

removing newline stripping that was causing single results to count as zero lines, and hence fail the == 1 check. Resolves #198

→ <<cset 772ca3b445d7>>