Yeah to provide atomicity of the file operation we do not support symbolic link to prevent potential data corruption.

If more request to this we can consider switching to an embedded database rather than plain text.

My programs plugin recursively tried to count symlinks in the start menu, which is why the log weighed 15 GB

My programs plugin recursively tried to count symlinks in the start menu, which is why the log weighed 15 GB

huh that's a different issue. Could you fire another one? Also could you show some snippet inside the very large log that count symlink?

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

@taooceros Wouldn't this be trivial to solve by simply first resolving the path, then call ReplaceFile()?

@taooceros Wouldn't this be trivial to solve by simply first resolving the path, then call ReplaceFile()?

I guess it makes sense? I am not quite familiar with symlink.

Are you proposing we resolve the final path and then replace the final file instead of the symlink?

Are you proposing we resolve the final path and then replace the final file instead of the symlink?

Correct. If the problem is a path that includes one or more symlinks being passed to one of the functions, it should work to just first resolve it (that is, the resolved path no longer contains any symlink(s), it'll just be a simple absolute path) and then invoke the function.
I don't use C# but just intuitively I would guess that should work.

My programs plugin recursively tried to count symlinks in the start menu, which is why the log weighed 15 GB

huh that's a different issue. Could you fire another one? Also could you show some snippet inside the very large log that count symlink?

Ouch.... I didn't see the notification. I can try to repeat that bug. It's done in a couple of minutes.

@ashish0kumar try this build? https://ci.appveyor.com/project/JohnTheGr8/flow-launcher/builds/51303267/artifacts

@taooceros I tested the build, and I'm now able to symlink files without any issues. Thanks for the fix!