|
gmueller Apprentice
Joined: 06 Apr 2004 Posts: 173
|
Posted: Sat May 19, 2007 7:19 am
Not sure if this is a blessing or a bane... |
I like to script in a way that makes aliases go invalid when they're not in use, but before they are used they will write themselves.
My old system had tons and tons of <> and []'s in it because I love functional programming.
I've noticed that the scripts/aliases will disable themselves (i.e. a user doesn't EXPLICITLY call #T- or disable it from the pane) if there is incorrect syntax, but if the alias is modified it is already in a disabled state, and once enabled, dependent triggers WONT reenable themselves.
I think it's fine for cmud to disable things, but, if cmud does it, and not the user, I would pray that it would undo it's observations at runtime. |
|
|
|
gmueller Apprentice
Joined: 06 Apr 2004 Posts: 173
|
Posted: Sat May 19, 2007 7:20 am |
I think in zmud it would invalidate the line on which the error occurred and not the entire script.
|
|
|
|
gmueller Apprentice
Joined: 06 Apr 2004 Posts: 173
|
Posted: Sat May 19, 2007 7:21 am |
a rather unsafe thing, but at least it didn't insert it's own prejudice?
|
|
|
|
Larkin Wizard
Joined: 25 Mar 2003 Posts: 1113 Location: USA
|
Posted: Sat May 19, 2007 10:55 am |
Can you give an example of an alias or trigger that disables itself? I've not seen this behavior on my CMUD. I just get an error message when my alias isn't valid syntactically.
|
|
|
|
gmueller Apprentice
Joined: 06 Apr 2004 Posts: 173
|
Posted: Sat May 19, 2007 11:20 pm |
It happened like 3 times to me last night, but I can't reproduce it today... I've tried a number of things. If I can get it to do it again I'll post.
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon May 21, 2007 5:19 pm |
CMUD doesn't disable settings themselves. What is probably happening is that the alias doesn't compile properly if it has a syntax error, and then won't execute properly. But it shouldn't be actually disabling anything. Are you sure you are not accidentally double-clicking on the setting in the tree view (which will toggle the enabled flag).
|
|
|
|
|
|