Closed
Bug 899821
Opened 13 years ago
Closed 1 year ago
Add $(tab) keyword to Chatzilla alias syntax to capture all tab types
Categories
(Other Applications Graveyard :: ChatZilla, enhancement)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: will.pittenger1+mozbugzilla, Assigned: rginda)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212
Steps to reproduce:
Sometimes it might be handy to have a keyword that represents the current tab name. $(tab) perhaps. $(network) would evaluate to the name of the current network even if the network tab isn't current. Some discussion would be needed as to whether $(tab) would output the entire url or just the literal channel name for a channel.
| Reporter | ||
Updated•13 years ago
|
Severity: normal → enhancement
From the FAQ:
$(recip) - Gets the name of the target of the alias. This is the name of the view the alias is run on, e.g. channel name.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Comment 2•13 years ago
|
||
(In reply to Mardeg from comment #1)
> From the FAQ:
> $(recip) - Gets the name of the target of the alias. This is the name of the
> view the alias is run on, e.g. channel name.
Yes, but:
- AFAIK there's no easy way to get the network name from a query or channel tab
- $(recip) gives an error in a client or network tab, so there's no general way to access the "tab name", which may be:
- "*client*" in the client tab
- the network name (e.g. "moznet") in a network tab
- the nick being talked to (e.g. "NickServ", or maybe "NickServ,isnick") in a query tab
- the channel name (e.g. "#chatzilla") in a channel tab.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: WORKSFORME → ---
(In reply to Tony Mechelynck [:tonymec] from comment #2)
> - AFAIK there's no easy way to get the network name from a query or channel
> tab
> - $(recip) gives an error in a client or network tab, so there's no general
> way to access the "tab name", which may be:
> - "*client*" in the client tab
> - the network name (e.g. "moznet") in a network tab
The *client* tab wasn't mentioned in comment 0, and bug 899844 has already been filed for $(network)/$(server)
Please file a separate bug for either $(client) or a general way for any tab.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → WORKSFORME
Comment 4•13 years ago
|
||
(In reply to Mardeg from comment #3)
> The *client* tab wasn't mentioned in comment 0, and bug 899844 has already
> been filed for $(network)/$(server)
> Please file a separate bug for either $(client) or a general way for any tab.
Comment #0 mentioned "the current tab name" (and later on special-cased channel tabs), I just elaborated on that.
Resolution: WORKSFORME → FIXED
Updated•13 years ago
|
Resolution: FIXED → WORKSFORME
Re-opening this just for $(tab)
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Add keyword to Chatzilla alias syntax to allow it to include the channel name → Add $(tab) keyword to Chatzilla alias syntax to capture all tab types
Comment 6•13 years ago
|
||
FWIW, I'm happy to either fix $(recip) to work on all tabs (slightly surprised it doesn't) or add a new alias expansion for the name of the current tab (and one for URL perhaps while we're here).
Comment 7•13 years ago
|
||
(In reply to James Ross from comment #6)
> FWIW, I'm happy to either fix $(recip) to work on all tabs (slightly
> surprised it doesn't) or add a new alias expansion for the name of the
> current tab (and one for URL perhaps while we're here).
IMHO that would be nice.
After having a cursory look at xul/content/commands.js it seems to me that bug 899844 and this bug will have to be fixed one at a time to avoid mutual bit-rot in functions parseAlias and replaceAll.
Updated•1 year ago
|
Status: REOPENED → RESOLVED
Closed: 13 years ago → 1 year ago
Resolution: --- → INCOMPLETE
Updated•1 year ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•