Subject: Re: [External] : bug#13649: boobytrapped dired-do-async-shell-command question

From: Eli Zaretskii <[email-masked]>
Date: Thu, 12 May 2022 08:22:08 +0300

> From: Drew Adams <[email-masked]>
> CC: "[email-masked]" <[email-masked]>,
>         "[email-masked]"
> 	<[email-masked]>,
>         "[email-masked]" <[email-masked]>
> Date: Wed, 11 May 2022 20:27:39 +0000

> > >> ‘C-l’, ‘C-v’, ‘M-v’ don't scroll the original buffer.
> > >
> > > Isn't that expected?  y-or-n-p doesn't need to allow you to edit the
> > > text in the minibuffer.
> > 
> > Maybe this difference is unimportant.  But still remains the need
> > to find a key to show help text from yes-or-no-p.  y-or-n-p now
> > uses C-h to show help, but in yes-or-no-p C-h is useful as
> > a help key prefix.
> 
> Apologies for not following this.
> If you're looking for a key that will show some help,
> maybe consider `?'.

How can we use a printable character in yes-or-no-p, which expects the
user to type readable text?  Are you saying that the answer to
yes-or-no-p can never include a question mark?  And even if we, for
some strange reason, decide that for yes-or-no-p the question mark is
not needed as itself, this issue is AFAIU general to all uses of
reading from the minibuffer, where we definitely cannot usurp any
printable character for help commands.