emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Martin Pohlack <mp26@os.inf.tu-dresden.de>
To: Jason Dunsmore <jason.public@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org and git blame integration?
Date: Thu, 03 Dec 2009 09:17:25 +0100	[thread overview]
Message-ID: <4B177415.6060602@os.inf.tu-dresden.de> (raw)
In-Reply-To: <87r5rcncdk.fsf@riotblast.dunsmor.com>

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:

  <file>:<line>: message/string

or

  <file>:<line>:<col>: 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

next prev parent reply	other threads:[~2009-12-03  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03  0:13 Org and git blame integration? Jason Dunsmore
2009-12-03  8:17 ` Martin Pohlack [this message]
2009-12-08  0:20 ` Samuel Wales

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B177415.6060602@os.inf.tu-dresden.de \
    --to=mp26@os.inf.tu-dresden.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=jason.public@gmail.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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).