unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Van L <van@scratch.space>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Off Topic (was: bug#31544)
Date: Tue, 22 May 2018 23:24:07 -0400	[thread overview]
Message-ID: <E1fLKNj-0006iA-OQ@fencepost.gnu.org> (raw)
In-Reply-To: <6271469D-6B02-4334-828E-D81816143734@scratch.space> (message from Van L on Tue, 22 May 2018 16:58:32 +1000)

[[[ 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. ]]]

  > If a voice-recognition module is workable and Emacs has the skill
  > to compose raw regexps from less terse human friendly natural
  > language statements, with marks and point at data, would it be
  > easy to marry the two?

We don't have adequate free software for voice recognition, as far as
I know, and we should not add Emacs support for any such nonfree
program.

Compiling a clearer syntax into regexps is feasible.
We have such things but we haven't adopted any of them in Emacs itself.
Perhaps they are not really convenient.  It would be good to figure out
why not, and make one that is convenient to use, and then use it.

Perhaps the inconvenience has to do with combining the complex
parts of the regexp with the simple strings to match.  Is that so?


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2018-05-23  3:24 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 [this message]
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
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=E1fLKNj-0006iA-OQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).