Well, what about notes? Notes get logged too, I think.., and they *do not* go through either aliases or triggers before being stored. To correctly replay a custom log for such things, scripted to function with some application that needs more than a time appended, you would have to find every single "note" function, in every plugin/script you hve installed, including other people's, then manually add code to also generate a modified log entry for them. This is just bloody rediculous, especially if the point is to "accurately" show what happened in the client during replay, or when re-parsing the text, or what ever it is you are actually doing with it, which requires having those notes logged correctly as well. You can't do that with text that isn't generate through user commands or server text with any method we have available right now, not without a lot of recoding of things that we might have personally created.
And, one can also imagine applications that use the table interface for Mushclient and call the "note" function directly, which you wouldn't be able to recode so easilly. Like if you have a database for something, and it used "note" or "colornote" to display errors directly to the world. That note would be produced by the external application, which may have been written by someone completely different, and where you don't have access to the source to add in code to write the modifies log entry.
We are dealing with three text streams, while your suggestion only deals with two of them. I think I need to revise this from, "This might be an interesting idea.", to, "We might need this in some cases, so please add it." I really hadn't even thought about the issue of what happens with note and colornote, especially from applications using the .tbl bindings to call the functions for those. |