-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
function definition is void: ad-Advice-newline-and-indent #3172
Comments
I'm not sure what could be causing this. I don't think it is a Doom issue, specifically, because I avoid anonymous advice in Doom on principle. It makes debugging their issues so much harder. There is a plugin somewhere (or perhaps in your private config) that advises From within Doom, try |
Try running Alternatively, a user on our Discord claims that deleting |
Searching the load path doesn't show anything except this: Running
Thanks! This worked! (I also had to remove |
So it's definitely an org package, these are the packages that were removed and rebuilt:
|
I can also confirm that deleting |
I ran into this issue as well, after upgrading Doom by nuking For reference, a list of the
|
I ran into this today. Rather than wholesale Here are my results:
Based on that seems like it's probably something to do with |
But I don't use my org-*
|
@AloisJanicek Weird. Might have been a false positive or my test steps might not have been complete / fresh. It stands though, that removing only those three packages fixed it. Might have been one of the others and I didn't test properly afterward -- which is more than likely 😅 |
This happened again to me today and I got a little more detail on the issue / what file is getting messed up. The cause of the error is the byte compiled function I also ran Since I can continually get the build to produce the broken |
I'm having the same issue, and if it matters I just updated to emacs 27.1. No fix that I tried worked.
When launching emacs, I get a If I then do a I tried to run |
To make progress, is there a way to know which function is advised, so that I can remove the advice? |
This must be a load-order issue at compile time. Try adding this to the top of (package! org-mode
:recipe (:host github
:repo "emacs-straight/org-mode"
:files ("*.el" "lisp/*.el" "contrib/lisp/*.el"))
:pin "a1e5bee5cb9c34ceb8226597605a49638bee7cec") Then run |
Running into this again, here's what I did
At this point, I get the
This fixes the
|
The user's private packages.el is read first, to ensure disabled packages are recorded as soon as possible, however, this means private packages are recorded early into `doom-packages`, and so are built first (and thus, before org-mode, which is later registered by the lang/org module). This compilation order can cause lots of issues with org packages loading the older, built-in version of org included with Emacs, instead of the newer org-mode. May address #3172
As of f3740d4 this issue should be fixed (org packages should build in the right order from now on). For folks coming from older versions of Emacs, please update doom and run Let me know if that doesn't fix the issue and I'll reopen it. |
I ran:
and the bug returned.
and it fixed the issue. BUT, once I ran another:
the bug is back once again. |
@archiif Just in case you're on a particular commit of Doom where git -C ~/.emacs.d pull
doom sync -u
doom build
The crux of the issue is that org plugins are being compiled in the wrong order. For example, if f3740d4 fixed the case where private packages (org plugins) were all installed before |
I'm currently having the same issue as well. I don't have org manually installed, and I can provide my config files if need be. I attempted to load org with |
I have the same experience as @archiif using I saw Here is the debug trace:
|
I am experiencing the same problem on my laptop, As @bsermons mentioned, the issue is resolved by disabling I've applied a bandaid to the problem with the following hook.
Hopefully smarter people will find a better solution, or the issue will magically resolve itself. |
Want to add to the weirdness of this problem, I just updated my arch linux today and randomly started getting this issue. Must be something to due with some dependencies of emacs/doom. |
Also seeing this after an upgrade of arch after completely wiping the entire install and starting from scratch. Disabling electric-indent-mode in org seems to be a working band-aid but it would be good to know what's actually going on. |
Same here with the 27.1 system upgrade.
As said above, with the force update, it still does not work. |
I guess I can add that when using native comp instead of 27.1, the issue goes away. |
On 27.1, this is my exact situation. "Manually building" makes it work whereas doom build causes the bug to reappear. |
Same issue with emacs 27.1. The delete .local/straight/repos/org-* trick still works, but is not ideal. |
Sorry folks. No closer to figuring out why this happens. I've yet to reproduce it on any of my NixOS systems or Arch/MacOS VMs, with 26.3, 27.1 and 28 (gccemacs). I have no other leads. At the very least, make sure you're on the very latest version of Doom (which will install the latest You could try searching your load-path with |
I have the same problem runing 27.1 and 28 on arch, i also noticed inserting a new line deletes everything after the cursor and pressing u doesn't undo this behaviour. running the specified command returns the following: This also only seems to occure for me if the line is over the 80 char limit so its possibly a problem with the TPU-edt package |
I'm having the same issue, I'm on 27.1 on OSX right now, and when I run that search I get hits from I think I can reliably reproduce this on both OSX and Arch if you want to screenshare - let me know and we can find a time. I'm in the discord. |
The problem starting again for me. One recent change is that I unpinned org-journal (I need some recent bug fixes). I'm running with #3172 (comment) (disabling electric-indent-mode for org file) at the moment, and it alleviates the issue. |
I just saw this on the org-mode mailing list. I think it is related:
|
I've recently started getting this error as well on macOS, will investigate |
As of right now, nothing works. All that stated above have not changed even a bit. I have no idea how to change that. Can you please help with it? |
As for said debugger and running to determine what exactly is wrong, there is no new contribution either. i.e. Same problem/ result with all methods stated above. But is that what we have to live with right now regarding this problem. The system is manjaro Linux, and the emacs version is 27.1. |
@jorschach-g have you tried this? (add-hook 'org-mode-hook (lambda () (electric-indent-local-mode -1))) |
Yes! That actually worked. So if there is no contradiction to other use cases (i.e. reference to other packages that use this entrance under org-mode), I believe we found one solution [not particularly easy one for me] that ultimately worked for this problem. Then we can close this now? @hlissner Please check this solution. |
Unfortunately, this is a workaround, not a solution. I'll leave this open until the root of the issue is addressed. |
This work around works for me as well. This seems to be a better workaround than the old "delete straight/org ...". |
May address #3172 and some issues with certain files failing to byte-compile because certain dependencies were missing at compile-time.
Doom sync and build yesterday, and I ran into the exact same problem on archlinux. Tried
with no luck. The temporary work-around proposed above did work. (add-hook 'org-mode-hook (lambda () (electric-indent-local-mode -1))) But as @hlissner commented, it's not resolving the root of the issue. |
Actually, pressing enter when zoomed into a node, and in evil's insert mode. The issue doomemacs/doomemacs#3172 mentions the same errors I ran into.
This issue has been automatically marked stale because of a lack of recent activity. If this issue is still valid, reply to it or remove the label or it will be closed in 7 days. |
What did you expect to happen?
Pressing
RET
inorg-mode
inserts a new lineWhat actually happened?
Triggers an error:
Symbol's function definition is void: ad-Advice-newline-and-indent
Additional details:
Backtrace:
Steps to reproduce:
RET
to insert a new line. Nothing happens.System information:
The text was updated successfully, but these errors were encountered: