bug#81439: Wrong symlink parsing in dired buffers

Ping!  Eduardo, could you please answer my questions below?

> Cc: [email protected]
> Date: Thu, 23 Jul 2026 10:19:15 +0300
> From: Eli Zaretskii <[email protected]>
> 
> > From: Eduardo Duenez <[email protected]>
> > Date: Sun, 19 Jul 2026 16:12:03 +0000
> > 
> > ls --dired reports a single byte range spanning linkname -> target for
> > symlinks; dired-filename text property is then set on the full string
> > linkname -> target, causing
> > Dired-move-to-end-of-filename
> > to return the position after the target rather than after the link name.
> > 
> > The observed behavior is that, in Dired buffers, all symlinks are
> > displayed as broken (yellow text on orange background).  In Dired's
> > view, a symlink `linkname` pointed to `target` becomes a file literally
> > named `linkname -> target` which, of course, does not exist in the
> > filesytem; therefore, any and all attempted Dired operations on the
> > symlink result in a minibuffer message "File no longer exists; type g
> > to update Dired buffer". For the reasons explained, refreshing with g
> > does not change or fix the problem in the dired buffer.
> 
> I cannot reproduce this.  Are you sure you use GNU 'ls' from GNU
> Coreutils?  If so, what does "ls --version" report?
> 
> 
> 
>