From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Pohlack Subject: Re: Org and git blame integration? Date: Thu, 03 Dec 2009 09:17:25 +0100 Message-ID: <4B177415.6060602@os.inf.tu-dresden.de> References: <87r5rcncdk.fsf@riotblast.dunsmor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NG6sX-0006ZT-M8 for emacs-orgmode@gnu.org; Thu, 03 Dec 2009 03:17:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NG6sT-0006Z0-BJ for emacs-orgmode@gnu.org; Thu, 03 Dec 2009 03:17:33 -0500 Received: from [199.232.76.173] (port=36227 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NG6sT-0006Yx-7M for emacs-orgmode@gnu.org; Thu, 03 Dec 2009 03:17:29 -0500 Received: from os.inf.tu-dresden.de ([141.76.48.99]:37893) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NG6sS-0001uG-Ly for emacs-orgmode@gnu.org; Thu, 03 Dec 2009 03:17:29 -0500 In-Reply-To: <87r5rcncdk.fsf@riotblast.dunsmor.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jason Dunsmore Cc: emacs-orgmode@gnu.org Hi Jason, Jason Dunsmore wrote: [...] > git blame todo.org|cut -c29-|cut -c 20-25 --complement|sort -n|less -S > > I made a couple of bash functions based on this: > > function org_history () { > git blame $1|cut -c29-|cut -c 20-25 --complement|sort -n|less -S > } > > # Limit the output to Org headlines > function org_history_headings () { > git blame $1|grep ') \*'|cut -c29-|cut -c 20-25 --complement|sort -n|less -S > } > > But I still have to go back and forth between the git-blame output and > Org. > > It'd be nice if I could view and edit the git-blame output in org-mode, > group the sort by a certain level heading, cycle body visibility, etc... > I'm not sure how difficult that would be to implement. Does this sound > like a reasonable feature request? I'm not sure how git blame would help with finding stuck projects, but if you tweak the output to be similar to this: :: message/string or ::: message/string You could call the script from a compile buffer (M-x compile). In this buffer, this kind of output is linked back to the original files and you could iterated over the found lines. Cheers, Martin Pohlack