From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Mendler via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] New major-mode: bicep-ts-mode Date: Sun, 07 Jan 2024 19:04:37 +0100 Message-ID: <87jzoldnpm.fsf@daniel-mendler.de> References: <7121354D-5D04-4B22-A0D3-54C469BF5B85@secure.kjonigsen.net> Reply-To: Daniel Mendler Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36728"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: "Ergus via Emacs development discussions." , Yuan Fu , Theodor Thornhill , Dmitry To: Jostein =?utf-8?Q?Kj=C3=B8nigsen?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 07 19:05:34 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rMXWf-0009KU-P0 for ged-emacs-devel@m.gmane-mx.org; Sun, 07 Jan 2024 19:05:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rMXVx-0008L3-7C; Sun, 07 Jan 2024 13:04:49 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rMXVr-0008KZ-RC for emacs-devel@gnu.org; Sun, 07 Jan 2024 13:04:44 -0500 Original-Received: from server.qxqx.de ([2a01:4f8:121:346::180] helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rMXVp-0007o3-I3 for emacs-devel@gnu.org; Sun, 07 Jan 2024 13:04:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=qxqx.de; s=mail1392553390; h=Content-Transfer-Encoding:Content-Type:MIME-Version: Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=hQYEcQXnS6FJsdZQI7dYTH/pr+QWx6xQpSawi5GOaK8=; b=d0HUZ+fmpVTeASpaubOiXN6FyK qLrgjaREutoWjsgho9Ovy1lHjexpOT9Fb5CBMOkvBDZ8Cg8gZ9Cj+WAa4DTTdWAcROO/ALBWWpuHl tig5YsQSb94pxoY84JZ10Ruh/Y6ntl5vSS/vru7k/hLQOk5aNduSACd5SgY4raUn4X/M=; In-Reply-To: <7121354D-5D04-4B22-A0D3-54C469BF5B85@secure.kjonigsen.net> ("Jostein =?utf-8?Q?Kj=C3=B8nigsen=22's?= message of "Thu, 21 Dec 2023 15:32:16 +0100") Received-SPF: pass client-ip=2a01:4f8:121:346::180; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314705 Archived-At: Jostein Kj=C3=B8nigsen writes: > Currently if one works with Microsoft-oriented solutions (C#, .NET, TypeS= cript, > Azure, etc) one often also has to work with Bicep. Bicep is a programming > language used to describe Infrastructure-as-Code used for deploying servi= ces in > Microsoft Azure cloud. > > Unfortunately the only editor currently available with useful Bicep-suppo= rt is > Microsoft VSCode. Working with Bicep in Emacs currently is not really fea= sible. > > The Bicep language itself is a type-safe language with an associated open= -source > toolchain, which in turn gets compiled to JSON-formatted Azure Resource > Manager (ARM) templates, which can actually provision resources in Azure. > > With appropriate editor-support, working with Bicep is superior to workin= g with > the untyped JSON for ARM template purposes. As such, adding support for B= icep > to Emacs, would mean most Azure-developers can still stay 100% within Ema= cs > to do their job :) Stefan Kangas writes: > Daniel Mendler via "Emacs development discussions." writes: >> Also, recently there has also been a >> discussion to add a `bicep-ts-mode' to Emacs core, with the argument >> being that VSCode supports it. Makes sense, it is a Microsoft product to >> help using Microsoft products. The description of Bicep on Github >> (https://github.com/Azure/bicep) is "Bicep is a declarative language for >> describing and deploying Azure resources". Does Bicep really need to be >> part of Emacs core? Couldn't it be added to ELPA instead? > > I think we should be sympathetic to arguments such as the above, yes, > but why not ask this question in the Bicep thread instead? :-) Agree, the question if `bicep-ts-mode' should be added to ELPA instead of core should be discussed in the Bicep thread.