discussion and development of piem
 help / color / mirror / code / Atom feed
From: Leo <sourcehut@relevant-information.com>
To: piem@inbox.kyleam.com
Subject: Re: [PATCH 1/1] piem-notmuch-am-ready-mbox: Add option to edit patches before applying them
Date: Thu, 09 Dec 2021 14:00:11 +0100	[thread overview]
Message-ID: <87zgpaylus.fsf@hako.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87v8zynkhy.fsf@relevant-information.com>

Leo <sourcehut@relevant-information.com> writes:

> I actually thought something similar a while after I sent the patch.
> Instead of editing the buffer generated by notmuch we could use the
> buffer returned by `piem-am-ready-mbox'. That way we get all the
> libraries for free. Perhaps a new command `piem-am-edit' could be added
> that calls `piem-am-ready-mbox' with your suggested dedicated piem mode
> for editing. Would it be a good idea to filter out email headers that
> `git am' doesn't care about here? Otherwise it can be a bit overwhelming.
>
>
>
Here is a sketch based on the sketch you sent. The workflow being: 1)
call `piem-edit' 2) edit the mbox buffer 3) call `piem-edit-patch-am'.


---
 piem.el | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/piem.el b/piem.el
index afe6b7a..807de65 100644
--- a/piem.el
+++ b/piem.el
@@ -900,6 +900,35 @@ (defun piem-am-read-worktree (coderepo branch)
           (concat (file-name-nondirectory fname) "-"
                   (replace-regexp-in-string "/" "-" branch))))))
 
+(defvar-local piem-edit-patch--coderepo nil)
+(defvar-local piem-edit-patch--format nil)
+(defvar-local piem-edit-patch--mid nil)
+
+(defun piem-edit-patch-am ()
+  (interactive)
+  (piem-am (current-buffer)
+       "mbox"
+       (piem-extract-mbox-info (current-buffer))
+       piem-edit-patch--coderepo))
+
+(define-derived-mode piem-edit-patch-mode nil "piem-edit-patch"
+  "TODO"
+  :group 'piem)
+
+(defvar piem-edit-patch-mode-map
+  (let ((map (make-sparse-keymap)))
+    (define-key map (kbd "C-c C-c") #'piem-edit-patch-am)
+    map)
+  "TODO")
+
+(defun piem-edit ()
+  (interactive)
+  (piem-am-ready-mbox)
+  (let ((coderepo (piem-inbox-coderepo)))
+    (switch-to-buffer " *piem am-ready mbox*")
+    (piem-edit-patch-mode)
+    (setq piem-edit-patch--coderepo coderepo)))
+
 ;;;###autoload
 (defun piem-am (mbox &optional format info coderepo toggle-worktree)
   "Feed an am-ready mbox to `git am'.
-- 
2.31.0

  reply	other threads:[~2021-12-09 13:00 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 [this message]
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
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=87zgpaylus.fsf@hako.i-did-not-set--mail-host-address--so-tickle-me \
    --to=sourcehut@relevant-information.com \
    --cc=piem@inbox.kyleam.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).