git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: Wincent Colaiuta <win@wincent.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] diffit - A git plugin for vim
Date: Sun, 16 May 2010 11:41:57 +0200	[thread overview]
Message-ID: <20100516094157.GA9553@localhost> (raw)
In-Reply-To: <514EDDA1-E8A4-45CD-ACF5-F7FE18CABD4F@wincent.com>

Hi Wincent,

On Sun, May 16, 2010 at 11:12:37AM +0200, Wincent Colaiuta wrote:

> El 15/05/2010, a las 12:50, Clemens Buchacher escribió:
> 
> > Hi,
> > 
> > I am currently working on a git plugin for vim. My aim is for it to imitate
> > much of git-gui's functionality. Right now, it is still closer to "add -p".
> > 
> > But I believe it's already useful. And since I'm new to vim scripting, it
> > can use some testing.
> 
> Clemens, were you aware that there are already a couple of Git plug-ins
> for Vim? Of these, the most advanced one currently is almost certainly
> Fugitive:

The git plugins I am aware of, including vim-fugitive, mostly implement git
commands to be executed from vim. I find that utterly useless, since I can
already do that from the command line.

What I can not do from the command line is staging hunks and lines
interactively, possibly interrupted by a quick fix to a change. This is what
I would use git-gui for, only it does not integrate very well with my vim +
cmdline centric workflow.

Here's my TODO list:

- handle file mode changes

- navigation (prev/next hunk/file)

- stage individual lines and (virtual) range

- unstage changes

- file browser (modified, staged, untracked)

- prepare commit message

- git add -e?

If existing plugins already implement these features, then I have missed it,
and I will be happy to use or improve them instead.

As for diffing, some of the existing plugins implement side-by-side, or even
inline diff, using the vimdiff feature. I prefer the native git-diff format,
however.

Cheers,
Clemens

      reply	other threads:[~2010-05-16  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15 10:50 [ANNOUNCE] diffit - A git plugin for vim Clemens Buchacher
2010-05-15 14:40 ` Jakub Narebski
2010-05-16  9:12 ` Wincent Colaiuta
2010-05-16  9:41   ` Clemens Buchacher [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

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

  git send-email \
    --in-reply-to=20100516094157.GA9553@localhost \
    --to=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=win@wincent.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.
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 NNTP newsgroup(s).