From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: David Ongaro Newsgroups: gmane.emacs.devel Subject: Re: Should yaml-ts-mode inherit from prog-mode? Date: Tue, 21 Mar 2023 19:37:21 -0700 Message-ID: References: <83mt478w48.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27835"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 22 03:57:43 2023 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 1peofW-00073x-Dk for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Mar 2023 03:57:42 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1peoeW-0008HT-TL; Tue, 21 Mar 2023 22:56:40 -0400 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 1peoeU-0008FE-RY for emacs-devel@gnu.org; Tue, 21 Mar 2023 22:56:38 -0400 Original-Received: from cosmopolitan.snafu.de ([2001:1560:3:255::151]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1peoeT-0005Vs-2P for emacs-devel@gnu.org; Tue, 21 Mar 2023 22:56:38 -0400 Original-X-Trace: 507c64617669642e6f6e6761726f4068616d627572672e64657c33342e3231312e 37342e387c3170656f4c752d3030304266752d4d307c31363739343532363437 Original-Received: from cosmopolitan.snafu.de ([10.151.10.15] helo=localhost) by cosmopolitan.snafu.de with esmtpsa (Exim 4.94.2) id 1peoLu-000Bfu-M0 for emacs-devel@gnu.org; Wed, 22 Mar 2023 03:37:29 +0100 In-Reply-To: (Rudolf Schlatte's message of "Mon, 20 Mar 2023 15:37:05 +0100") X-VISP-ShouldScan: 1 X-VISP-Virus-Check: clean X-VISP-Spam-Score: -0.5 (/) X-VISP-Spam-Report: This message has been scanned on "cosmopolitan.snafu.de" to identify if it is considered spam or not. Contact the support hotline for details. Content analysis details: (-0.5 points) pts rule name description ---- ---------------------- -------------------------------------------------- 0.5 JMQ_SPF_NEUTRAL ASKDNS: SPF set to ?all [hamburg.de TXT:v=spf1 include:_spf1.snafu.de] [include:spf.crsend.com ?all] -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 KAM_DMARC_STATUS Test Rule for DKIM or SPF Failure with Strict Alignment X-VISP-Spam-Max-Score: +++++ X-SA-Exim-Connect-IP: 34.211.74.8 X-SA-Exim-Mail-From: david.ongaro@hamburg.de X-SA-Exim-Scanned: No (on cosmopolitan.snafu.de); SAEximRunCond expanded to false Received-SPF: pass client-ip=2001:1560:3:255::151; envelope-from=david.ongaro@hamburg.de; helo=cosmopolitan.snafu.de X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 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:304689 Archived-At: Rudolf Schlatte writes: > From memory, my (probably unfair) impression of the arguments against > the change were "I checked the spec, and it isn't a programming language > and has no keywords, so it's clearly text" Nobody is arguing whether it is a programming lanugage, and the keyword argument was refuted. So what is left besides momentum? I can understand the resistance to change something which is already working in the wild (even if it's not ideal). But in contrast to yaml-mode it seems yaml-ts-mode is quite new, so it's rather a chance than a risk to change it.