What I think is a useful development:
In the notify list: each time a notify nick is on-line and you get the msg in status or activ window, add date and time in the .ini-file. Then you can look throu the file now and then and see if there is some nick that you could remove that haven't been on-line in a while
Easy to keep it up to date then :-)

While this might be a useful development, it's also easily scripted using the ON NOTIFY event.

This is just an example. There are lots of different ways of organizing the file depending on just how you want it.

think your missing a space ie: $logdir notify.ini ... etc...

other than that, a great suggestion

These location identifiers don't need spaces.
//echo -a $logdirtest

Yeah, $logdir, $scriptdir, $mircdir etc don't need spaces... but it's not a bad idea to use spaces (or \'s) just in case that's ever changed. A space in that instance probably wouldn't work anyhow... a \ would be used instead. Haven't tested it though, so maybe mIRC can understand with a space.

Using a slash doesn't change the fact that the syntax is inconsistent, and $*dir aliases have a slash on the end already.

The robust solution is $qt($+($logdir,notify.ini))

I didn't say it wasn't inconsistent. I pointed out that it's better to be consistent by including a space/slash. And, yes, I do know that the \'s are part of the $*dir commands. They wouldn't work otherwise in the form of $*dirfile.ext . I was pointing out that you wouldn't be able to use a space there, but that you can use a \. Double \'s in a path are fine.

As to using $+() to combine the items... I'm not sure why you would bother doing that. It might prevent an issue later if the ability to type it out as $*dirfile.ext is removed, but that's not guaranteed. It would depend on how it's removed. If it's removed in a way that leaves the final \ on the $*dir command, then that would prevent an issue. If it's removed along with the final \ on the $*dir command, then it doesn't prevent the issue. Instead, including the \ will prevent the issue either way. It's also shorter and doesn't require the $+() command, which means it's faster (though probably by no more than a couple miliseconds). $qt() is always a good idea, of course.

In any case, at this time, it's just a preference. Some will write it one way and some will write it another. Unless mIRC changes this, and there is a really good change that it won't get changed because of the large number of scripts that use the $*dirfile.ext format, there isn't any reason you can't write it the way you want to. It's just a matter of deciding whether or not you want to try and avoid any potential issues down the road or if you want to either assume there won't ever be an issue or that you'll update when there is.

Using a space doesn't work (even in identifiers or in quotes). Using a slash does work.

The primary reason I use $+ is for readability of code. Someone reading my code can tell how it would behave without any special knowledge of the quirky behavior of $*dir identifiers in mIRC. The fact that it also would not break if the quirky behavior was removed is just a bonus.

I don't see any reason why the ending slash would be removed from the response given by $*dir identifiers, so I don't really accommodate for that possibility.

I did say that space isn't valid.

Anyhow, $logdir\logfile.txt is more readable imo. It looks like a path that most people are familiar with, whereas someone may not know what $+() means. Either way.

Thank u all for the ideas!
But since i'm not that familiar with irc in these ways, where do i type this stuff?

Alt-R > File > New.

Thanks!

Did it and clicked ok. In the Staus window i now get "*:{ Unknown command".
So where excatly do i get those "stamps"?

Make sure you paste all of what was shown so that it looks exactly the same. From that error message, you either copied starting at the "*:{" instead of starting at "on" or else you have an Enter in the middle of the line. Make sure it's the only thing in the file (File>New should give you a blank file).

RusselB made either a typo or an error, the on notify event doesnt take a parameter, use:



Edit: Riamus, no, he is simply executing the command named "*:{"

Thanks! No error msg now! U guys r the best
So where do i find this time stamps?

Didn't notice that extra parameter. Good catch.

Thamks again guys!

But were do I find those time stamps?

What time stamps? If you want to enable/disable time stamps, Alt-O > IRC > Messages.

OK sorry wrong words. I mean where do i find the notes when a nick on my notift list lasst was seen. I e what the scrpit is suppouse to do if i got it right....

//run $logdirnotify.ini

no file named logdirnotify.ini on my pc :-(

Did you leave off the $ ?

//run $logdirnotify.ini <-- exactly like that.

Another possibility is that the code doesn't handle space in the path, which would result in the filename being incorrect, use that code instead:

Right. Like Wims said, if you have a space in your path, then you'd want $qt() around the filename/path as that puts quotes around it. Then, to access the file, use:

//run $qt($logdirnotify.ini)

And where do i run this command?
Sorry for all the stupid questions....

Commands are run from the command line (where you type to talk to people).

You can also create a popup for this. Add the following to the bottom of the script you created:



The menu item will be available in the "Commands" menu at the top of mIRC (after Tools).

Thanks!!! :-)