> On 15/12/2021 03:53, Kalyan Sriram wrote:
> > Improve show buffer numbers on "/buffer" command. Checks completion
> > against list of commands to avoid ambigious "/b" matching ("BUFFER" v.
> > "BAN"). Matches uppercase and mixed case i.e. "/BU" or "/bU".
> I see, thanks for the patch. While I don't use neither buffer numbers
> nor /buffer myself, I expect typing "/b <number>" be the common
> practice, and this patch breaks it? What do you think?
Yes, typing /b is the common practice but unfortunately doesn't
currently work since the "BAN" command was introduced. /b brings up the
numbers, but once the user presses enter, the command complains saying
"b" is ambigious. Hence I thought this would be the least intrusive way
to fix that. What do you think? Is there a better way to address this?