I'd like to see this prefix working on *all* (no exceptions) mIRC commands. For example, it has no effect on commands such as /hop or /server, which show information that could be customized when aliased versions take part of both. It's not that nice to have mIRC's information display mostly gaged in an own fashion while I can't really get rid of the default text it provides for a few commands only.

the reason these don't seem to work is that your examples trigger multiple things.

If you use .notice $nick blah ; you don't see it
If you use notice $nick blah ; you do see it

You CAN use a dot infront of the .hop and .server commands. however once either of those commands are done it starts a series of events that will produce RAW outputs, so your no longer dealing with a single return such as with .notice or .msg

I hope that helped.

If you're talking about numeric raws, there are no numeric raw replies being triggered for those. /.server echoes right after you typed it: *** connecting to blah blah. /.hop says it's attempting to rejoin a channel, before it really tries to.

If by "raw" you mean mIRC internal work, well every command has its internal tasks being executed. It'd be quite possible to halt the default text for /server when even /.dns, which does use even an mIRC-run event, works quietly.

after executing the /server command you do indeed get RAW msg's upon reconnection ie RAW 1-5 for example. Joining a channel, you also get RAW replies. 353, 366, 324 and 329 by default (on DALnet anyways).

These are not related strictly to the command. They're from the server's end. I'm not talking about these, as you could read in my previous post.. I'm talking about "* Connecting to <server> (<port>)", which is local, however /.server doesn't hide it. Also, "* Attempting to rejoin channel <channel>" and "* Rejoined channel <channel>", which aren't hidden by /.hop. On the other hand, /.dns hides its default message before looking up any address, and it even hides late info which comes after the lookup as well.

Edited. Of course, I edit all my posts.

It's local, but iirc, it's actually done AFTER the command is executed. That wouldn't make it impossible to change though...

That's why I suggest to make it able to be changed, as there is no need for it to have this limitation.
There're probably more commands behaving like that, I can't remember though

Hmm, come to think of it, the /say command doesn't work with the . prefix. There's just no excuse for that .

lol.. but hey, that leads me to think why does /me work.. hehe :tongue:

wonder how old this post is? anyway, I came across the /say thing and I do wish that could be silenced. that's entirely local, and I wanted to make it its own alias like I did with /msg, so that I could reformat the output (I like seeing [$me] intead of <$me>). Seems like this could just as easily have a silent option. like you said, /me can be silenced if you want.

-Venoman

You can easily silence it via a script: alias say { ! $+ $iif(!$show,.) $+ msg $active $1- }

Obviously that's no reason not to add it to mIRC though.

huh. that worked, go figure. I used something very similar and it did not; the only significant difference I see is the ! in front. Translated, you have !.msg $active $1- (assuming $show is $false). I've never seen an ! used that way or documented in mirc.hlp. What exactly is it doing here / what is it used for?

-Venoman

If you have an alias with the same name as a mIRC command, the ! prefix makes the parser ignore your alias and call the original command (in your case, it will prefer the original /msg over an /msg alias).

The $iif() is redundant. Just use !msg $active $1- and it will work.
All commands within an alias inherit the show status used for it. That means that, using /.say, /!msg will become /!.msg.