[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon, 20 Jun 2016 07:17:29 -0700 (PDT)
Can someone check this recipe for crashing emacs please?
Ubuntu 16.4 running vanilla Unity -- yes this is likely related to X/WM stuff
1 Start emacs with
$ emacs --daemon
init contains just this 2 line function:
(defun kill-later ()
(run-with-timer 1 nil 'save-buffers-kill-emacs))
$ emacsclient -n -c somefile
3. Write something there (ie dirty it and get a '*' in modeline)
4. Remove the frame by clicking the X in the frame
5. Try to kill emacs with
$ emacsclient -c -e '(kill-later)'
6. top shows emacs running at 100% usage
7. killing it in top causes an apport crash
Note 1 Why is kill-later defined in that round-about way?
Because directly invoking save-buffers-kill-emacs from emacsclient
makes the -n option ignored
This in turn causes the save-buffers-kill-emacs to say "You have clients"
Note 2 If an emacs frame is present the save-buffer dialog appears as expected
and there is no issue
|[Prev in Thread]
||[Next in Thread]|