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

Remove 'edcompatible' #1902

Closed
Grimy opened this Issue Jan 28, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@Grimy
Contributor

Grimy commented Jan 28, 2015

When this option is on, the g and c substitute-flags are remembered globally, and toggled whenever they are given. For example:

:set edcompatible
:s/foo/bar/c     " ask confirmation
:s/bar/baz/      " ask confirmation
:s/baz/foo/c     " do not ask

This is as stupid as it sounds. The doc actually discourages setting this option. I think we should remove it entirely. We could make set noedcompatible a noop like we did for set nocompatible; since edcompatible is used much less than compatible, I’m not sure that’s necessary.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jan 28, 2015

The majority of removed options so far have been completely removed, as opposed to being made no-ops (cp & nocp being one exception). It should be fine to remove it completely (except a stub in the docs), because as you said, the docs discourage its usage. We might want to wait on some more opinions though, as I'm too keen on removing things.

ghost commented Jan 28, 2015

The majority of removed options so far have been completely removed, as opposed to being made no-ops (cp & nocp being one exception). It should be fine to remove it completely (except a stub in the docs), because as you said, the docs discourage its usage. We might want to wait on some more opinions though, as I'm too keen on removing things.

@ghost ghost referenced this issue Jan 29, 2015

Closed

[RFC] Remove 'edcompatible' #1911

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost commented Jan 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment