Skip to content
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.

API: hexchat_get_info(ph, "network") is wrong #1439

Open
philicious opened this issue Aug 3, 2015 · 3 comments
Open

API: hexchat_get_info(ph, "network") is wrong #1439

philicious opened this issue Aug 3, 2015 · 3 comments

Comments

@philicious
Copy link
Contributor

... it returns the name of the network as seen in network-window list. However the name in the network tree is actually set to networks name. This should return the real network name, just like seen in the tree.

e.g.:

  • name in network-window: "bouncer-for-efnet"
  • network tree displays "EFNet"
  • API call returns bouncer-for-efnet but should be EFNet
@TingPing
Copy link
Member

TingPing commented Aug 3, 2015

It is odd that the tree does not match but I think returning the network-list name is the correct move personally.

@philicious
Copy link
Contributor Author

XChat also has this correct. Correct as in this bug doesnt appear.

I think the tree should display as is now, the network name, parsed out from network response.
But the API call should be fixed.
hexchat_get_info(ph, "channel") returns the correct network name if context is set to network window

( If you connect to a bouncer, the tree shows the name from network-list UNTIL connection to the "real" network is established. Then it somehow parses the response and updates the tree. )

But yes, both behaviors are somehow valid.

@TingPing
Copy link
Member

TingPing commented Aug 3, 2015

d934e60

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants