Re: Crash force-deleting the only frame

[David Kastrup]

Chong Yidong <address@hidden> writes:

> Andreas Schwab <address@hidden> writes:
>
>>> Okay, I looked at this, and now I'm not sure there's any bug.  If you
>>> specify an --eval command-line arg that deletes the only frame, what
>>> else could Emacs possibly do other than abort execution?
>>
>> IMHO there are two options:
>>
>> - refuse to delete the frame despite FORCE,
>> - exit gracefully.

3: stay around in case gnuclient will open another window.  But I
don't think that emacsclient has this functionality, and we'd probably
need the multi-tty branch.

> The latter is not difficult to arrange:
>
> *** emacs/lisp/startup.el.~1.419.~    2006-09-26 13:10:39.000000000 -0400
> --- emacs/lisp/startup.el     2006-11-01 17:55:11.000000000 -0500
> ***************
> *** 1877,1883 ****
>                            (setq line 0)
>                            (unless (< column 1)
>                              (move-to-column (1- column)))
> !                          (setq column 0))))))))
>   
>         ;; If 3 or more files visited, and not all visible,
>         ;; show user what they all are.  But leave the last one current.
> --- 1877,1884 ----
>                            (setq line 0)
>                            (unless (< column 1)
>                              (move-to-column (1- column)))
> !                          (setq column 0))))))
> !       (unless (frame-live-p (selected-frame)) (kill-emacs nil))))

Does this not do to much when we delete the last frame on the current
display/terminal, but there are still frames on other displays?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum