If your expectation wasn't to display the message with this
function, then perhaps it's better to not make it equivalent to
display-message, but try to display a more appropriate error message
instead.
This is exactly what I meant. I think it would be best to not make it
equivalent to display-message in the index.
Personally, I see a couple of possible solutions for select-message in index:
1. If bound for index or a binding that contains the index, display an
error message on mutt start, about the function not being available in
index.
2. Keep allowing it in binds for index/that include index, but when
the key is pressed, show an error message in mutt that the function
isn't available for this menu.
3. Make it equivalent to tag-message. To me, this makes the most
sense, as I can't speak for everyone but, looking at the function
names, I'd expect select-message to do what tag-message does, while
I'd expect tag-message to do what edit-label does.
Best Regards,
IFo Hancroft
