Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
vim_dev
Home
+ new post
About this group
Join this group
Message from discussion {count}v command
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ingo Karkat  
View profile  
 More options Oct 31 2012, 3:59 pm
From: Ingo Karkat <sw...@ingo-karkat.de>
Date: Wed, 31 Oct 2012 20:59:01 +0100
Local: Wed, Oct 31 2012 3:59 pm
Subject: Re: {count}v command
Print | View thread | Show original | Report this message | Find messages by this author
On 31-Oct-2012 20:43:19 +0100, ZyX wrote:

>> g?gvg? is really nice, I'll give it a try.  I tested it over digraphs,
>> and it works.

> You can also use

>     :<C-u><Esc>
> . Unlike g? workaround it alters neither undo nor command history.

Great input, ZyX! For me, it even works without the <C-u>, just :<Esc>. Though
this looks like a bug to me: I would understand that a no-op command like
:<C-u>echo<CR> would be treated as a modification, but an aborted command
definitely does not count as a modification; it also isn't added to the history.
I guess this special behavior is just a side effect of a simple implementation
that doesn't take command aborts into account.

The more I learn about it, the more I would prefer that {count}v _always_ uses
the previous selection (as proposed here again), modification yes or no. But I
guess we would need more vocal support to sway Bram, so please speak up! (Or
voice your concerns if you happen to know someone/thing that relies on the
current behavior.)

-- regards, ingo


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google