From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Wedler, Christoph" Newsgroups: gmane.emacs.devel Subject: RE: antlr-mode.el - need some support by python.el Date: Wed, 18 Feb 2015 14:13:56 +0000 Message-ID: References: <54E40954.7000706@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1424268865 20153 80.91.229.3 (18 Feb 2015 14:14:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Feb 2015 14:14:25 +0000 (UTC) Cc: =?iso-8859-1?Q?Fabi=E1n_E=2EGallina?= , "emacs-devel@gnu.org" To: Stefan Monnier , Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 18 15:14:25 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YO5OS-0003Bq-1e for ged-emacs-devel@m.gmane.org; Wed, 18 Feb 2015 15:14:24 +0100 Original-Received: from localhost ([::1]:51080 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YO5OR-00062q-A6 for ged-emacs-devel@m.gmane.org; Wed, 18 Feb 2015 09:14:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YO5O7-00061G-Er for emacs-devel@gnu.org; Wed, 18 Feb 2015 09:14:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YO5O4-0006qF-1B for emacs-devel@gnu.org; Wed, 18 Feb 2015 09:14:03 -0500 Original-Received: from smtpgw03.sap-ag.de ([155.56.66.98]:55169 helo=smtpgw.sap-ag.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YO5O3-0006on-Nm for emacs-devel@gnu.org; Wed, 18 Feb 2015 09:13:59 -0500 Thread-Topic: antlr-mode.el - need some support by python.el Thread-Index: AQHQSz6DxsXFZU5LQTeH9ayNQUY/OZz2czpg In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.40.114] X-detected-operating-system: by eggs.gnu.org: Windows 7 or 8 X-Received-From: 155.56.66.98 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183245 Archived-At: >> Since multi-mode machinery, in the general case, will require support fr= om >> the "primary" major modes, too, I suppose prog-mode it's not the proper >> place for the facilitating code. > We could place it elsewhere. E.g. indent.el. It sounds so obvious after you have said it... How should we call the variable then? Just `indent-context' ? Or `indent-multi-mode-context'? >> And overall, this change looks very specific to this one use case >> (Antlr and literate programming modes, I guess). > It's definitely not the end of the story, indeed. But I don't think > anyone knows what a good general solution looks like, right now > (especially if "good" includes "can be made to work OK without > re-implementing the indentation algorithm of all submodes"). > We've been waiting for such a magic bullet for a long time, and I don't > expect it to come any time soon. This proposed prog-indentation-context > is just a very small step along the way, but at least it's making > some progress. I fully agree. It can happen that a problem becomes easier when you generalize it extensively. But quite often, it becomes more complex. > [...] There are many other problems to solve (e.g. interaction with > syntax-ppss, font-lock, eldoc, ...), tho, so time will tell which step > will come second. Exactly. Already this specific problem is quite complex. Indentation is the first step for me, because doing it wrongly could uglify your code as file content, whereas non-perfect syntax highlighting just looks non-ideal in your Emacs buffer. (Of course, I also checked syntax-highlighting - it looks pretty good even with the current hands-on approach). Christoph