[Bug] traversal changes folder context for symlinks / Aliases

[creechy]

In version 1.7.4, it seems like there is some new functionality to support files that are symlinks (maybe also called Aliases).

I have a problem where I have some images symlinked to another folder. When I view a symlinked image then try to navigate to other images in the folder, it seems like FlowVision changes the folder context to where the image actually lives, which, in my case contains additional images I'm not interested in.

For example, say I have this structure

main/
   image1.jpg -> ../work/image1.jpg
   image2.jpg -> ../work/image2.jpg
work/
  image1.jpg
  image2.jpg
  image3.jpg
  image4.jpg

When say I navigate to main/image1.jpg then use keyboard navigation (left/right arrow) I will end up viewing image3.jpg and image3.jpg even though they are not in the folder main/.

Hope that makes sense.

I think this may be related to the Alias support recently added - #155

I just tried version 1.6.9, the last version before the Alias support, and traversal stays in the folder.

[netdcy]

Yes, this is a known limitation that arose because it wasn’t considered during the initial design, making subsequent refactoring quite costly. For now, we’ve adopted a compromise implementation, which is why “partial Alias support” appears in the release notes. As for your use case, I had assumed most users wouldn’t create Aliases for a large number of individual images.

Full‑fledged support would require substantial changes; while AI could assist, we’d need to thoroughly assess the potential for introducing bugs, which may take some time.