No Command Echo

I'm experiencing problems recalling my command history when I use No Command Echo (Ctrl+Shift+E). By default, I have No Command Echo turned OFF, and when I turn it on, none of the commands I typed are saved in the command history buffer, using either the up key to recall, or the "Command History..." right-click menu feature.

Dave

Could be because the MUD has sent "echo off" (eg. for the password), when MUSHclient gets that it doesn't save what you type in the history buffer (for security reasons).

Try checking "Ignore 'echo off' messages" in the Commands configuration screen.

This happens while playing normally on the MUD, well after any password prompts, and the command buffer works fine. When I turn No Command Echo ON, nothing is saved to the command buffer. I enabled "Ignore 'echo off' messages", closed the world, reoped, and tried again, with the same result. I also thought MCCP might have been the cause (who knows?!), but I tried on a non-MCCP mud with no success.

Hmmm - you mean "no command echo" also means "no command history"? Sounds like a bug.

Trigger: "You are stuck in the goo, and don't move."
send: last command (direction) attempted.

Heh... I noticed keypad commands aren't put in the command history either... Mind you, I can see why... When a repeat is just another keypress away. :)

Man, this seems to be happening to me every time I make a post lately... I just figured out a workaround! The mud has it's own history buffer, I could use that one instead. :)

You can work around that with a plugin, plugins can capture all output to the MUD (after expansion etc.).

I don't remember the exact name, but can look it up if you are interested.

*bump*

I'm still experiencing the original issue. Let me attempt to explain further, and no, there is no 'echo off' issues.

(command echo is on)
I type: blah
(up will return blah)
I keypress: Ctrl+Alt+E
(command echo is off)
I type: moo
(up will return blah, WRONG)
I type: test
I keypress: Ctrl+Alt+E
(command echo is on)
(up will return blah, still WRONG)
I type: nick
(up will return nick, back to normal, minus the commands entered while command echo was off)

Ideas?

Dave

Hmm, I think this is by design.

eg.

The MUD asks you for a password. You want to be cautious because someone is looking over your shoulder, so you turn command echo off. You type in the password and then turn command echo on (some MUDs will do this automatically with a telnet sequence).

However the whole point is defeated if (while you go to get a coffee) someone can up-arrow and recall the "hidden" command.

Of course, this contradicts my earlier comment that you have found a bug. ;)

Okay, so it's by design. Could you possibly add a feature that enables command-buffer saving while the Command Echo is off?

Ah, you want the design changed? :)

OK then, in version 3.29 you can set an option to do that. It is not in the GUI interface, so you need to do this.

Open the world, and then type:

/world.SetOption "always_record_command_history", 1

Then save the world.

So I realise this is a necro of gargantuan proportions, but it was the thread that came up from a search and it seems relevant.

Would it be possible, in the same light as above, to have commands stay on the prompt (in conjunction with the option "Keep Commands On Prompt" being checked) when No Command Echo (CTRL-ALT-E) is enabled and the world option "always_record_command_history" is 1?

Would be great!

I don't quite understand that. If no command echo is enabled, then you don't see the commands you type, so how can they be on the same line (if you don't see them)?

Heh sorry that was a bit confusing, I admit.

If you have No Command Echo (CTRL-ATL-E) disabled, and have the option "Keep Commands On Prompt Line" (Input -> Commands -> Keep Commands On Prompt Line tickbox) enabled, then after pressing enter the command you just sent remains on the command line.

However, if you have No Command Echo (CTRL-ALT-E) enabled, then regardless of whether or not you have "Keep Commands On Prompt Line" enabled, the command disappears from the command line as soon as you enter it.

Is that any clearer?

Ah I see. The "No Command Echo" tick is normally turned on when it receives an "echo off" command from the MUD, which is usually sent when it asks for your password (although you can turn it on and off manually via the menu). When checked, it disables repeating the last command because it assumes you have just typed your password and you don't want people to see it.

If you just want to not normally display your commands, but keep them automatically repeating in the command window, instead of checking "no command echo" go to the commands configuration and uncheck "echo my input in ..." near the top of that window.

I normally use that, but I'm not aware of a way to toggle it via script functions like the No Command Echo can be with DoCommand().

Unless there's a way to do that?

I'm pretty sure you can set that with SetOption(). Try running this to see what options are available:

To turn off command echoing:



To turn it back on:

Doh, sorry. Thanks! :)