Hi Benjamin! On Fr, 12 Mär 2010, Benjamin R. Haskell wrote:
> > which shows up with my default settings (listchars='tab:»·,trail:·') as: > > 0»··1»··1.00»···101010 > 1»··2»··1.00»···101010000101 > > becomes: > > 0 1 1.00 101010······· > 1 2 1.00 101010000101· > > ...ah, and after composing that, I see why: > > In ArrangeCol, there's this comment: > > " If a delimiter is a <Tab>, replace it by Space > (and then it does) That was intended. Well, acutally I think I could keep the tabs. > Possible bug: Even without the :ArrangeColumn, :SearchInColumn 4 /0000/ > doesn't find the 0000 in the fourth column. (Though this works: > :SearchInColumn 3 /00/) > > The plugin also seems to handle all of those horrible CSV quoting rules. > (Which, of course, it should, for editing CSV data) That's the main > reason I vastly prefer tab-separated. (And the many *nix tools that > operate on tab-separated.) > > Thanks anyway for pointing this out (I'm keeping it installed for true > CSV). Yeah, there are a couple of other nasty bugs (unfortunately the RE is not quite right yet. It seemed to work fine, but I just got a report about it being broken), I just found out. I'll update the plugin as soon as possible. BTW: Please give me some sample data, so I can test the bugfix. regards, Christian -- 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
