From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: yasu@yasuaki.com
Cc: help-guix <help-guix@gnu.org>
Subject: Re: VSCode DevContainer for Guix? (Yasuaki Kudo)
Date: Tue, 11 Jul 2023 19:23:43 +0000 [thread overview]
Message-ID: <b68204c7-03f0-9f98-f485-289b6cf696c8@posteo.de> (raw)
In-Reply-To: <mailman.87.1689091255.20905.help-guix@gnu.org>
Hello Yasu,
There are some legal aspects about using the official "marketplace" from other
than the official VSCode build:
https://github.com/VSCodium/vscodium/blob/master/DOCS.md#extensions--marketplace
at least according to the VSCodium linking to
https://github.com/microsoft/vscode/issues/31168, wherein someone interpreted
things: https://github.com/microsoft/vscode/issues/31168#issuecomment-1136375670.
Not sure this plays any role in your proposed process. It is something to keep
in mind.
Regards,
Zelphir
On 7/11/23 18:00, help-guix-request@gnu.org wrote:
> Send Help-Guix mailing list submissions to
> help-guix@gnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/help-guix
> or, via email, send a message with subject or body 'help' to
> help-guix-request@gnu.org
>
> You can reach the person managing the list at
> help-guix-owner@gnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Help-Guix digest..."
>
>
> Today's Topics:
>
> 1. VSCode DevContainer for Guix? (Yasuaki Kudo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 11 Jul 2023 05:55:33 +0900
> From: Yasuaki Kudo <yasu@yasuaki.com>
> To: help-guix <help-guix@gnu.org>
> Subject: VSCode DevContainer for Guix?
> Message-ID: <BB9B5B1E-810C-4315-AD49-9FEC156F5E9E@yasuaki.com>
> Content-Type: text/plain; charset=utf-8
>
> Hello!!
>
> So I have just spent a month battling with Docker and VSCode for a project and became familiar with them. Combining both, we can create a very pleasant and reproducible developer environment that everyone can copy.
>
> DevContainer is like Screen/Tmux on steroids - the heavy lifting of compilation and running can be shifted to a Docker, a remote SSH session, or a combination of both, while the end-programmer can interact with the local VSCode IDE. And the developer-facing computer can be any of the 3 - Linux, Windows or Macintosh (inclusive of Apple custom CPU)
>
> A development team can share the exact same environment using this mechanism.
>
> I think we should have such a DecContainer for Guix programmers? 😄
>
> -Yasu
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Help-Guix mailing list
> Help-Guix@gnu.org
> https://lists.gnu.org/mailman/listinfo/help-guix
>
>
> ------------------------------
>
> End of Help-Guix Digest, Vol 92, Issue 9
> ****************************************
--
repositories: https://notabug.org/ZelphirKaltstahl
next parent reply other threads:[~2023-07-11 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.87.1689091255.20905.help-guix@gnu.org>
2023-07-11 19:23 ` Zelphir Kaltstahl [this message]
2023-07-12 1:22 ` VSCode DevContainer for Guix? (Yasuaki Kudo) Yasuaki Kudo
2023-07-12 8:27 ` wolf
2023-07-12 11:27 ` Ekaitz Zarraga
2023-07-12 23:50 ` Yasuaki Kudo
2023-08-23 15:12 ` Simon Tournier
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b68204c7-03f0-9f98-f485-289b6cf696c8@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).