Bug 247892

Summary:	Channel Settings dialog should respect CHANMODES (005)
Product:	[Applications] konversation	Reporter:	Jonas Thiem <contact>
Component:	protocol	Assignee:	argonel <argonel>
Status:	ASSIGNED ---
Severity:	normal	CC:	hein
Priority:	NOR
Version First Reported In:	1.5-rc1
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonas Thiem 2010-08-14 21:17:33 UTC

Version:           1.3.1
OS:                Linux

Konversation always allows to enter parameters in the "Advanced Modes" section (channel setings dialog).

Since many IRCds provide information about whether a mode takes a parameter or not inside the 005 with the CHANMODES= block, Konversation should read this and just allow entering parameters for those modes that are actually listed to have parameters there (and fallback to old behaviour with no 005/CHANMODES available).

Also, if the built-in translated mode descriptions dictate a mode to have no parameter and CHANMODES apparently says something else, Konversation should put the mode into "Advanced Modes" instead since then it apparently works differently on the given server than the built-in description/translation of  Konversation assumes.

Reproducible: Always

Comment 1 argonel 2010-08-15 03:27:00 UTC

i'm about 25% of the way through a revamp of the 005 support, including CHANMODES