Open Bug 429256 Opened 12 years ago Updated 7 years ago

Implement option for cycling tab auto-complete

Categories

(Other Applications :: ChatZilla, enhancement)

enhancement
Not set

Tracking

(Not tracked)

People

(Reporter: s.barnes, Assigned: rginda)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: ChatZilla 0.9.81 [Firefox 3.0b5/2008032620]

When typing the string "Ke" and hitting tab twice ChatZilla minimises the text entered and offers nickname matches of "[INFO] 4 matches for “ke”: [kevinsbot`, Kev, Kevin`, kelvin911]" when only 2 are suitable.

A check box in Preferences to "Match nickname case for tab auto-complete" or "Preserve nickname case for tab auto-complete" would be useful.

Reproducible: Always

Steps to Reproduce:
1. Enter initial characters to a nick that exists in channel in both lower/upper case format.
2. Press <tab> twice.
3. Behold results offered as "matching".
4. Grumble at having to type extra-long crypto nick manually.


Expected Results:  
Preserved the case of the string entered. If I say "Ke" I mean "Ke" not "ke".
The tab-completion code uses the same case-comparisons as IRC itself (it varies a little between servers, but a-z are always the same as A-Z). Being able to ignore what case the nickname is in when typing is amazingly useful.

I don't really like the idea of an option for this.
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
(In reply to comment #1)
> The tab-completion code uses the same case-comparisons as IRC itself (it varies
> a little between servers, but a-z are always the same as A-Z). Being able to
> ignore what case the nickname is in when typing is amazingly useful.
> 
> I don't really like the idea of an option for this.
> 

Me neither. We could probably simply keep the case of what the user typed until we fully completed the nickname, though. That seems to be at least part of the bugreport. It wouldn't really change any of the matching, obviously - but it would maybe disturb users less.
I'm not sure if it'd be less disturbing actually, as it uses the first of the list of matches for the substitution; having it keep your bit in your case and add a bit in a potentially different case, which results in something that may not match any possibility (in case) might be pretty weird too.
I agree with James, on this. Changing tab-completion behaviour to preserve case would be jarring, to say the least.
Just to clarify my perception on this one, take for example 2 nickname's
"Kevin`" and "kevinsbot`". In the current implementation of nick tab
auto-complete, there is no way for me to tab-match "Kevin`". I have to type it
in full each time. If I enter "Ke" and hit <tab>, the text is lower-cased
automatically, <tab> a second time offers me "[INFO]     2 matches for
“kevin”: [kevinsbot`, Kevin`]" so in this particular instance, tab
auto-complete fails to assist.

Not throwing my toys out of the pram, just making sure i've given you guys
enough info to help you to achieve the most functional design.
I think you'd be better served by a rotation tab-complete (where it completes to one entire nick, and subsequent tabs cycle through the list) than trying to do anything with the case typed. (I thought we had an open bug on adding that, but I can't find it.)

I'm not sure which style users actually prefer, alas. :(
(In reply to comment #6)
> I think you'd be better served by a rotation tab-complete (where it completes
> to one entire nick, and subsequent tabs cycle through the list) than trying to
> do anything with the case typed. (I thought we had an open bug on adding that,
> but I can't find it.)
> 
> I'm not sure which style users actually prefer, alas. :(
> 

I definitely prefer the current style, but we can morph this bug, to add the other style and a pref, if you want. I could imagine others might prefer the style you describe.
Morphing + confirming per comment #7. Also, bug 419137 comment 1 says it needs this bug. Fixing that.
Blocks: 419137
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Tab auto-complete for nicknames does not preserve case. → Implement option for cycling tab auto-complete
Does this tab completion differ in Thunderbird? I don't get a list of matching nicks when I press tab twice. First tab completes to first matching nick and second tab does nothing.
No, ChatZilla behaves the same in all hosts.
You need to log in before you can comment on or make changes to this bug.