all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: kmacro?
Date: Thu, 23 Nov 2006 14:31:15 +0100	[thread overview]
Message-ID: <m3irh61e8s.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <BDEIJAFNGDOAGCJIPKPBCEPFCAAA.drew.adams@oracle.com> (Drew Adams's message of "Wed\, 22 Nov 2006 22\:51\:24 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

> I came across kmacro in the Emacs manual, but not in the Elisp manual (with
> the exception of a passing mention of `kmacro-start-macro'). Perhaps the
> latter is normal; I don't know, but I might have expected at least a mention
> of `kmacro-ring'.

The Elisp manual describes the C-primitives (start-kbd-macro etc), and
the basic support functions defined in macro.el.

The Emacs manual decribes how the user uses keyboard macros for editing.
Whether that is based on the built-in commands, the commands in macro.el,
or commands in kmacro.el is a technical detail which I don't see can be
of much intest to the user.

In Emacs 22, keyboard macros are more advanced than previous Emacs releases,
since it includes -and uses- the new kmacro.el package.  The Emacs manual
correctly describes the new interface.

I don't really see the problem.

> I think kmacro needs a better presentation in the doc, with some explanation
> of the relation to the formerly standard way of doing things (macros.el and
> the built-ins). If kmacro is meant to replace macros.el and the built-in
> commands, then that should be done completely. 

What part is missing?  Is there something which doesn't work as documented?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-11-23 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  6:51 kmacro? Drew Adams
2006-11-23 13:31 ` Kim F. Storm [this message]
2006-11-23 16:23   ` kmacro? Drew Adams
2006-11-26 12:15     ` kmacro? Kim F. Storm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3irh61e8s.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.