From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: =?utf-8?Q?Jostein=20Kj=C3=B8nigsen?= <jostein@secure.kjonigsen.net>
Newsgroups: gmane.emacs.devel
Subject: Re: nxml-mode: Derive from prog-mode instead of text-mode
Date: Thu, 11 May 2017 09:29:59 +0200
Message-ID: <1494487799.3240345.972964808.43DA610E@webmail.messagingengine.com>
References: <1494412509.2069441.971865104.0646ACD6@webmail.messagingengine.com>
	<8337ccbrar.fsf@gnu.org>
	<1494439153.1311720.972341016.7C2EC66A@webmail.messagingengine.com>
	<83o9v0a66q.fsf@gnu.org>
Reply-To: jostein@kjonigsen.net
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="_----------=_149448779932403450"
Content-Transfer-Encoding: 7bit
X-Trace: blaine.gmane.org 1494487820 29879 195.159.176.226 (11 May 2017 07:30:20 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Thu, 11 May 2017 07:30:20 +0000 (UTC)
Cc: emacs-devel@gnu.org
To: Eli Zaretskii <eliz@gnu.org>, jostein@kjonigsen.net
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 11 09:30:16 2017
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([208.118.235.17])
	by blaine.gmane.org with esmtp (Exim 4.84_2)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1d8iYB-0007di-V7
	for ged-emacs-devel@m.gmane.org; Thu, 11 May 2017 09:30:16 +0200
Original-Received: from localhost ([::1]:46610 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1d8iYF-0006e5-KS
	for ged-emacs-devel@m.gmane.org; Thu, 11 May 2017 03:30:19 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49879)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jostein@secure.kjonigsen.net>) id 1d8iY3-0006ZM-DP
	for emacs-devel@gnu.org; Thu, 11 May 2017 03:30:13 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jostein@secure.kjonigsen.net>) id 1d8iY2-00005Y-GM
	for emacs-devel@gnu.org; Thu, 11 May 2017 03:30:07 -0400
Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35111)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <jostein@secure.kjonigsen.net>)
	id 1d8iXw-0008U5-LF; Thu, 11 May 2017 03:30:00 -0400
Original-Received: from compute6.internal (compute6.nyi.internal [10.202.2.46])
	by mailout.nyi.internal (Postfix) with ESMTP id A978A209CB;
	Thu, 11 May 2017 03:29:59 -0400 (EDT)
Original-Received: from web5 ([10.202.2.215])
	by compute6.internal (MEProxy); Thu, 11 May 2017 03:29:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	secure.kjonigsen.net; h=cc:content-transfer-encoding
	:content-type:date:from:in-reply-to:message-id:mime-version
	:references:reply-to:subject:to:x-me-sender:x-me-sender
	:x-sasl-enc; s=fm1; bh=BicXSCLSIIEaqjf/3Zhy4S7WWKSFLYHdZo2Wq0s1H
	Lk=; b=NYbqBKiQC39V8Xu9wM5idrsAsiOA4+jH5Gcy0Dcx7rfsXsA5sK6vage6P
	ghYbU0KdOMBHOqnEx8xhzWE9ftyT0v1zjxxB1izJKlH8Drnz+mS9BMXUgOlMRnrQ
	oURAQFrYPOauH/QrykZgkVF1WdhLW0eADCHwSRc+ZwafRN4GsPZ03ZYyBE6/1ZXT
	B6RIJ7kWE2Ee2XqqCKLCPLW8DYlkrlqLii8//LJ56R2b+kvB0BYiQTBQ9WOvIECS
	FtMOw9LmtOjue76eN0D9m00HcrfBtsswRsvdugvlL6vtvDcW1eV3GJMLs4LIybbR
	Uy+QPWTaoA1mA1owey/H8+J5fJWBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1;
	bh=BicXSCLSIIEaqjf/3Zhy4S7WWKSFLYHdZo2Wq0s1HLk=; b=PvoPZGajwyYh
	3th3ilPtnyjLPhB7J2BFVDfPR0oC+wmLxbSNyQCqnjUAU7mSVr2WMDxs5v41BfPS
	JNbMZoZNiWTKscpmqhfwnssb2Emvt2/C5sCRx/+sHMyIAzddhzshOE9fKAxhAH71
	SkN9T/yi+jPKWGJSboG3OTkMpTUgVpNAM5g/Py6MsKhDSe42zvaDlsPKW+3vsw2t
	fCsJGTJ6nZ5B9VvIsIJLJRZR3HskmSBhkYVjMPm2/STL01ddRi6SEOU9yPhDJDHC
	JfvaSnAw+PYaqvYp1/PgKhNCzAvZCPg71hpsDO5K94b5dBYPSc1hGwEBDpEeKkm+
	0u8cXJYFfg==
X-ME-Sender: <xms:9xIUWRh8L4o8y_VWFNdEw4dSRvP3tPoILBU8BFaYnq2xr7WdWOo9YA>
Original-Received: by mailuser.nyi.internal (Postfix, from userid 99)
	id 744D99E1CF; Thu, 11 May 2017 03:29:59 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface - ajax-6cc55fe1
In-Reply-To: <83o9v0a66q.fsf@gnu.org>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
	[fuzzy]
X-Received-From: 66.111.4.28
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:214789
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/214789>

This is a multi-part message in MIME format.

--_----------=_149448779932403450
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Wed, May 10, 2017, at 08:59 PM, Eli Zaretskii wrote:
> These seem all to stem from your personal setup, not from inherent
> features of prog-mode that are absent from text-mode.  In fact,
> prog-mode is exceedingly minimal: it only sets 3 variables, none of
> them related to what you describe.

Obviously.=20

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.
> 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.
That could be another approach, and I'd be happy with that, if
done properly.
--
Regards
Jostein Kj=C3=B8nigsen

--_----------=_149448779932403450
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Wed, May 10, 2017, at 08:59 PM, Eli Zaretskii wrote:<br></div>
<blockquote type=3D"cite"><div>These seem all to stem from your personal se=
tup, not from inherent<br></div>
<div>features of prog-mode that are absent from text-mode.&nbsp; In fact,<b=
r></div>
<div>prog-mode is exceedingly minimal: it only sets 3 variables, none of<br=
></div>
<div>them related to what you describe.<br></div>
</blockquote><div><br></div>
<div>Obviously. <br></div>
<div><br></div>
<div><div>But prog-mode represents a API, a endpoint, for end-users and dev=
elopers to wire up anything and any customization they deem programming-rel=
ated.<br></div>
<div><div><br></div>
<div>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 t=
hing to do.<br></div>
<div><div><div><br></div>
<div>That Emacs <i>ships</i> with only 3 such customizations out of the box=
 seems to me irellevant.<br></div>
</div>
<div><div><div><div><br></div>
</div>
</div>
</div>
</div>
</div>
</div>
<blockquote><div>I could understand an argument that nowadays XML and even =
HTML deviate<br></div>
<div>a lot from text with markup, but I don't see how prog-mode would be<br=
></div>
<div>more appropriate.&nbsp; I tend to think that we should come up with a =
new<br></div>
<div>family of modes, which specifically caters to the likes of XML-based<b=
r></div>
<div>coding.<br></div>
</blockquote><div><br></div>
<div>Something like structured-text-mode ?&nbsp; Which for instance nxml-mo=
de, json-mode, yaml-mode (etc etc) could derive from.<br></div>
<div><br></div>
<div><div>That could be another approach, and I'd be happy with that, if do=
ne properly.<br></div>
<div><div><br></div>
</div>
</div>
<div>--<br></div>
<div>Regards<br></div>
<div>Jostein Kj=C3=B8nigsen<br></div>
</body>
</html>

--_----------=_149448779932403450--