4

What would cause emacs to "mostly" freeze when creating an org agenda?

I say "mostly" because when you type C-g, it does show "Quit" in the minibuffer, and the time logging number in the minibuffer still increments. Nothing else seems to respond though that I could think of.

I was only able to get emacs to respond by getting the emacs pid with ps aux | grep emacs and then running kill -SIGUSR2 {PID}.

After that, emacs opened a buffer with:

Debugger entered--Lisp error: (quit)
  redisplay_internal\ \(C\ function\)()

What can I do to prevent this behavior?

3
  • 1
    Does this happen when you start emacs with emacs -q?
    – Tobias
    Apr 7, 2016 at 5:18
  • It happens rarely, and is only reproducible within a session. If it happens once, it will likely happen again, but I can't get it to happen reliably. I haven't seen it happen with emacs -q, but I haven't tried running a -q session for days opening 100's of files (and even when I do that with a normal session I usually have no issues).
    – avv
    Apr 15, 2016 at 17:52
  • Find an answer? Getting a similar issue May 22, 2018 at 20:29

1 Answer 1

0

Check your org-agenda-files variable for file duplicates that are in separate directories.

Context: I had the same issue with Doom Emacs after I had copied org files to a new directory and added the newly copied files to the org-agenda-files variable without removing the original files from org-agenda-files.

Remove the unneeded files from org-agenda-files by opening the offending file in a buffer and typing C-c ] or M-x org-remove-file RET.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.