[Konversation-devel] [Bug 137843] New: Possibility to access serverport in scripts
Daniel Roschka
danielroschka at web.de
Sat Nov 25 00:01:50 CET 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=137843
Summary: Possibility to access serverport in scripts
Product: konversation
Version: unspecified
Platform: Debian testing
OS/Version: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
AssignedTo: konversation-devel kde org
ReportedBy: danielroschka web de
Version: 1.0.1 (using KDE KDE 3.5.5)
Installed from: Debian testing/unstable Packages
OS: Linux
In scripts for konversation you can only access the ip of the actual server, the actual channel and the name of the application (normally konversation).
That lead's to problems if you 're connected twice to a server with different irc-networks. This could happen if you use irssi-proxy or a similar tool.
Then you 've the same server ip for different networks and some scripts won't work as they should (e.g. sayclip will print out it's information on in all networks which are accessed via irssi-proxy). To avoid that it would be useful to provide a possibility to give scripts also the actual port of a server and let konversation accept the target server for a script in form auf ip:port .
More information about the Konversation-devel
mailing list