New answers tagged

0

If this happens it means that Emacs is having trouble communicating with some subprocess. It is a good idea to leave Emacs and look at its subprocesses from the hosting operating system. For example, on Unix this may be done with pstree $(pidof emacs). This won't show which process is causing the problem, but can at least serve as a kind of sanity check.


2

Elisp relies on cooperative concurrency, so yes, these are "atomic". But I suspect, like Tobias, that this answer won't help you very much because you're probably not asking the right question.


Top 50 recent answers are included