[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#54017: add regexp translation option to read-regexp
From: |
emacsq |
Subject: |
bug#54017: add regexp translation option to read-regexp |
Date: |
Tue, 15 Feb 2022 20:21:35 +0000 |
Suppose, the user wants to use ( ) for capturing and
\( \) for matching parens. He provides a function
which does this translation.
If this new option is set and is a function which does
the translation then read-regexp will
- accept the format which the user prefers, in this case
( ... ) for capturing.
- store regexps in this format in history, so the user
can work with the user's preferred format even when
retrieving history entries.
- return the elisp format regexp by calling the function
provided by the user which does the translation.
- bug#54017: add regexp translation option to read-regexp,
emacsq <=
- bug#54017: add regexp translation option to read-regexp, Juri Linkov, 2022/02/16
- bug#54017: add regexp translation option to read-regexp, emacsq, 2022/02/16
- bug#54017: add regexp translation option to read-regexp, Juri Linkov, 2022/02/17
- bug#54017: add regexp translation option to read-regexp, Juri Linkov, 2022/02/17
- bug#54017: add regexp translation option to read-regexp, Eli Zaretskii, 2022/02/17
- bug#54017: add regexp translation option to read-regexp, emacsq, 2022/02/17
- bug#54017: add regexp translation option to read-regexp, Juri Linkov, 2022/02/17
- bug#54017: add regexp translation option to read-regexp, emacsq, 2022/02/20
- bug#54017: add regexp translation option to read-regexp, Eli Zaretskii, 2022/02/20
- bug#54017: [External] : bug#54017: add regexp translation option to read-regexp, Drew Adams, 2022/02/20