From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexis Newsgroups: gmane.emacs.devel Subject: Re: Regular expression creation [was: Re: Emacs Lisp's future] Date: Fri, 19 Sep 2014 10:00:36 +1000 Message-ID: <87y4tgwjso.fsf@gmail.com> References: <87wq97i78i.fsf@earlgrey.lan> <20140917202418.240bbd2c@forcix> <87egv9y5m6.fsf@gmail.com> <541B0AFC.9080501@dancol.org> <87zjdwwpab.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1411085574 27754 80.91.229.3 (19 Sep 2014 00:12:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Sep 2014 00:12:54 +0000 (UTC) To: Emacs development discussions Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 19 02:12:45 2014 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 1XUlob-0008Jg-5u for ged-emacs-devel@m.gmane.org; Fri, 19 Sep 2014 02:12:45 +0200 Original-Received: from localhost ([::1]:54875 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUloa-00077S-7E for ged-emacs-devel@m.gmane.org; Thu, 18 Sep 2014 20:12:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47918) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUlo1-0006Yo-Up for emacs-devel@gnu.org; Thu, 18 Sep 2014 20:12:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUlnw-0001CP-Gs for emacs-devel@gnu.org; Thu, 18 Sep 2014 20:12:09 -0400 Original-Received: from mail-pd0-x22e.google.com ([2607:f8b0:400e:c02::22e]:53523) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUlnw-0001Bx-Ap for emacs-devel@gnu.org; Thu, 18 Sep 2014 20:12:04 -0400 Original-Received: by mail-pd0-f174.google.com with SMTP id v10so2422564pde.19 for ; Thu, 18 Sep 2014 17:11:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:to:subject:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; bh=5VlqZ4ezxijc+qbk+xkZmzpnpA6Kgt2ZLNmJHq8lT9Y=; b=Fjid2GNdv6mUrqgekJ3bbLhjIsHmJvMvWoqTk0zmWW2wQS+CqNI76vlxPHaCF0wg1q mNSDBzNzMFJ3DaxRc2MpKN9MjMHC0zzojmOnTC1Mq8CYmCtC/NVfXDTSBeE8vmQAP8n8 1v67oG5hu4A3X15CcEGG7agqOczKLKSYcZovwtH/Hg8p6tU/M5w/VfndfId8TjNaAhCh 9+ZBbYGY/PqZIKP7Oey8q1j/AJVTpY1gO8CSECby9MTGfpb5EzWZdV9b0h8LDuNyPzuQ N1Jo4dnyiPYTCNuSbYMWZr4Q65xHS8FGw4+15rkKQw3LogLWpi8rj9EeTNCAn6wSFIxl 6NdA== X-Received: by 10.67.23.103 with SMTP id hz7mr6855968pad.118.1411085518220; Thu, 18 Sep 2014 17:11:58 -0700 (PDT) Original-Received: from localhost (ppp118-209-61-149.lns20.mel4.internode.on.net. [118.209.61.149]) by mx.google.com with ESMTPSA id xu4sm164777pab.30.2014.09.18.17.11.55 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Sep 2014 17:11:57 -0700 (PDT) In-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c02::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:174527 Archived-At: Aurélien Aptel writes: > Le 19 sept. 2014 00:14, "Alexis" a écrit : >> >> Daniel Colascione writes: >> >> > On 09/17/2014 07:07 PM, Alexis wrote: >> i find rx .... unwieldy. For me, rx is to PCREs as a putative function >> 'apply-function-to-each-element-of-sequence' is to 'mapcar'. i don't >> want an English-language wrapper for regular expressions; i want regular >> expressions that don't suffer from backslashitis. And, given the several > > See http://lists.gnu.org/archive/html/help-gnu-emacs/2014-07/msg00086.html Yes, that was a great discussion - thank you for initiating it, and for your explorations in this area! i might indeed try making use of that `my-raw-string` function when creating REs .... But, setting aside the debates around raw strings, i still feel something like Stefan's suggestion for a built-in `re-escape` function would probably solve most of the issues i have with ELisp REs. Alexis.