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 20:33:25 +0200	[thread overview]
Message-ID: <87ip396t1m.fsf@gmail.com> (raw)
In-Reply-To: 7vtxmtxm4j.fsf@alter.siamese.dyndns.org

Junio C Hamano <gitster@pobox.com> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>>  ... 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).
>
> Hmph, isn't that what "emacsclient" is for?  I have these
>
> 	(setenv "PAGER" "cat")
> 	(setenv "EDITOR" "emacsclient")
> 	(server-start)
>
> somewhere in my ~/.emacs to make commands in "M-x compile" behave.

I was a big fan of emacsclient and used it quite some time - but finally
those frequent Emacs crashes caused by it were just unbearable, so I
went back to 'normal' use of Emacs.

But maybe you are right - I should run a second Emacs instance as server
only used to popup emacsclient buffers on demand, while doing all the
serious stuff in a non-server instance of Emacs. 

-- 
cheers,
Thorsten

      reply	other threads:[~2013-04-26 18:33 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
2013-04-26 17:00         ` Junio C Hamano
2013-04-26 18:33           ` Thorsten Jolitz [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=87ip396t1m.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).