From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Benjamin Slade" <beoram@gmail.com>,
"Yasuaki Kudo" <yasu@yasuaki.com>,
"Olivier Dion" <olivier.dion@polymtl.ca>,
help-guix@gnu.org
Subject: Re: Enterprise Guix Hosting?
Date: Mon, 10 Oct 2022 09:58:42 +0200 [thread overview]
Message-ID: <8735bwt8i5.fsf@gmail.com> (raw)
In-Reply-To: <87bkqmb7yz.fsf@beadling.co.uk>
Hi Phil,
Thanks for your feedback. Very helpful and I would be interested by
detailing many items. :-)
Well, for now I am specifically interested in:
On sam., 08 oct. 2022 at 17:23, Phil <phil@beadling.co.uk> wrote:
> Most of the developers I work with are comfortable using the console so
> most of my demos are at the xterm level. Where it makes sense, I wrap
> commands into scripts that can be called from VS Code, and then demo
> them from VS Code too.
Do you have a Guix recipe for building VS Code?
> So far, only 1 or 2 developers will currently go as far as writing
> scripts in Guile (for example more advanced/custom manifests), but if I provide
> Guile scripts most developers are comfortable knowing what to do with
> them - running them from 'guix repl' from example. Developers are
> getting more confident/ambitious with more advanced usage, which I
> promote as where much of the real power of Guix's approach really lies!
Do you recommend some VS Code plugins for editing Guile Scheme?
Cheers,
simon
next prev parent reply other threads:[~2022-10-10 10:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via
2022-07-30 16:20 ` Phil
2022-07-30 23:18 ` Yasuaki Kudo
2022-07-31 0:42 ` Benjamin Slade
2022-07-31 11:01 ` Phil
2022-08-09 20:37 ` Ludovic Courtès
2022-08-09 22:24 ` Yasuaki Kudo
2022-08-14 9:53 ` Phil
2022-08-14 22:03 ` Yasuaki Kudo
2022-08-15 20:50 ` Phil
2022-08-25 18:37 ` Olivier Dion via
2022-08-26 6:40 ` Yasuaki Kudo
2022-10-12 9:55 ` Ade Malsasa Akbar
2022-10-12 10:18 ` Olivier Dion via
2022-08-26 7:24 ` Ricardo Wurmus
2022-08-31 1:42 ` Thompson, David
2022-08-31 6:33 ` Ricardo Wurmus
2022-08-31 10:46 ` [EXT] " Thompson, David
2022-08-31 11:42 ` Olivier Dion via
2022-08-31 12:54 ` Thompson, David
2022-09-05 19:38 ` [EXT] " Ludovic Courtès
2023-01-23 15:34 ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Giovanni Biscuolo
2023-01-23 16:48 ` Przemysław Kamiński
2023-01-23 17:59 ` Wojtek Kosior via
2022-09-05 19:42 ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03 ` zimoun
2022-10-08 16:23 ` Phil
2022-10-10 7:58 ` zimoun [this message]
2022-10-10 10:30 ` (
2022-10-10 10:49 ` zimoun
2022-10-10 19:35 ` Phil
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=8735bwt8i5.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=phil@beadling.co.uk \
--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).