Hi Tim!
On Di, 02 Jun 2015, Tim Chase wrote:
> Just noticed this evening that the documentation for
>
> :help <space>
>
> doesn't distinguish between "l", <right>, and <space>. However, at
> the end of a line (if 'nocp' is set) <space> will proceed to the
> first character on the subsequent line while "l" and "right" don't.
> To repeat,
>
> $ vim -u NONE -c "set nocp" multiline_example.txt
>
> then "$" to get to the end of a line. Try "l" and <right>, noticing
> they don't do anything. Try <space> and it takes you to the next
> line.
>
> Should the documentation be updated to reflect that difference?
That behaviour depends on the 'whichwrap' option.
This patch adds a link to the 'whichwrap' option.
diff --git a/runtime/doc/motion.txt b/runtime/doc/motion.txt
--- a/runtime/doc/motion.txt
+++ b/runtime/doc/motion.txt
@@ -172,6 +172,8 @@ CTRL-H or *CTRL-H* *<BS>*
l or *l*
<Right> or *<Right>* *<Space>*
<Space> [count] characters to the right. |exclusive| motion.
+ See 'whichwrap' option for adjusting behaviour on
+ end of line
*0*
0 To the first character of the line. |exclusive|
Best,
Christian
--
Je vornehmer einer ist, desto höflicher behandelt er den Niedrigen.
-- Ludwig Börne
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Tuesday, June 2, 2015
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment