unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Daniel Berdine <rothaar@gmail.com>
Subject: Re: igrep on remote files with tramp? (~Solved)
Date: Mon, 1 Aug 2005 01:01:07 -0400	[thread overview]
Message-ID: <0001HW.BF1324D30245A568F0305550@news.ispnetbilling.com> (raw)
In-Reply-To: rothaar-CADE09.13380328072005@news.ispnetbilling.com

In case it helps anyone else, I've found an acceptable solution to this 
problem through color-moccur.el 
(http://www.bookshelf.jp/elc/color-moccur.el).

For cases where there are likely to be several searches, it seems the fastest 
method is to first load all the files one wishes to search (C-u 
dired-do-find-marked-files in my case) and then run moccur. For a one-off 
search, or for local searches where read-times aren't so prohibitive, 
dired-do-moccur works nicely.

Other than the necessity of loading all the files, this actually seems 
preferable to an igrep solution, and short of running the search remotely, 
some such delay or memory hit is inevitable.

Thanks for the input, and hopefully this is useful for someone else.

-Dan

      parent reply	other threads:[~2005-08-01  5:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 17:38 igrep on remote files with tramp? Daniel Berdine
2005-07-28 17:55 ` Daniel Berdine
2005-07-28 19:28 ` Kevin Rodgers
2005-07-28 21:02   ` Michael Albinus
2005-07-28 22:54     ` Kevin Rodgers
2005-07-28 19:43 ` Michael Albinus
     [not found] ` <mailman.1998.1122579165.20277.help-gnu-emacs@gnu.org>
2005-07-31 23:52   ` Daniel Berdine
2005-08-02 20:35     ` Kevin Rodgers
2005-08-02 23:56       ` Kevin Rodgers
2005-08-03  8:10       ` Michael Albinus
     [not found] ` <mailman.2000.1122579980.20277.help-gnu-emacs@gnu.org>
2005-08-01  0:04   ` Daniel Berdine
2005-08-01  5:01 ` Daniel Berdine [this message]

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=0001HW.BF1324D30245A568F0305550@news.ispnetbilling.com \
    --to=rothaar@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).