Kebap
Kebap
> This is an attempt to close https://github.com/Mudlet/Mudlet/issues/5960 That issue was already solved. As it turned out, the window size was calculated wrong. Which issue does this PR fix now?
#6273 seems improved / solved with this PR. #6449 seems unaffected / not solved with this. Please let me know what else is there to test.
Got the same effect now in PTB 2022-12-25 on a different machine, also Win 10, but different Mudlet profiles altogether. Not sure why noboy else is reporting this at all....
Workaround: Use keyboard shortcut ALT + F4
> if (and probably ONLY if) their user name contains character that cannot be encoded in (I think) ASCII... You are talking about the Windows username? So then, what happens...
A person often runs both Mudlet release version, and Mudlet PTB on the same machine. Now during testing, also a Mudlet DEV version is used next to those other two...
Windows: Looks like you mostly need the installer to insert something into the registry. See https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa767914(v=vs.85) Linux: ? MacOS: ? Unsure what happens in Mudlet after clicking the link, in...
So, let's just assume for a second, we do indeed succeed on all operating systems, and Mudlet will know when a user clicks a telnet link. Now what should Mudlet...
It is supposed to encapsulate and mean: Do this logic repeatedly once for every profile listed
Your revision seems fair. We can always add that gateway you removed if an increased desire arises... If autoload is activated, I don't think I would expect a different result...