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

Racket-Layer No Autocomplete After Update to 0.200.0 #7320

Closed
exrok opened this issue Oct 7, 2016 · 2 comments
Closed

Racket-Layer No Autocomplete After Update to 0.200.0 #7320

exrok opened this issue Oct 7, 2016 · 2 comments

Comments

@exrok
Copy link

exrok commented Oct 7, 2016

Description :octocat:

No proper autocomplete in racket mode when using the racket layer
like in the older version of spacemacs the one right before 0.200.0
it work like good but now it don't like at all. Talk'in like company-mode
and shiz, it used to be like I wouldn't get user defined identies inside the
auto-complete without running but I still got something. Now I get nothing with
out running and even after running racket in buffer I only get user defined
funcs downgrading backto older spacemacs fixes it.

Reproduction guide 🪲

  • Start Emacs
  • Open Buffer
  • Enter Racket Mode
  • Type "(eq"
  • hit tab
  • observe the lack of autocomplete

Observed behaviour: 👀 💔
no auto-complete

Expected behaviour: ❤️ 😄
autocomplete

System Info 💻

  • OS: gnu/linux
  • Emacs: 25.1.1
  • Spacemacs: 0.200.0
  • Spacemacs branch: master (rev. e6357a5)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(auto-completion emacs-lisp racket latex themes-megapack theming python org unimpaired)
@jmiven
Copy link
Contributor

jmiven commented Oct 15, 2016

I believe that racket-mode requires that you declare a #lang at the top of the file, or at least a module.

Auto-completion works for me when:

  1. the file contains a #lang declaration
  2. the file has been run through racket-run (SPC m s b)

@exrok
Copy link
Author

exrok commented Oct 16, 2016

Yes, this resolves it. Weird it worked before the update with #lang but whatever.

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

3 participants