 |
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
 Posted: Mon Nov 13, 2006 3:30 pm
[1.15] Not gagging blank lines
|
As a side effect of the enabling of sending blank lines to the MUD (thank you, by the way :) ), my scripts now echo any blank lines when import them. I like to use the whitespace as a way to break up sections and make things a little more readable.
I thought I would gag the blank lines by making my first line in the script a trigger to do just that. Needless to say, it didn't work. I looked in the preferences for a setting similar to zMUD's "match triggers on blank lines" option, but could not find one. Am I missing something? Or is this a minor bug?
| Code: |
| #TRIGGER "no_blanks" {^$} {#GAG} |
|
|
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Mon Nov 13, 2006 5:20 pm
|
If it is a blank line that you sent you need to make it a command input trigger.
|
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
 |
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Mon Nov 13, 2006 5:28 pm
|
Maybe it is counted as a blank line I sent. That's a good point. I just forget that the script import counts as sending text now. Thanks for the tip.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Nov 13, 2006 8:45 pm
|
I'll see if I can fix this without breaking the sending a blank line from the command line. Blank lines in scripts are not supposed to send anything to the MUD. That's what #CR is for. So this sounds like a bug.
|
|
|
|
|
|
|
|
