From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: kmacro.texi Date: Tue, 30 Nov 2004 10:53:21 +0100 Message-ID: References: <200411300430.iAU4UdV26748@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1101808433 1537 80.91.229.6 (30 Nov 2004 09:53:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 30 Nov 2004 09:53:53 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 30 10:53:41 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CZ4hY-0005Yv-00 for ; Tue, 30 Nov 2004 10:53:41 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CZ4r0-0006lE-3j for ged-emacs-devel@m.gmane.org; Tue, 30 Nov 2004 05:03:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CZ4qO-0006bZ-7J for emacs-devel@gnu.org; Tue, 30 Nov 2004 05:02:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CZ4qM-0006b3-9n for emacs-devel@gnu.org; Tue, 30 Nov 2004 05:02:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CZ4qK-0006ax-Ss for emacs-devel@gnu.org; Tue, 30 Nov 2004 05:02:45 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1CZ4gp-0001rD-LU for emacs-devel@gnu.org; Tue, 30 Nov 2004 04:52:56 -0500 Original-Received: (qmail 72386 invoked from network); 30 Nov 2004 09:52:54 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 30 Nov 2004 09:52:54 -0000 Original-To: Luc Teirlinck In-Reply-To: <200411300430.iAU4UdV26748@raven.dms.auburn.edu> (Luc Teirlinck's message of "Mon, 29 Nov 2004 22:30:39 -0600 (CST)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) 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: main.gmane.org gmane.emacs.devel:30523 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30523 Luc Teirlinck writes: > I propose the following changes to man/kmacro.texi. If they look OK, They are _really_ good. Thanks. > I believe that `(emacs)Keyboard Macro Counter' and `(emacs)Keyboard > Macro Step-Edit' are specialized sections and should be moved to > emacs-xtra. Would that be OK? Since macros are the "poor mans" Lisp functions, I think the macro counter is an important feature of macros (personally, I use them quite often), so unless there are strong reasons to omit them, I think they should be described in the printed manual. It's ok to move the step-edit part to emacs-xtra. > I have left `(emacs)Keyboard Macro Step-Edit' unchanged, > but `(emacs)Edit Keyboard Macro' already explains, much more briefly, > an easier to learn alternative way to edit kmacros. True. > > We also decided some moths ago that it would be good to move > kmacro.texi back to after the discussion of key bindings and related > topics, which `(emacs)Save Keyboard Macro' heavily relies on. Is this > still OK? Currently, `(emacs)Save Keyboard Macro' is nearly > impossible to understand for a reader reading the manual back to > front. IIRC, I moved it to its current position (near text editing, search and replace, etc) because macros basically is more related to "repeating the same editing" than about key bindings and customization. But I wont object to the move if you think that gives a better flow. > > I submit a patch without those "moving around" changes, because I want > to separate that from the actual content changes in the patch below. I suggest you install these changes in the current position -- and do the moves in a separate change. -- Kim F. Storm http://www.cua.dk