unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Incorporate package macrostep into Emacs core
Date: Thu, 25 Apr 2024 18:30:00 +0300	[thread overview]
Message-ID: <86bk5x1mvb.fsf@gnu.org> (raw)
In-Reply-To: <875xw7ep5d.fsf@jeremybryant.net> (message from Jeremy Bryant on Tue, 23 Apr 2024 22:37:50 +0100)

> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: monnier@iro.umontreal.ca,  emacs-devel@gnu.org
> Date: Tue, 23 Apr 2024 22:37:50 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Jeremy Bryant <jb@jeremybryant.net>
> >> Cc: monnier@iro.umontreal.ca,  emacs-devel@gnu.org
> >> Date: Fri, 19 Apr 2024 20:30:30 +0100
> >> 
> >> >   . 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"?
> >
> > Yes, a section under "Programs" sounds good.
> >
> > Thanks.
> 
> Please find attached a revised patch for consideration.  Any feedback on
> style and conventions welcome.
> 
> Text is adapted from the macrostep package - I believe Jonathan's FSF
> paperwork is still outstanding but is expected soon.

Thanks, but it looks like you attached the wrong patch?  It seems like
it's the same patch you sent the first time, not a revised one after
all the comments above, where we agreed to have this in the Emacs user
manual instead.



  reply	other threads:[~2024-04-25 15: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
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 [this message]
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=86bk5x1mvb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --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).