The "echo my input in <colour>" says whether or not you want to see what you type. Regardless, it is kept in the command history.
The "no command echo" is triggered by an "echo off" from the server, generally when it asks for your password. This stops echoing, and storing in the command history, so someone can't just up-arrow to get your password back.
Yes, thank you WillFa for that fix! Local echo is not displaying now and the command history works, this is great. Thank you to Nick Gammon also for the help =) (and the awesome client)
Amended on Sun 10 May 2009 05:36 AM (UTC) by WillFa
Message
If you leave "No Command Echo" on the display menu unchecked, and bring up the Commands option page (ALT+0) and uncheck "Echo my input in" (normally custom 10)...
I think that's the setup you're looking for. That how I'm configured and everything works. (history, up arrows, no brown text in the output window that may split an incoming line at a packet boundary thus not trigger correctly, etc etc)
Actually, the client always has echo on when I boot it up, even if I had turned it off before I closed it the session before. I just did what you'd told me to do and I'm still having the same problem.
It is probable the client received an "echo off" message (possibly while asking for your password) and didn't turn echoing on again. As a security precaution, the password you type is not entered into the command history. Thus, if the server does not re-enable echoing, then nothing goes into the command history.
You can confirm this by looking at the Display menu, bottom item (No Command Echo) which is probably checked. Uncheck that and commands should be saved.
To avoid this problem permanently, go to the world configuration, Input -> Commands, and check "Ignore 'Echo Off' Messages". Then it will never do that.
Yep, it is a positive number, it is currently set to 1000. I've checked also and it seems that when local command echo is not on the command history does not get updated at all.
Odd. I have "Echo My Input" off as well in version 4.40, and mine works. On the ALT+0 options page, can you check the Command History Keep <n> Lines frame and make sure there's a positive number in there? (defaults to 500, mine's set to 2000)
Hey yall, I was referred to MUSHclient by a friend and so far am loving it but there's a small problem I'm having with it. Auto-Repeat Command and using the up arrow to get your last command entered are not working for me. Strangely, there is a caveat to this. They both work when I have local command echo turned on.
I talked to the person who referred the client to me and he has no problems at all with having local echo off and bringing up his last commands. So I don't know if this problem is unique to me or not.
I'm also sorry if this isn't the right place to put this, if it's just reporting bugs to the author to fix at a later date. Or if I'm allowed to ask for help with a problem I can't seem to figure out. But if anyone has any ideas on something that could be wrong I would appreciate any suggestions and advice.
Edit: Sorry, I forgot to add that I started at using Version 4.37 then updated to 4.40. I have the same problem with both versions.
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.