unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Rudolf Schlatte <rudi@constantly.at>
Cc: emacs-devel@gnu.org
Subject: Re: Should yaml-ts-mode inherit from prog-mode?
Date: Fri, 3 Mar 2023 13:58:28 -0800	[thread overview]
Message-ID: <E8881E81-7635-47DE-A98F-10C5C1B8027E@gmail.com> (raw)
In-Reply-To: <m1356mgqf1.fsf@constantly.at>



> On Mar 3, 2023, at 1:00 AM, Rudolf Schlatte <rudi@constantly.at> wrote:
> 
> Philip Kaludercic <philipk@posteo.net> writes:
> 
>> Deriving from prog-mode or from text-mode doesn't mean much in practice.
>> I see it as less of a formal taxonomy of programming languages, and more
>> of a convenience measure to make changes that (vaguely speaking) "all
>> programming modes" or "all text-related modes" have in common.  E.g. I
>> have this in my init.el:
>> 
>>  (add-hook 'text-mode-hook #'flyspell-mode)
>>  (add-hook 'prog-mode-hook #'flyspell-prog-mode)
> 
> Similarly, I use variable-width fonts for text mode buffers and fixed
> width fonts for prog-mode buffers.  Since in yaml indentation is
> significant, it would be preferrable for me to have yaml-mode inherit
> from prog-mode, if only for convenience's sake.
> 
> 

Agreed. I think of prog-mode as “programming mode” as opposed to “prose mode”, aka text-mode. In that sense, deriving from prog-mode makes more sense to me.

In text related to programming, one would assume monospace font, flyspell-prog-mode, structured text, etc.

Yuan


  reply	other threads:[~2023-03-03 21:58 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 [this message]
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=E8881E81-7635-47DE-A98F-10C5C1B8027E@gmail.com \
    --to=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rudi@constantly.at \
    /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).