From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: antlr-mode.el - need some support by python.el Date: Sat, 21 Mar 2015 17:30:55 +0200 Message-ID: <550D8EAF.2080602@yandex.ru> References: <54E4AC06.60300@yandex.ru> <54E54DE7.1010807@yandex.ru> <54E558C8.9040600@yandex.ru> <54E90362.8070904@yandex.ru> <54F38FD3.1020307@yandex.ru> <54F47CD3.5080708@yandex.ru> <54F4A62F.3040403@yandex.ru> <54F4BA93.4000801@yandex.ru> <54F742DA.3080106@yandex.ru> <54F78E3B.1080000@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1426951873 4625 80.91.229.3 (21 Mar 2015 15:31:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Mar 2015 15:31:13 +0000 (UTC) Cc: "Wedler, Christoph" , "=?windows-1252?Q?Fab?= =?windows-1252?Q?i=E1n?= E.Gallina" , "emacs-devel@gnu.org" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 21 16:31:11 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 1YZLMk-0007bn-3M for ged-emacs-devel@m.gmane.org; Sat, 21 Mar 2015 16:31:10 +0100 Original-Received: from localhost ([::1]:48107 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZLMj-0006RX-Ey for ged-emacs-devel@m.gmane.org; Sat, 21 Mar 2015 11:31:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZLMf-0006Og-Fk for emacs-devel@gnu.org; Sat, 21 Mar 2015 11:31:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZLMc-0005en-B2 for emacs-devel@gnu.org; Sat, 21 Mar 2015 11:31:05 -0400 Original-Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:36264) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZLMc-0005db-4j for emacs-devel@gnu.org; Sat, 21 Mar 2015 11:31:02 -0400 Original-Received: by wibg7 with SMTP id g7so11705121wib.1 for ; Sat, 21 Mar 2015 08:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Y8c4HpfYkYhZmugqMxj0e5KaQsAv9H2D5hi4mzyU2zY=; b=B4UgoBUBRHt/nJf7EBe4OgMppM9FQm1GMKWuPPUqf4tqxbGjhK4NzcxTn/O+FqLYTs 8KGEnUk+bGrjGtkJ5SHFtm86c4m79MveFSvRa5Z2JTvwcsPID33cSnfXIH+IyGJ4bwlb 1RP62ujGe0X55m2ALEVZ0Q46ZyhhZZHGAOsAPeismHcED/CQ2CsdQnP1zvqVzLzVt1Kb GMmzcEgymkebxUcUorzQY0jJgTFTyi62n7gZUxD3WralH0OezZD8lo3SMwb4F8E9HBm3 ciEfArM1Shtiyzd41Q0V9yHxrd3t1uilaav17UIjiIP2Enqrmjv6PM05iUvwWoivkYDr fChA== X-Received: by 10.181.13.82 with SMTP id ew18mr5168974wid.84.1426951860884; Sat, 21 Mar 2015 08:31:00 -0700 (PDT) Original-Received: from [192.168.1.3] ([82.102.93.54]) by mx.google.com with ESMTPSA id jy7sm2820896wid.22.2015.03.21.08.30.58 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Mar 2015 08:31:00 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Thunderbird/36.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::230 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:184102 Archived-At: On 03/10/2015 03:16 AM, Stefan Monnier wrote: > I'm not sure what you mean by that question: if the outer mode uses > narrowing to specify the bounds of the chunk, then indentation code > can't use `widen'. Use of narrowing inside the indentation code will be > fine, but use of widen will not. Yet, "grep widen lisp/progmodes/*.el" > suggests that it's probably used by several indenters. The same places that use `widen' now would have to be adapted anyway, whether not to use it at all, or to behave according to the new variable. The former change sounds simpler to me. > I think specifying the chunk bounds via some dynamically-scoped var is > a pretty safe option. Maybe it will be supplanted in the future by some > other alternative, but it doesn't impose any particular implementation > constraint, contrary to the use of narrowing. What do you think of `prog-narrow-to-region' and `prog-widen'? Just having a dynamically-scoped var by itself seems a more verbose and error-prone approach to me.