From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Completion for search queries
Date: Tue, 03 Nov 2009 09:35:34 -0800 [thread overview]
Message-ID: <1257269366-sup-159@masanjin.net> (raw)
In-Reply-To: <1257265840-sup-9752@thinkpad-ubuntu>
Reformatted excerpts from Christopher Bertels's message of 2009-11-03:
> Cool, anyone who knows how & wants to implement this? ;)
If anyone is interested, I would suggest this approach: have each index
(Ferret and Xapian) have a method that returns a list of query terms,
and then look at how BufferManager#ask_many_emails_with_completions
works, and implement something similar called ask_for_search_query or
the like. Then have bin/sup circa line 275 call that instead of #ask.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-03 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 8:26 Christopher Bertels
2009-11-02 15:58 ` William Morgan
2009-11-03 16:31 ` Christopher Bertels
2009-11-03 17:35 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1257269366-sup-159@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.org \
/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