On Sunday, May 19, 2013 10:18:48 PM UTC-5, mattn wrote: > On Monday, May 20, 2013 11:50:08 AM UTC+9, Ben Fritz wrote: > > > > > > I'm using the "Vim without Cream" build, version 7.3.822, on Windows 7 > > > 64-bit. > > > > > > And cmd.exe really does stop responding when I pass gvim the -f flag. > > > No prompt appears until Vim closes. Any typing done in the cmd.exe > > > window does not appear until Vim closes. When Vim closes, any text > > > typed while Vim was open does appear on the command line. > > > > > > Maybe on Windows the -f is handled elsewhere or something. > > > > Also, I've relied on this behavior in the past, to set gvim as my > > $EDITOR variable used by ClearCase to invoke an external editor to edit > > a config spec with the edcs command. Without this behavior working, > > ClearCase would not be able to wait for Vim to exit and check the file > > for modifications. > > > gvim.exe handle STDIN handle if using dash argument like follow. > > C:\>dir | gvim - > > But -f doesn't do it. >
Where did handling STDIN come into the discussion? The original post was that Vim doesn't support the -f option at all in Windows. As I've said, this does NOT seem to be true. It's pretty easy to tell whether or not -f works, because the cmd.exe prompt does really stop and wait for Vim, as does ClearCase, and any other external application I've tried it in. If Vim doesn't support reading from stdin while using -f, that's a different problem. And, it's a different problem I also cannot reproduce. Using your example, "dir | gvim -f -", I see cmd.exe stop responding until Vim exits. Even with the STDIN reading, -f seems to work as intended, whether I invoke gvim from the path (which will find the gvim.bat file installed with Vim), or invoke gvim.exe directly from the installed path under Program Files (x86). > -------------------- > C:\vim\src>grep dofork *.c > [SNIP] > I didn't see anything in particular in the output of your grep search for some flag without context, which would indicate specifically that this feature will absolutely not work in Windows. What I do see is very convincing evidence that it DOES work in Windows, by running the program and trying it. > > What version of vim do you use? As mentioned, "Vim without Cream" version 7.3.822, on Windows 7 64-bit. As far as I know, this is a native Windows build, not cygwin or anything else. I relied on the -f feature in Windows before I ever had cygwin installed on my machine. Even now, I never invoke Vim from cygwin, though I occasionally use a cygwin-based compiler as my 'makeprg'. Does it matter what is used to compile Vim? I think (but do not know) that the "Cream" distribution is compiled in MinGW, which I use at home to compile Vim when I'm on Windows. I was under the impression Bram used Visual Studio. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
