|
Ghurmuzh Newbie
Joined: 10 Apr 2009 Posts: 8
|
Posted: Tue Apr 14, 2009 6:52 pm
Controlling what gets put in command history |
I've noticed that most commands that get sent to the mud unprocessed
do not end up being put in the command history. This makes it
quite a bit less useful than it otherwise would be. Is there a way to
make all commands entered into the command line show up in the history?
Thanks,
Ghurmuzh |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Tue Apr 14, 2009 8:40 pm |
All commands larger than 2 letters get entered into the command history, even if the command is sent to the MUD unprocessed. Short commands 2 letters and less are not added to the history because it's just as quick to type them again as it is to recall them from the history.
|
|
|
|
Ghurmuzh Newbie
Joined: 10 Apr 2009 Posts: 8
|
Posted: Wed Apr 15, 2009 1:36 pm |
Thanks Zugg,
I use the command history like my shell history so I'd really like to know even
those easily typed 2-letter commands. The reason isn't so much for ease of
typing as it is for command context. Not sure if you would be interested in
changing this at all, just giving a reason why it can be useful. |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Wed Apr 15, 2009 4:20 pm |
The reason they're excluded is to prevent the history being filled with movement commands if you're going a long way - but an option to disable that could perhaps be useful. For extra credit, perhaps only valid directions (as defined in direction objects) could be excluded.
|
|
|
|
|
|