unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: ltolenaar@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to find lines not matching a certain pattern - ie grep -v
Date: Wed, 25 Feb 2015 01:29:11 +0000	[thread overview]
Message-ID: <871tleok2g.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <3fc1ac7e-624f-4fa5-8770-345d504c48f7@googlegroups.com> (ltolenaar@gmail.com)

ltolenaar@gmail.com writes:

> The grep -v may not work if it is not installed as is likely to be the
> case on windows. Apparently what is needed is a true grep
> implementation in compiled elisp. I would be glad to do this if there
> are substantial pointers or instruction.

If your on MS Windows there are plenty of ways to get Grep.  It's
available in Eli Zaretski's ezwinports:
http://sourceforge.net/projects/ezwinports/

That also includes find, man, diff, groff, make, gnutls and a bunch of
other useful GNU programs.  There's MinGW, MinGW2 and GNUWin32 for all
the stuff it doesn't cover (I use MinGW).

Vincent Goulet supplies an Emacs for MS Window which comes with some of
these things (though not grep, AFAIK).

Making a grep replacement in elisp would certainly be possible but it
would be slow.  Emacs regexps aren't fast and neither is it's byte-code
interpreter.  Performance is quite critical for Grep.

There is a "find" replacement in Emacs, find-lisp.el,
e.g. find-lisp-find-dired.  It's useful if you're stuck without a port
of GNU find, but it's not as fast and doesn't have the same features.

If your looking for a project making an MS Win distribution of Emacs
with all the GNU utilities it uses would be a good one.

BR,
Robert Thorpe



  reply	other threads:[~2015-02-25  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 18:11 How to find lines not matching a certain pattern - ie grep -v gnuist006
2015-02-22 20:40 ` Dan Espen
2015-02-22 22:01   ` ltolenaar
2015-02-25  1:29     ` Robert Thorpe [this message]
2015-02-22 20:55 ` Drew Adams
2015-02-23  3:23 ` Barry Margolin
2015-02-23  4:20   ` Michael Heerdegen

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=871tleok2g.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=ltolenaar@gmail.com \
    /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.
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).