Subject: bug#38219: closed (Re: bug#38219: Error on leaving Ediff after killing vital buffer)

From: [email-masked] (GNU bug Tracking System)
Date: Mon, 18 Nov 2019 21:55:11 +0000

Your bug report

#38219: Error on leaving Ediff after killing vital buffer

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
38219: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38219
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#38219: Error on leaving Ediff after killing vital buffer
From: Juri Linkov <[email-masked]>
To: martin rudalics <[email-masked]>
Cc: Richard Copley <[email-masked]>, [email-masked]
Date: Mon, 18 Nov 2019 23:53:29 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

>> You could argue that 'ediff' already breaks
>>
>> (defalias 'y-or-n-p 'yes-or-no-p)
>>
>> They would probably say that consulting 'this-command' after a
>> 'y-or-n-p' "has worked ever since".  Guess whose argument wins.
>
> Good example.  This means that 'ediff' is broken, here is the fix:

Now pushed and closed. 

Subject: Error on leaving Ediff after killing vital buffer
From: Richard Copley <[email-masked]>
To: [email-masked], Juri Linkov <[email-masked]>
Date: Fri, 15 Nov 2019 13:50:32 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

If you kill one of Ediff's vital buffers, then try to leave Ediff (by
typing q in the control window), there is an error.

The error is:
ediff-visible-region: You have killed a vital Ediff buffer---you must leave
Ediff now!

Recipe from 'emacs -Q' (Windows GUI build):

* Visit a file under version control with unstaged changes.
* [M-x ediff-revision RET RET RET RET]
* In the main frame, kill one of the buffers being diffed
* In the Ediff control window frame, type [q y]

Bisected to this commit:

a26a8cc1c85f29fb11209c16d53a8ae4e4ab7ced
Author: Juri Linkov <[email-masked]>
Date: Sun Nov 10 00:04:13 2019 +0200

'y-or-n-p' now uses the minibuffer to read 'y' or 'n' answer (bug#38076)