On Thu, 21 May 2015 09:39:14 +0200
Magnus Therning <mag...@therning.org> wrote:
> >>> If you are using the command line I'd start with removing `notepad
> >>> ++` from the equation and go with the default (most probably
> >>> that's `vi`).
> >> I seconds this.
> > Personally I disagree ;-) I do use a balance of Windows and Git
> > tools. (I remember the 70's with real teletypes, especially the
> > good bits; but, just the same, if it's OK with you ...;-)
> I think you misunderstood me. My suggestion was to remove notepad++
> from the equation *while troubleshooting*. Removing possible causes
> of the observed problem one at a time is a rather good strategy when
> troubleshooting, I find.
Yeah, that's what I read from the Magnus's message, too ;-)
Just factor out Notepad++, as it seemed a bit tricky to set up,
and see what happens. Since and interactive rebase wants to have
an editor, stock bundled vi seemed like a good pick for debugging.
If all works as expected, try to plug Notepad++ back in and concentrate
on doing that thing correctly.
That said, vi as shipped in GfW is indeed a bit long in teeth.
But Vim also has a GUI version which looks just okay on Windows,
and for those, like me, who invested into Vim's steep learning curve,
working in a "normal" text editor is, well, not a pain, but it just
does not feel right :-)
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.