unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 59986@debbugs.gnu.org
Subject: bug#59986: 30.0.50; Can't trash file with broken symbolic link
Date: Tue, 13 Dec 2022 22:24:52 +0300	[thread overview]
Message-ID: <Y5jRhF8NgDPK6UwA@protected.localdomain> (raw)
In-Reply-To: <83359jpdm1.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2022-12-13 17:45]:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47135
> > 
> > I can't locate on that page what you mean with recipe? Which one?
> 
> I mean your original description that opened the bug.

For original one, I cannot know.

Now I see that if symbolic link exists in Trash, such as:

1661195272884.jpg -> hyperscope/7/3/9/8/7/2022/11/2022-11-27/1661195272884.jpg

then the same symbolic link from ~/ cannot be deleted by moving to
Trash because it will say that file already exists.

Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  reply	other threads:[~2022-12-13 19:24 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 [this message]
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
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=Y5jRhF8NgDPK6UwA@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).