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

How to use this extension? #14

Closed
miko-ck opened this issue Jun 17, 2024 · 7 comments
Closed

How to use this extension? #14

miko-ck opened this issue Jun 17, 2024 · 7 comments

Comments

@miko-ck
Copy link

miko-ck commented Jun 17, 2024

I installed this extension in VSCode. How do I activate the blame view as shown in the picture on the extension page? I mean, the pictures are nice, but how do I get there?

I tried all the "blame" related options in the Ctrl+shift+p menu. They show various menus but not the main view I wanted. I found a sidebar on the left but there's nothing in it.

I found the 4 options in the context menu but they don't give me the normal blame view.

There's nothing in this repo's readme.

There's nothing on your website solomonkinard.com.

I literally tried everything I could. Please improve the documentation to make the extension usable.

@solomonkinard
Copy link
Owner

Does this work for you? That should probably be documented either way. If it doesn't work, can you share whether you're opening .md files, or any environment information? .md files probably don't have inline blame, which could also be documented. Thanks.

@miko-ck
Copy link
Author

miko-ck commented Jun 18, 2024 via email

@bb-soat
Copy link

bb-soat commented Jul 15, 2024

On my side, I had to downgrade to V0.2.21 because latest version does not work anymore.

@solomonkinard
Copy link
Owner

Thanks for sharing. It hasn't been updated in the last few weeks. What didn't work for you then?

@bb-soat
Copy link

bb-soat commented Jul 16, 2024

From v0.2.22, the "Show Blame Inline" does not work

@solomonkinard
Copy link
Owner

Agreed that v0.2.21 is stable; it's the recommended version for anyone looking for stability. The next version introduced a ton of changes from open issues and beyond. To help debug your issue, consider sharing more specifics, like if the setting is enabled and the OS. This seems to be working on Mac. However, there are several known and unknown problems. Opening new issues with specific details helps a lot for triaging and prioritization.

@solomonkinard
Copy link
Owner

  • This bug was opened as "how to use this extension", which is a general question. Answered.
  • Comments about documentation have been resolved by adding a "> Git Blame: Help" command.
  • Comments about inline blame not being visible were resolved by stating that they are on the right.
  • Comments about "Show Blame Inline" did not provide any specifics, but a fix as a guess was published anyway in v0.2.32.

Closing this bug now. It's unclear if your issue is resolved without specifics, even though a potential fix was published. Instead of leaving this bug open for people to find, I put a summary of parts of this thread in the README. Anyone can open a new issue if there is something specific that they'd like to be addressed. General complaints are also welcome. The more the merrier.

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

No branches or pull requests

3 participants