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: Sun, 3 Nov 2019 08:54:59 -0800 (PST) Message-ID: <25fcac1f-16bf-4229-8710-dd22b5a9e01e@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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="170647"; mail-complaints-to="usenet@blaine.gmane.org" Cc: mattiase@acm.org, eliz@gnu.org, rajeev@sivalik.com, emacs-devel@gnu.org To: rms@gnu.org, Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 03 17:56:36 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 1iRJB5-000iFK-Pm for ged-emacs-devel@m.gmane.org; Sun, 03 Nov 2019 17:56:35 +0100 Original-Received: from localhost ([::1]:54886 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRJB4-00022G-DB for ged-emacs-devel@m.gmane.org; Sun, 03 Nov 2019 11:56:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53127) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRJ9z-0001xH-F4 for emacs-devel@gnu.org; Sun, 03 Nov 2019 11:55:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRJ9y-0008UJ-AB for emacs-devel@gnu.org; Sun, 03 Nov 2019 11:55:27 -0500 Original-Received: from userp2120.oracle.com ([156.151.31.85]:33802) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iRJ9w-0008T3-1X; Sun, 03 Nov 2019 11:55:24 -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 xA3Glk8T062491; Sun, 3 Nov 2019 16:55:04 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=OotUGCGFtL6F1eqHthso6pRkdbMRgDIvQ0p/ZL39wqQ=; b=rbDCClDS17wEkgLyL82K0ZrHsXehLrC8im1P8Dymn7PLIkIOBhWPh1VylYrIYfJtePgP QhItJlSepEC7tI5NcZcG2SBVSk1HbAbRafWc1a6e1ggRQMNi/R+lU7UGh7FVH7Ft2zhs vjfGmwdd9tWLQMr/La4pTQb7GeYMIXakfr16J21d/uzuMBs1XsfCFACV3CDwxZdWUoTx PjFBwPcUknAzRWAvXQcb2EMGSaaL47lHO/lEOilVDfZZyyGQfSqWwXtUdSBIZCSqSyqR 9WyePkVr8OZHi9ESaYuJHlpxI2q5ddCuFGWMjcXkrYAnuZcLYRyXQOjGFEj7rA79faed aw== Original-Received: from userp3020.oracle.com (userp3020.oracle.com [156.151.31.79]) by userp2120.oracle.com with ESMTP id 2w12equkcg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 03 Nov 2019 16:55:03 +0000 Original-Received: from pps.filterd (userp3020.oracle.com [127.0.0.1]) by userp3020.oracle.com (8.16.0.27/8.16.0.27) with SMTP id xA3GkEei110582; Sun, 3 Nov 2019 16:55:03 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userp3020.oracle.com with ESMTP id 2w1kxbs8h9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 03 Nov 2019 16:55:03 +0000 Original-Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id xA3Gt0rS026264; Sun, 3 Nov 2019 16:55:00 GMT In-Reply-To: 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=9430 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=658 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911030174 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9430 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=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=738 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911030174 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:241754 Archived-At: >> But since the concept is useful, how about if we >> create an escape for it? For example, we could >> establish \! as a regexp that matches any single >> character. >=20 > +1. [Interesting. I skipped this thread, based on the Subject. Just stumbled on this part of it, about having a simple pattern to match what `\\(.\\|[\n]\\)' matches. Wouldn't have guessed that from the Subject.] FWIW, I proposed this back in 2006. Actually, I proposed a toggle, so you could use the _same_ regexp to match either any char or any char except newline. Nothing wrong with having a separate escape, such as `\!', to always match what `\\(.\\|[\n]\\)' matches. But it would still be good to (also) have a toggle, to be able to make just `.' match the same thing. https://lists.gnu.org/archive/html/emacs-devel/2006-03/msg00162.html In 2012 I again voiced the proposal (in the context of mentioning how Icicles lets you do such things): I proposed long ago, for instance, a toggle for a `.' in regexp search to match also newlines, i.e., any character. IOW, `.' in one mode state of the toggle, would be equivalent to "\\(.\\|[\n]\\)" in the other (traditional) state. https://lists.gnu.org/archive/html/emacs-devel/2012-08/msg00832.html So how about adding an escape, such as `\!', and _also_ adding a toggle (variable and command to toggle it) that treats both `\!' and plain `.' the same; that is; have them each match any char?