unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jeremy Bryant <jb@jeremybryant.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca,  emacs-devel@gnu.org
Subject: Re: Incorporate package macrostep into Emacs core
Date: Fri, 19 Apr 2024 20:30:30 +0100	[thread overview]
Message-ID: <87edb1duax.fsf@jeremybryant.net> (raw)
In-Reply-To: <867cgtdfhg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Apr 2024 09:38:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jeremy Bryant <jb@jeremybryant.net>

>> >> Should the documentation for macrostep be included in the Emacs Lisp
>> >> manual section Macros?
>> >
>> > Yes, I think so.

For convenience, to recap from a month ago, this facility is about Lisp
macros, not keyboard macros.  macrostep is useful for Emacs Lisp macro
expansion or exploration, and development.


>> From: Jeremy Bryant <jb@jeremybryant.net>
>> * doc/lispref/macros.texi (Macros):
>> Describe macrostep's usage to explore and write macros.
>
> This is filled sub-optimally; please use change-log-mode to help you
> fill better.

Thank you for the pointer, I will use in future.

For this commit I have used magit-generate-changelog, is this suboptimal?

(..)

Thank you for all the comments on style, I will work on that.

(...)

> And finally, two more questions:
>
>   . should this be in the user manual instead? it sounds like a
>     user-level feature, not Lisp programming level feature

Sure, perhaps this is more suited.

I initially followed your confirmation to write in the Emacs Lisp manual
(top of this message), but indeed this may belong more appropriately in
the Emacs manual.  How about in "(emacs) Programs"?

Please confirm your preference either way and I'll continue the rewrite.

>   . how is this mode different from "C-x C-k SPC", which is already
>     described in the user manual as a similar feature?

Thanks, I'll be clearer in the next iteration. This facility is about
Lisp macros, not keyboard macros.  ('C-x C-k SPC runs the command
kmacro-step-edit-macro').  I'll improve the documentation in the next round.






  reply	other threads:[~2024-04-19 19:30 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zfvl8r4e.fsf@jeremybryant.net>
     [not found] ` <874jdspsqb.fsf@bernoul.li>
2024-02-28 20:56   ` Incorporate package macrostep into Emacs or NonGNU ELPA? Jeremy Bryant via Emacs development discussions.
2024-02-28 21:16     ` Stefan Monnier
2024-02-28 23:04       ` Jeremy Bryant
2024-02-29 20:44         ` Jeremy Bryant
2024-03-01  4:15           ` Adam Porter
2024-03-01 23:26           ` Stefan Monnier
2024-03-02 21:50             ` Jeremy Bryant
2024-03-02 22:51               ` Stefan Monnier
2024-03-03  7:26                 ` Adam Porter
2024-03-03  7:51                   ` Eli Zaretskii
2024-03-03  7:53                     ` Adam Porter
2024-03-03  8:57                       ` Eli Zaretskii
2024-03-03 14:28                   ` Stefan Monnier
2024-03-04 11:25                     ` Ihor Radchenko
2024-03-04 15:35                       ` Stefan Monnier
2024-03-03 22:40                 ` Jeremy Bryant
2024-03-04 12:00                   ` Eli Zaretskii
2024-03-11 22:47                     ` Jeremy Bryant
2024-03-02  6:51           ` Eli Zaretskii
2024-03-02 21:36             ` Jeremy Bryant
2024-03-17 21:48               ` Incorporate package macrostep into Emacs core Jeremy Bryant via Emacs development discussions.
2024-03-18  9:09                 ` Philip Kaludercic
2024-03-18 23:03                   ` Jeremy Bryant
2024-03-19  6:36                     ` Philip Kaludercic
2024-03-19  7:11                       ` Gerd Möllmann
2024-03-19  7:26                         ` Philip Kaludercic
2024-03-19  7:30                           ` Gerd Möllmann
2024-03-19  9:33                             ` Philip Kaludercic
2024-03-19  9:48                               ` Gerd Möllmann
2024-03-19 17:03                     ` Jonathan Oddie
2024-03-19 21:57                       ` Jeremy Bryant via Emacs development discussions.
2024-03-22 20:47                         ` Jeremy Bryant
2024-03-22 20:50                           ` Stefan Monnier
2024-03-18 12:48                 ` Eli Zaretskii
2024-03-18 13:22                   ` Stefan Monnier
2024-03-18 22:58                   ` Jeremy Bryant
2024-03-19 12:26                     ` Eli Zaretskii
2024-04-18 21:19                   ` Jeremy Bryant
2024-04-19  6:38                     ` Eli Zaretskii
2024-04-19 19:30                       ` Jeremy Bryant [this message]
2024-04-19 22:26                         ` Stefan Monnier
2024-04-20  6:07                           ` Eli Zaretskii
2024-04-20 17:14                             ` Adam Porter
2024-04-20  6:00                         ` Eli Zaretskii
2024-04-23 21:37                           ` Jeremy Bryant
2024-04-25 15:30                             ` Eli Zaretskii
2024-04-25 21:27                               ` Jeremy Bryant
2024-04-26  8:15                                 ` Eshel Yaron
2024-04-27  9:52                                 ` Eli Zaretskii
2024-04-29 21:38                                   ` Jeremy Bryant
2024-05-02  9:32                                     ` Eli Zaretskii
2024-05-02 22:03                                       ` Jeremy Bryant

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=87edb1duax.fsf@jeremybryant.net \
    --to=jb@jeremybryant.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).