View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004249 | unreal | ircd | public | 2013-12-12 21:12 | 2014-02-01 12:33 |
| Reporter | dg | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | wont fix | ||
| Summary | 0004249: Allow disabling NAMESX | ||||
| Description | Hi, Could an option for disabling NAMESX please be added? It's causing issues with tab completion in many clients. If "&@dg" is in the userlist, d<tab> will not expand to "dg". This is problematic, so, a workaround is for me to disable NAMESX. Thanks. | ||||
| 3rd party modules | |||||
|
|
NAMESX is enabled on a per-connection basis and ONLY if the client requests it by use of the PROTOCTL or CAP command. If a client can't handle NAMESX, then it shouldn't ask UnrealIRCd to enable it! |
|
|
The client in question can handle NAMESX but it breaks tab completion. I wish to disable NAMESX for all clients due to the amount o clients that break w/ NAMESX + tab completion. |
|
|
What client are you using? |
|
|
Hexchat 2.9.6 |
|
|
In what way does it break tab completion exactly? As in my experience I have yet to have issues with tab completion and NAMESX in Hexchat |
|
|
>This is problematic, so, a workaround is for me to disable NAMESX. Would it not be easier to just disable it in your client? |
|
|
To quote Hexchat's developers, "either stop by #hexchat [on freenode] or open an issue on our tracker." Turning off NAMESX completely just to work around a client bug is bad. |
|
|
I've decided not to add such an option. The reason there's an option to disable UHNAMES - which was a bit debatable as well - was purely because it could consume a lot more bandwidth.. for NAMESX there's no such case (impact is minimal). The disable option would only be there to workaround broken clients that say they support option X but then fail to.. support it.. like you said. I feel this is not worth spending resources on. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-12-12 21:12 | dg | New Issue | |
| 2013-12-12 22:00 | syzop | Note Added: 0017860 | |
| 2013-12-12 22:10 | dg | Note Added: 0017861 | |
| 2013-12-12 22:23 | syzop | Note Added: 0017862 | |
| 2013-12-14 12:44 | dg | Note Added: 0017863 | |
| 2013-12-22 19:55 | Jobe | Note Added: 0017868 | |
| 2013-12-22 19:57 | Jobe | Note Edited: 0017868 | |
| 2014-01-11 00:32 | ShawnSmith | Note Added: 0017869 | |
| 2014-01-22 01:04 | grawity | Note Added: 0017893 | |
| 2014-02-01 12:33 | syzop | Note Added: 0017895 | |
| 2014-02-01 12:33 | syzop | Status | new => closed |
| 2014-02-01 12:33 | syzop | Assigned To | => syzop |
| 2014-02-01 12:33 | syzop | Resolution | open => wont fix |
