On Monday, May 20, 2013 11:50:08 AM UTC+9, Ben Fritz wrote: > On Sunday, May 19, 2013 9:17:42 PM UTC-5, Ben Fritz wrote: > > On Sunday, May 19, 2013 9:12:17 PM UTC-5, mattn wrote: > > > On Monday, May 20, 2013 10:53:28 AM UTC+9, Ben Fritz wrote: > > > > On Saturday, May 18, 2013 11:27:20 PM UTC-5, Taro MURAOKA wrote: > > > > Windows gvim works fine with -f for me. > > > > > > > > If I open cmd.exe and type "gvim -N -u NONE -i NONE -f" > > > > > > > > Then Vim launches, and the cmd window does not advance to the next > > > > prompt. It waits for Vim to finish. When I quit the gvim window, the > > > > cmd prompt brings up a new prompt and lets me continue. > > > > > > > > What situations have you found where -f doesn't work in Windows? > > > > > > I don't beleave it. Are you using cygwin gtk version of vim? it seens the > > > codes of '-f' isn't passing in gui.c for windows gui. > > > > > > > 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. -------------------- On Monday, May 20, 2013 11:50:08 AM UTC+9, Ben Fritz wrote: > On Sunday, May 19, 2013 9:17:42 PM UTC-5, Ben Fritz wrote: > > On Sunday, May 19, 2013 9:12:17 PM UTC-5, mattn wrote: > > > On Monday, May 20, 2013 10:53:28 AM UTC+9, Ben Fritz wrote: > > > > On Saturday, May 18, 2013 11:27:20 PM UTC-5, Taro MURAOKA wrote: > > > > Windows gvim works fine with -f for me. > > > > > > > > If I open cmd.exe and type "gvim -N -u NONE -i NONE -f" > > > > > > > > Then Vim launches, and the cmd window does not advance to the next > > > > prompt. It waits for Vim to finish. When I quit the gvim window, the > > > > cmd prompt brings up a new prompt and lets me continue. > > > > > > > > What situations have you found where -f doesn't work in Windows? > > > > > > I don't beleave it. Are you using cygwin gtk version of vim? it seens the > > > codes of '-f' isn't passing in gui.c for windows gui. > > > > > > > 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. -------------------- C:\vim\src>grep dofork *.c gui.c:97: if (gui.dofork && !vim_strchr(p_go, GO_FORG) && recursive <= 1) * This require MAY_FORK not Windows (i.e. defined(UNIX) && !defined(MACOS_X) && !defined(__APPLE__) gui.c:451: result = gui.dofork ? gui_mch_early_init_check() : gui_mch_init_check(); * This require FEAT_GUI_GTK not Windows gui.c:4944: gui.dofork = (arg[1] == 'b'); * This is part of :gui command not about this talking. gui_gtk_x11.c:524: gui.dofork = FALSE; /* don't fork() when starting GUI */ * This is gtk part not windows. gui_x11.c:1242: gui.dofork = FALSE; /* don't fork() when starting GUI */ * This is x11 part not windows. gui_x11.c:1256: gui.dofork = FALSE; /* don't fork() when starting GUI */ * This is x11 part not windows. main.c:280: gui.dofork = TRUE; /* default is to use fork() */ main.c:1717: gui.dofork = FALSE; main.c:1863: gui.dofork = FALSE; /* don't fork() when starting GUI */ main.c:1955: gui.dofork = FALSE; /* don't fork() when starting GUI */ main.c:3370: gui.dofork = FALSE; * This is the codes that just only set TRUE/FALSE values. -------------------- What version of vim do you use? -- -- 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.
