As I have read a lot about assumed breakindent bugs in previous threads: This reminds me of the strange behavior related to line formatting I mentioned in the vim_use mailing list. It can still be reproduced with the following test.
[email protected], 15.02.2014 02:11: > ... it seems that formatting really behaves > differently if "linebreak" is set. After setting options with > ":se all& co=79 tw=80", place the cursor in the first test line and format > both > lines with "gqj". Try this with and without "linebreak". > xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx > xxx > xxx > In the first case, there are two words in the second line; in the second case, > it is just one word. This can also be reproduced when starting Vim with > "vim -u NONE +'se all& co=79 tw=80'". According to the help page for linebreak, this option should not affect formatting. > Unlike "wrapmargin" and "textwidth", this does not insert <EOL>s in the file, > it only affects the way the file is displayed, not its contents. -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
