Bug 383801 - inputline adds # to every channel string when joining making local joins impossible
Summary: inputline adds # to every channel string when joining making local joins impo...
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: inputline (show other bugs)
Version: 1.7.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-21 15:59 UTC by Rigo Wenning
Modified: 2017-08-25 07:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rigo Wenning 2017-08-21 15:59:42 UTC
The W3C Team uses a private IRC server for its internal worldwide communication. Within this private IRC server there is a distinction between local channels (following the &channel convention) and public channels (following the #channel convention). 

The latest version of Konversation adds a "#" sign to all channel strings typed after the join command. This is also true for joining via the menus or the channel list. Typing "/j &channel" results in joining "#&channel" whatever join mechanism is used. Expectation is that "/j &channel" results in joining channel "&channel".

Evidently joining normal public #channels works, even if the #is omitted on the input line.
Comment 1 argonel 2017-08-24 23:24:13 UTC
Git commit 72de2027f3d3e7a0c48aef6acd666e04fc0b19b1 by Eli MacKenzie.
Committed on 24/08/2017 at 23:13.
Pushed by argonel into branch '1.7'.

Fix prefix-addressed message handling

Messages sent to all channel operators or other mode-prefixed classes of
channel members could use flags that conflict with channel prefix flags.
This tries harder to ensure that the actual channel prefix is found.

M  +1    -0    ChangeLog
M  +1    -1    src/commit.h
M  +19   -15   src/irc/server.cpp
M  +5    -2    src/irc/server.h

https://commits.kde.org/konversation/72de2027f3d3e7a0c48aef6acd666e04fc0b19b1
Comment 2 Rigo Wenning 2017-08-25 06:33:31 UTC
Thanks for the fast fix. I will now try
Comment 3 Rigo Wenning 2017-08-25 07:12:21 UTC
Yes, fixed. Thanks