-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
SPC SPC doesn't work #15360
Comments
Seems to be broken when not using a window system: |
@tofuya @fantostisch (I assume @fantostisch also uses macOS here.) |
Adding Forgot to mention my setup, tested on Ubuntu 21.10: System Info 💻
(markdown spell-checking xclipboard)
|
Have you restarted your Emacs after you added it into If you've already restarted Emacs, try this: Comment out these lines and then restart Emacs
spacemacs/layers/+spacemacs/spacemacs-editing-visual/packages.el Lines 37 to 38 in ee3c558
|
I am not using a daemon and restarted Emacs. On startup I saw a message I just discovered that it only shows the Tested with both the |
Thanks for your explanation. I suspect Your finding can now rule out this possibility. Next, try these:
Also, what's your |
After starting Emacs without disabling the The same issue persists after updating the packages. My
|
@fantostisch To clarify, in b7e1dee does SPC SPC works? Or do you mean it's the commit that introduces "symbol's function definition is undefined"? |
SPC SPC does not work in b7e1dee, b7e1dee is the commit that introduced the bug. Just tested and the commit also seems to introduce the |
@fantostisch Thanks for the clarification. (featurep 'all-the-icons)
(configuration-layer/package-used-p 'all-the-icons)
(fboundp 'all-the-icons-material)
(fboundp 'all-the-icons-octicon) |
Run on the latest develop (ee3c558):
|
@fantostisch
In your |
Yes, there is a
|
@fantostisch What's the result if you type Also: Can you try to update Emacs to latest version (27.2)? |
Just tried 27.2 by using the Emacs snap package and it has the same issue.
|
@fantostisch Can you post your .spacemacs? |
My .spacemacs: spacemacs.txt |
@fantostisch Can you post the value of |
load-path: load-path-nw.txt |
@fantostisch In ielm, can you try again with: (featurep 'all-the-icons)
(require 'all-the-icons) |
|
After executing the require command, the output of the featurep command changes:
|
@fantostisch emacs -nw --eval '(setq debug-on-error t)' If any error occurs, please attach the log. |
An error occurred: error.txt |
@fantostisch It seems like I didn't submit the correct fix last time. (defmacro spacemacs-buffer||propertize-heading (icon text shortcut-char)
`(concat (when dotspacemacs-startup-buffer-show-icons
(concat ,icon " "))
(propertize ,text 'face 'font-lock-keyword-face)
(propertize (concat " (" ,shortcut-char ")")
'face 'font-lock-comment-face))) |
This fixes the issue! Thanks! |
@fantostisch |
@tofuya |
It has been fixed. Thank you for your quick response. |
@lebensterben I confirm your latest commit fixes the issue when using spacemacs-base. Thanks a lot! |
I had a similar issue, i.e This is what I found out by attaching the debugger with
I don't know what happens here exactly, but at some point this code tries to retrieve the spacemacs buffer with (kill-buffer "*spacemacs*") in my |
Same here (
At first I blamed recently installed Emacs 28.1, but temporarily rolling back to 27.1 made no difference (no 27.2 available from PPA). |
This issue seems to have reappeared in the latest commit b74da79
|
It seems the |
I also have issues with 'org-assert-version' after an update of spacemacs. I downgraded spacemacs to commit 7991003 (the one before org was upgraded to 9.6) and now I can work again. Can this be fixed by configuration (i.e. downgrading org-mode only) ? |
There are discussions on @dalanicolai what's your thought on this? |
to people still experiencing this issue:
|
I am not sure when (I guess it mostly happens correctly) the upgrade to org-9.6 introduces this error. What I am more or less sure about, is that this error appears because I guess if any such I am not sure what is the best strategy to prevent/fix this. At least, I guess users should generally quickly find the solution here now (if this is it, but I guess it is). After writing this, I have also found this explanation. And the same thread mentions that it should have been fixed now. |
I tried a lot of things yesterday, including trying to delete the complete elpa folder and org-9.6 individually without any success (emacs 28.2 on wsl). The only solution for me was downgrading spacemacs. The issue mentioned by @dalanicolai also says, that the issue is not solved |
is there a functionality to select the org-mode version I would like to use or to use the built-in version? If not, could this be added? |
This commit might be interesting to you. Don't forget to remove the I am not aware of any other way to put 'restrictions' on the org-version. |
I forgot to post the link of the discussion from org-mode's mail list: https://list.orgmode.org/87bkonzisl.fsf@gnu.org/T/#u @dalanicolai Please take a look. It seems like the upstream has messed up this time. |
@lebensterben Thanks for the link. It confirms what @smile13241324 mentions in #15861 (comment). I think Maxi is trying to come up with a permanent fix (which indeed probably is not a straightforward thing to do). Now I had a quick look, and it seems that the Therefore, as I mentioned already, I guess that a quick temporary fix could be to add the correct org-mode dir to the front of the load path before that (let ((elpa-org-dir (car (seq-filter (apply-partially #'string-match-p "^org-9.*[0-9]$")
(directory-files package-user-dir)))))
(when elpa-org-dir
(add-to-list 'load-path (print (concat package-user-dir elpa-org-dir))))) so that the correct org-mode gets loaded already when creating the Spacemacs buffer. (No problem if that code stays there for a while... we will automatically get remembered about/to remove it when org-mode reaches version 10) @lebensterben It is not so messed up, just it gives problems when users use org-mode before they load/configure it (so that the 'built-in' org-mode version gets (auto)loaded first) |
Hmmm I think its worth a try, given that my hotfix wasn't that effective, I am definitely open for more drastic approaches now. Once it works again we can take the time to check the details properly. |
The side effects of my hotfix are fixed now, if you are still affected by an org version mismatch please report. |
Description
SPC SPC
doesn't work.(
M-x
work)The log output to the Message buffer is as follows.
SPC SPC
stopped working at commit b7e1deeReproduction guide
– Start Emacs
– Press
SPC SPC
Observed behaviour:
Pressing the
SPC SPC
will result inSPC SPC-
, prompting me to continue entering commands.Expected behaviour:
helm-M-x(or perhaps spacemacs/helm-M-x-fuzzy-matching)
System Info 💻
– OS: darwin
– Emacs: 28.0.91
– Spacemacs: 0.999.0
– Spacemacs branch: develop (rev. ee3c558)
– Graphic display: nil
– Distribution: spacemacs
– Editing style: vim
– Completion: helm
– Layers:
– System configuration features: ACL GIF GLIB GMP GNUTLS JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP $
The text was updated successfully, but these errors were encountered: