-
-
Notifications
You must be signed in to change notification settings - Fork 278
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.
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
Objectionable settings #20
Comments
I'm boggling at Are you sure you read the help for
|
@tpope leave smartcase, just in case. I think you were right from the beginning on that one. Maybe just a comment in front of it, stating it is in effect only whenever ignorecase is on. |
Thanks for the feedback. I was reasonably sure that I'm in the minority with finding You're right about The help for |
@zehrizzatti the other half of this is that I'd rather discourage the use of I have some ideas about other ways to battle |
I just discovered another person that doesn't like |
DOZENS OF US |
Well, you did say if anyone objects to anything...
incsearch
breaks the "install on remote servers" usecase imo, in the case of a crap connection or a machine swapping violently, vim trying to redraw the screen on each keystroke is a pain. Also, the option has bugged me since day 1, but that's a more scientific objection than simply "it bugs me".fileformats+=mac
I'm assuming this doesn't actually set the line ending to CR like the first docs I found suggest, since even OSX doesn't do this any more. Surely if you're going to pick a horse in this race, unix is the right default?smartcase
I'm still not sure this is necessarily expected behaviour. If I search for a lowercase identifier I expect to only see lowercase matches, that could just be me though. I foresee the usecase for this config being almost exclusively code, and not free text which I generally assumed was the main usecase for smartcase.The text was updated successfully, but these errors were encountered: