Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't set noruler #88

Closed
mtglsk opened this issue Dec 17, 2014 · 4 comments
Closed

Can't set noruler #88

mtglsk opened this issue Dec 17, 2014 · 4 comments

Comments

@mtglsk
Copy link

mtglsk commented Dec 17, 2014

It only works after vim is running, but not when it is sourced from .vimrc
@mtglsk mtglsk closed this as completed Dec 17, 2014
@mtglsk mtglsk reopened this Dec 17, 2014
@justinmk
Copy link

https://github.com/tpope/vim-sensible#faq

How can I override a setting?

Normally, sensible.vim loads after your vimrc, making it a bit tricky to override (although you could use after/plugin/sensible.vim). If you want to load it earlier, add the following line to you vimrc, then put your overrides below.
runtime! plugin/sensible.vim

@mtglsk
Copy link
Author

mtglsk commented Dec 17, 2014

Ok, I figured it out, thanks. Btw, why is laststatus set to 2? When there is one window visible isn't it purely cosmetic and superficial? Vim default seem more sensible to me. Closing.

@mtglsk mtglsk closed this as completed Dec 17, 2014
@justinmk
Copy link

I don't see what's superficial about knowing the current line, column, filename, encoding, etc, at a glance. You should use windows more often.

@mtglsk
Copy link
Author

mtglsk commented Dec 17, 2014

I use title and number, so for me a statusline & ruler is just a distraction most of the time. Thanks for helping.

@ghost ghost mentioned this issue Mar 7, 2015
Closed
@trevordmiller trevordmiller mentioned this issue Feb 27, 2018
Closed
tpope added a commit that referenced this issue Dec 29, 2022
@tpope
Don't override user configured value of options
cdb3801 
While `:runtime plugin/sensible.vim` does allow for effectively
superseding any option set by sensible.vim, it has never sat right with
me that this was necessary.  This change attempt to use the output of
`:verbose set` to determine if an option should be overridden or not.

Excluded from this change is options we alter, rather than override,
since a user could conceivably have their own alterations that do not
conflict with sensible.vim.  If any of these alterations were to receive
pushback, I would reconsider this decision.

References: #129
References: #88
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@justinmk @mtglsk