unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: van@scratch.space, eliz@gnu.org,
	Noam Postavsky <npostavs@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Off Topic
Date: Thu, 24 May 2018 11:03:33 +0200	[thread overview]
Message-ID: <87d0xltogq.fsf@gmail.com> (raw)
In-Reply-To: <E1fLgJH-0007py-MH@fencepost.gnu.org> (Richard Stallman's message of "Wed, 23 May 2018 22:48:59 -0400")

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > > We have such things but we haven't adopted any of them in Emacs itself.
>
>   > Doesn't rx.el qualify?
>
> It's an example of what I said.  We have it, but we don't actually use it
> much if at all.  This suggests to me that it has drawbacks which prevent
> it from being clearly superior.
>

Iʼve never used rx.el because I didnʼt know it existed. Itʼs not
described in the regular expression chapter of the emacs lisp
reference manual, nor in the emacs user manual.

> If someone comes up with a replacement syntax that reduces the drawbacks,
> we might start using it all the time.

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.

Robert



  reply	other threads:[~2018-05-24  9:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7D0B397D-5D1B-4B8C-93B6-1CA207DD552A@scratch.space>
     [not found] ` <E1fKwoI-0000Ug-Lv@fencepost.gnu.org>
     [not found]   ` <A424F9A2-E4C4-47CD-A4B4-E9CEB32A60FD@scratch.space>
     [not found]     ` <A2BA1EF2-D393-43D5-8F44-E802DC705C0A@gnu.org>
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               ` Robert Pluim [this message]
2018-05-24 15:20                 ` Off Topic Eli Zaretskii
2018-05-24 15:41                   ` Robert Pluim
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

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=87d0xltogq.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=npostavs@gmail.com \
    --cc=rms@gnu.org \
    --cc=van@scratch.space \
    /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).