Should 'list' be enabled by default? about vim-sensible HOT 6 CLOSED

Okay, let's lay out some pros and cons. Pros:

1. People will be less sloppy with whitespace with this enabled.
2. Commands like { and } behave much more predictably when you can see trailing whitespace on blank lines.

Cons:

1. It's a bit more cluttered, particularly if whoever wrote the code was an oblivious buffoon. (Note: a majority of code was written by oblivious buffoons.)
2. It can interfere with copying and pasting from a terminal.

Did I miss anything? I'm not sure what you mean by "an obvious default."

The second pro is a big deal to me. It's why I'm not using @zehrizzatti's autocommands, even though they're really cool. And it's why I'm so reluctant to remove it. Predictability is huge.

Still, after discussing it on IRC, I'm leaning towards yanking it. But not without giving people a bit more time to add their two cents here.

from vim-sensible.

I didn't use to like it either, but I changed my mind, specially due to the following in my vimrc now:

    autocmd InsertEnter * setlocal nolist
    autocmd InsertLeave * setlocal list

from vim-sensible.

Still, I don't think it's an obvious default.

from vim-sensible.

I decided that the same arguments I would make against 'hlsearch' apply to 'list' as well.

Maybe I'll make some maps for easily toggling those options (and 'spell' too, why not?).

from vim-sensible.

Another plugin :)

from vim-sensible.

I just got tripped up by this, I saw 'listchars' in the source and assumed it would be enabled. Perhaps this decision should be explained in the README?

from vim-sensible.