From: Oleh Krehel <ohwoeowho@gmail.com>
To: Erik Hetzner <egh@e6h.org>
Cc: Org Mode <emacs-orgmode@gnu.org>, John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: John's amazing indexing posts
Date: Tue, 28 Jul 2015 10:14:37 +0200 [thread overview]
Message-ID: <8761541yxe.fsf@gmail.com> (raw)
In-Reply-To: <55b65efa.c765460a.f3aa8.1380@mx.google.com> (Erik Hetzner's message of "Mon, 27 Jul 2015 09:40:25 -0700")
Erik Hetzner <egh@e6h.org> writes:
> I believe that you can rewrite using the recoll tool directly instead
> of recollq, using `recoll -t -b 'search string'`:
>
> (defun counsel-recoll-function (string &optional _pred &rest _unused)
> "Grep in the current directory for STRING."
> (if (< (length string) 3)
> (counsel-more-chars 3)
> (counsel--async-command
> (format "recoll -t -b '%s'" string))
> nil))
>
> If you use `recoll -A -t 'search string'` and do some post processing
> you could get snippets, too. I can’t see how to do that easily with
> counsel--async-command, though.
Thanks, Erik. I've merged your pull request. So now it's very easy to
start using recoll with Emacs - outside of Emacs the only necessary
thing is:
sudo apt-get install recoll
And inside Emacs it's:
package-install counsel
I did look into the annotation switch. The thing is that it just shows
some database aggregates instead of the actual line context, like grep
does. With 30 candidates and no line context, a pure list of files looks
simpler than a list of files and a list of out-of-sequence words that
each file contains.
--Oleh
next prev parent reply other threads:[~2015-07-28 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 9:41 John's amazing indexing posts Matt Price
2015-07-13 14:31 ` John Kitchin
2015-07-27 5:16 ` Erik Hetzner
2015-07-27 13:19 ` Oleh Krehel
2015-07-27 14:19 ` John Kitchin
2015-07-27 16:40 ` Erik Hetzner
2015-07-28 8:14 ` Oleh Krehel [this message]
2015-07-31 7:55 ` Xebar Saram
2015-07-31 8:31 ` Oleh Krehel
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=8761541yxe.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=egh@e6h.org \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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.