From: Phillip Susi <phill@thesusis•net>
To: git@vger•kernel.org
Subject: gitk external diff on Windows
Date: Wed, 02 Mar 2022 11:27:20 -0500 [thread overview]
Message-ID: <87fso0qphj.fsf@vps.thesusis.net> (raw)
I'm running git version 2.28.0.windows.1 on Windows and trying to set it
up to run winmerge as the external diff tool. I am pretty sure I used
to do this following the instructions here:
https://igorsgames.wordpress.com/2015/05/28/using-winmerge-as-an-external-diff-tool-in-gitk/
When I point gitk to the batch file and try to open the external diff
tool, nothing happens. Winmerge does not open, nor do I get an error
from gitk. I noticed the next box below on the preferences screen
contains "cmd /c" so I tried prefixing the path to the batch file with
that, and instead I get an error that says:
cmd /c C:/Program Files/WinMerge/winmerge.bat: command failed: couldn't
execute "cmd \c C:\Program Files\WinMerge\winmerge.bat": no such file or
directory.
Why does nothing happen in the first case, and why in the second case is
gitk apparently changing regular slashes into back-slashes before
trying to pass the string directly to CreateProcess as the name of the
executable binary, rather than to a shell or ShellExecute or something?
Also I just tried having the batch file echo something to a text file to
see if it was running at all or if winmerge just isn't opening, and the
text file ( full path to my home directory to make sure permissions
aren't a problem ) isn't created, so the batch file isn't executing even
though there is no error given by gitk.
next reply other threads:[~2022-03-02 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:27 Phillip Susi [this message]
2022-03-04 8:37 ` gitk external diff on Windows Erik Cervin Edin
2022-03-04 20:50 ` Phillip Susi
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=87fso0qphj.fsf@vps.thesusis.net \
--to=phill@thesusis$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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