Tab completion should show list of possible matches
The current tab completion approach (tab cycles through one nick at a time) is not easily discoverable nor very efficient for the user.
I didn't know it even existed until someone told me. I thought it just completed the first match.
When on a channel with a large number of users, tab completion is often the way I discover if someone is currently connected. With the current design, I have to tab through to where they nick I'm looking for would fall alphabetically to know.
It would be much clearer for the user if when there was a tab completion with multiple possibilities a list would pop up that the user could tab through. Bonus points for nicks that were recently speaking in the channel to come first.
For reference, this is the way Konversation works by default and I find it much more intuitive to use and more easily discoverable for the new user.
#1 Updated by Sputnick over 11 years ago
#3 Updated by valuial almost 11 years ago
Would it be possible to add:
- bash like Nick completion (as an option) i.e. complete as far as possible for all solutions, then echo possible completions to the current buffer?
- completion of filesystem (folders filees), when the "word" starts with a /, instead of nicks?
/etc/portage/packages (+list possible files/folders in bash completion style or whatever style the user chose)
#4 Updated by Ycros almost 11 years ago
I don't like the idea of bash-style completion for nicknames. I much prefer the irssi way of tab completion where it simply cycles through MRU nicks. Displaying possible matches is fine by me, I don't really care if they're displayed or not.
I find it really useful, when holding a conversation in a large channel in the middle of other conversations to be able to just type one or two letters and let MRU take care of it, first go. I wouldn't like to wade through several letter-tab-letter-tab-letter cycles for each of my messages.
#6 Updated by rikai about 8 years ago
The way it currently works is the default way used in most popular irc clients and is the expected behavior.
If alternative methods such as those outlined above are going to be added, i suggest making it a choice in the configuration and defaulting to the current functionality.