On Oct 6, 4:21 pm, Bram Moolenaar <[email protected]> wrote: > Christian Brabandt wrote: > > On Mi, 05 Okt 2011, James Vega wrote: > > > > On Wed, Oct 05, 2011 at 11:07:44PM +0200, Christian Brabandt wrote: > > > > Hi jpetrie! > > > > > On Mi, 05 Okt 2011, jpetrie wrote: > > > > > > > J r mie Roquet wrote: > > > > > >> 2009/10/28 Bram Moolenaar <[hidden email]>: > > > > > >> >> It adds "space" in the allowed "listchars" arguments. > > > > > >> > I'm not sure how useful it is to show something instead of a > > > > > >> > space. > > > > > >> > Isn't it obvious that there is a space when there is nothing? > > > > > >> Sometimes it's not : I'm using a visible character for the first > > > > > >> column of tabs, but an invisible one for the remaining columns. > > > > > >> So cases where a tab is followed by a space are not that obvious. > > > > > >> And as Steve pointed out, double spaces are not always obvious > > > > > >> either. > > > > > > Well, I might consider including this. Can you write a patch for > > > > > > the > > > > > > documentation as well? > > > > > > I know this thread is from 2009 and I hope I'm not stomping on some > > > > > kind of > > > > > list etiquette by bringing it back to life, but I'm wondering what > > > > > happened > > > > > to this patch to enable a "space" option for listchars? > > > > It's in the todo list (c.f., :help todo). > > > > > Can you point me to the patch? > > > > http://mid.gmane.org/[email protected] > > > Thanks, applies, but needs some updates. > > Bram, would you like an updated patch, including documentation? > > We already have enough options to completely confuse a beginning user. > Every time a proposal is made to add another option or option value, the > question is: do we really need this? How many people would actually > use it? Isn't there another way to do almost the same? >
I think this one in particular could be useful. I was a bit surprised to see a way to show non-breaking space, tabs, trailing space, but not spaces in general. > You can at least use :match if you want to highlight specific use of > spaces. > One use I could see would be to make it easier to see the number of spaces. :match wouldn't let you do this. Or easier to see specific differences in diff view. Steve Hall also listed a few other reasons in the initial set of posts: * other non-printing characters that look like dec 032 * double spaces * spaces after chars at window edges with wrap on * every char as a byte > I have been overwhelmed with bugs and bug fixes, these always go before > new features, especially when I'm not sure if it's a useful feature. > And also because new features tend to introduce new bugs that then have > to be fixed... > I agree, bugfixes first makes sense :-) -- 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
