emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Jason Dunsmore <jason.public@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org and git blame integration?
Date: Mon, 7 Dec 2009 17:20:49 -0700	[thread overview]
Message-ID: <20524da70912071620h4b975394n84a53e84586522ab@mail.gmail.com> (raw)
In-Reply-To: <87r5rcncdk.fsf@riotblast.dunsmor.com>

Some type of git integration here would be nice.  I like the idea of
eliminating most todo state changes, because then there isn't an issue
with ellipses on empty headilnes..  I.e.  no need to cycle to see if a
headline is empty because it only contains a logbook drawer.

Of course, you will still need semi-manual interaction to track a
headline that changes and has a todo state change in the same commit.

On 2009-12-02, Jason Dunsmore <jason.public@gmail.com> wrote:
> Hi,
>
> I used to use state change logging (configured with "!" in
> org-todo-keywords), but I didn't like the way it cluttered my org files
> and I rarely referred to the logged times.
>
> As an alternative, I found the git-blame utility to be useful for
> finding out stuck projects and tasks in my Org files.  For example, the
> following command will sort each line in an org file by the date it was
> committed:
>
> 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?
>
> Regards,
> Jason
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>


-- 
Q: How many CDC "scientists" does it take to change a lightbulb?
A: You only think it's dark. [CDC has denied ME/CFS for 25 years]
=================================================================
Retrovirus: http://www.wpinstitute.org/xmrv/xmrv_qa.html

      parent reply	other threads:[~2009-12-08  0:20 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
2009-12-08  0:20 ` Samuel Wales [this message]

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=20524da70912071620h4b975394n84a53e84586522ab@mail.gmail.com \
    --to=samologist@gmail.com \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).