From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Off Topic
Date: Thu, 24 May 2018 17:41:04 +0200 [thread overview]
Message-ID: <87tvqxrrhr.fsf@gmail.com> (raw)
In-Reply-To: <83sh6haxm9.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 24 May 2018 18:20:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Noam Postavsky <npostavs@gmail.com>, van@scratch.space, eliz@gnu.org, emacs-devel@gnu.org
>> Date: Thu, 24 May 2018 11:03:33 +0200
>>
>> Documenting rx.el would be a more productive use of time, I think,
>> especially since Iʼve now noticed via reading rx.el that we already
>> have sregex as well. Let's pick one rather than inventing a third
>> syntax.
>
> I'm all for more documentation, but in this case what would you add to
> the doc string that already is very long and very detailed?
I meant documentation of its existence, something like:
diff --git i/doc/emacs/search.texi w/doc/emacs/search.texi
index 263c4c5dcc..fd65cf3b38 100644
--- i/doc/emacs/search.texi
+++ w/doc/emacs/search.texi
@@ -802,7 +802,8 @@ Regexps
This section (and this manual in general) describes regular
expression features that users typically use. @xref{Regular
Expressions,,, elisp, The Emacs Lisp Reference Manual}, for additional
-features used mainly in Lisp programs.
+features used mainly in Lisp programs. For an alternative and more
+verbose syntax, see the @code{rx} package.
Regular expressions have a syntax in which a few characters are
special constructs and the rest are @dfn{ordinary}. An ordinary
next prev parent reply other threads:[~2018-05-24 15:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:18 bug#31544: Emacs 26.1 rc-1 Texinfo View fails to italicize all 6 lines in paragraph Van L
2018-05-21 16:23 ` Eli Zaretskii
2018-05-21 23:45 ` Van L
2018-05-22 2:13 ` Richard Stallman
2018-05-22 2:40 ` Van L
2018-05-22 4:32 ` Eli Zaretskii
2018-05-22 6:58 ` Off Topic (was: bug#31544) Van L
2018-05-23 3:24 ` Richard Stallman
2018-05-23 3:44 ` Van L
2018-05-23 11:06 ` Noam Postavsky
2018-05-24 2:48 ` Richard Stallman
2018-05-24 9:03 ` Off Topic Robert Pluim
2018-05-24 15:20 ` Eli Zaretskii
2018-05-24 15:41 ` Robert Pluim [this message]
2018-05-24 17:07 ` Eli Zaretskii
2018-05-25 2:59 ` Richard Stallman
2018-05-24 16:35 ` Off Topic (was: bug#31544) Alan Mackenzie
2018-05-24 16:53 ` Yuri Khan
2018-05-24 19:57 ` Alan Mackenzie
2018-05-24 20:24 ` Noam Postavsky
2018-05-24 20:36 ` Off Topic Stefan Monnier
2018-05-25 3:01 ` Off Topic (was: bug#31544) Richard Stallman
2018-05-25 2:59 ` Richard Stallman
2018-05-24 17:01 ` Eli Zaretskii
2018-05-28 22:42 ` bug#31544: Emacs 26.1 rc-1 Texinfo View fails to italicize all 6 lines in paragraph Noam Postavsky
2022-01-23 13:57 ` bug#31544: texinfo-mode fails to consistently fontify multiline @i{italic text} Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvqxrrhr.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.