On Jul 19, 2008, at 9:55 AM, Markus Heidelberg wrote:
Your patch is malformed. - wrapped long line
No way. My patch didn't contain any long lines!
- tabs are spaces
bah... okay, I'll retab it.
- wrong line numbers (why? I'm on svn revision 1114, too)
Weird... that patch is just from "svn diff".
To have the chance to get the feature included at all, please read :helpdesign-documented
okay
Consider these files: runtime/doc/quickref.txt (:h option-list) runtime/doc/tags (not sure if necessary) runtime/doc/options.txt (:h option-summary) runtime/doc/motion.txt (:h paragraph) runtime/syntax/vim.vim (search for vimOptions) runtime/optwin.vim
Thx... yeah, I meant to do that :-/... but forgot.
I stumbled over ap and ip at the text-objects (:h ap), where lines
with
whitespace are also handled as a paragraph boundary. Isn't this a
little bit
inconsistent with } and { and the description at :h paragraph?
I agree. ":h paragraph" and ":h text-objects" are not in agreement. "h:paragraph" describes the current behavior ("empty line" as boundary), "h: text-objects" does not.
You *could* actually view this as a (non-doc) bug; i.e., decide that ":h text-objects" is normative, implement my change to the startPS() logic but without the new option, and correct "h:paragraph".
So let me know what you want to do here, as long as I'm revising my patch. If you want to "fix" Vim so that the current :h text-objects does not lie, then I will remove the option, fix startPS(), and correct ":h paragraph" in my patch.
While replying to this mail, I noticed that it would be useful to define ownparagraph boundaries, not only an option for whitespace. I use Gvim asexternal editor for KMail and want to delete some paragraphs of quoted text from Mark, but the > quote sign forbids it. I saw 'paragraphs' in the help, but I think that's a bit of another thing. Or is it already possible with thisoption?
No... it isn't. cheers, —ml—
smime.p7s
Description: S/MIME cryptographic signature
