Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explorer Plugin Enhancement: Display Target Path for .lnk Files (in addition to Location Path) #2560

Open
EnigmaSolved opened this issue Feb 11, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@EnigmaSolved
Copy link

EnigmaSolved commented Feb 11, 2024

I think it could be useful in general (as well as for my specific use case, described below) if .lnk shortcut files would display the Target Path (probably with the prefix Target:) below the currently displayed Location Path.

This is particularly useful for the following scenario: I have my Recents folder (%APPDATA%\Microsoft\Windows\Recent Items) indexed by Everything, and I have this folder added to my Quick Access Links in Flow. This allows me to type recent into Flow, then Tab to expand it and > to search a list of recent files and folders (and, of course, a Custom Query Hotkey makes all this even quicker!). But since the Windows Recent Items folder is a special folder it is full only of .lnk files and thus the path information is useless in this case.

Now, while it would be nifty to add special handling for this unique folder (such that instead of displaying File/Folder Location Path at all we only displayed the .lnk Target), the easier and more universally useful thing would be an option to additionally display the Target Path beneath Location Path for all .lnk files. This would allow me to distinguish between multiple Target files of the same name (but different Target locations) and more quickly isolate what I am looking for. :)

Thanks for considering my request!

Edit: Meant to add that I wonder if this request overlaps at all with #2390, at least in terms of some of the backend code?

@EnigmaSolved EnigmaSolved added the enhancement New feature or request label Feb 11, 2024
@jjw24
Copy link
Member

jjw24 commented Feb 24, 2024

Edit: Meant to add that I wonder if this request overlaps at all with #2390, at least in terms of some of the backend code?

That's fine, it's more of a dependency, need to get that code done to get the target path before able to display. Displaying would be easy change.

@EnigmaSolved
Copy link
Author

That's fine, it's more of a dependency, need to get that code done to get the target path before able to display. Displaying would be easy change.

Excellent. That's great to hear!

@EnigmaSolved
Copy link
Author

Edit: Meant to add that I wonder if this request overlaps at all with #2390, at least in terms of some of the backend code?

That's fine, it's more of a dependency, need to get that code done to get the target path before able to display. Displaying would be easy change.

@jjw24 Just bumping this now that #2390 / #2508 is done in hopes that this can get added into the 1.18.0 release (though I will totally understand if it needs to be pushed to a later release). :) Thank you for all of your hard work!

Copy link

github-actions bot commented Jun 4, 2024

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

@github-actions github-actions bot added the Stale label Jun 4, 2024
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
@EnigmaSolved
Copy link
Author

Would still love to see this implemented! :)

@jjw24 jjw24 reopened this Jul 3, 2024
@jjw24 jjw24 removed the Stale label Jul 3, 2024
@EnigmaSolved
Copy link
Author

Thanks much for reopening -- though it is a little thing, I think it will be a really useful enhancement! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants