Recent changes to bugs

[mailmsg.js]Wscript.Arguments

Anonymous — Fri, 27 Jun 2008 08:38:27 -0000

In japanese Windows XP,temporary file was made in

C:\Documents and Settings\xxxxx\Local Settings\temp\aaz42.txt

So,
var objArgs = WScript.Arguments;
var tmpfilename = objArgs(0);

must be

var objArgs = WScript.Arguments;
var ary = new Array();
for(var i=0;i<objArgs.length;i++){
ary.push(objArgs(i));
}
var tmpfilename = ary.join(" ");

or,cscript must call mailmsg.js with arguments wrapped by double quotes.

EditInVim stops working

Anonymous — Thu, 29 Aug 2002 19:39:57 -0000

Using gvim 6.1.165 compiled with OLE
CubicleVim.dll - 0.1.0.1 5/23/2002
Outlook 2002
W2K sp2

If I start Outlook, this works great for a little while. Then
when I open an existing email and choose to EditInVim,
nothing happens (no errors).

If I shutdown Outlook and restart it, it works again for a
bit.

Another time, the toolbars just disappeared. When I
shutdown Outlook, it eventually GPFed, when I restarted
everything was fine.

cubiclevim toolbar position

Hari Dara — Wed, 14 Aug 2002 00:36:06 -0000

The toolbar doesn't remember the position. When you
open a new compose window, or restart outlook, it goes
back to the same location, wasting the screen real
estate.

Thanks,
Hari

autocommands are adding up

Hari Dara — Wed, 14 Aug 2002 00:18:34 -0000

If there is an existing instance of vim, cubiclevim uses
that instance to open the temp file for editing. This
wouldn't be normally a good idea, because I for one want
to keep my vim session clean, without cluttering it with
all kinds of files, and temp files would only make it
worse, but fortunately my first vim sessions is always
used for browsing source code (tags, id-utils and misc.
things), and I don't mind cluttering this, as this is a
different vim instance than the one I use for source code.
That said, I don't want to throw away this vim session
(which was already existing before I used cubiclevim)
after I am done with composing mail. But this means
that the next time I need to compose another email, the
same vim session will be reused. But cubiclevim doesn't
cleanup the autocommands before editing a new one
(may be assumes a fresh instance), so the
autocommands keep adding up. Normally, I use
autocommand group with the following pattern for this:

aug CubicleVim
au! " First cleanup any existing au commands.
au BufWritePost !start cscript //b c:/mailmsg.js %
aug END

Thanks for making this utility. I find it useful for
composing long emails.

Hari