Friday, April 12, 2013

Re: Consider lines containing a tab a paragraph boundary

Gary Johnson <garyjohn@spocom.com> a écrit:
> On 2013-04-12, zappathustra@free.Fr wrote:
> > Hello Christian,
>
> > Anyway I've already found two buglets :) (unless your patch was just a
> > proof of concept): first, branches won't work:
> >
> > set paragraphs=/^\s*$\|whatever
> >
> > doesn't find anything; ...
>
> I haven't installed the patch, so I can't test this, but your branch
> is probably not working because of
>
> :help :set-args
> :help option-backslash
>
> You should use either
>
> set paragraphs=/^\\s*$\\|whatever

Indeed. Actually, the bar should be preceded by three backslashes, if
I'm not mistaken (two denote a single one, and the last escapes the
bar).

In the meanwhile I've found that if you're on a paragraph line, you
can't jump to paragraph lines just below if you're one the first
character. E.g.:

set paragraphs=foo

with file:

foo
foo

foo

If you're on the first "f", you'll jump to the last line; if you're on
the first "o", you'll jump to the second line... With file:

foo
foo
foo

you won't jump anywhere from the first "f". Normally, "}" with the
usual 'paragraphs':

- jumps to the next blank line when on a non-blank line;
- jumps to the next blank line following a non-blank line when on a
blank line;
- jumps to the end of the file if there is no blank line below the
current one.

(``Blank line'' here of course means a real blank lines or the nroff
macros.)

With Christian's patch, I think that behavior should be mimicked by
simply replacing ``(non-)blank line'' with ``line (not) matching the
option''.


Best,
Paul

--
--
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/groups/opt_out.

No comments: