Ok, when you go to load a new file into the editor, you get certain options (in my case *.ini,*.mrc as the default). My suggestions is (via dialog box in oiptions somewhere) a checkbox checklist where we can specify which files to show in the "open file" dialog. Like say we wanted to see *.txt, *.ini, *.mrc, *.mirc, *.whatever-my-custom-mircscript-file-extension-is in that "open file" dialog? perhaps make a selection for "custom extensions" in a comma separated list . Ths way we can really manipulate how we want the open file dialog to respond

I've thought that would be cool too .. or it could actually
remember file types that've been successfully opened/loaded.

not a bad idea either

I dont want it to rmember sucessfully opening a .exe tho.....

A valid point tho mirc couldnt run an EXE by loading it could it? I wouldnt think it could. However, this gets back to my "use this list" suggestion so we can designate which extensuons to use.

mIRC wouldnt 'run' the .exe, no.

However, unbelievably, some people do infact script with .exe file extensions, just for the sake of it.

I dont see what all the fuss is about, mIRC obviously makes it clear that .ini and .mrc are its default file extentions, why dont people stick to it.

Personally, if it was up to me, I'd prevent mIRC from loading any file that doesnt end with .ini or .mrc, PURELY, because of idiots who create 'trojans' that run in the background and hide their scripts as .exe or .dll files in your system directory, But thats just me.

Eamonn.

Don't blame the ones making the trojans .. they're just having
a good time, getting all that they can out of life by reeking
havoc on the rest of the world. The ones to blame would
be the idiots that load those scripts disguised as .exe & .dll
files and for not knowing what scripts they're running or what
programs are running on their machines. You know the ones,
they're the ones that get an email with an attatchment from
someone they've never heard of before, and the only thing
they can think is hmmm I wonder what this is? It was so
nice of blahblahblah@aol.com to send it to me, I
bet it's some cute and fuzzy little program that will solve all
my problems in this world and put a cute and fuzzy picture
thingy on my desktop .. *CLICK* .. and that's all she
wrote. If it weren't for those morons, you wouldn't need to
make a suggestion that takes away my freedom to use any
file extension I want to use for my own scripts.

If people didn't write trojans, viruses, worms, etc, then "idiots" wouldn't have to worry about what is running on their systems, the authors of the malicious programs are to blame, not the people that get infected with them.

And while we're at it, might as well remove the support for (creating) *.ini file scripts. *.mrc files are shorter, clearer and have a decent identifying extension. Those ini files are good (not great) for storing some kinds of data, not for scripts imo... You have a blah.mrc for the script and blah.ini for config info, clean & simple; not a blah.ini for the script and foobar.ini for the config...

Indeed.

Well one hting thats bad about the Save.. dialog is that it doesnt asuto add .mrc to the end of a script. a little frustrating if you ask me.

Cheers