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

When are safe operators enabled by default? #37

Open
jellelicht opened this issue Apr 16, 2018 · 2 comments
Open

When are safe operators enabled by default? #37

jellelicht opened this issue Apr 16, 2018 · 2 comments

Comments

@jellelicht
Copy link

jellelicht commented Apr 16, 2018

Unless I am somehow misunderstanding a major part of lispyville and how it can be used, I am having some issues getting the operators such as safe delete to work properly.

If we have, line-by-line C-M-x'ed:

(require 'evil) ; => evil
(require 'lispyville) ; => lispyville
(evil-mode) ; => t
(lispyville-mode) ; => t

(defun inc (n)
 | (+ 1 n))

With | being the cursor/point in normal mode, pressing D deletes the whole line (including )), leaving us in an inconsistent state:

(defun inc (n)
|

Am I somehow misconfiguring lispyville, or am I misunderstanding what should be happening? Calling e.g. lispyville-delete-whole-line via M-x does lead to a consistent state, where the last ) is kept.

@jellelicht
Copy link
Author

Nvm, I figured it out; the last release of evil barely predates a commit (by you even, if I'm not mistaken) that slightly changes evil-define-key*. Sorry for the noise, and thanks for the amazing package!

@noctuid
Copy link
Owner

noctuid commented Apr 16, 2018

Right, I should probably make it more clear in the readme that this package tracks the latest evil.

@noctuid noctuid reopened this Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants