From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, nathaniel.l.desimone@intel.com
Subject: Re: [edk2-devel] Recommended VSCode Extensions and Settings
Date: Thu, 17 Jun 2021 13:06:01 -0600 [thread overview]
Message-ID: <7fe8a77a-79b9-6f4e-4062-0aeb5407ea88@nuviainc.com> (raw)
In-Reply-To: <59158572-BDE8-4627-846F-F868784214F0@intel.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
I wonder, should we add a .vscode directory in the edk2 repo and add the
recommended extensions to an extensions.json file (See Workspace
Recommended Extensions in
https://code.visualstudio.com/docs/editor/extension-marketplace)?
--
Rebecca Cran
On 6/17/21 12:39 AM, Nate DeSimone wrote:
>
> Hi Everyone,
>
> I have compiled a list of recommended extensions and settings for
> using Visual Studio Code to develop EDK II code. I have posted them on
> the wiki:
> https://github.com/tianocore/tianocore.github.io/wiki/Nate's-Recommended-VSCode-Extensions-and-Settings
> <https://github.com/tianocore/tianocore.github.io/wiki/Nate's-Recommended-VSCode-Extensions-and-Settings>
>
> Feel free to add to the list if there is something you believe to be
> missing.
>
> Nate
>
>
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
prev parent reply other threads:[~2021-06-17 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 6:39 Recommended VSCode Extensions and Settings Nate DeSimone
2021-06-17 19:06 ` Rebecca Cran [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fe8a77a-79b9-6f4e-4062-0aeb5407ea88@nuviainc.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox