(C)ancel - Prompt hang

[J.Hofmann]

When i click the system exit button (x - cross) *or* I choose the system menu
entry Exit, vim has the following behavior.

Save changes to Untitled?
[Y]es, (N)o, (C)ancel:

When I press Y or N, all is ok.
When I press C, the line
Save changes to Untitled?  
remains and there is no cursor anywhere,
until I then press ESC. Then the cursor appears in the buffer and the
command line completely disappears.

Pressing Enter at the [Y]es, (N)o, (C)ancel prompt makes vim write and
exit.

If I press Alt-F4 *directly*, the command line disappears and the cursor
immediately draws back in the buffer, as I am expecting. 

VIM - Vi IMproved 7.0
MS-Windows 32 bit GUI version 

Joachim
###

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/

Re: two NetBSD specific patches

[Bram Moolenaar]

Geert Hendrickx wrote:

 could these two simple patches from pkgsrc be applied to Vim?
 
 patch-ab adds a few NetBSD/*BSD specific filesystems and options for
 correct /etc/fstab syntax highlighting on NetBSD.
 
 patch-ae enables ipfilter syntax highlighting for ipf6.conf as well
 (this file contains IPv6 ipfilter rules).

I'll include the change to filetype.vim.  For the syntax file contact
the maintainer, he is mentioned in the header.

-- 
Just think of all the things we haven't thought of yet.

 /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

Re: Why vta doesn't work when a is one character away?

[A.J.Mechelynck]

Bill McCarthy wrote:

On Mon 27-Nov-06 9:39pm -0600, A.J.Mechelynck wrote:


[EMAIL PROTECTED] wrote:

For example, the word

Cat

When the cursor is on C, and I press vta, the cursor doesn't move.
However, if I press
vtt, it moves two characters to the right. Is this an intentional design
decision or a bug?

I've tried this in both vim 6.4 and the latest version of vim 7.0 on the
download page. 



Works for me with gvim 7.0.168 with Gnome2 GUI on SuSE Linux 9.3, both in GUI
mode and in console mode

With the cursor on the C of Cat in Normal mode

after vta the cursor is on the C (i.e., one character left of the a), one
character is visually highlighted as shown at bottom right of the screen. (In
console mode the highlight color is not noticeable because the only character
of the Visual selection is at the cursor position.)

after (Esc to clear Visual mode, then) vtt the cursor is on the a (i.e., one
character left of the t), two characters (Ca) are visually highlighted.


With typical windows settings, select=exclusive (from
:behave mswin).  With that, vta leaves the cursor to the
left of C and zero is shown in the lower right (vfC produces
identical results).  However vtt highlights Ca and two is
shown in the lower right (vta produces identical results).



IIUC, vf or vt create the visual areas inclusively (to the looked-up character 
or the one before it respectively), but then selection=exclusive interprets 
any selection as exclusive (the last character of the visually highlighted 
area is not included in the selection).


If this is true, I might venture that the behaviour is correct in the case of 
vta (cursor ends up on the left of a, sel=exclusive interprets the selection 
as zero-length) and incorrect (or not as advertised) in all other cases (vf 
and vt produce identical results, instead of vt selecting one less character 
than vf).


It seems that my choice of options, i.e.
 don't use mswin.vim
set selectmode=mouse,key
set mousemodel=popup
set keymodel=startsel
set selection=inclusive
(which is neither :behave mswin nor :behave xterm but some kind of 
compromise between the two), was a lucky one.



Best regards,
Tony.