From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: icalendar.el bug fix patch Date: Mon, 4 Nov 2019 07:16:19 -0800 (PST) Message-ID: <47f31dc2-0d39-4709-b54a-1e9305a4eb00@default> References: <875zkfd1rz.fsf@hm.sivalik.com> <83eeyslytn.fsf@gnu.org> <87imo3g8af.fsf@hm.sivalik.com> <831rurn3vs.fsf@gnu.org> <321C5595-5EBF-4231-9179-FE1CA4A412F7@acm.org> <83tv7nlo16.fsf@gnu.org> <34fad408-c220-7980-c7fe-1299093d842f@cs.ucla.edu> <871ruq88yp.fsf@mail.linkov.net> <87bltsisui.fsf@mail.linkov.net> <197e1e7e-5cdc-f91d-bc1d-23fe10de8897@cs.ucla.edu> <7D108819-09C6-4B48-BC54-FDC47DA51AB1@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="4775"; mail-complaints-to="usenet@blaine.gmane.org" Cc: rajeev@sivalik.com, Eli Zaretskii , emacs-devel@gnu.org, Stefan Monnier , Juri Linkov To: =?iso-8859-1?B?TWF0dGlhcyBFbmdkZWflcmQ=?= , Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 04 16:21:25 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iReAW-00016f-Si for ged-emacs-devel@m.gmane.org; Mon, 04 Nov 2019 16:21:25 +0100 Original-Received: from localhost ([::1]:34474 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iReAV-0003OM-Gr for ged-emacs-devel@m.gmane.org; Mon, 04 Nov 2019 10:21:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41100) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRe5r-0005F7-Ep for emacs-devel@gnu.org; Mon, 04 Nov 2019 10:16:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRe5p-0003q2-KE for emacs-devel@gnu.org; Mon, 04 Nov 2019 10:16:34 -0500 Original-Received: from userp2120.oracle.com ([156.151.31.85]:54804) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iRe5n-0003oU-9W; Mon, 04 Nov 2019 10:16:31 -0500 Original-Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xA4FCHJ1018099; Mon, 4 Nov 2019 15:16:25 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2019-08-05; bh=hhHt3bWJpKKZqsfXiOVUY8zchhXwrCL6XUMyNUCe5ms=; b=Y5NdcrKUbNhOD5YY4FlAUVKppjucoRdZaamQzo76vmX8yaMATc9BKlBUFxRhXFsJ2nVq DMOs3S6WX3IlHsfmlnft4p9YtL3VHgbFXqfeUOlYkoR8t4CVDmpNc5x0j0eiX/g8+pqZ FSsVml7ZPrUJ2lPT46dxyUSOGtXSEmPPfEGVT4hqGfsJuTuzHTBxHynoS97AzhH57X7U T26sV1eWTKAaG4shh2x2Y0VBHIPOpR2E3TcHp6iH/SRZ711YdnGpjMCvizaGz0lB9u0f vGUsaENlpd+tWyhTgtGZi36WIJtu9MAPuf6/jutgqcVxnFwqQbd8PJY3nw8VG3+sz5cW zQ== Original-Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2120.oracle.com with ESMTP id 2w12eqyvkq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 Nov 2019 15:16:25 +0000 Original-Received: from pps.filterd (aserp3030.oracle.com [127.0.0.1]) by aserp3030.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xA4FAAX2019911; Mon, 4 Nov 2019 15:16:24 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserp3030.oracle.com with ESMTP id 2w1kxmhnje-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 Nov 2019 15:16:24 +0000 Original-Received: from abhmp0006.oracle.com (abhmp0006.oracle.com [141.146.116.12]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id xA4FGKxT015983; Mon, 4 Nov 2019 15:16:21 GMT In-Reply-To: <7D108819-09C6-4B48-BC54-FDC47DA51AB1@acm.org> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4900.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9431 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=922 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911040151 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9431 signatures=668685 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911040151 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 156.151.31.85 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.org gmane.emacs.devel:241780 Archived-At: > > If we want to keep with this tradition, Emacs should use a separate > escape sequence for "match any single character including newline". >=20 > I very much agree, for practicality more than tradition. An atomic > notation is far superior to a modal mechanism. A single escape is a good thing to have. That's a good start. But it's not either-or. There's also an advantage, for users (interactively) and for code, to be able to use the _same regexp_ to optionally interpret `.' as match-any-char-including-newline. IMO we should do both: (1) add an escape for this and (2) provide a variable and toggle command that makes `.' match either possibility: any char or any char except newline. There are lots of places in existing code that use predefined regexps, including complex ones. Letting these optionally interpret `.' to include a newline adds functionality. Even more importantly probably is letting users use `.' interactively either way. It's also possible to limit the variable and its toggling to interactive use (as I explained earlier). IOW, (optionally) not let it affect regexps in code.