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

Unexpected interaction with evil-embrace on Doom Emacs #212

Open
countvajhula opened this issue Jun 27, 2024 · 2 comments
Open

Unexpected interaction with evil-embrace on Doom Emacs #212

countvajhula opened this issue Jun 27, 2024 · 2 comments

Comments

@countvajhula
Copy link

Hi there,
I'm bringing this issue to your attention that was reported on the Symex repo, in case you feel a fix is warranted in evil-surround. It appears that Doom Emacs enables some advice by default that leads to unexpected interaction between evil-surround and evil-embrace.

I personally am not experiencing this issue but it seems that it affects (all?) Doom Emacs users.

Reproducing it:

(f1 |(x1 x2))

M-: (evil-surround-change (following-char))

Causes:

Debugger entered--Lisp error: (error "No surrounding delimiters found")
  error("No surrounding delimiters found")
  evil-select-paren("( " " )" 1847 1847 nil 1 t)
  evil-surround-outer-overlay(("( " . " )") 40)
  evil-embrace-evil-surround-change(40)
  apply(evil-embrace-evil-surround-change 40)
  evil-surround-change(40)
  eval-expression((evil-surround-change (following-char)) nil nil 127)
  funcall-interactively(eval-expression (evil-surround-change (following-char)) nil nil 127)
  command-execute(eval-expression)

for affected users.

@countvajhula
Copy link
Author

Looks like there is an existing issue on evil-embrace that may be connected: cute-jumper/evil-embrace.el#12

@tomdl89
Copy link
Member

tomdl89 commented Jul 2, 2024

Thanks for raising @countvajhula . As evil-embrace aims to be "making evil-surround even better" my initial take is to let them investigate. If there's a bug in evil-surround that's uncovered by evil-embrace doing an otherwise sensible thing, I'm happy to fix.

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

2 participants