Forums Bug Reports Double spaces in file names.

mIRC generally has huge problems when it comes to double spaces. Which can be easily overlooked, but given a file called "hello hi.txt" with two spaces mIRC apparently can't access the file at all. I'd like to see double spaces preserved in general, but in this case it's pretty bad, as the file could already exist and wouldn't be able to be accessed.

Two spaces in any filename gets crushed down to one space which means they can't be seen by mIRC.

This probably relates closely with the tokenization routine in mIRC.

//echo .... $gettok(;;;;;;This is broken, 1, $asc(;))

Apparently, $null tokens are impossible. Which is a shame.

This is a limitation, not a bug.

There's a workaround you can use for files:

hi <3 spaces> test.txt contains "this is a test that worked"

The following successfully reads the file:



To save using $findfile every time, you could use this:



You can now read the file using $read(%file).

You don't need $findfile() in this case. In fact, when you want to pass the filename to an identifier (and not a command), you don't even need to use its short name:

//echo -a $read(ambience\hi $chr(32) test.txt)

The only limitation is that you cannot hardcode the actual consecutive spaces in it; you need to use $chr(32) accordingly (ie make sure that there are no pairs of literal spaces).

I knew about not having to use short filenames or double quotes in files for identifiers, I assumed mIRC would read hi $chr(32) test.txt the same way it would hi<3 spaces>.txt and strip extra spaces.
I used a short filename because there aren't any spaces in them

Thanks though, it's always good to have more than one way of doing things.