cmdheight should = 1 about vim-sensible HOT 12 CLOSED

Did you see my commit where I explained how much this helps with Press ENTER prompts?

This is actually one of the ones I expected might be controversial. I'm quite willing to consider yanking it. But let's give it a few days to see what everyone else has to say.

I'd like to make everything user overridable, but it's hard (though not impossible) to tell the difference between a Vim default and a user setting. As a workaround, you could most certainly override it in .vim/after/plugin/sensible.vim.

from vim-sensible.

I'd like to make everything user overridable, but it's hard (though not impossible) to tell the difference between a Vim default and a user setting. As a workaround, you could most certainly override it in .vim/after/plugin/sensible.vim

That's rather unpleasant! For this to actually be sensible-settings every setting should able to be overridden. We don't want a handful of forks, each with their own modifications

from vim-sensible.

As for overriding things, I have a thought: maybe the "README recommended" way of loading this "plugin" should be "download + manually source at the top of .vimrc" rather than "use plugin manager and then override in .vim/after/*" ?

from vim-sensible.

I would hope most people wouldn't respond to a minor inconvenience in overriding with a fork. Seems like a petty way to handle it.

Why the aversion to after/plugin/sensible.vim? If you really, really must have everything in your vimrc, you can do

autocmd VimEnter * set cmdheight=1

I'm going to wait for a second option to be objected to before I worry about this any more. If it's really just cmdheight, I'll nuke it and call it a day.

from vim-sensible.

@sickill my goal is to minimize vimrc junk, and this sounds like a step in the wrong direction. But you most certainly could use it that way if you wanted to

runtime! plugin/sensible.vim
set cmdheight=1

The include guard will prevent sensible.vim from loading a second time.

from vim-sensible.

Is there a way to increase cmdheight temporally, to match numer of displayed error lines?

from vim-sensible.

I don't think so. There's no autocommand for an error occurring. Even trickier would be deciding when to shrink it back down.

Is this a vote against cmdheight=2?

from vim-sensible.

For me these two lines are not esthetically pleasing, unfortunately ;/

If there is no hook, maybe there exist a way to display only first message in most annoying cases. For example echo Hello displays following ones:

E121: Undefined variable: Hello
E15: Invalid expression: Hello

But are these two really necessary?

I also can't find your commit with explanation, so sorry if I'm repeating something.

In principle this repository should be:

a universal set of defaults that (hopefully) everyone can agree on

And I guess not everyone is happy with that (as you've expected).

So probably it doesn't matter if it's right or wrong, it's just the default.

from vim-sensible.

Removed. Maybe I'll make a different plugin for "options tpope thinks you should set."

@sheerun, Vim's error messages are what they are. There's not really much we can do about them.

from vim-sensible.

The most sensible way out of this issue is to allow every setting to be easilly overridden.
The default doesn't really mind me, aslong as I can override those options I don't agree on I'm perfectly happy!

from vim-sensible.

I gave 3 different ways to override. Are none of them "easy" enough for you?

from vim-sensible.

@tpope why not have a g:sensible_tpope_options for that "options tpope thinks you should set". Would be funny at least ;)

from vim-sensible.