discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: sourcehut@relevant-information.com
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH v2] Add ability to edit patches before applying them
Date: Fri, 24 Dec 2021 13:32:16 -0500	[thread overview]
Message-ID: <87ee61g8gf.fsf@kyleam.com> (raw)
In-Reply-To: <20211221140212.30248-1-sourcehut@relevant-information.com>

sourcehut@relevant-information.com writes:

> +(defun piem-edit-patch-am ()
> +  "Apply the patch that is currently edited."
> +  (interactive)
> +  (let ((buf (current-buffer)))
> +    (piem-am  buf
> +          "mbox"
> +          (piem-extract-mbox-info (current-buffer))
> +          piem-edit-patch--coderepo))
> +  (kill-buffer buf))

This last 'buf' is outside of the let-binding:

  $ make compile
  emacs --batch -Q -L . -L tests -f batch-byte-compile piem-maildir.el
  emacs --batch -Q -L . -L tests -f batch-byte-compile piem.el
  
  In piem-edit-patch-am:
  piem.el:1012:16:Warning: reference to free variable ‘buf’
  [...]

I've moved it inside (diff below).

Tested this out a bit, and it seems to work as advertised.  Pushed
(a996e8d4).  Thanks for proposing and implementing this feature.

diff --git a/piem.el b/piem.el
index eef06492..b06719b2 100644
--- a/piem.el
+++ b/piem.el
@@ -1005,11 +1005,11 @@ (defun piem-edit-patch-am ()
   "Apply the patch that is currently edited."
   (interactive)
   (let ((buf (current-buffer)))
-    (piem-am  buf
-          "mbox"
-          (piem-extract-mbox-info (current-buffer))
-          piem-edit-patch--coderepo))
-  (kill-buffer buf))
+    (piem-am buf
+             "mbox"
+             (piem-extract-mbox-info (current-buffer))
+             piem-edit-patch--coderepo)
+    (kill-buffer buf)))
 
 (defvar piem-edit-patch-mode-map
   (let ((map (make-sparse-keymap)))

  reply	other threads:[~2021-12-24 18:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 16:01 Adding support for editing patches before applying them sourcehut
2021-12-08 16:01 ` [PATCH 1/1] piem-notmuch-am-ready-mbox: Add option to edit " sourcehut
2021-12-09  3:43   ` Kyle Meyer
2021-12-09  5:20     ` Kyle Meyer
2021-12-09 10:10     ` Leo
2021-12-09 13:00       ` Leo
2021-12-10  5:08         ` Kyle Meyer
2021-12-10  9:31           ` Leo
2021-12-11 21:44             ` Kyle Meyer
2021-12-16 20:05               ` [PATCH] Add ability " sourcehut
2021-12-17  5:58                 ` Kyle Meyer
2021-12-21 14:02                   ` [PATCH v2] " sourcehut
2021-12-24 18:32                     ` Kyle Meyer [this message]
2021-12-27 16:07                       ` Leo
2021-12-27 21:07                         ` distributing piem via *ELPA Kyle Meyer
2021-12-27 21:30                           ` Kyle Meyer
2021-12-09  3:38 ` Adding support for editing patches before applying them Kyle Meyer

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://git.kyleam.com/

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

  git send-email \
    --in-reply-to=87ee61g8gf.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=sourcehut@relevant-information.com \
    /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.kyleam.com/piem/

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).