>- Win32: Dropping a shortcut on the Vim icon edited the shortcut
instead
> of the file it refers to (old problem).
Any way to actually edit the shortcut? :D
Seriously, I was curious if anyone came across this issue on any 95/98
systems: Highlight the file and simply bang on the return key (if the
filetype gets associated with 'vim' instead of Exploder, etc.), and it
doesn't know spaces in filenames, so something like 'c:\my
documents\fooey.htm' will essentially crap out as 'vim' tries to edit
c:\my
documents\fooey.htm
as 2 separate files.
Perfectly logical, when handed the path+name via a commandline w/o
encompassing quotes, but wonder if there be a workaround for this. I
don't like using the moose if I can at all avoid it, so rclicking and
"Edit with Vim..."ing is a less-desirable option.
One more reason to never use spaces in file-/pathnames... Well, except
for .mp3s and such. Ain't gonna manually edit *those*...
