From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 33336@debbugs.gnu.org
Subject: bug#33336: 26; Document how to restore trashed files
Date: Sun, 11 Nov 2018 19:24:43 +0200 [thread overview]
Message-ID: <83efbra5no.fsf@gnu.org> (raw)
In-Reply-To: <ef62bc42-6bda-4bba-9642-350fd4115490@default> (message from Drew Adams on Sun, 11 Nov 2018 08:47:28 -0800 (PST))
> Date: Sun, 11 Nov 2018 08:47:28 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, 33336@debbugs.gnu.org
>
> But this would presumably require recording the original
> directory, to where each file should be restored (by default).
> And the "restoring" code would need to, e.g., prompt the user
> for some alternative directory if the recorded directory no
> longer existed.
That's exactly what the freedesktop spec does, and the side effect is
that the files in the trash don't have their original names.
> The Emacs doc for this can make clear that Emacs may not
> be able to help in some cases where the system trash bin
> is used, and in such cases users should consult their
> system doc for how to restore a file.
I added there yesterday a sentence saying that restoring files from
trash needs system-dependent tools. I don't think we need to do more.
next prev parent reply other threads:[~2018-11-11 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 19:31 bug#33336: 26; Document how to restore trashed files Drew Adams
2018-11-10 20:00 ` Eli Zaretskii
2018-11-10 21:26 ` Glenn Morris
2018-11-11 3:35 ` Eli Zaretskii
2018-11-11 15:28 ` Eli Zaretskii
[not found] ` <<83o9avab16.fsf@gnu.org>
2018-11-11 16:52 ` Drew Adams
2018-11-11 17:22 ` Eli Zaretskii
[not found] ` <<pzr2fs39qo.fsf@fencepost.gnu.org>
[not found] ` <<83pnvc9thl.fsf@gnu.org>
2018-11-11 16:47 ` Drew Adams
2018-11-11 17:24 ` Eli Zaretskii [this message]
2019-10-12 21:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efbra5no.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33336@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.