Am 14.03.2017 um 09:57 schrieb Nikolay Aleksandrovich Pavlov:
2017-03-14 0:29 GMT+03:00 Bram Moolenaar <b...@moolenaar.net>:
Andy Wokula wrote:
Am 13.03.2017 um 21:00 schrieb Ben Fritz:
On Sunday, March 12, 2017 at 10:33:06 AM UTC-5, Bram Moolenaar
wrote:
Someone noticed that although $ takes a count to go down (count -
1) lines, the ^ does not. Since currently the count is ignored, we
could make it used to go (count - 1) lines up.
Would this break anything?
We currently have _ and g_ that are similar to ^ and $, except that ^
doesn't take a count.
_ goes downward or stays on the same line. To move up, you can use -,
which always goes up, it won't stay on the same line.
It would make more sense for me if ^ went downward rather than upward
when given a count. This would be consistent with existing commands.
But I won't be extremely disappointed if it goes upward instead, it
would just be one more oddity in an editor full of such quirks. :-)
I'd vote for [count]^ going to the [count]th character in the line.
(We can easily go to the [count]th screen column and to the [count]th
byte, but not yet to the [count]th character, unless I'm missing
something).
You can already use 3| to go to the third screen position. Only with
double-wide characters you would see a difference with character count.
Also with tabs. And, possibly, with combining characters: depends on
the definition of the “character”. Though I do not know why one would
want to go to the N’th character in first place.
@Andy Wokula define a “character”. This term is neither obvious nor
non-controversal. This looks like Vim documentation is mostly taking
it as “unicode codepoint” given statements like “composing characters
are considered separate characters here”, but yet it is clear that
“character” may mean something different (or such statements would not
be needed).
This sounds like a secondary question.
And if there is no clear definition => one more Vim option.
For now I use the `l' motion in my mapping to get to the target character
(with default 'virtualedit' and 'whichwrap').
--
Andy
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
