From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Adding the `prescient` packages to NonGNU ELPA? Date: Sun, 20 Nov 2022 13:39:23 -0500 Message-ID: References: <16193c73-ab80-04c9-558f-d5e6142f38f3@protonmail.com> <871qpydllo.fsf@posteo.net> <874jutft6g.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7013"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Philip Kaludercic , Okamsn , emacs-devel@gnu.org To: Visuwesh Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 20 19:40:29 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1owpEy-0001bE-E1 for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Nov 2022 19:40:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owpE4-00038T-RD; Sun, 20 Nov 2022 13:39:32 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1owpE4-00038L-AB for emacs-devel@gnu.org; Sun, 20 Nov 2022 13:39:32 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1owpE1-000818-MG for emacs-devel@gnu.org; Sun, 20 Nov 2022 13:39:31 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id BB96280781; Sun, 20 Nov 2022 13:39:26 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1DEB380496; Sun, 20 Nov 2022 13:39:25 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1668969565; bh=WG0ggFC/vO9IlqrIE/BUcksHGCEHQN0GPVqdyLQUKeg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pJCul0rEkd7wbLtxrTMIOiOg/4+l/fPl+5nwJWFu4Ypw4XoetKMpQB6uZj7UhC7ps tMB1hyC5DclI8AaV4AS7zC5T3HyTPb6CsEu60QEjOAc3XU1GJqKsg2rX+gNTfanZoX axpolAglv4rEbEdXXvuUAVUwBECMOwq4oEX2lGgEMPJIIjqazFpjlVgKtBs57JloQF WsXwT9MENzw7VrZHAoZxXaK0AW9LrjmHzRkuF24t15ylm75e20vjBaiY0CG+J/jUhT X4h4/Xtg7RrWSUpTfd8S7VqtcTD0FEXBzAMMJo0SXedWqHvmy45tu18A4OHu57g8Xr 21wPzMkrwF/Zg== Original-Received: from pastel (unknown [104.247.241.157]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id BCD56120CE3; Sun, 20 Nov 2022 13:39:24 -0500 (EST) In-Reply-To: <874jutft6g.fsf@gmail.com> (Visuwesh's message of "Sun, 20 Nov 2022 22:40:31 +0530") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300262 Archived-At: > AFAIU, it is because there is no common way to call a function after > ending a completing-read and/or completion-in-region call so we end up > needing a UI specific way to do so. The function records the selected > candidate, necessary for fuzzy(?) matching based on frequency and > recency ("frecency"). Hmm.. indeed we have no way in the framework to let the UI tell the completion-table or the completion-style which candidate was chosen in the end. The closest we have is the history variables (and that's only available for minibuffer completions). :-( Stefan