PowerToys Run: Adding Clear Functionality For Older Files/Directories

[RadhiRasho]

Description of the new feature / enhancement

I use VS Code a lot and switching/opening directories where my projects are has been made so much easier due to PowerToys Run.

One thing I find lacking is the inability to clear out older/non-existent files/directories. This happens a lot especially when working with stuff like older project that were delete.

What I'm requesting is a way to clear out history of sorts, or individually get rid of files and directories that no longer exist.

In the image above, you see a bunch of folder/workspaces (I tend to work a lot with Development Containers, hence the extra (Dev Container) bit there)

Except none of those exist and yet they are still in the searchable list/history.

Scenario when this would be used?

Say I created a folder, name it FolderA, then I go to that folder and right click and open with vscode, that folder should now be in history/list of available options via the vs code plugin { FolderA, so I'm easily able to access it.

Created FolderA

Opened FolderA using Open With VS Code:

Used {FolderA to open it using PowerToy Run:

Now, Say I then decide FolderA is a terrible name, and that it shouldn't exist anymore, so I delete it completely, even from the trash bin.

Sense the folder no longer exists, I shouldn't see it in the list of results anymore, right? Wrong, it still shows up, only it leads to nowhere now:

Supporting information

No response

[RadhiRasho]

I've also noticed that Dev Container directories seem to shows a random Id sequence on all containers:

unsure whether adding this here or I should create a new issues.

this issue started occurring around version 0.72

EDIT: Moved to here: #32275

[kjohnsen]

Also, besides removing nonexistent workspaces, a related useful feature would be to sort workspaces with the same name so the most recently opened ones are on top. Having opened the same repo on multiple WSL distros, I find myself having to go to the bottom every time to get to Ubuntu-22, even though it's the main one I use

[htcfreek]

@RadhiRasho
Is this issue still existing? Thought someone implemented a clean-up feature in one if the last releases (#30488). Can you please double check.

And if I understand correctly there are two issues:

1. Clean up of inaccessible workspaces.
2. The random id of dev containers.

If yes please split the issue into two separate ones that we can track the issues and work better.

[RadhiRasho]

@htcfreek
It looks like the issue with non-existent directories has been cleaned up on the windows local disk side of things. Sorry I was not aware of that.

However the issue seems to persist when it comes to CodeSpaces, SSH-Remotes, and Development Containers (which I use often) as I have a list of non-existent ones still being displayed here:

Anything within the workspaces "Work" and Rando has been deleted, but is still being displayed.

Now that I've taken a look at issue #30488 I notice that it's specifically checking for WSL and Local and is ignoring the rest of the possible Remote workspaces. I could attempt to fix that issue if that's alright?

As for the issue with the Random ID of dev containers, I believe that is brought about due to the extra information bit, which I was thinking of maybe adding a Setting specifically for the VSCode Plugin that would either hide or show that detail (sense it's extra/unnecessary info).

I can move the Random ID one out to a different issue and edit my comment to point it there.

Hopefully this clarifies things

[htcfreek]

@RadhiRasho
That sounds good. Pleas split the issue.

If you then like to work on one of them feel free to open a PR. If you have any further questions don't hesitate to ask for help.

[RadhiRasho]

@htcfreek
Thank you, I'll proceed once I've got some time

[RadhiRasho]

@htcfreek this is the new issue for the Random Id Sequence: #32275

Should I edit my comment on the Contribution discussion to work on that as well?

[htcfreek]

@htcfreek this is the new issue for the Random Id Sequence: #32275

Should I edit my comment on the Contribution discussion to work on that as well?

@RadhiRasho
Should I assign both issues to you?

[RadhiRasho]

@htcfreek I'd like to tackle the Random Id issue just to get my feet wet, after that I can work on the results issue

if by the time I'm done the result issue isn't taken I can take a look at that as well, sound good?

ps. this is my first OS project contribution so I'd like to take my time and learn a bit, if that's alright