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
➜ Problem with command history
|
Problem with command history
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Kvothe
(8 posts) Bio
|
| Date
| Wed 14 Aug 2019 07:50 AM (UTC) |
| Message
| Hello, I updated the MushClient to version 5.6 and I have a conflict with the command history since it seems that the option "No Commands Echo" is automatically activated and deactivated.
That is to say that some commands save them, then stop saving several and save them again.
I find it very strange because with previous versions I have no problem.
I could temporarily solve it by activating "Ignore 'Echo Off' messages", but I would like to know if there is another alternative because I don't want the passwords to be saved in the history. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Wed 14 Aug 2019 09:40 PM (UTC) |
| Message
| That's strange. I don't see anything in the release notes for 5.06 that might account for that.
http://www.gammon.com.au/scripts/showrelnote.php?version=5.06&productid=0
You didn't say what version you upgraded from, so if it was a somewhat earlier version you might need to check more release notes. Having said that, I wouldn't deliberately add in a "randomly turn command history off" feature.
As a work-around you could make a couple of triggers, like this:
<triggers>
<trigger
enabled="y"
match="Welcome to XXX MUD"
send_to="12"
sequence="100"
>
<send>
SetOption ('no_echo_off', 0) -- allow echoing of commands to be turned off
</send>
</trigger>
<trigger
enabled="y"
match="You have logged on"
send_to="12"
sequence="100"
>
<send>
SetOption ('no_echo_off', 1) -- disallow echoing of commands to be turned off
</send>
</trigger>
</triggers>
 |
For advice on how to copy the above, and paste it into MUSHclient, please see Pasting XML.
|
The first one should match some text that appears before you are asked for your password. That turns off the "Ignore 'Echo Off'" feature. That way your password can be entered securely.
The second one should match some text that appears after you log on with your password. That turns the "Ignore 'Echo Off'" feature back on.
I can't help with the actual bug unless you can reproduce it, preferably with a packet debug capture. That is, go to the Edit menu -> Debug packets. That captures what is actually being sent by the MUD so I can reproduce what it is that is causing this.
Be warned that capturing packets can potentially produce a lot of data in the packet debug window, which will slow the client down eventually. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Kvothe
(8 posts) Bio
|
| Date
| Reply #2 on Thu 15 Aug 2019 03:42 AM (UTC) |
| Message
| Thank you very much, I will try to find the problem with "Debug Packets".
It is very rare because I was using version 5.5 and before 4.94 and had no problem.
In fact I also looked at the release notes and found nothing related to this. | | 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.
12,981 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top