[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: icalendar.el bug fix patch
From: |
Drew Adams |
Subject: |
RE: icalendar.el bug fix patch |
Date: |
Mon, 4 Nov 2019 07:16:19 -0800 (PST) |
> > 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.
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.
- Re: icalendar.el bug fix patch, (continued)
- Re: icalendar.el bug fix patch, Stefan Monnier, 2019/11/03
- Re: icalendar.el bug fix patch, Juri Linkov, 2019/11/03
- Re: icalendar.el bug fix patch, Stefan Monnier, 2019/11/03
- Re: icalendar.el bug fix patch, Juri Linkov, 2019/11/03
- Message not available
- Re: icalendar.el bug fix patch, Paul Eggert, 2019/11/03
- Re: icalendar.el bug fix patch, Mattias EngdegÄrd, 2019/11/04
- RE: icalendar.el bug fix patch,
Drew Adams <=
- Re: icalendar.el bug fix patch, Richard Stallman, 2019/11/02
- RE: icalendar.el bug fix patch, Drew Adams, 2019/11/03
- Re: icalendar.el bug fix patch, Howard Melman, 2019/11/01
- Re: icalendar.el bug fix patch, Richard Stallman, 2019/11/01