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.

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

Closed
richo opened this issue Jan 17, 2013 · 6 comments
Closed

Objectionable settings #20

richo opened this issue Jan 17, 2013 · 6 comments

Comments

@richo
Copy link

richo commented Jan 17, 2013

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.

@tpope
Copy link
Owner

tpope commented Jan 18, 2013

I'm boggling at 'incsearch'. That was my go-to example of "stuff everyone agrees on." Also, I've never had a crap connection for which 'incsearch' was the deciding factor in usability (and if I ever win that jackpot, I'll just override it.) I'll keep your input in mind, but it's going to take more than one person to change my mind on this.

Are you sure you read the help for 'fileformats' and not 'fileformat'? All this does is tell Vim to consider that the file might be Mac format after checking for UNIX and DOS line endings.

'smartcase' is relevant only if 'ignorecase' is set. I can't stand 'ignorecase', and this option makes it slightly more tolerable. But I think I'll drop it just because an ineffective setting has the potential to confuse.

@rizzatti
Copy link
Contributor

@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.

@richo
Copy link
Author

richo commented Jan 18, 2013

Thanks for the feedback. I was reasonably sure that I'm in the minority with finding incsearch incredibly annoying (I have had the connection issue I described, but it's not a regular occurance by any stretch) but thought it was at least putting that vote out there.

You're right about fileformats, I missed the trailing s. As you were.

The help for smartcase is a little confusing, after reading it I thought it implied ignorecase, but I now see that isn't the case. Maybe leaving it in, with a comment describing it's effect and intention would be the right middleground.

@tpope
Copy link
Owner

tpope commented Jan 18, 2013

@zehrizzatti the other half of this is that I'd rather discourage the use of 'ignorecase' rather than compensate for it. The more 'ignorecase' burns people, the less people will set it. Hopefully.

I have some ideas about other ways to battle 'ignorecase'. But that's for another plugin.

@tpope tpope closed this as completed in 6083bf4 Jan 19, 2013
@sedm0784
Copy link

I just discovered another person that doesn't like incsearch. So now there are at least two of you!

@richo
Copy link
Author

richo commented May 25, 2018

DOZENS OF US

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants