From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "T. V. Raman" Newsgroups: gmane.emacs.devel Subject: minibuffer-completion-help, metadata and determining completions sort order Date: Sat, 18 Jun 2011 09:46:30 -0700 Message-ID: <19964.54886.521086.231349@gargle.gargle.HOWL> Reply-To: tv.raman.tv@gmail.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1308416663 27209 80.91.229.12 (18 Jun 2011 17:04:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 18 Jun 2011 17:04:23 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 18 19:04:20 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QXywV-0006HR-1d for ged-emacs-devel@m.gmane.org; Sat, 18 Jun 2011 19:04:19 +0200 Original-Received: from localhost ([::1]:58152 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QXywU-0008F1-0U for ged-emacs-devel@m.gmane.org; Sat, 18 Jun 2011 13:04:18 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:45713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QXyfO-0003pF-F0 for emacs-devel@gnu.org; Sat, 18 Jun 2011 12:46:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QXyfN-0007fL-9V for emacs-devel@gnu.org; Sat, 18 Jun 2011 12:46:38 -0400 Original-Received: from mail-pv0-f169.google.com ([74.125.83.169]:40342) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QXyfM-0007fF-Sp for emacs-devel@gnu.org; Sat, 18 Jun 2011 12:46:37 -0400 Original-Received: by pvc12 with SMTP id 12so3256447pvc.0 for ; Sat, 18 Jun 2011 09:46:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:content-type :content-transfer-encoding:message-id:date:to:subject:x-mailer :reply-to:from:x-attribution; bh=b5PEmWYZIuZCCeNBN19GvEPN73X+oOvl3GKVHtHHbiE=; b=CROA5LNqaYdvoFlnzvZa1Ge1+MCbEg66euj8bLhT5YI+ze9OWaW4BMvXkLP2IMnb22 63i5SuY8NuAKhJz3yXH7HVVjdwLMTVojLUDAHSxJnRkBQMESKEFEouS5mUIgoC74PX6/ DczukM8H4HipUfHihTAY2gvpB8FnisY4tpEi8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-type:content-transfer-encoding:message-id:date :to:subject:x-mailer:reply-to:from:x-attribution; b=wABOpiJwBiJ1PtT3twBzw0dmMLOYA7eDZQbIN0UjUByidM/pjUFLOaHXkJ2XMXevj6 hNcQqRnWxK3EFvT0utHLIVlysH2lRJVMej5GFYrLnII4asWe6zxnmtIEHhYOzXuyUnol kwdabl9yY2D/0w4MhKAJZr0KPA0S/BCZUBBIg= Original-Received: by 10.142.14.10 with SMTP id 10mr532936wfn.417.1308415595716; Sat, 18 Jun 2011 09:46:35 -0700 (PDT) Original-Received: from labrador.emacspeak.org (c-71-202-188-217.hsd1.ca.comcast.net [71.202.188.217]) by mx.google.com with ESMTPS id f3sm2146698pbj.16.2011.06.18.09.46.34 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 18 Jun 2011 09:46:34 -0700 (PDT) X-Mailer: VM 8.1.1 under 24.0.50.1 (i686-pc-linux-gnu) x-attribution: tvr X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 74.125.83.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140653 Archived-At: I'm having a hard time understanding how one provides custom metadata to completion-all-completions and friends. Also, looking at the code in minibuffer-completions-help, I see that the metadata can provide a custom sort function -- sounds good. However the specific use case I want is the ability to not sort the completions -- Ineed this for implementing Google Suggest in the minibuffer. I had asked about this many moons ago and Stefane had said that the code in minibuffer.el would be changing to support this, assuming the metadata functionality is to address that and other use cases? Anyway, I'd like the ability to be able to set things up for Google Suggest so the completions list goes through unmolested, and as things stand, Isuppose I could provide a no-op sorter once I figure out to supply the metadata; however that still feels wasteful since we would end up traversing the list of completions for no reason --- there is no option to avoid the sort call in minibuffer-completions-help -- Best Regards, --raman