From: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Add smerge-mode, conflicted-files support to vc-git.
Date: Mon, 13 Jan 2014 13:31:21 +0100 [thread overview]
Message-ID: <4442754.RCCqqyGa7X@descartes> (raw)
In-Reply-To: <jwviotpyl2s.fsf-monnier+emacs@gnu.org>
On Saturday 11 January 2014 21:52:23 Stefan Monnier wrote:
> This is the main problem, of course. It means running git twice per
> file rather than once. We could probably improve this by only calling
> vc-git-conflicted-files if the file is under Git's control and only if
> it's locally modified. If you can think of some other check we could do
> to call the file even less frequently, that'd be even better.
>
> Also, I think the check shouldn't be in find-file-hook but in
> vc-git-state (so as to return `conflicted' state).
Yes, `vc-git-state' should indicate conflicts. Right now it calls `git diff-
index' and treats U as edit instead of `conflicted'. I'm not very familiar
with the details of `vc-git' and therefore am not sure if we can simply change
it.
The hg implementation lacks a `conflicted' state as well and simply checks if
the file is edited and looks for the merge markers. Maybe that would be
enough for git as well.
> I haven't looked in detail at the patch but did notice also that
> vc-git-conflicted-files is documented to take a `directory' as argument
> whereas here you call it with a file name.
Yes, `vc-conflicted-files' is documented to take a `directory'. But `vc-git-
conflicted-files' should work with a `file name' argument. I guess this
should be documented.
Regards,
Rüdiger
prev parent reply other threads:[~2014-01-13 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 1:14 [PATCH] Add smerge-mode, conflicted-files support to vc-git Rüdiger Sonderfeld
2014-01-12 2:52 ` Stefan Monnier
2014-01-13 12:31 ` Rüdiger Sonderfeld [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=4442754.RCCqqyGa7X@descartes \
--to=ruediger@c-plusplus.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.