I recently discovered that GVim for Windows evidently doesn't Save files the same way that other text editors for Windows do. So I'm:
+ Making others aware of this as a possible issue + Looking for a circumvention so that I can continue to us GVim with Madcap Flare ------ OVERVIEW: There seems to be some sort of incompatibility between Madcap Flare and GVim for Windows file-save operation. Madcap Flare (http://www.madcapsoftware.com/products/flare/overview.aspx): + Is a Windows-only authoring tool used by technical writers + Makes extensive use of the Microsoft .NET framework + Includes GUI editors for topics and CSS ------ THE PROBLEM: + IF one uses one of Flare's internal GUI editors, AND one also uses an "approved" external editor (including but not necessarily limited to notepad, notepad2, notepad++, or Komodo Edit) to simultaneously edit the same file, THEN Flare automatically reloads the file when using the external editor to modify and save a file. No problem. + IF one uses one of Flare's internal GUI editors, AND one also uses GVim for Windows to simultaneously edit the same file, THEN Flare gets "confused" about the state of a Saved / :w file and its location; Flare can no longer work with the file if it has been modified and Saved by Gvim for Windows. That is a problem if one prefers to use GVim. ------ SUPPLEMENTARY INFORMATION: Madcap support (which is quite good) currently *supposes* that "edits get written to a temp file while using GVim and Flare doesn't automatically update the CSS with the temp file." This is a *preliminary* supposition pending additional research and so may NOT accurately identify the cause. I have also verified that several other text editors for Windows do not produce the same problem. So it does indeed appear to be a GVim for Windows peculiarity. ------ THE GOAL: + My first objective is to see if there might be some sort of practicable work-around wherein I can continue to use GVim in conjunction with Flare. + My second objective is to make the community aware of this so that it might be looked at, and perhaps addressed, in some future version of Vim / GVim for Windows. Cheers, thanks inadvance for any attempts to help, & hope this helps, R SFO -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
