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: Upcoming loss of usability of Emacs source files and Emacs. Date: Mon, 29 Jun 2015 02:31:44 +0300 Message-ID: <559083E0.7080801@yandex.ru> References: <20150615142237.GA3517@acm.fritz.box> <87y4jkhqh5.fsf@uwakimon.sk.tsukuba.ac.jp> <557F3C22.4060909@cs.ucla.edu> <5580D356.4050708@cs.ucla.edu> <87si9qonxb.fsf@gnu.org> <5581C29E.1030101@yandex.ru> <55826FFA.2040907@yandex.ru> <5583FEA0.4050600@yandex.ru> <558448A3.9040501@yandex.ru> <5590482E.6060604@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 1435534341 15612 80.91.229.3 (28 Jun 2015 23:32:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Jun 2015 23:32:21 +0000 (UTC) Cc: acm@muc.de, stephen@xemacs.org, Paul Eggert , rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 29 01:32:14 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 1Z9M3Y-0003wz-IE for ged-emacs-devel@m.gmane.org; Mon, 29 Jun 2015 01:32:12 +0200 Original-Received: from localhost ([::1]:40110 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9M3X-0002OP-GC for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2015 19:32:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34609) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9M3U-0002OJ-F7 for emacs-devel@gnu.org; Sun, 28 Jun 2015 19:32:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9M3P-00010T-3k for emacs-devel@gnu.org; Sun, 28 Jun 2015 19:32:08 -0400 Original-Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:36415) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9M3O-0000y0-TE; Sun, 28 Jun 2015 19:32:03 -0400 Original-Received: by wguu7 with SMTP id u7so127480153wgu.3; Sun, 28 Jun 2015 16:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=+iA8fg/xk0rp2gIVQkTtNbP9c1oPz7Sfn3bAovsMN2o=; b=gXoHihJqhsL+I+1iXVt+cG/oJFTU6eHnOsAi+oNKY17sOdbV/5F5WDEWkExbA30dkV AMT2p36dsxl6zUny/ObyBniX8GlI9xkNhUbzq2wJx+EU1N/nhGdF1PIHaPWukj1ZRWN5 Gpxb1RwuDjbgOV38QRMx16+YqmCuDsHf8zob8qGUniRsT5Np+TBqiVFI2DLuP037MGWG Mx4Nt//5WkGHMKEvYAorzPIdJqll/ZPTGRT/TzKpngC6DbUO4HFckUH5pnAW+YtW9UNW YV5WHv58gpOFyUQX5baWZXlCnfomDZPz0w6cFumHS2UNPH6b0Xh73eywQaW66VZ6CBR3 YT4A== X-Received: by 10.180.106.137 with SMTP id gu9mr17659952wib.54.1435534314684; Sun, 28 Jun 2015 16:31:54 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id j7sm61181941wjz.11.2015.06.28.16.31.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jun 2015 16:31:54 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <5590482E.6060604@yandex.ru> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22e 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:187631 Archived-At: On 06/28/2015 10:17 PM, Dmitry Gutov wrote: > That seems non-ideal because the regexp engine has no way to check the > text property on a quote character. Thus, we can't make a regexp that > will match asd'asd in `asd\\'asd', if the escaped is handled in > substitute-command-keys. > > Although admittedly, this could be handled programmatically. Never mind, I just did that in a functional matcher. And there's no reasonable way to get by with just a regexp with Paul's latest requirements.