GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Support workspace symbols by eyalk11 · Pull Request #511 · python-lsp/python-lsp-server

Conversation

@eyalk11

@eyalk11 eyalk11 commented Jan 6, 2024

Copy link
Copy Markdown

It simply works. (Telescope lsp_workspace_symbols)

The only comment is that the formatting of document.path and d.module_path was different (don't know why the hell) -
(C:\... vs uri or \...) , so I used the full path for telescope to handle this.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

rchl reacted with thumbs down emoji
All reactions
  • 👎 1 reaction
@eyalk11
Support workspace symbols
a1e74f2
@eyalk11 eyalk11 mentioned this pull request Jan 6, 2024
Support for workspace symbols #237
Open
@eyalk11

eyalk11 commented Jan 6, 2024 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Author

I really suggest to use it with natecraddock/workspaces.nvim#29 . LSP workspace folders is just hell. I improved the commit a bit. but would like to hear from you before investing more time in publishing this.

Just want to make sure the general tendency is to include this after fixes.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@eyalk11
eyalk11 marked this pull request as draft January 6, 2024 21:58
@eyalk11
improved log
0ccf39f
@eyalk11
eyalk11 marked this pull request as ready for review January 7, 2024 23:06
@ccordoba12

ccordoba12 commented Jan 8, 2024

Copy link
Copy Markdown
Member

Hey @eyalk11, thanks for your contribution! I think Jedi provides a better way to extract workspace symbols than doing it file by file, which seems inefficient.

Besides that, your work is also missing tests.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@eyalk11

eyalk11 commented Jan 27, 2024

Copy link
Copy Markdown
Author

What is the better method? I mean I suppose it doesn't parse all the files by default.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@feakuru

feakuru commented May 30, 2024

Copy link
Copy Markdown

i'd like to help with this, but i'm reading jedi docs and i can't find any included method to extract workspace symbols, only getting names from a singular script. @ccordoba12 could you clarify what exactly you meant here?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ccordoba12

ccordoba12 commented May 31, 2024

Copy link
Copy Markdown
Member

@feakuru, you can take a look at what jedi-language-server does. If I'm not mistaken, they implemented getting workspace symbols the right way with Jedi.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@niilohlin niilohlin mentioned this pull request Jun 2, 2024
Implement support for workspace/symbol #564
Open
@Hanatarou Hanatarou mentioned this pull request Feb 20, 2026
Add pylsp-workspace-symbols to third-party plugins list #699
Open
@nuglifeleoji nuglifeleoji mentioned this pull request Mar 25, 2026
docs: add pylsp-workspace-symbols to third-party plugins #700
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@eyalk11 @ccordoba12 @feakuru
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.