CHILL.DLL

[Steve Fabian]

Charles,
Your CHILL.DLL plug-in is unique - it's the only one which displays a
"loaded" message at TCC start. I think it could be skipped.
--
Steve

 

[dcantor]

Charles,
Your CHILL.DLL plug-in is unique - it's the only one which displays a
"loaded" message at TCC start. I think it could be skipped.

ISO8601.dll also does this. I agree, it could be skipped.

 

[Charles Dye]

Charles,
Your CHILL.DLL plug-in is unique - it's the only one which displays a
"loaded" message at TCC start. I think it could be skipped.

The startup message is omitted if you load the plugin in a transient or pipe shell.

 

[dcantor]

The startup message is omitted if you load the plugin in a transient or pipe shell.

Ah. Now I understand. I couldn't figure out why some of my %@EXECSTR[] calls hadn't failed! Excellent, Charles.

 

[Steve Fabian]

| ---Quote (Originally by Charles Dye)---
|| The startup message is omitted if you load the plugin in a transient
|| or pipe shell.
---End Quote---
| Ah. Now I understand. I couldn't figure out why some of my
| %@EXECSTR[] calls hadn't failed! Excellent, Charles.

But it adds to the TCC sign-on message. In the past I had captured that
message and obtained information from it. I don't do it at present, don't
even look at it, but I may need to resurrect some of that old code.
--
Steve

 

[Charles Dye]

Okay, you can now define an environment variable NOLOADMSG which will also suppress the startup message. (Of course, you must define the variable before loading the plugin. If the .DLL is autoloaded from your PlugIns directory, that means you have to set the variable in the parent shell, or create a system variable.)