Hi all :) Some months ago I described here a problem I was having using "gqip". This is the thread:
http://groups.google.com/group/vim_use/browse_thread/thread/7465b6b2599ed11f/7a013084a8a1022d?hl=en&lnk=gst&q=gqip#7a013084a8a1022d The thing is that now I know how to reproduce the problem, I've made a sample text file that shows the problem and I can reproduce it even for "vim -u NONE". How to reproduce: 1. Open the sample file with Vim: 'vim -u NONE sample.txt' At this time you should see this on the screen: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ~ ... 2. Now set text width to 72 chars: ':set tw=72' 3. Enter insert mode: 'i'. This is important as this only happens in insert mode! 4. Press '<C-O>gqip', that is, from insert mode press Ctrl-O and after that 'gqip', reflow inner paragraph. At this time you should see this on the screen: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ~ ... The last three lines have been reflowed, although the third one didn't need reflowing at all, since it was exactly 72 chars long. 5. Press '<C-O>gqip' again. This time the text is reflow and ends up being just like in the beginning. Pressing '<C-O>gqip' switches back and forth between the two "text flows" shown above. My vim is 7.2.267, although this problem happens with older versions too, and although the example looks weird, it has been extracted from real text, substituting letters and spaces by "X" except where spaces did actually matter: in that case spaces were preserved. This led to the example I'm providing, which is the simplest case where I could reproduce the problem. The sample text is attached and gzipped, since line endings may matter. The file has been created under Linux (that is, has 0x0a line endings). -- Raúl "DervishD" Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
sample.txt.gz
Description: GNU Zip compressed data
