Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Conversation

HarshNarayanJha
Copy link

@HarshNarayanJha HarshNarayanJha commented Oct 9, 2024

This Python plugin lets you browse and open your Zed Editor Workspaces at the speed of thought!

Repo: https://github.com/HarshNarayanJha/albert_zed_workspaces

Technical Description

There is the database file at ~/.local/share/zed/db/0-stable/db.sqlite. I just read and parse it and display list items for each of them, and open it up using whatever binary found (zed, zeditor, etc)

There are still issues with this, like I don't know the database path on MacOS yet (searching for that), and a the local_path is actually a binary object (don't know why), so some workspaces miss out right now. I will fix them

Corresponding Discussion: zed-industries/zed#18895

@HarshNarayanJha
Copy link
Author

Hey @ManuelSchneid3r !
Sorry for the ping... But is anything stopping to merge this?

@ManuelSchneid3r ManuelSchneid3r force-pushed the main branch 3 times, most recently from 03e8ee2 to f10c789 Compare July 26, 2025 21:47
@ManuelSchneid3r
Copy link
Member

Hey @ManuelSchneid3r ! Sorry for the ping... But is anything stopping to merge this?

Nothing to be sorry about. We need reviewers. I can't stem this all on my own.

I changed the structure of the repo. Plugins are now submodules. I am still thinking about the most reasonable way to integrate outside collaborations.

  1. I need write access to script any api changes.
  2. We need reviewing.

We have two options.

  1. Transfer the repository into the Albertlauncher org and you fork it
  2. You could also keep the repo an give me write access.

There are two points were we could have the reviewing.

  1. The commit of the submodule hash.
  2. The commit of the changes into the upstream repo. And everything that makes it into the upstream repo will be accepted as shippable. Meaning no reviewing in step 1.

I'd prefer the latter because Github offers a nice UI for reviews and code comments and we have all officially shipped plugins in one place.

If you don't have any objections please transfer the repo to albertlauncher organization. Ofc I am open to a discussion.

@ManuelSchneid3r
Copy link
Member

Please see #226

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants