From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Vong Subject: Re: [PATCH] Add tintin. Date: Sun, 21 Aug 2016 00:38:06 +0800 Message-ID: <877fbb1jm9.fsf@gmail.com> References: <87r39z81zo.fsf@we.make.ritual.n0.is> <8760rbot2y.fsf@we.make.ritual.n0.is> <877fbdnne4.fsf@we.make.ritual.n0.is> <87y43tm73e.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52895) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb9Hp-0003sC-Qx for guix-devel@gnu.org; Sat, 20 Aug 2016 12:38:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bb9Hj-0001PT-R2 for guix-devel@gnu.org; Sat, 20 Aug 2016 12:38:20 -0400 Received: from mail-pa0-x241.google.com ([2607:f8b0:400e:c03::241]:35628) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bb9Hj-0001Oq-I7 for guix-devel@gnu.org; Sat, 20 Aug 2016 12:38:15 -0400 Received: by mail-pa0-x241.google.com with SMTP id cf3so5135857pad.2 for ; Sat, 20 Aug 2016 09:38:14 -0700 (PDT) In-Reply-To: (David Craven's message of "Fri, 19 Aug 2016 11:48:51 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: David Craven Cc: guix-devel David Craven writes: >> I usually attach the patches as files, in notmuch emacs they are saved >> by pressing >> . s >> when in the displayed attached files part. Or what exactly do you mean? > > Yep that's what I mean. I'm currently doing this: > Look at the patch in gmail > touch 0.patch > copy paste the email into 0.patch > git am 0.patch > copy paste again because I didn't copy the right part > git am 0.patch > > and was wondering if there was a better way... I've read good things > about emacs, but I still haven't taken the learning curve. I gave it a > try a couple of weeks ago but gave up after a couple of hours =P Hmmm, my way of learning emacs is to read the Emacs Tutorial but not to read the Emacs Manual, because it goes into things too deep for newbies IMO. Then, I try to code in emacs and eventually I get comfortable in emacs key bindings. Only then I start to look into packages and elisp programming. (emacs is actually what get me into learning scheme) Alternatively, if you are used to vim, you could try Evil Mode, which emulates vim key bindings.