T

On Tuesday, July 24, 2012 8:59:48 PM UTC-7, Tony Mechelynck wrote:
> On 24/07/12 22:12, sfosparky wrote:
> > 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
> >
> 
> 
> Try
>       :set backupcopy=yes
> when running Vim together with Flare. I think setting backupcopy=auto or 
> even =no might be the reason Flare gets confused.
> 
> See :help 'backupcopy'
> 
> 
> Best regards,
> Tony.
> -- 
> GEMINI (May 21 to Jun. 20)
>       Good news and bad news highlighted.  Enjoy the good news while
> you can; the bad news will make you forget it.  You will enjoy praise
> and respect from those around you; everybody loves a sucker.  A short
> trip is in the stars, possibly to the men's room.

THANK YOU Tony!

In GVim, :set backupcopy=yes seems to enable me to save changes made in GVim 
that are then immediately captured by the Flare CSS editor.  That setting has, 
as far as I can tell with only superficial experimentation, thus added GVim to 
Flare's list of "approved" editors.

Good one!

Cheers & THANKS! 'gain,
Riley
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

Raspunde prin e-mail lui