unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31529-done@debbugs.gnu.org, ayanokoji.takesi@gmail.com
Subject: bug#31529: Sentence order in dired.texi(emacs-26)
Date: Sat, 09 Jun 2018 11:59:58 +0300	[thread overview]
Message-ID: <831sdgtjw1.fsf@gnu.org> (raw)
In-Reply-To: <878t7q2n88.fsf@gmail.com> (message from Noam Postavsky on Thu, 07 Jun 2018 19:25:27 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Date: Thu, 07 Jun 2018 19:25:27 -0400
> Cc: 31529@debbugs.gnu.org
> 
> On 19 May 2018 at 12:47, Takesi Ayanokoji <ayanokoji.takesi@gmail.com> wrote:
> 
> > I think the sentence
> >
> > Even if you have set @code{dired-recursive-deletes} to
> > @code{nil}, you might want sometimes to delete recursively directories
> > without being asked for confirmation for all of them.
> >
> > and the sentence
> >
> > This is handy
> > when you have marked many directories for deletion and you are very
> > sure that all of them can safely be deleted.
> >
> > is reverse order.
> 
> I don't think they're reversed, "this is handy" refers to the previous
> sentence "delete [...] without being asked [...] for all of them".
> Maybe it would be clearer if the second sentence said "For example"
> instead of "This is handy".
> 
> Also, I'd say the word "recursively" *is* reversed with one of the words
> around it, it should be either "recursively delete directories" or
> "delete directories recursively".

OK, I clarified the text there, and I'm marking the bug done.





      reply	other threads:[~2018-06-09  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 16:47 bug#31529: Sentence order in dired.texi(emacs-26) Takesi Ayanokoji
2018-06-07 23:25 ` Noam Postavsky
2018-06-09  8:59   ` Eli Zaretskii [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=831sdgtjw1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31529-done@debbugs.gnu.org \
    --cc=ayanokoji.takesi@gmail.com \
    --cc=npostavs@gmail.com \
    /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 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).