GNU bug report logs - #31529
Sentence order in dired.texi(emacs-26)

Previous Next

Package: emacs;

Reported by: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>

Date: Sat, 19 May 2018 16:49:02 UTC

Severity: minor

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31529 in the body.
You can then email your comments to 31529 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#31529; Package emacs. (Sat, 19 May 2018 16:49:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sat, 19 May 2018 16:49:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Sentence order in dired.texi(emacs-26)
Date: Sun, 20 May 2018 01:47:59 +0900
[Message part 1 (text/plain, inline)]
Hi emacs developers.

In dired.texi:240..253

 You can delete empty directories just like other files, but normally
Dired cannot delete directories that are nonempty.  If the variable
@code{dired-recursive-deletes} is non-@code{nil}, then Dired can
delete nonempty directories including all their contents.  That can be
somewhat risky.  If the value of the variable is @code{always}, Dired
will delete nonempty directories recursively, which is even more
risky.  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.  This is handy
when you have marked many directories for deletion and you are very
sure that all of them can safely be deleted.  For every nonempty
directory you are asked for confirmation; if you answer @code{all},
then all the remaining directories will be deleted without more
questions.

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.

How is this?

ayatakesi <ayanokoji.takesi <at> gmail.com>
[Message part 2 (text/html, inline)]

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#31529; Package emacs. (Thu, 07 Jun 2018 23:26:01 GMT) Full text and rfc822 format available.

Message #8 received at 31529 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>
Cc: 31529 <at> debbugs.gnu.org
Subject: Re: bug#31529: Sentence order in dired.texi(emacs-26)
Date: Thu, 07 Jun 2018 19:25:27 -0400
On 19 May 2018 at 12:47, Takesi Ayanokoji <ayanokoji.takesi <at> 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".




Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Sat, 09 Jun 2018 09:01:01 GMT) Full text and rfc822 format available.

Notification sent to Takesi Ayanokoji <ayanokoji.takesi <at> gmail.com>:
bug acknowledged by developer. (Sat, 09 Jun 2018 09:01:02 GMT) Full text and rfc822 format available.

Message #13 received at 31529-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 31529-done <at> debbugs.gnu.org, ayanokoji.takesi <at> gmail.com
Subject: Re: bug#31529: Sentence order in dired.texi(emacs-26)
Date: Sat, 09 Jun 2018 11:59:58 +0300
> From: Noam Postavsky <npostavs <at> gmail.com>
> Date: Thu, 07 Jun 2018 19:25:27 -0400
> Cc: 31529 <at> debbugs.gnu.org
> 
> On 19 May 2018 at 12:47, Takesi Ayanokoji <ayanokoji.takesi <at> 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.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 07 Jul 2018 11:24:03 GMT) Full text and rfc822 format available.

This bug report was last modified 7 years and 77 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.