Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ MUSHclient ➜ Bug reports ➜ MushClient refuses to negotiate Terminal Type

MushClient refuses to negotiate Terminal Type

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by Falkreon   (1 post)  Bio
Date Thu 16 Aug 2007 06:00 AM (UTC)
Message
Example:
Server> IAC WILL TELOPT_TERMINAL_TYPE
MushClient> IAC WONT TELOPT_TERMINAL_TYPE

in Configuration>Appearance>Output there is an option called "Telnet Terminal Type", which defaults to "mushclient". So, I figure the fact that MC refuses to negotiate term type is a bug.
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #1 on Thu 16 Aug 2007 06:18 AM (UTC)
Message
If you check RCC 1091:

http://www.faqs.org/rfcs/rfc1091.html


Part way down the document, this example appears:


8. Examples

   In this example, the server finds the first type acceptable.

      Server: IAC DO TERMINAL-TYPE

      Client: IAC WILL TERMINAL-TYPE

         (Server may now request a terminal type at any time.)


You will notice that the server should send "IAC DO TERMINAL-TYPE" and the client responds "IAC WILL TERMINAL-TYPE".

MUSHclient does this.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #2 on Thu 16 Aug 2007 06:21 AM (UTC)
Message
Further up the page it also says:


2. Command Meanings

      IAC WILL TERMINAL-TYPE

         Sender is willing to send terminal type information in a
         subsequent sub-negotiation.


This is not appropriate for the server (the MUD) to send, because it wants to receive terminal type information, not send it.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Mastermosley   (2 posts)  Bio
Date Reply #3 on Thu 19 May 2011 08:00 AM (UTC)
Message
I am working on a MUD Client and am making sure that my server detects the clients color system. I send the IAC DO when the socket first accepts:

byte[] cmd = new byte[] { 0xFF, 0xFA, 0x18, 0x01, 0xFF, 0xf0 };

And I recieve a bunch of bytes from the client which has the color system label inside it. I tested this on the windows client and got ANSI, and putty, which I got XTerm, but when I tested this with MUSH Client I received no reply. Am I going about this wrong?
Top

Posted by Mastermosley   (2 posts)  Bio
Date Reply #4 on Thu 19 May 2011 08:06 AM (UTC)
Message
Nevermind, I just made it loop a few times and the client sent me mush client.

Cheers.
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #5 on Thu 19 May 2011 08:19 AM (UTC)
Message
Communications are asynchronous. The next thing you receive won't necessarily be the one you asked about. For example in a MUD you might type:


look


But because of time differences (server queues) you might get:


The sun sets in the west.


... before the response to "look".

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.


19,327 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.