all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 27940@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>,
	jidanni@jidanni.org
Subject: bug#27940: Recursively delete dir34? (yes, no, all, quit)
Date: Sat, 5 Aug 2017 01:18:01 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708050116210.11976@calancha-pc> (raw)
In-Reply-To: <4ad9397b-7771-4914-85a3-9dd0e998fa0c@default>



On Fri, 4 Aug 2017, Drew Adams wrote:

>>>> Shouldn't the valid-answers be "yes" and "no", not "y" and "n", for
>>>> backward compatibility?
>>> Yes, they should.
>
>>>> Maybe the "!" and "q" parts should be explained?  Or maybe just use
>>>> "yes", "no", "all", and "quite", which are self-explanatory?
>>> Look the updated patch; it's a mix:
>>> 1. uses 'yes', 'no'
>>> 2. '!', 'q', 'help'
>>>   This is similar like `query-replace' does (there is used '!', 'q', and
>>>   '?').  With 'help', a Help buffer is shown with a help message.
>
> I haven't been following this thread, so apologies if I misunderstand.
>
> Is it a good idea to mix `yes-or-no-p'-style (minibuffer) input,
> such as `yes' and `no', with `read-char'-style input, such as `!'
> and `q'?  I don't think so, a priori.  Especially for `!', which
> has worse repercussions in case of a mistake than does `y'.  No?
Agreed.  If you see my first answer i was reluctant to allow the dangerous
operation.
I will use "all" and "quit" instead of "!", "q".

* Question:
Do we need to show the help after this change?





  reply	other threads:[~2017-08-04 16:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 23:26 bug#27940: Recursively delete dir34? (yes, no, all, quit) 積丹尼 Dan Jacobson
2017-08-04  8:25 ` Tino Calancha
2017-08-04  8:31   ` Eli Zaretskii
2017-08-04  9:29     ` Tino Calancha
2017-08-04  9:37       ` Tino Calancha
2017-08-04 12:46       ` Eli Zaretskii
2017-08-04 14:33         ` Tino Calancha
2017-08-04 14:54           ` Eli Zaretskii
2017-08-06  4:52             ` Tino Calancha
     [not found]               ` <87k22e9obk.fsf@ctlt579.codethink.co.uk>
2017-08-09  5:54                 ` Tino Calancha
2017-10-15 14:17                   ` Noam Postavsky
2017-10-16  5:20                     ` Tino Calancha
2017-10-16 10:36                       ` Noam Postavsky
2017-10-16 10:43                         ` Tino Calancha
2017-10-17 12:40                           ` Noam Postavsky
     [not found]         ` <<871sorz9kg.fsf@calancha-pc>
     [not found]           ` <<83tw1nwfhp.fsf@gnu.org>
2017-08-04 15:51             ` Drew Adams
2017-08-04 16:18               ` Tino Calancha [this message]
2017-08-04 16:22                 ` Drew Adams
2017-08-04 16:34                   ` Tino Calancha
     [not found] <<87o9rwxmfz.fsf@jidanni.org>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1708050116210.11976@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=27940@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=jidanni@jidanni.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.