This is an archive of the discontinued LLVM Phabricator instance.

Summary: This documentation patch adds information to allow remote users to also use the plugin as it will be invisible to them using the current instructions. It solves issue #58252.
ClosedPublic

Authored by HenriqueBucher on Oct 10 2022, 6:34 AM.

Details

Summary

This documentation patch adds information to allow remote users to also use the plugin as it will be invisible to them using the current instructions. It solves issue #58252.

Diff Detail

Event Timeline

HenriqueBucher created this revision.Oct 10 2022, 6:34 AM
Herald added a project: Restricted Project. · View Herald TranscriptOct 10 2022, 6:34 AM
HenriqueBucher requested review of this revision.Oct 10 2022, 6:34 AM
Herald added a project: Restricted Project. · View Herald TranscriptOct 10 2022, 6:34 AM
JDevlieghere requested changes to this revision.Oct 10 2022, 9:09 AM
JDevlieghere added inline comments.
lldb/tools/lldb-vscode/README.md
39

Please wrap this so it fits in the 80 col limit.

70–71

Remove

This revision now requires changes to proceed.Oct 10 2022, 9:09 AM
jryans added a subscriber: jryans.Oct 10 2022, 9:38 AM

Please also give this patch a title that would make sense as the first line of a commit message. It currently just says "Summary:" at the moment.

Formatted text to wrap in 80 columns

Removed 2 extra blank lines

HenriqueBucher added inline comments.Oct 10 2022, 9:51 AM
lldb/tools/lldb-vscode/README.md
39

Most of this file has lines with more than 80 columns. Would you want the other lines to be reformatted as well?

JDevlieghere added inline comments.Oct 10 2022, 10:22 AM
lldb/tools/lldb-vscode/README.md
39

I wouldn't say "most": there are a few lines that exceed the 80 col limit for a valid reason (i.e. having a URL in them) but you're right that there's a few lines that should be reflowed (line 25 for example). Since that would be orthogonal to this patch, it should be a separate patch. For the same reason there's no expectation for you to do that, but it would of course be very much appreciated!

Ok submitted another patch. Added you as reviewer. Check if it is okay.
https://reviews.llvm.org/D135607

lgtm. Jonas?

This revision is now accepted and ready to land.Oct 11 2022, 9:36 AM

Henrique, do you have commit access?

Whoever ends up committing this, please make sure the commit has a reasonable commit description and not "Summary:".

I assume not since I have never committed on any LLVM project.
But I would like to as I plan to contribute more in the future.
Just sent Chris Clattner an email with the request.
Note: The reason the summary is so terse is that the ARC tool opens two windows and I was very confused about where to write what.
Maybe a little paragraph in the documentation would make this clearer?

Note: The reason the summary is so terse is that the ARC tool opens two windows and I was very confused about where to write what.

Certainly would confuse me, maybe I've learned to autopilot through this though. Can you describe them? We can certainly add a note in the docs.

Oh and if you would like someone to land this on your behalf please provide a name and email address for the commit (of course waiting for access is fine too).

Visual Studio code has different folders for plugins when used by local users and users remoting into the box.
The current instructions show how to install the lldb-vscode plugin only for the local users and it will be invisible to them if they remote.
This patch adds instructions on how to install the plugin for remote users too.
It solves issue #58252.

HenriqueBucher retitled this revision from Summary: to Summary: This documentation patch adds information to allow remote users to also use the plugin as it will be invisible to them using the current instructions. It solves issue #58252..

The current documentation shows how to install the lldb-vscode plugin as a local user.
When they remote, the plugin will be invisible.
This documentation patch adds information on how to extend the plugin to remote users as well.

Got a very nice email from Chris Lattner with the approval. Very nice.
Dude I took the plunge and did it. I hope it went through right. Please let me know if I screwed it up.

Exciting, welcome to the LLVM community! 🙂

Overall your commit looks okay, but here are a few tips for the future... The "Summary:" prefix in the commit title is not needed. It's good to start the commit title with an active verb e.g. "Add foo to bar". You can optionally use prefix tags like "[Docs]" to suggest the area. I recommend looking over other commit messages (https://github.com/llvm/llvm-project/commits/main) to get a feel for the typical style.

Is there anything to be done at this point? Can I reset my branch?

No, once it has been committed, it can’t really be removed from a project of this size. Changes can be reverted, but the existence of the commits and messages remains. Don’t worry about it for this one, just something to think about next time.

I mean my local changes, can I consider this done and clean up?
Sorry for the very newbie question.

Ah yes, it’s all done now, feel free to clean up your local state however you prefer.