From: Pierre Habouzit <madcoder@debian.org>
To: "Peter Baumann" <peter.baumann@gmail.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH] nice ftplugin for vim, that shows the commited diff in a split'ed buffer.
Date: Tue, 17 Oct 2006 13:04:38 +0200 [thread overview]
Message-ID: <200610171304.39131.madcoder@debian.org> (raw)
In-Reply-To: <802d21790610170359v3f17438dn8009ae9a55b2405c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
Le mar 17 octobre 2006 12:59, Peter Baumann a écrit :
> 2006/10/17, Pierre Habouzit <madcoder@debian.org>:
> > because for me, wherever I'm from, the cwd is .git/ but it's maybe
> > due to the fact that I use autochdir, I don't know.
>
> Wouldn't it make sense to use something like 'git-rev-parse
> --git-dir' or 'git-rev-parse --show-cdup' to get to the root of the
> repository?
Yes it does, SungHyun Nam already sent a patch to me about that, that is
quite interesting. I've merged it partly, and will make that commit
plugin slightly better, so that people can:
1/ trig it by hand
2/ chose if the split is vertical or horizontal (I always have very big
terms with a lot of vertical splits in vim, so I like the latter,
other prefer the former)
3/ chose via a let g:gitcommit_diff_mode or sth like that in the vimrc
if that has to spawn automatically (0: none, 1: horiz split, 2: vert
split)
and that time, I'll send that to the git contrib/vim maintainer so that
I won't bother the list too much :)
a corrected version of the commit file wrt the cwd is on my site
already, with a bit of SungHyun changes[1].
[1] http://madism.org/~madcoder/dotfiles/vim/ftplugin/git.vim
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-17 11:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 0:31 [PATCH] be more vim-ish, and also syntax hilight Signed-off-by lines Pierre Habouzit
2006-10-17 0:31 ` [PATCH] nice ftplugin for vim, that shows the commited diff in a split'ed buffer Pierre Habouzit
2006-10-17 8:22 ` Peter Baumann
2006-10-17 10:38 ` Pierre Habouzit
2006-10-17 10:59 ` Peter Baumann
2006-10-17 11:04 ` Pierre Habouzit [this message]
2006-10-17 21:48 ` Christian MICHON
2006-10-17 22:04 ` Junio C Hamano
2006-10-18 1:57 ` Petr Baudis
2006-10-17 7:46 ` [PATCH] be more vim-ish, and also syntax hilight Signed-off-by lines Junio C Hamano
2006-10-18 0:38 ` contrib/vim patches, replace the previous set Pierre Habouzit
2006-10-18 0:39 ` Pierre Habouzit
2006-10-18 0:39 ` [PATCH] be more vim-ish, and also syntax hilight Signed-off-by lines Pierre Habouzit
2006-10-18 0:39 ` [PATCH] Nice ftplugin for vim, that shows the commited diff in a split'ed buffer Pierre Habouzit
2006-10-18 0:40 ` Pierre Habouzit
2006-10-18 0:47 ` Make the ftplugin right wrt gitdir Pierre Habouzit
2006-10-18 0:47 ` [PATCH] be more robust wrt the git-dir Pierre Habouzit
2006-10-18 7:02 ` Make the ftplugin right wrt gitdir Jeff King
2006-10-18 8:10 ` Pierre Habouzit
2006-10-18 9:02 ` Jeff King
2006-10-18 9:07 ` Pierre Habouzit
2006-10-18 9:46 ` Jeff King
2006-10-18 6:59 ` [PATCH] be more vim-ish, and also syntax hilight Signed-off-by lines Jeff King
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=200610171304.39131.madcoder@debian.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=peter.baumann@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.
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).