XYplorer Beta Club

[Using 22.20.0200]

How do I configure a color filter for symbolic links, but NOT mount points? The filter I have set up for mount points is also rendering for symbolic links which I want to see differently.

Maybe prop:#LinkTarget:*:*>000000,00EE00?

highend wrote: ↑15 Sep 2021 15:42 Maybe prop:#LinkTarget:*:*>000000,00EE00?

No effect.

Works fine here for symlinks on local drives

attr:junction ?

That doesn't target normal symbolic links

Still can't get this to work, even when it's the very first filter in the list. I created the symbolic link with mklink /D and the target resides on on a different drive/partition.
Is there some spacing required?

mklink /d is different from creating a normal symlink^^

A drive mounted to a folder has e.g.: And a mklink /d has just the full path for that key: In other words you can only check for those if they are local (no UNC paths involved) via
and regarding your other thread: viewtopic.php?f=3&t=23237&p=189070#p189070

you have to move the entry from here above the entry from the other thread or think about a different solution for the other one...

highend wrote: ↑17 Sep 2021 18:12 mklink /d is different from creating a normal symlink^^

Not sure what you mean by "normal symlink". I am using mklink to create a BSD Unix-style symbolic link, as opposed to an old Unix-style hard link. (The latter requires the /H option.) I'm doing this in Windows of course, not Unix, and not in any Unix shell. Just the basic Command Prompt. I am also making a symbolic link to a directory, not to a file, using the /D option. I am NOT mounting an external drive under a folder (which I use Disk Administrator to do.); that was the subject of my other thread.

The directory is C:\Users\Jerry\AppData\Local\Google which I have relocated to another partition on the same physical drive. The original mklink command (with command prompt) was: I'm not sure if a Windows symbolic directory link (SYMLINKD) is technically a junction or not. In any case, running DIR /A in a Command Prompt shows the following for the link I created: [ And Cygwin's ls command correctly reports that Google is a BDS Unix-style symbolic link to the folder of that name on the P: partition, on the same physical drive: ]

I'm doing the same as Jerry, to have a number of AppData folders actually located in RamDisk, so I use the same command as he did:
mklink /d "C:\Users\JLoftus\AppData\Local\Google\" "R:\JLoftus\Google"

When I use attr:junction in the Color Filters, these folders appear correctly filtered. I too have tried many variants of what Highend posted and I can't get any of those to work for these links as well.

Don't know what exactly the problem is...

f is an usb stick mounted to an empty folder
videos a mklink /d link to another drive

If there is something missing:
Show a screenshot and how that link was created + filter definitions (only the relevant ones)...

weird, I pasted your first line "prop:#JunctionTarget:*:*" directly over mine, which appeared to be the exact same text, and now it works. It also appears (at least for my system) to behave exactly the same as attr:junction ¯\_(ツ)_/¯

Here's what I am seeing (not seeing) using xyplorer /fresh:

The + in front is only there when you manage them via the pencil button, not when entered in the gui where you have the checkbox...

highend wrote: ↑18 Sep 2021 14:23 The + in front is only there when you manage them via the pencil button, not when entered in the gui where you have the checkbox...

Ok, that was it. I removed the leading plus sign, and now it works. Thanks.