What steps will reproduce the problem?
1. Open a file in gvim.
2. Unfocus the gvim window.
3. Change file outside of gvim.
4. Click "close window" button on window.
What is the expected output? What do you see instead?
Expect: window closes immediately.
Actual: closing is interrupted by dialog "W11 Warning: File ... has changed
since editing started [OK] [Load File]".
This dialog is meaningless if the buffer is clean, since the next action will
be to quit.
What version of the product are you using? On what operating system?
OS: Linux with XFCE4 (Xubuntu).
$ gvim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 9 2015 16:31:56)
Included patches: 1-622
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by dbarnett@google.com
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
+balloon_eval +float +mouse_urxvt -tag_any_white
+browse +folding +mouse_xterm +tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme +textobjects
+clientserver -hangul_input +netbeans_intg +title
+clipboard +iconv +path_extra +toolbar
+cmdline_compl +insert_expand +perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con_gui +lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind +X11
+dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent +xim
+emacs_tags +mouseshape -sniff +xsmp_interact
+eval +mouse_dec +startuptime +xterm_clipboard
+ex_extra +mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop +xpm
Please provide any additional information below.
Original issue reported on code.google.com by fri...@google.com on 20 Jul 2015 at 7:05
Original issue reported on code.google.com by
fri...@google.comon 20 Jul 2015 at 7:05