Re: Bug or feature? When running GUI-enabled Vim in a console

Tony Mechelynck wrote: Bug or feature? When running GUI-enabled Vim in a console (not possible on W32, but on Unix it is), the has() and exists() functions do not always reflect the _current_ reality. Examples: :echo has(gui_gtk2) 1 In the above case it may be regarded as a

Re: Bug or feature? When running GUI-enabled Vim in a console

Bram Moolenaar wrote: Tony Mechelynck wrote: Bug or feature? When running GUI-enabled Vim in a console (not possible on W32, but on Unix it is), the has() and exists() functions do not always reflect the _current_ reality. Examples: :echo has(gui_gtk2) 1 In the above case it may be

vim cannot quit after certain tabs manipulation

After certain 3-step manipulation with tabs, can't quit vim with :q!. (vim 7.0.42). Tabline is not updated properly. % vim -u NONE -U NONE ixescmake 1st buffer modified :tabnewcr create 2nd tab ixescmake 2nd buffer modified

Re: vim cannot quit after certain tabs manipulation

Yakov Lerner wrote: After certain 3-step manipulation with tabs, can't quit vim with :q!. (vim 7.0.42). Tabline is not updated properly. % vim -u NONE -U NONE ixescmake 1st buffer modified :tabnewcr create 2nd tab ixescmake 2nd

Re: vim cannot quit after certain tabs manipulation

Yakov Lerner wrote: On 8/6/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Yakov Lerner wrote: % vim -u NONE -U NONE ixescmake 1st buffer modified :tabnewcr create 2nd tab ixescmake 2nd buffer modified :tabclose! 1