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

( search function makes slime almost unusable #7315

Closed
asmyers opened this issue Oct 7, 2016 · 3 comments
Closed

( search function makes slime almost unusable #7315

asmyers opened this issue Oct 7, 2016 · 3 comments

Comments

@asmyers
Copy link

asmyers commented Oct 7, 2016

Description

When using slime one tends to type ( quite a lot. This inserts the character but there appears to be some kind of search function that starts when the cursor is after a (. After inserting a ( an error is immediately emitted in the minibuffer which says:

Search failed. This means there is unmatched expression somewhere or we are at the beginning/end of file.

It's hard to discover what is doing this because describe key just tells you that ( is bound to self insert. However once the slime repl buffer is a few thousand lines this search function locks up emacs for seconds or minutes. Even better is that it immediately restarts after failing if the cursor is still on or after the paren. To recover emacs it is necessary to click madly somewhere else so the cursor is moved in the small window between emacs becoming responsive and the search triggering again.

Reproduction guide

  • Start Emacs
  • start slime
  • generate a repl a few thousand lines long. (dotimes (i 10000) (format t "foobar~%"))
  • Type ( at the repl.

Observed behaviour:
Emacs becomes unresponsive for several seconds and there is an error in the minibuffer. Madly smash a cursor movement operation in order to recover Emacs interaction.

Expected behaviour:
Nothing

System Info

  • OS: gnu/linux
  • Emacs: 24.5.1
  • Spacemacs: 0.105.22
  • Spacemacs branch: master (rev. 9f9faa4)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(auto-completion emacs-lisp git version-control markdown org gtags dash haskell purescript idris agda rust clojure java common-lisp asciidoc spell-checking syntax-checking version-control)
@fouric
Copy link

fouric commented Feb 3, 2017

Can confirm this with spacemacs 0.200.5 and layers (vimscript haskell markdown helm emacs-lisp common-lisp), and everything else sans branch being identical. Why was this closed?

@scrathat
Copy link

Can reproduce the minibuffer message with spacemacs 0.200.9 and emacs 25.2.1 but only after enabling and then disabling smartparens.
If smartparens is disabled from the start everything works.
If smartparens is enabled everything works, too.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Mar 14, 2022
@github-actions github-actions bot closed this as completed May 1, 2024
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

5 participants