No, I have no idea what it could be useful for. Voice prompts? Error messages? @EXECSTR silliness in your PROMPT? It's fun to play with, anyway.
http://www.unm.edu/~cdye/plugins/say.html
http://www.unm.edu/~cdye/plugins/say.html
> No, I have no idea what it could be useful for. Voice prompts? Error
> messages? @EXECSTR silliness in your PROMPT? It's fun to play with,
> anyway.
>
> http://www.unm.edu/~cdye/plugins/say.html
>
>
>
>
>
I think it is cute but do not like the "Say plugin v0.50.1 loaded." message at all.
set /e /u noloadmsg=1
> ---Quote (Originally by Jim Cook)---
> I think it is cute but do not like the "Say plugin v0.50.1 loaded." message
> at all.
> ---End Quote---
>
> Code:
> ---------
> set /e /u noloadmsg=1
> ---------
>
>
>
>
I think "noloadmsg" is much too generic a name and doesn't imply anything, let alone a SAY plugin for TCC.
Can a plugin be sensitive to its own name at load time? What if say.dll displayed a banner, but sayquiet.dll did not, or something like that.
> ---Quote (Originally by Jim Cook)---
> I think "noloadmsg" is much too generic a name and doesn't imply anything,
> let alone a SAY plugin for TCC.
> ---End Quote---
> It's deliberately generic; the same variable works in all of my plugins. I
> can't imagine why you would want to disable the startup message in one, but
> not in another. (Actually, I can't imagine why you'd want to disable it at
> all, but apparently some folks do.)
>
>
> ---Quote---
> Can a plugin be sensitive to its own name at load time? What if say.dll
> displayed a banner, but sayquiet.dll did not, or something like that.
> ---End Quote---
> It could, but that would involve adding code. Checking an environment
> variable was a zero-line fix, since I'm doing an ExpandVariables() there
> anyway.
>
>
>
>
>
When I load TCC, there are at least 60 different .dll files that get loaded
Of those files, only Say.dll announces itself. Your plugin very nicely responds to @VERINFO[Say.dll] if I want to know what version it is. (BTW: None of my other plugin .dll files do respond to that.)
Beggars can't be choosers, but I wanted to at least express my opinion about the interface. Still, I stand by the opinion that using a system wide environment variable of that generic a name is inappropriate.
>I can't imagine why you would want to disable the startup message in one,
>but not in another. (Actually, I can't imagine why you'd want to disable
>it at all, but apparently some folks do.)