From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44217@debbugs.gnu.org, Jean Louis <bugs@gnu.support>
Subject: bug#44217: none
Date: Tue, 27 Oct 2020 21:20:32 +0100 [thread overview]
Message-ID: <87mu07to8f.fsf@gmx.de> (raw)
In-Reply-To: <87a6w736qm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 27 Oct 2020 18:42:57 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> However, in "~/.local/share/Trash/info/aaa.trashinfo" there is
>>
>> Path=/ssh%3aford%3a/tmp/aaa
>>
>> This will be unexpected, at least for tools which try to restore trashed
>> files.
>
> Yes, perhaps the .trashinfo file shouldn't be created in these
> instances...
It is created according to the XDG spec. We shouldn't fail to do it. And
maybe, Emacs will add an own trash recovery function, which would be
able to handle such remote paths?
>> However, perhaps Tramp shall call move-file-to-trash when deleting
>> remote files, argument TRASH and variable delete-by-moving-to-trash are
>> non-nil? Instead of calling the remote trash command?
>
> Yes, I think that would make sense.
>
> But if trash-directory is nil, and there is a remote trash command...
> perhaps Tramp should call the remote trash command anyway? (Many
> permutations of possibly correct behaviour here. :-/)
We must be consistent. A remote trash command will move the file to the
remote trash can. Tramp, using move-file-to-trash, will move the file to
the local trash can. A user couldn't know, whether a trash can for a
remote file will be located locally or remotely. So we shall use either
a remote or a local trash can, and not mixed.
The local trash can can be used always. The remote trash can can be used
only, when the remote system offers the "trash" command. This doesn't
happen by default.
Best regards, Michael.
next prev parent reply other threads:[~2020-10-27 20:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 19:38 bug#44217: 28.0.50; Incorret during delete in Tramp: Trashing...done Jean Louis
2020-10-26 11:14 ` bug#44217: bug#44216: " Lars Ingebrigtsen
2020-10-26 11:51 ` Jean Louis
2020-10-26 16:56 ` Michael Albinus
2020-10-26 17:01 ` Eli Zaretskii
2020-10-26 13:11 ` Michael Albinus
2020-10-26 13:17 ` Lars Ingebrigtsen
2020-10-26 15:35 ` Michael Albinus
2020-10-27 7:42 ` Lars Ingebrigtsen
2020-10-27 15:32 ` Michael Albinus
2020-10-27 17:17 ` Jean Louis
2020-10-27 20:12 ` Michael Albinus
2020-10-28 10:54 ` Jean Louis
2020-11-01 11:59 ` Michael Albinus
2020-11-01 12:36 ` Jean Louis
2020-11-01 13:03 ` bug#44217: " Michael Albinus
2020-11-01 13:33 ` Jean Louis
2020-11-01 14:48 ` Michael Albinus
2020-10-27 17:42 ` bug#44217: (no subject) Lars Ingebrigtsen
2020-10-27 20:20 ` Michael Albinus [this message]
2020-10-28 9:27 ` bug#44217: none Lars Ingebrigtsen
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=87mu07to8f.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=44217@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=larsi@gnus.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 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).