From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: rmail and mime encoded patches annoyance Date: Fri, 19 May 2023 13:51:15 +0300 Message-ID: <83pm6wtx0c.fsf@gnu.org> References: <83sfbsu8el.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13368"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "Alfred M. Szmidt" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 19 12:52:05 2023 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 1pzxiP-0003El-Hz for ged-emacs-devel@m.gmane-mx.org; Fri, 19 May 2023 12:52:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pzxha-0001Gs-PT; Fri, 19 May 2023 06:51:14 -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 1pzxhY-0001FT-Qo for emacs-devel@gnu.org; Fri, 19 May 2023 06:51:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pzxhY-0005yc-JI for emacs-devel@gnu.org; Fri, 19 May 2023 06:51:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Sh2zRrZbA6h9aXxweYQ2l2jo7Sm/S4OvMkCwCDim8dk=; b=oxqltGwMaotN gtZ/8rurbxWN1pKYoHdhCASP/gl6U1fDqLKqHbzZ9dsn6Og3CaDS1kc3xMpBIcELzhioZ6g5fujZF spNHIfUYdLlbD1UOYZTXHvC7eB9OoLM9JCW62vL0EBSBy7EqHjanK6bDcE/T1gIQMswJEJGeytpJ1 cTdzNk9XQOCON7of2/InimtIabvPfYYAW9My+xnIiabW13mBBsxaKZ+McDwFYWjOw1kzkqb50lnTs /B4SDvmTuLEGxmkuzV60cDTV1SBUUl/S7W+/y2tWhWhm21lhPvKffNjYUGCn2GvdAwCd1Xwex9dDS rg1CGmcg1dYPa8YkZaBLwA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pzxhN-0007GC-BO; Fri, 19 May 2023 06:51:09 -0400 In-Reply-To: (ams@gnu.org) 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:306203 Archived-At: > From: "Alfred M. Szmidt" > Cc: emacs-devel@gnu.org > Date: Fri, 19 May 2023 03:17:27 -0400 > > FWIW, I almost never use rmail-edit, and don't really understand why > it's useful, let alone when a MIME patch is attached to it. If what > you need is to edit the patch before applying it, > > It is more for commenting about the patch, in this case. One could > start a new reply, but those aren't presitent, and sometimes patches > take a week or two to go over. I don't understand: if you reply with the attachment displayed (i.e., after you pres the "Show" button on the MIME attachment header line), "C-c C-y" will yank the decoded attachment's text as well, and you can then comment on it like you do with any other text of the original message. > Similar, I use this for longer responses, where I edit the message and > add my reply/comments/... and then save the RMAIL buffer. And when > you're done, you just reply with the notes you did. I still don't understand why you need to use rmail-edit for that. What's wrong with adding your reply/comments in the response message after rmail-reply? If you want to save the response for editing or replying later, there's FCC, or you can use BCC to send a copy to yourself. > then (a) that is not really recommended, since you will be applying > code attributed to someone else with your own changes; and (b) you > could always copy the patch to another buffer, edit it there, and > then apply. > > Doing that multiple times a day gets old quick; was hoping to find a > better way. Like I say above: I don't understand why you'd need to do that even once a day. I don't, and you can believe me that I review a lot of patches sent as attachments, and not only for Emacs.