On Thu, Apr 18, 2013 at 4:58 PM, glts 676c7...@gmail.com wrote:
Hi,
I have recently learnt of a patch that was submitted to the list almost
five years ago. Please see here:
https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ
The reception was positive but for some reason the
On Apr 19, 2013, at 5:50 PM, glts 676c7...@gmail.com wrote:
...
Here's a good real-life example.
The textobj-word-column.vim plugin lets you select a column (Visual
block) of words/WORDs based on the word/WORD under the cursor. If
v:motiontype were available, the plugin could let you
On 18-Apr-2013 16:16 +0200, glts wrote:
Hi,
I have recently learnt of a patch that was submitted to the list almost
five years ago. Please see here:
https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ
Oh dear, I remember that! It's frightening how quickly time passes :-)
Ingo,
On Fri, Apr 19, 2013 at 8:58 PM, Ingo Karkat sw...@ingo-karkat.de wrote:
On 18-Apr-2013 16:16 +0200, glts wrote:
As for the name of the variable, how about:
v:motiontype
The documentation says that when no motion type is given the variable
will be empty, when an explicit motion
On Saturday, April 20, 2013 6:50:58 AM UTC+9, glts wrote:
On Fri, Apr 19, 2013 at 8:58 PM, Ingo Karkat wrote:
With v:motiontype, I'd expect that to be applicable to _every_ motion,
not just those few special ones. I would prefer v:forcedmotiontype. The
only saving grace for this unreadable
Hi,
I have recently learnt of a patch that was submitted to the list almost
five years ago. Please see here:
https://groups.google.com/d/msg/vim_dev/lR5rONDwgs8/iLsVCrxo_WsJ
The reception was positive but for some reason the discussion was
abandoned. I would like to reopen the discussion. I'd
