unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>, "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: eggert@cs.ucla.edu, 28792@debbugs.gnu.org
Subject: bug#28792: 26.0.60; Deleting to a custom trash directory in Dired gives error
Date: Thu, 12 Oct 2017 13:02:31 +0000	[thread overview]
Message-ID: <CAFyQvY2WvWc2FEhTi_=ST6SdbjSxoZ1UCgKZ6gQCWggoiYfdKg@mail.gmail.com> (raw)
In-Reply-To: <831sm8mskc.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On Thu, Oct 12, 2017 at 8:58 AM Eli Zaretskii <eliz@gnu.org> wrote:

> This use case raises an interesting question: what should be the
> behavior of delete-by-moving-to-trash when the Trash directory already
> includes a directory by the same name as the non-directory file being
> deleted?  Are files in the Trash directory generally unimportant
> enough to disregard these situations, or does this use case run afoul
> of the ability to restore the trashed files later?
>

The fact that the user deleted the files means that the files were not
important. If the user deleted them by mistake, then the trash serves as a
last-resort to restore the files from. Trash is not a "backup".. so unlike
the Emacs backup, there shouldn't be a need to store multiple revisions of
trash.

IMO, if a file or a directory exists by the same name in trash, the
move-file-to-trash should just overwrite that.. if a foo file already
exists and a foo/ dir is being trashed, then just delete the old trashed
foo file and replace with the newly trashed foo/ dir.
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1481 bytes --]

  reply	other threads:[~2017-10-12 13:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  3:26 bug#28792: 26.0.60; Deleting to a custom trash directory in Dired gives error Kaushal Modi
2017-10-12  3:36 ` Kaushal Modi
2017-10-12  3:51   ` Kaushal Modi
2017-10-12 12:50     ` Göktuğ Kayaalp
2017-10-12 12:58       ` Eli Zaretskii
2017-10-12 13:02         ` Kaushal Modi [this message]
2017-10-12 13:37         ` Göktuğ Kayaalp
2017-10-12 12:58       ` Kaushal Modi
2017-10-12 13:16         ` Eli Zaretskii
2017-10-12 13:31           ` Kaushal Modi
2017-10-12 13:44             ` Eli Zaretskii
2017-10-12 14:02             ` Andreas Schwab
2017-10-12 14:06               ` Kaushal Modi
2017-10-12 15:07                 ` Kaushal Modi
2017-10-12 15:15                   ` Eli Zaretskii
2017-10-12 15:27                 ` Andreas Schwab
2017-10-12 15:31                   ` Kaushal Modi
2017-10-12 20:25                   ` Paul Eggert
2017-10-12 21:41                     ` Kaushal Modi
2017-10-15  7:18                       ` Paul Eggert
2017-10-15 13:35                         ` Kaushal Modi
2017-10-15 13:47                           ` Noam Postavsky
2017-10-12 14:24           ` Noam Postavsky
2017-10-12 14:43             ` Drew Adams
2017-10-12 15:07               ` Andreas Schwab
2017-10-12 15:10                 ` Drew Adams
2017-10-12 13:34 ` Tino Calancha

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='CAFyQvY2WvWc2FEhTi_=ST6SdbjSxoZ1UCgKZ6gQCWggoiYfdKg@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=28792@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=self@gkayaalp.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).