This is a true fix for #20. The `maparg()` function still does not report back enough information to know whether or not the "<script>" tag was specified for the mapping. So, let's take another approach and parse the output of the map command. The presence of an "&" appears to be a good indicator that you need the "<script>" tag. Let's key off that and use that information when generating the command to restore the mapping.
Fixes a minor bug in some Vim installations.
From e.g. "[LustyExplorer-Files]" to "LustyExplorer--Files". This is because internally we call something like `:split [LustyExplorer-Files]` in order to create the explorer window. The argument to :split is the name of the file to edit (or, if it doesn't exist, a new buffer with that name). However, :split does some wildcard expansion on its argument, and can interpret [LustyExplorer-Files] as a regex-ish range. In most versions of Vim, this :split call may emit a warning, but Vim will go ahead and create the new buffer named [LustyExplorer-Files] in a new window. In some versions of Vim 7.3, however, it will emit the warning (stifled by `!silent` in lusty-explorer.vim) and not create the new buffer or the new window. I could probably work around this by escaping the square bracket characters, but I'm not sure how that will affect Windows, in which the escape character '\' is also a directory separator. So, I'll do the easier thing and use more innocuous names for the explorer windows.
…m default cancel keys. I hope this change will make the keyboard mappings more robust since it can no longer miss unmapping keys.