From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jeremy Bryant Newsgroups: gmane.emacs.devel Subject: Re: Incorporate package macrostep into Emacs core Date: Fri, 19 Apr 2024 20:30:30 +0100 Message-ID: <87edb1duax.fsf@jeremybryant.net> References: <87zfvl8r4e.fsf@jeremybryant.net> <874jdspsqb.fsf@bernoul.li> <877cio8fzf.fsf@jeremybryant.net> <87y1b46vhg.fsf@jeremybryant.net> <878r336lvb.fsf@jeremybryant.net> <86y1b1p1ni.fsf@gnu.org> <87y1b0mi4b.fsf@jeremybryant.net> <8734sobkdj.fsf@jeremybryant.net> <86sf0n4sfq.fsf@gnu.org> <87plume5cn.fsf@jeremybryant.net> <867cgtdfhg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23245"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 19 21:31:23 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rxtxD-0005q9-4J for ged-emacs-devel@m.gmane-mx.org; Fri, 19 Apr 2024 21:31:23 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rxtwZ-0005am-7C; Fri, 19 Apr 2024 15:30:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rxtwU-0005Ze-Rc for emacs-devel@gnu.org; Fri, 19 Apr 2024 15:30:38 -0400 Original-Received: from out-178.mta1.migadu.com ([2001:41d0:203:375::b2]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rxtwR-0008Dx-Ph for emacs-devel@gnu.org; Fri, 19 Apr 2024 15:30:37 -0400 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1713555032; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EBYmz1sjTcIKUvSwxWnaHRuRZoyQj5H/PRma0to3JYs=; b=onPCht+a5oY8grCMNNyWTyVy39BaOn1mBhLLFceJS+Jq4bzKSQraU1v3rgo02RC5+M6HYr nkYHXw1JiSAPnFWYWB4hjD/Yts8QsnF3yUcxuAyrhLFTCQRg0URFfYh+CMMHAFsEZQKlxw ZLQzgEIF8hpW7H6m+9v22H2n5U3leppHGwIO/4EFKsKfw7AtILRowzj/8rR58Hr1kJ1Oxc Tyv2b/BtEI+eG7SAuY8QQPi75pgXf837l0iqZK8sHv1rsrjBFRWqrl3nkxZsyJf6vFNTdf y5vBh75dr2yh3mGAeiuiMGW8ycu9zMmrHDa70857QQVS/pjcPwgN01UdeUxZKw== In-Reply-To: <867cgtdfhg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 Apr 2024 09:38:19 +0300") X-Migadu-Flow: FLOW_OUT Received-SPF: pass client-ip=2001:41d0:203:375::b2; envelope-from=jb@jeremybryant.net; helo=out-178.mta1.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317850 Archived-At: Eli Zaretskii writes: >> From: Jeremy Bryant >> >> 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 >> * 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.