-
Notifications
You must be signed in to change notification settings - Fork 23
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
Using lispyville operators as drop-in replacements #55
Comments
There is the formatting issue mentioned in that issue currently (e.g. delete does prettification that only makes sense for lisp modes). It may be annoying if you don't want to use safe operations always. You may need to configure Also, I wouldn't alias |
Thanks, for the info. Wouldn't the The reason I wanted an alias is https://github.com/Somelauw/evil-org-mode calls Also it would be really awesome if we can generalize all operators and have a global-minor-mode in the same vein as |
Yes, but you could use lispyville-mode with a different configuration for lisp modes (more than just operators) and just bind the operators globally if you wanted. I'm not confident it's a good idea to change all calls to evil-delete. Where is evil-org-mode using evil-delete where you would want it to use lispyville-delete? If you do want to try that, I'd suggest using advice with I'm planning on having a global minor mode for non-lisp modes at some point when I get rid of the lisp-specific functionality in the operators. |
That would be awesome. The main use case was my config file which is in org-mode and I have src blocks. It is partly a bad habit of mine to not open a org-src edit buffer, which will do the right thing. But in general I think safe operators are the better way. I have never used Thanks a lot for your advice. |
You could also try polymode if you haven't already. |
Hi,
Can the lispyville operators be used as drop-in replacements for evil operators using
defalias
likeDo you foresee any issues with doing that?
Thanks for the wonderful package.
PS: I'm trying to use lispyville in non-lispy modes same as #54
The text was updated successfully, but these errors were encountered: