git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: emacs as mergetool

From
NNick <oinksocket@letterboxes.org>
Date
Sep 28, 2011, 17:03 UTC
Message-ID
<4E835373.1070006@letterboxes.org>
In-Reply-To
<201109261821.28382.thomas@koch.ro>
On 26/09/11 17:21, Thomas Koch wrote:
> would you be so kind and give an emacs newbie (and vim refugee) a hint about 
> using emacs as mergetool?
> 
> - Which one? ediff vs. emerge (I don't bother learning, just give me the best)

I tend to use git.el - which provides the M-x git-status command - and therefore ediff. It's not necessarily the best git interface, but I've been too lazy learn anything else so far. git-status allows you to do basic git adding/committing etc. and will show modification diffs.

Given a git-status buffer, a conflicted merge will show up with certain files in red. You can then view the conflicted versions side-by-side positioning the cursor over the conflicted file, and using the key-sequence 'd E' to start interactive merges in ediff mode. Afterwards you have to save the buffers and mark the file as 'resolved' in git-status ('r').

There are other things you can do in a git-status buffer. M-x describe-mode (C-h m) and M-x describe-bindings (C-h b) will provide some idea.

Show 5 quoted lines
> - I'd like to have a setup, where I can run mergetool with different options 
> to
>   - connect to a running emacs server
>   - run emacs in X
>   - or in the terminal (default)
git-status works with all the above.  I don't use git-mergetool at all.

To keep things in one emacs session I sometimes use git directly in emacs shell buffers. i.e.

 - Run emacs
 - Open the repo in dired: M-x find-file <path to your git repo>
 - Invoke git-status:      M-x git-status
 - (do stuff)
 - Open a shell            M-x shell, M-x eshell, or M-x ansi-term
 - (do more stuff)
> - Is it possible to resolve all conflicting files in one session instead of
> having emacs called again for every file?

As I said, I don't use git-mergetool, but git-status should allow most basic things in fairly straightforward way. For anything more complicated (e.g. git commit --amend, or git add --interactive) I open an shell in emacs.

If you tell git to use emacsclient as the editor, and then git commit and co. will open an emacs buffer so you can invoke git from the command line without leaving your emacs session. To do this:

 - invoke: git config --global core.editor emacsclient
 - in emacs: M-x server-start
   (or add "(server-start)" to your ~/.emacs file)

At some point I might check out magit. I'd be interested to hear about comparisons between git.el and the alternatives.

Cheers,
N
Previous: Vijay Lakshminarayanan
Message 4 of 4 in “emacs as mergetool”
  1. Thomas KochSep 26, 2011
  2. Rémi VanicatSep 26, 2011
  3. Vijay LakshminarayananSep 28, 2011
  4. NickSep 28, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.