|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
alias teste { . $+ me is testing }
was working on 6.2, not working anymore, it doesn't do anything
|
|
|
|
Joined: Dec 2002
Posts: 3,138
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 3,138 |
Reproduced here, well spotted $+(.,me) is a reasonable workaround.
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
|
|
|
|
Joined: Dec 2002
Posts: 3,138
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 3,138 |
alias teste {
$+(.,me) is testing
} Works fine here, if I type /teste in a query window to myself I receive my message back. Remember the . prefix will hide the local output
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
ok in fact my code looks like alias teste { $+(.,$replace(hello,hello,/me)) is testing }
in 6.3: /ME Unknown command in 6.2 * //me: not connected to server (line 2, script1.mrc)
|
|
|
|
Joined: Dec 2002
Posts: 3,138
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 3,138 |
Remove the /
The reason you get two different errors is that in one you're connected to a server and in the other you are not.
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
yeah i fixed it, thanx, but i had to change my code, too bad
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
Remove the /
The reason you get two different errors is that in one you're connected to a server and in the other you are not. yeah i know, the second error is normal, but not the first
|
|
|
|
Joined: Dec 2002
Posts: 3,138
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 3,138 |
If one is normal so is the other. In both cases "/me" is being taken as the command name, not just "me". /ME Unknown command * / /me: not connected to server (line 2, script1.mrc) Edit: May as well point out this bug is probably related to items 21/22 of the 6.3 versions.txt: 21.Fixed command prefix /!. parsing inconsistencies across routines. 22.Fixed "// echo hello" being parsed as "//echo hello". The parser now halts parsing of empty // commands.
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
If one is normal so is the other. In both cases "/me" is being taken as the command name, not just "me".
/ME Unknown command * //me: not connected to server (line 2, script1.mrc) no, wrong i've connected my second mirc (6.2) and he say * /me: cannot use /me in this window while 6.3 says /ME Unknown command
|
|
|
|
Joined: Dec 2002
Posts: 3,138
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 3,138 |
That's because you've tested 6.2 with one script and 6.3 with another. alias teste {
$+(./me) is testing
} Gives: /ME Unknown command * //me: not connected to server (line 2, script.ini) In both 6.2 and 6.3. It's worth pointing out that the following: alias teste {
./me is testing
} doesn't produce an error, which is a bit inconsistent.
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
That's because you've tested 6.2 with one script and 6.3 with another. alias teste {
$+(./me) is testing
} Gives: /ME Unknown command * //me: not connected to server (line 2, script.ini) In both 6.2 and 6.3. ok, so there is a bug in both versions in 6.2 . $+ /me << works $+(.,/me) << don't work $+(.,me) << work
in 6.3 . $+ /me << don't work $+(.,/me) << don't work $+(.,me) << work
|
|
|
|
Joined: Dec 2002
Posts: 5,424
Hoopy frood
|
Hoopy frood
Joined: Dec 2002
Posts: 5,424 |
In mIRC 6.21 and earlier it was possible for the parser to treat / ! and . in different combinations and orders, with more than one of each being stripped out depending on the parsing order. This resulted in inconsistent behaviour.
In mIRC 6.3 the behaviour that you see is by design. Prefix parsing is now strictly handled across all routines in the order /!. to ensure consistent behaviour.
|
|
|
|
Joined: Jan 2003
Posts: 62
Babel fish
|
OP
Babel fish
Joined: Jan 2003
Posts: 62 |
thanx
|
|
|
|
|