From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joe Corneli Newsgroups: gmane.emacs.help Subject: Re: Is Emacs becoming Word? Date: Sun, 27 Mar 2005 22:39:24 -0600 Message-ID: References: <20050328001728.GA29944@dionysus.ucolick.org> <87wtrssbsa.fsf@rocksteady.printf.se> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1111985059 12504 80.91.229.2 (28 Mar 2005 04:44:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Mar 2005 04:44:19 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Mar 28 06:44:16 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DFm6i-00085H-C9 for geh-help-gnu-emacs@m.gmane.org; Mon, 28 Mar 2005 06:44:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DFmMj-0003Rc-QT for geh-help-gnu-emacs@m.gmane.org; Mon, 28 Mar 2005 00:00:41 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DFmMJ-0003QZ-PT for help-gnu-emacs@gnu.org; Mon, 28 Mar 2005 00:00:16 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DFmME-0003O1-15 for help-gnu-emacs@gnu.org; Mon, 28 Mar 2005 00:00:10 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DFmMC-0003Mh-Lb for help-gnu-emacs@gnu.org; Mon, 28 Mar 2005 00:00:08 -0500 Original-Received: from [146.6.139.124] (helo=dell3.ma.utexas.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DFm29-0003nK-4L for help-gnu-emacs@gnu.org; Sun, 27 Mar 2005 23:39:25 -0500 Original-Received: from lab45.ma.utexas.edu (mail@lab45.ma.utexas.edu [128.83.133.159]) by dell3.ma.utexas.edu (8.11.0.Beta3/8.10.2) with ESMTP id j2S4dOC06086; Sun, 27 Mar 2005 22:39:24 -0600 Original-Received: from jcorneli by lab45.ma.utexas.edu with local (Exim 3.36 #1 (Debian)) id 1DFm28-000680-00; Sun, 27 Mar 2005 22:39:24 -0600 Original-To: help-gnu-emacs@gnu.org In-reply-to: <87wtrssbsa.fsf@rocksteady.printf.se> (message from Henrik Enberg on Mon, 28 Mar 2005 05:13:25 +0200) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:25227 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:25227 tom.horsley@att.net (Thomas A. Horsley) writes: >>I think it probably wouldn't be too ungodly hard to write a >>`what-just-happened' function (but I'm not sure). > > I don't know about that. Certainly the lisp interpreter should know > what function slots it has been executing through. Seems like it would > be primarily a job of adding a gazillion entry "recently called functions" > array together with some AI for filtering which functions in the > array are important to describe "what just happened" (something like > keeping track of how frequently each entry was called and recognizing > that someone saying "what just happened" was probably startled > by some function that hasn't been called much up to this point. Maybe > toss in some weighting factor for functions that have changed or are new > since the last release as well). Seems almost doable (says someone > who is not volunteering :-). C-h v last-command RET That would appear to be of only passing relevance. It is considerably easier to keep track of a list of interactive functions (commands) than it is to sort out the list of all functions that have run, and separate them into "user-visible" and not-user-visible. But `command-history' has an infrastructure that could be used, I'm sure. On Thomas's "AI" - how about just screening out the functions that overlap with Common Lisp, and a list of other built-in functions (`goto-char', etc.) that aren't likely to do anything particularly interesting in and of themselves. And in terms of "volunteering", someone should produce a `last-function' command (maybe 100 entry array would be enough for testing purposes :)), then a bunch of people could collaborative on a list of functions to filter out. A wiki could be used to generate that list... I'm pretty sure I've already seen something closer to `last-function' than `last-command', but I don't remember what it is.