[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: yes-or-no-p prompt conditionally broken in master?

From: Marcin Borkowski
Subject: Re: yes-or-no-p prompt conditionally broken in master?
Date: Thu, 03 Sep 2015 21:26:53 +0200

On 2015-09-03, at 20:25, Dmitry Gutov <address@hidden> wrote:

> On 09/03/2015 09:18 PM, Marcin Borkowski wrote:
>> The whole point of yes-or-no-p is to make user type something less
>> convenient (and less probable to hit accidentally) then just `y'.
> And as a power user, I've found it immensely useful not to type that 
> "less convenient" thing. If it were a problem in my usage, I'd probably 
> have noticed.

I understand.  (In fact, AFAIK, confirm-kill-emacs is the only place
I ever used yes-or-no-p, and quite often I disable even y-or-n-p,
e.g. in the case of (setq TeX-save-query nil).

OTOH, being a power user does not help _at all_ when e.g. working on
someone else's computer with a different keyboard.  ;-)

>> FWIW, I have (setq confirm-kill-emacs #'yes-or-no-p) in my init.el.
>> I just can't count the times I pressed C-x C-c by mistake.
> It's a personal choice. I don't kill Emacs too often by mistake, and 
> even if I press that conbination, usually I would be greeted with 
> prompts about modified buffers and running processes.

You're probably right.  It's an ancient setting in my init.el, and most
probably I don't need it anymore.  When I was a beginner, though, it
happened to me all the time, and I deeply appreciated the sheer
existence of both y-or-n-p and yes-or-no-p.


Marcin Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

reply via email to

[Prev in Thread] Current Thread [Next in Thread]