unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jostein@kjonigsen.net
Cc: emacs-devel@gnu.org
Subject: Re: nxml-mode: Derive from prog-mode instead of text-mode
Date: Thu, 11 May 2017 18:26:41 +0300	[thread overview]
Message-ID: <83h90r9zym.fsf@gnu.org> (raw)
In-Reply-To: <1494487799.3240345.972964808.43DA610E@webmail.messagingengine.com> (message from Jostein Kjønigsen on Thu, 11 May 2017 09:29:59 +0200)

> From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
> Cc: emacs-devel@gnu.org
> Date: Thu, 11 May 2017 09:29:59 +0200
> 
> But prog-mode represents a API, a endpoint, for end-users and developers to wire up anything and any
> customization they deem programming-related.
> 
> With prog-mode API-wise being a "success", shouldn't Emacs core honour that API by using it where
> appropriate? That would IMO be the consistent thing to do.
> 
> That Emacs ships with only 3 such customizations out of the box seems to me irellevant.

My point is, given how little prog-mode customizes, there's no
particular reason why your customizations should start from prog-mode.
They could start from any other major mode, since you need to invent
most of them from scratch anyway; prog-mode doesn't help you make
fewer customizations.

>  I could understand an argument that nowadays XML and even HTML deviate
>  a lot from text with markup, but I don't see how prog-mode would be
>  more appropriate. I tend to think that we should come up with a new
>  family of modes, which specifically caters to the likes of XML-based
>  coding.
> 
> Something like structured-text-mode ? Which for instance nxml-mode, json-mode, yaml-mode (etc etc) could
> derive from.

Yes.



  parent reply	other threads:[~2017-05-11 15:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 10:35 nxml-mode: Derive from prog-mode instead of text-mode Jostein Kjønigsen
2017-05-10 10:40 ` Yuri Khan
2017-05-10 10:52   ` Jostein Kjønigsen
2017-05-10 11:42     ` Yuri Khan
2017-05-10 12:00 ` Stefan Monnier
2017-05-10 16:38 ` Eli Zaretskii
2017-05-10 17:59   ` Jostein Kjønigsen
2017-05-10 18:59     ` Eli Zaretskii
2017-05-10 19:28       ` Eli Zaretskii
2017-05-11  7:29       ` Jostein Kjønigsen
2017-05-11 15:15         ` raman
2017-05-11 15:29           ` Eli Zaretskii
2017-05-11 15:26         ` Eli Zaretskii [this message]
2017-05-14 19:28         ` Philipp Stephani
2017-05-14 19:58           ` Dmitry Gutov
2017-05-15  3:05           ` Tom Tromey
2017-05-16 10:34             ` Jostein Kjønigsen
2017-05-16 11:17               ` Yuri Khan
2017-05-16 12:12                 ` Stefan Monnier
2017-05-16 14:04                   ` Drew Adams
2017-05-16 14:08                     ` Eric Abrahamsen
2017-05-16 18:19                       ` Drew Adams
2017-05-16 21:48                         ` Stefan Monnier
2017-05-17  5:13                         ` Yuri Khan
2017-05-17 12:53                           ` Stefan Monnier
2017-05-17 16:02                           ` Drew Adams
2017-05-17 16:20                             ` Yuri Khan
2017-05-17 16:37                             ` Stefan Monnier
2017-05-17 17:28                               ` Drew Adams
2017-05-17 18:42                                 ` Stefan Monnier
2017-05-17 18:52                                   ` Johan Bockgård
2017-05-16 14:11                     ` Stefan Monnier
2017-05-16 12:11               ` Stefan Monnier
2017-05-16 18:54               ` Eli Zaretskii
2017-05-16 19:02                 ` Jostein Kjønigsen
2017-05-24  8:50                   ` Jostein Kjønigsen
2017-05-30  8:05                     ` Jostein Kjønigsen
2017-05-31 11:52                       ` Stefan Monnier
2017-06-02 12:34                       ` Jostein Kjønigsen
2017-06-06 14:45                         ` Stefan Monnier
2017-05-16 21:50                 ` Stefan Monnier
2017-05-11  1:32 ` Rolf Ade

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=83h90r9zym.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    /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).