* bug#29313: Replace gnus-yes-or-no-p with yes-or-no-p?
@ 2017-11-16 1:49 Eric Abrahamsen
2017-11-16 2:00 ` Noam Postavsky
0 siblings, 1 reply; 3+ messages in thread
From: Eric Abrahamsen @ 2017-11-16 1:49 UTC (permalink / raw)
To: 29313
Gnus has the following defined:
(defun gnus-y-or-n-p (prompt)
(prog1
(y-or-n-p prompt)
(message "")))
(defun gnus-yes-or-no-p (prompt)
(prog1
(yes-or-no-p prompt)
(message "")))
I wonder if I'm missing something here: for the life of me I can't see
how the behavior is different from the built-ins. The built-ins don't
put anything in the minibuffer, why would we'd have to blank it? Is this
historical?
I'm putting this on my list of little Gnus tweaks to eventually commit,
unless someone points out why I shouldn't.
Gnus v5.13
GNU Emacs 27.0.50 (build 5, x86_64-pc-linux-gnu, GTK+ Version 3.22.25)
of 2017-11-09
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#29313: Replace gnus-yes-or-no-p with yes-or-no-p?
2017-11-16 1:49 bug#29313: Replace gnus-yes-or-no-p with yes-or-no-p? Eric Abrahamsen
@ 2017-11-16 2:00 ` Noam Postavsky
2017-11-16 2:11 ` Eric Abrahamsen
0 siblings, 1 reply; 3+ messages in thread
From: Noam Postavsky @ 2017-11-16 2:00 UTC (permalink / raw)
To: Eric Abrahamsen; +Cc: 29313
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Gnus has the following defined:
>
> (defun gnus-y-or-n-p (prompt)
> (prog1
> (y-or-n-p prompt)
> (message "")))
>
> (defun gnus-yes-or-no-p (prompt)
> (prog1
> (yes-or-no-p prompt)
> (message "")))
>
> I wonder if I'm missing something here: for the life of me I can't see
> how the behavior is different from the built-ins. The built-ins don't
> put anything in the minibuffer, why would we'd have to blank it? Is this
> historical?
They put the prompt in the minibuffer, don't they? (not sure why it's
important to blank that out though)
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#29313: Replace gnus-yes-or-no-p with yes-or-no-p?
2017-11-16 2:00 ` Noam Postavsky
@ 2017-11-16 2:11 ` Eric Abrahamsen
0 siblings, 0 replies; 3+ messages in thread
From: Eric Abrahamsen @ 2017-11-16 2:11 UTC (permalink / raw)
To: Noam Postavsky; +Cc: 29313
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Gnus has the following defined:
>>
>> (defun gnus-y-or-n-p (prompt)
>> (prog1
>> (y-or-n-p prompt)
>> (message "")))
>>
>> (defun gnus-yes-or-no-p (prompt)
>> (prog1
>> (yes-or-no-p prompt)
>> (message "")))
>>
>> I wonder if I'm missing something here: for the life of me I can't see
>> how the behavior is different from the built-ins. The built-ins don't
>> put anything in the minibuffer, why would we'd have to blank it? Is this
>> historical?
>
> They put the prompt in the minibuffer, don't they? (not sure why it's
> important to blank that out though)
Oh! The prompt is *left* in the minibuffer. Of course I figure that out
moments after making the bug report.
Well, at least the functions actually *do* something. Whether that's
worth doing is another question, but I'll leave it for now.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-11-16 2:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-16 1:49 bug#29313: Replace gnus-yes-or-no-p with yes-or-no-p? Eric Abrahamsen
2017-11-16 2:00 ` Noam Postavsky
2017-11-16 2:11 ` Eric Abrahamsen
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).