git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: git@vger.kernel.org
Subject: Re: Zile as git core editor?
Date: Fri, 26 Apr 2013 18:08:05 +0200	[thread overview]
Message-ID: <87ppxh6zru.fsf@gmail.com> (raw)
In-Reply-To: vpqppxhfz3i.fsf@grenoble-inp.fr

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> BTW - would 'git config --global core.editor zile' or 'git config
>> --global core.editor /usr/bin/zile' the right way to set it (both did
>> not work)? I can start Zile simply with 'zile' on the command line. 
>
> What do you mean by "did not work"? Does the launching fail? Or is
> another editor launched?
>
> Try:
>
> GIT_TRACE=true git commit -a
>
> to see what's going on.
>
> BTW, you may also try "emacs -nw -Q" instead of zile.


Thanks for the tip, I found out that:

1. on the command-line, zile actually works as core editor, but
2. not from within Emacs (Magit) where I tried it

 "emacs -nw -Q" is a nice tip, but I think what I really would like to
 have it that, when I use GNU Emacs Magit and enter a git command 

,-----------------------------
| Run git like this: <command>
`-----------------------------

that calls an editor (e.g. commit --amend), the running Emacs instance
is (re)used and a new buffer is opened for editing (instead of starting
another Emacs instance).

-- 
cheers,
Thorsten

  reply	other threads:[~2013-04-26 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  7:39 Zile as git core editor? Thorsten Jolitz
2013-04-26  8:28 ` Tay Ray Chuan
2013-04-26  8:37   ` Thorsten Jolitz
2013-04-26  8:57     ` Matthieu Moy
2013-04-26 16:08       ` Thorsten Jolitz [this message]
2013-04-26 17:00         ` Junio C Hamano
2013-04-26 18:33           ` Thorsten Jolitz

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=87ppxh6zru.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=git@vger.kernel.org \
    /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).