From: Erik Blake <erik@icefield.yk.ca>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Escape character for .gitconfig
Date: Tue, 20 Dec 2011 09:04:41 +0100 [thread overview]
Message-ID: <4EF04199.1010008@icefield.yk.ca> (raw)
In-Reply-To: <4EEF5F59.8030802@dirk.my1.cc>
Hi Dirk,
I ended up using "'C:/Program Files (x86)/Notepad++/notepad++.exe'
-multiInst -notabbar -nosession -noPlugin" which works nicely for me
(note the placement of the inner quotations).
It is notepad.exe (the default Windows editor) that fails on files with
only <lf> termination. That's why I was trying to set notepad++ as the
git editor as it is vastly superior.
Cheers,
Erik
On 2011-12-19 16:59, Dirk Süsserott wrote:
> Am 18.12.2011 10:51 schrieb Jeff King:
>> On Sun, Dec 18, 2011 at 08:53:09AM +0100, Erik Blake wrote:
>>
> [...]
>>> Now, however, I have a different problem in that notepad++ is somehow
>>> signalling git that editing is complete before I even get a chance to
>>> edit the file. I am trying the command
>>>> git commit --amend
> [...]
>> I know nothing about notepad++, but a quick google turned up the
>> "-multiInst" option, which would avoid attaching to the existing
>> instance. That might work for you.
>>
>> -Peff
> Jeff is right! I also use notepad++ and have set
>
> export GIT_EDITOR='notepad++ -multiInst'
>
> in my .bashrc (msysGit). And btw: notepad++ DOES handle cr/lf. Look at
> the "Format" menu.
>
> Dirk
next prev parent reply other threads:[~2011-12-20 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 10:10 Escape character for .gitconfig Erik Blake
2011-12-17 10:58 ` Jeff King
2011-12-18 7:53 ` Erik Blake
2011-12-18 9:51 ` Jeff King
2011-12-19 15:59 ` Dirk Süsserott
2011-12-20 8:04 ` Erik Blake [this message]
2011-12-20 19:46 ` Dirk Süsserott
2011-12-21 12:54 ` Peter Krefting
2011-12-21 13:59 ` demerphq
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=4EF04199.1010008@icefield.yk.ca \
--to=erik@icefield.yk.ca \
--cc=git@vger.kernel.org \
--cc=newsletter@dirk.my1.cc \
--cc=peff@peff.net \
/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).