unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Juri Linkov <juri@linkov.net>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	rajeev@sivalik.com
Subject: Re: icalendar.el bug fix patch
Date: Mon, 4 Nov 2019 12:56:29 +0100	[thread overview]
Message-ID: <7D108819-09C6-4B48-BC54-FDC47DA51AB1@acm.org> (raw)
In-Reply-To: <197e1e7e-5cdc-f91d-bc1d-23fe10de8897@cs.ucla.edu>

4 nov. 2019 kl. 01.50 skrev Paul Eggert <eggert@cs.ucla.edu>:

> If we want to keep with this tradition, Emacs should use a separate escape sequence for "match any single character including newline".

I very much agree, for practicality more than tradition. An atomic notation is far superior to a modal mechanism.

> On looking into what other systems do, I find that I prefer Vim's syntax of '\_.' to match any single character including newline.

Thanks for finding that. Another advantage of '\_.' is that it does not change the behaviour of existing regexps; '\!' currently means '!', but '\_.' is a syntax error.

There doesn't seem to be much else in Vim's '\_' family worth appropriating for Emacs. If anything, I'd favour adding some (non-Vim) Unicode patterns: \p and \P for general categories and \X for graphemes.





  reply	other threads:[~2019-11-04 11:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 13:33 icalendar.el bug fix patch Rajeev Narang via Emacs development discussions.
2019-11-01  9:40 ` Eli Zaretskii
2019-11-01 10:51   ` Mattias Engdegård
2019-11-01 13:00     ` Eli Zaretskii
2019-11-01 11:12   ` Rajeev Narang via Emacs development discussions.
2019-11-01 13:05     ` Eli Zaretskii
2019-11-01 13:24       ` Mattias Engdegård
2019-11-01 13:33         ` Eli Zaretskii
2019-11-01 21:19           ` Paul Eggert
2019-11-01 21:38             ` Mattias Engdegård
2019-11-02 18:39             ` Juri Linkov
2019-11-03 13:21               ` Richard Stallman
2019-11-03 16:55                 ` Drew Adams
2019-11-03 19:55               ` Stefan Monnier
2019-11-03 20:54                 ` Juri Linkov
2019-11-03 21:10                   ` Stefan Monnier
2019-11-03 21:32                     ` Juri Linkov
     [not found]                     ` <E81C3456-834F-469D-B8CA-80B1CDD311F8@acm.org>
2019-11-04  0:50                       ` Paul Eggert
2019-11-04 11:56                         ` Mattias Engdegård [this message]
2019-11-04 15:16                           ` Drew Adams
2019-11-03  3:24             ` Richard Stallman
2019-11-03 16:54               ` Drew Adams
2019-11-01 16:44         ` Howard Melman
2019-11-01 14:30       ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7D108819-09C6-4B48-BC54-FDC47DA51AB1@acm.org \
    --to=mattiase@acm.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=rajeev@sivalik.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).