Closed
Bug 131633
Opened 23 years ago
Closed 22 years ago
pressing tab key after typing # should complete current channel name
Categories
(Other Applications Graveyard :: ChatZilla, enhancement)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gwalla, Assigned: bugzilla-mozilla-20000923)
Details
Attachments
(1 file, 2 obsolete files)
2.44 KB,
patch
|
Details | Diff | Splinter Review |
In mIRC, you can type # and hit tab to insert the name of the current channel.
It can be quite useful.
Assignee | ||
Comment 1•22 years ago
|
||
I would also like to have all the channels for the current network to be
tab-completable, maybe even all the channel open on all the networks...
Assignee | ||
Comment 3•22 years ago
|
||
Ok, first go - this patch should add the ability to tab complete any channel on
the network/server you're currently viewing, in adition to the nicknames in the
current channel.
Assignee | ||
Comment 4•22 years ago
|
||
Taking properly - damn Bugzilla and it's odd options.
Assignee: rginda → twpol
Status: ASSIGNED → NEW
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 5•22 years ago
|
||
James: do you mean it'll tab-complete any channel you're joined to on a single
server? Because tab-completing any channel on the server would require a LIST
query, which would be an awful lot of overhead for one tab-completion.
Assignee | ||
Comment 6•22 years ago
|
||
Ok, I'll just clear up what the patch does (I've been asked about this on IRC too).
The patch modifies the routine that generates the list of tab-completion
choices. What it does is include the list of known users (in the channel, or
network as appropriate) and the list of known channels on the network.
This means that, like the nickname-completion, you can only tab-complete
channels you have been in, though you don't need to still be in them. This list
is seperate for each server, and is (I think) reset when you connect to the server.
In short, the patch only uses the existing information in the ChatZilla object
model to build the tab-completion list - there is no network activity. HTH.
Reporter | ||
Comment 7•22 years ago
|
||
I see. I still have to ask, however, if it addresses the issue in this bug's
summary: can the user type # <tab> to get the channelname of the current channel
tab?
Assignee | ||
Comment 8•22 years ago
|
||
Yes, the current channel will be one of the channels in the list. I thought it
would be nice (i.e. more consitent) if it had all the channels you were in on
the current server.
If you really only want the current channel tab-completable, or want anything
special (e.g. #c<tab> completes channels begining with c, but #<tab> always
fills in the current channel, even if there are other options) feel free to say.
Reporter | ||
Comment 9•22 years ago
|
||
> Yes, the current channel will be one of the channels in the list.
Yes, I figured as much.
> I thought it
> would be nice (i.e. more consitent) if it had all the channels you were in on
> the current server.
It would.
> If you really only want the current channel tab-completable,
I didn't mean to say that it should be *restricted* to that.
> or want
> anything special (e.g. #c<tab> completes channels begining with c, but #<tab>
> always fills in the current channel, even if there are other options) feel
> free to say.
#<tab> always completing the current channel even when there are other options
is the behavior this feature request was opened for. I think it's the
bare-minimum behavior, although being able to tab-complete other partly-typed
channels would be a convenient extra.
Assignee | ||
Comment 10•22 years ago
|
||
Ok, I'll do an updated patch to make #<tab> complete to the current channel name
irrespective of the other options (though the others will still be there, and
will be used if you've got anything after the #).
Assignee | ||
Comment 11•22 years ago
|
||
Changes the code to explictly cope with #<tab> by completing to the current
channel name, if there is one. If not, works like a normal tab-complete.
Attachment #110319 -
Attachment is obsolete: true
Reporter | ||
Comment 12•22 years ago
|
||
Great! Thank you.
Comment 13•22 years ago
|
||
Thanks for the patch. I edited it slightly and have included it in
0.8.12-pre8. Have a look a this attachment for the edits, nothing too severe.
Attachment #110418 -
Attachment is obsolete: true
Comment 14•22 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Other Applications
Updated•15 days ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•