From: Basil Contovounesios <contovob@tcd.ie>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Romanos Skiadas <rom.skiad@gmail.com>,
Daniel Fleischer <danflscr@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Should yaml-ts-mode inherit from prog-mode?
Date: Wed, 01 Mar 2023 13:35:01 +0000 [thread overview]
Message-ID: <87bklcoare.fsf@tcd.ie> (raw)
In-Reply-To: <ce7f008b-50b5-453c-1c5a-e84acc4fcda4@yandex.ru> (Dmitry Gutov's message of "Tue, 28 Feb 2023 20:33:39 +0200")
[ Copying Romanos (who's not subscribed to the list) back into this
subthread. Please remember to use 'reply to all'. ]
Dmitry Gutov [2023-02-28 20:33 +0200] wrote:
> On 28/02/2023 19:56, Daniel Fleischer wrote:
>> I think yaml doesn't look at all like a programming language. There are
>> no keywords, only free text. The bash scripts you mention are defined in
>> terms of a multi line string but these strings can contain anything, not
>> just code snippets. There's no need for parenthesis or oven quotation
>> marks, it's very lax. It looks much more like free text than a
>> structured language.
>
> That's fair impression, but it might not hurt to inherit from prog-mode too.
>
> One criterion that somebody wise once proposed, is whether the language has or
> requires some specific indentation logic, one that's totally different from
> indent-relative.
>
> YAML passes that test solidly. And I'm talking about its basic structure, not
> bash (or JSON, or etc) insertions.
--
Basil
next prev parent reply other threads:[~2023-03-01 13:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 12:24 Should yaml-ts-mode inherit from prog-mode? Romanos Skiadas
2023-02-28 15:52 ` Basil Contovounesios
2023-03-01 14:08 ` Randy Taylor
2023-03-01 14:28 ` Lynn Winebarger
2023-03-01 16:35 ` Vasilij Schneidermann
2023-03-02 12:55 ` Lynn Winebarger
2023-03-02 13:44 ` Philip Kaludercic
2023-03-03 9:00 ` Rudolf Schlatte
2023-03-03 21:58 ` Yuan Fu
2023-03-04 18:45 ` Juri Linkov
2023-02-28 17:50 ` Daniel Fleischer
2023-02-28 17:56 ` Daniel Fleischer
2023-02-28 18:33 ` Dmitry Gutov
2023-03-01 13:35 ` Basil Contovounesios [this message]
2023-03-12 2:14 ` Ongaro
2023-03-12 9:20 ` Daniel Fleischer
2023-03-12 12:31 ` Rudolf Schlatte
2023-03-13 8:44 ` Yuri Khan
2023-03-14 1:45 ` David Ongaro
2023-03-01 7:46 ` Matthias Meulien
2023-03-01 13:45 ` Basil Contovounesios
2023-03-07 11:27 ` Jostein Kjønigsen
2023-03-07 14:28 ` Matthias Meulien
-- strict thread matches above, loose matches on Subject: below --
2023-03-02 19:07 Romanos Skiadas
2023-03-03 4:23 ` Richard Stallman
2023-03-04 18:24 ` Romanos Skiadas
2023-03-20 1:52 ` Randy Taylor
2023-03-20 12:07 ` Eli Zaretskii
2023-03-20 14:37 ` Rudolf Schlatte
2023-03-20 16:20 ` Brian Cully via Emacs development discussions.
2023-03-20 16:53 ` Eli Zaretskii
2023-03-21 11:19 ` Jostein Kjønigsen
2023-03-21 13:26 ` Eli Zaretskii
2023-03-21 13:54 ` Rudolf Schlatte
2023-03-21 14:43 ` Yuri Khan
2023-03-21 15:03 ` Rudolf Schlatte
2023-03-22 6:04 ` Yuri Khan
2023-03-22 2:37 ` David Ongaro
2023-03-21 3:13 ` Randy Taylor
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bklcoare.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=danflscr@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=rom.skiad@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).