Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Exactly that worked fine for me, with the custom install path I'd picked anyway. It's worth noting that there's a difference between "path", which most guides use, and "cmd" which is specified here.
    – FauxFaux
    Commented Feb 24, 2013 at 15:40
  • I've tried both yours and Martin's solutions and neither have worked. I think there is something else going on. A window opens and then closes immediately, and then Meld opens with the paths pointing to Meld's installation directory instead of the repo. Could an arg passed to Meld be causing it to die and then it detects the problem and relaunches with the default path? I'm grasping here but I'm not sure how to troubleshoot this...
    – Nelson
    Commented Feb 25, 2013 at 23:11
  • You sure you're using the meld.exe and not the meld file which is in (I think) a bin folder. I remember having a problem where I used simply the meld file and it launches the application before git has a chance to put the files in the temporary folder.
    – schuess
    Commented Feb 26, 2013 at 2:36
  • I used your solution, but using the meld file in the bin directory (I actually renamed the file meld.py) and it worked without issue.
    – Jarrett
    Commented Nov 22, 2013 at 5:11