From: Jean Louis <bugs@gnu.support>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 41834@debbugs.gnu.org
Subject: bug#41834: 28.0.50; Dired-x: Y makes symlink with error: File is a symlink to a nonexistent target
Date: Sat, 13 Jun 2020 16:59:43 +0300 [thread overview]
Message-ID: <20200613135943.GJ21905@protected.rcdrun.com> (raw)
In-Reply-To: <87o8pnumxc.fsf@web.de>
* Michael Heerdegen <michael_heerdegen@web.de> [2020-06-13 16:16]:
> Jean Louis <bugs@gnu.support> writes:
>
> > I have only pressed Y and the symlink is created in such way that it
> > does not work.
>
> So you say you just confirm the suggested link name and you get an
> invalid link?
Yes, I pressed Y and I get invalid link
> I noticed that the path to your target dir contains a duplicate
> directory file name "/Pictures/Pictures/". These directories do really
> exist like this in your file system, yes?
Of course, I gave you real time situation with screenshots and real
directories.
Thank you for noticing, maybe that is exactly the problem, so the
directory:
/home/data1/protected/Media/Pictures/Pictures
is actually symlink to:
/home/data1/protected/Work/2nd-Dynamic/Division_3/Dept_9/Pictures
Maybe it is related to calculation of the relative symlink.
> I try to find out if there is something special in your use case.
> Personally I use Y very frequently and have never seen a problem like
> this.
I use it frequently too and this is first time that I have encountered
this.
prev parent reply other threads:[~2020-06-13 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 10:14 bug#41834: 28.0.50; Dired-x: Y makes symlink with error: File is a symlink to a nonexistent target Jean Louis
2020-06-13 10:52 ` Michael Heerdegen
2020-06-13 11:06 ` Jean Louis
2020-06-13 11:40 ` Michael Heerdegen
2020-06-13 11:57 ` Jean Louis
2020-06-13 12:05 ` Eli Zaretskii
2020-06-13 12:55 ` Jean Louis
2020-06-13 13:15 ` Michael Heerdegen
2020-06-13 13:59 ` Jean Louis [this message]
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=20200613135943.GJ21905@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=41834@debbugs.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).