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

use-package/smartparens Error on Cygwin #8507

Closed
gilch opened this issue Mar 12, 2017 · 3 comments
Closed

use-package/smartparens Error on Cygwin #8507

gilch opened this issue Mar 12, 2017 · 3 comments

Comments

@gilch
Copy link
Contributor

gilch commented Mar 12, 2017

Description :octocat:

Every time I start Spacemacs, a window appears with:
Error (use-package): smartparens :config: Symbol’s function definition is void: wrap

Reproduction guide 🪲

  • Install Cygwin on Windows with Cygwin emacs and Cygwin git packages.
  • Start Cygwin bash.
  • Rename the .emacs.d/ and clone Spacemacs in Cygwin home folder using Cygiwn git on Cygwin bash.
  • Start Cygwin emacs from Cygwin bash and do initial setup (evil, helm, and full install).
  • Every time you start emacs you see the error.

Observed behaviour: 👀 💔
Window with *Warnings* buffer appears with
Error (use-package): smartparens :config: Symbol’s function definition is void: wrap

Expected behaviour: ❤️ 😄
No errors/warnings.

System Info 💻

  • OS: cygwin
  • Emacs: 25.1.1
  • Spacemacs: 0.200.7
  • Spacemacs branch: master (rev. c2774bc)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(autohotkey helm emacs-lisp)
  • System configuration features: XPM JPEG TIFF GIF PNG IMAGEMAGICK SOUND DBUS NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS
@gilch gilch changed the title use-package/smartparens warning on Cygwin use-package/smartparens Error on Cygwin Mar 12, 2017
@gilch
Copy link
Contributor Author

gilch commented Mar 12, 2017

I noticed this error in the Windows version too. However, with the latest package update, I can no longer reproduce this issue. It may have already been resolved.

@gilch gilch closed this as completed Mar 12, 2017
@aijony
Copy link
Contributor

aijony commented Mar 14, 2017

Just for a side note, this seems to be #8500.

@Fuco1
Copy link

Fuco1 commented Mar 14, 2017

It's scary, there was maybe 20 hour window to get this issue and soooo many people were affected :O I guess this got a bit more popular than I thought and I should take more care releasing to master :/

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

4 participants