unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: kmacro.el
Date: Tue, 30 Nov 2004 10:36:51 +0100	[thread overview]
Message-ID: <m3r7mbvft8.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200411300400.iAU40Vn26724@raven.dms.auburn.edu> (Luc Teirlinck's message of "Mon, 29 Nov 2004 22:00:31 -0600 (CST)")

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> I have the impression that the above described behavior was actually
> always the _intended_ behavior and that the fact that the actual
> behavior is different is an inadvertent bug, rather than intentional.

Indeed -- thanks for working on this.

>
> The patch also removes the "(printf format)" from the `C-x C-k C-f'
> prompt.  This is misleading.  No C style printf format is used but an
> Elisp `format' format.  Better no hint than a false hint.  This is
> a specialized function intended for more knowledgeable users anyway.
>
> The other two small changes seem obvious:
>
> (and nil ...
>
> makes no sense.  The other `and' arguments are ignored.

I don't recall why I made that change -- maybe to debug something.

>
> In the call to `message' the extra "%s" is necessary, because the user
> could have used %s or %o sequences in the macro text, that are
> intended literally.

Can't we just eliminate the call to format, i.e. instead of

(message "%s" (format "%s%s..." ...))

use

(message "%s%s..." ...)

> Once it would be determined that these changes, as well as the changes
> I am going to propose to man/kmacro.texi are OK, 

They look OK.  Please install.

>                                                  I also intend to
> propose several changes to docstrings that are not very clear, or even
> misleading.

Please do.

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

  reply	other threads:[~2004-11-30  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30  4:00 kmacro.el Luc Teirlinck
2004-11-30  9:36 ` Kim F. Storm [this message]
2004-12-01  4:39   ` kmacro.el Luc Teirlinck
2004-12-01  2:57 ` kmacro.el Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m3r7mbvft8.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).