|
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Sat Nov 04, 2006 11:14 pm
New Feature request. |
I found the #gag issues when trying to redo the way echo commands worked.
The way it is currently done on my mud commands that I send get tacked to the end of the previous line like so.
The prompt looks like this.
1420h, 1420m -
When I enter a command I get.
1420h, 1420m - Command I sent to the mud
I wanted the command to show up on the next line under the prompt. like so
1420h, 1420m -
Command I sent to the mud
Basically All I wanted to do was adda %cr before my command. The problem with the way gag was functioning caused me a few headaches here.
Would it be possible to add a checkbox somewhere to add that newline so commands appear on the next line instead of at the end of the previous mud output?
edit:
Or even a checkmark for having a newline before and a checkmark for having a newline after each command block. So that if you are sending a block of 50 lines you are only adding or removing up to two newlines. |
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sun Nov 05, 2006 12:44 am |
Isn't this easy to do with an #ONINPUT trigger already:
Code: |
#ONINPUT {*} {#ECHO ""} |
or am I missing something. |
|
|
|
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Sun Nov 05, 2006 12:55 am |
It wasn't the last time I tried it. But I hadn't tried it in 1.12.
Just tried that and it appears to work. Thanks
Edit.
Bah I really need to try things out more thuroughly before posting.
It is MOSTLy working I'll let you know more after I get the new version tonight. |
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
|
|