From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: yzhh Newsgroups: gmane.emacs.devel Subject: Re: recording-elisp.el - try recording commands as elisp code Date: Mon, 05 Nov 2007 22:27:27 +0800 Message-ID: References: <87k5p05qsy.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: ger.gmane.org 1194272894 5458 80.91.229.12 (5 Nov 2007 14:28:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Nov 2007 14:28:14 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 05 15:28:18 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ip2w5-0007Ke-I3 for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 15:28:17 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip2vu-0001WU-PC for ged-emacs-devel@m.gmane.org; Mon, 05 Nov 2007 09:28:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ip2vp-0001TC-9J for emacs-devel@gnu.org; Mon, 05 Nov 2007 09:28:01 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ip2vn-0001Pp-8W for emacs-devel@gnu.org; Mon, 05 Nov 2007 09:28:00 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip2vn-0001Pa-1C for emacs-devel@gnu.org; Mon, 05 Nov 2007 09:27:59 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ip2vm-0003NR-M7 for emacs-devel@gnu.org; Mon, 05 Nov 2007 09:27:58 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ip2vW-0006Jn-8I for emacs-devel@gnu.org; Mon, 05 Nov 2007 14:27:42 +0000 Original-Received: from 211.90.238.185 ([211.90.238.185]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Nov 2007 14:27:42 +0000 Original-Received: from yezonghui by 211.90.238.185 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Nov 2007 14:27:42 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 50 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 211.90.238.185 User-Agent: KNode/0.10.5 X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:82576 Archived-At: Richard Stallman wrote: > You're being too perfectionist. I am, from time to time. :) I prefer generic solution over ad hoc ones. > Please stop asking whether you can "track them all", > and instead work on tracking common cases. > I am sure you will succeed. The only question is how far > you can carry it. My progress will be slow, but I'll stick to this for a long time. My major concern here is maintainability of the code. When details relating to other emacs packages accumulate in one place, I could lose control of it. I do want it last long. Since your "common case" policy looks practical and the code is now far from out-of-control, I'll do it that way. > We can add isearch-append-string for this. I'm still investigating work-arounds. I'd like to hear from isearch developers about their idea on recording isearch, if that's appropriate. > That is a good idea. Please do it that way. > > The same argument would apply to yanking something that was not > killed within the same macro. It depends on the above "yank sources tracking". So it'll be implemented after that. > The code to set up an argument in the minibuffer needs to be converted > into computing the argument to pass to a function. > > However, mere completion in most cases can be treated as a constant. > ... > The only possible exceptions to that statement are cases where the > effect of the completion is very dynamic. ... > ... > Thus, the issue that complicates minibuffer args is not completion. > It is yanking. So let's apply the "common case" policy here and use completed string constants for now. Later when yanking is dealt with, we can experiment on completion. -- regards, yzhh