From: Lynn Winebarger <owinebar@gmail.com>
To: Randy Taylor <dev@rjt.dev>
Cc: Basil Contovounesios <contovob@tcd.ie>,
Romanos Skiadas <rom.skiad@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Should yaml-ts-mode inherit from prog-mode?
Date: Wed, 1 Mar 2023 09:28:19 -0500 [thread overview]
Message-ID: <CAM=F=bC93awK3rRc3J8Wv-BsZGR8cNyFMVEWod4gUQKUjo7NbQ@mail.gmail.com> (raw)
In-Reply-To: <Gzj9Gg1HhvYRHFW7rS12F28VsNV-w-laKjEnMPmhQYDBHULyeztq4rTI39Js1a9SK6J5j71myDpun7m1AMSGQnMCjFZb5wneZfNe6V7SeyI=@rjt.dev>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Wed, Mar 1, 2023, 9:10 AM Randy Taylor <dev@rjt.dev> wrote:
>
> I think the JSON modes are prog-modes just because they are attached to
> the javascript modes in some way (usually derived from it). I'm not sure
> how much weight we can assign to certain modes deriving from other modes
> and saying we should do the same (especially in the case of ELPA/MELPA
> modes); instead we should ask which mode makes the most sense to derive
> from. Although there is the argument for consistency that you mentioned...
>
Perhaps since data serialization formats can be used to store data
structures in source files in a portable way, it makes sense to write
generic modes for them that can be adapted to specific PL modes?
I'm sure JSON developed in the opposite direction, but would it have been
better to start with JSON mode then embed it in JavaScript/Python/etc modes
from the start?
Lynn
[-- Attachment #2: Type: text/html, Size: 1450 bytes --]
next prev parent reply other threads:[~2023-03-01 14:28 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 [this message]
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
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='CAM=F=bC93awK3rRc3J8Wv-BsZGR8cNyFMVEWod4gUQKUjo7NbQ@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=contovob@tcd.ie \
--cc=dev@rjt.dev \
--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).