From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
59986@debbugs.gnu.org, bugs@gnu.support
Subject: bug#59986: 30.0.50; Can't trash file with broken symbolic link
Date: Thu, 15 Dec 2022 17:54:32 +0300 [thread overview]
Message-ID: <Y5s1KMHPYXU/FW4l@protected.localdomain> (raw)
In-Reply-To: <83v8mdkunj.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-12-15 10:12]:
> Sorry, I was confused when I wrote the question: I was actually
> interested in the file being moved to trash, not the file already in
> the trash.
If there is dangling symlink in Trash then even if the file to be
deleted to Trash exists and is not symlink, I get the same error
message:
To reproduce:
1. Create dangling symlink:
$ ln -s something more
2. Delete the file `more' to Trash by using Emacs
3. Create new file
$ touch more
4. Try deleting file `more' by moving to Trash, there is error:
file-already-exists: File already exists: /home/data1/protected/tmp/Trash/more
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-12-15 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 6:51 bug#59986: 30.0.50; Can't trash file with broken symbolic link Jean Louis
2022-12-13 3:51 ` Michael Heerdegen
2022-12-13 8:00 ` Jean Louis
2022-12-13 12:42 ` Eli Zaretskii
2022-12-13 13:49 ` Jean Louis
2022-12-13 14:44 ` Eli Zaretskii
2022-12-13 19:24 ` Jean Louis
2022-12-14 12:29 ` Eli Zaretskii
2022-12-15 0:13 ` Michael Heerdegen
2022-12-15 7:12 ` Eli Zaretskii
2022-12-15 14:54 ` Jean Louis [this message]
2022-12-15 16:07 ` Eli Zaretskii
2022-12-16 6:39 ` Jean Louis
2022-12-16 15:56 ` Eli Zaretskii
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=Y5s1KMHPYXU/FW4l@protected.localdomain \
--to=bugs@gnu.support \
--cc=59986@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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).