From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joaotavora@gmail.com (=?iso-8859-1?Q?Jo=E3o_T=E1vora?=) Newsgroups: gmane.emacs.devel Subject: Re: [OT] Working with patches inlined in emails Date: Thu, 18 Jun 2015 10:27:43 +0100 Message-ID: References: <87egldxn7p.fsf@petton.fr> <878ublkrqe.fsf@petton.fr> <87zj3x5sfb.fsf@petton.fr> <83lhfhl7pw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1434619699 13736 80.91.229.3 (18 Jun 2015 09:28:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Jun 2015 09:28:19 +0000 (UTC) Cc: Nicolas Petton , monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 18 11:28:00 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z5W73-0006cK-Ga for ged-emacs-devel@m.gmane.org; Thu, 18 Jun 2015 11:27:57 +0200 Original-Received: from localhost ([::1]:51328 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5W72-0006Ka-E0 for ged-emacs-devel@m.gmane.org; Thu, 18 Jun 2015 05:27:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5W6x-0006Hx-PQ for emacs-devel@gnu.org; Thu, 18 Jun 2015 05:27:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5W6u-00023c-Kh for emacs-devel@gnu.org; Thu, 18 Jun 2015 05:27:51 -0400 Original-Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:36853) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5W6u-00023S-Dz; Thu, 18 Jun 2015 05:27:48 -0400 Original-Received: by wgzl5 with SMTP id l5so58445418wgz.3; Thu, 18 Jun 2015 02:27:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=pbQpygwFTe1Updlzfate0uafH8REwGc6KDWtyDI+SXQ=; b=Hwzod1otwjpnO4mCSm+fed2gxLSVZqPE4JP9g6zbm54Z9y1JOij1G7GA6ZoIw1dY1/ FnMoLNT/0dqYBG6nulBSV98gTgklnp6/WRpJk7FXa5J1ElzsGGwK0ZkGJbXGql6GwzSu x/sD3UFH3lRyqfwlDtgTI/G7J6+SQ7fXQXW2LjNV35w8sbt6GgG9eSqMYEpuAdSg1whn U/heTv3sILCOTZrU3iIYoJSiAhBJt/8l+oAHy1JHM5Y0qmbX20W2WRpA5tjCHME4z6ZG 21wWMw4JmvFanPWgKKyJb0VXGIOa3ZLEOC4VjY8iShrNYl3HN4VRhQqb3gKu4s/2ZWY/ dkfg== X-Received: by 10.180.215.101 with SMTP id oh5mr27029335wic.6.1434619667510; Thu, 18 Jun 2015 02:27:47 -0700 (PDT) Original-Received: from GONDOMAR.yourcompany.com (mail3.siscog.pt. [195.23.29.18]) by mx.google.com with ESMTPSA id o6sm30519310wiz.24.2015.06.18.02.27.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jun 2015 02:27:46 -0700 (PDT) In-Reply-To: <83lhfhl7pw.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Jun 2015 11:51:55 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:187278 Archived-At: Eli Zaretskii writes: >> From: Nicolas Petton >> Date: Thu, 18 Jun 2015 10:31:20 +0200 >> Cc: emacs-devel >>=20 >> This is a bit off-topic, but I'm wondering how people work with emails >> in Emacs containing patches in the body of the email. > > With "M-|", of course. Here's an alternative that might a bit more portable, emacs-centric and user-friendly: just yank the patch region to a new buffer and `M-x diff-mode' there. Then you can `C-c C-c` and `C-c C-a` at will, applying, undoing and reading the differences as you go. If you're lazy, don't mark and yank to a new buffer, just `M-x diff-mode` whatever buffer you find the message in. diff-mode will ask you to locate the file. Alternatively, use `M-x cd` on that buffer to switch to the root of the project the patch pertains too. I think I've seen diff-mode automagically guessing the file but I'm too lazy right now to figure out and describe under which conditions that happens, if at all. Jo=E3o