Release Notes

Version 1.0.12

  • Fixed a rare crash caused by an out-of-bounds array index when generating a diff.
  • Fixed font size text field getting reset when using the other font drop-down controls.

Version 1.0.11

Updated the juxta installer to no longer change the owner of .gitconfig to root.

Version 1.0.10

  • Fixed a crash that could occur when diffing files that have a symbolic link in their path.
  • Fixed a deadlock that could occur when selecting a commit.
  • The “Compare with Previous Commit” action now attempts to diff with a parent of the selected commit rather than just the next commit that is listed.
  • Fixed: selecting an annotated tag from the references popup menu would result in an empty commit list being displayed.
  • The current (HEAD) branch now appears above other local branches and below the default branch in the references popup menu.
  • Added a “HEAD” badge to the current branch in the references popup menu.
  • Performance improvements, especially for repositories with many files or many commits.

Version 1.0.9

  • When a 2-way Git diff has focus, the ↓ and ↑ keys (without holding command or option) will now navigate between changes within a file but they will also navigate to the next/previous file rather than loop back to the start/end of the current file. The original looping-within-a-file behaviour when holding the option key is still available.

  • Improvements to the juxta installer to facilitate integrating with Git clients.

  • Performance improvements.

Version 1.0.8

  • Fix: clicking in the merge tool’s scrollbar could break scrolling for the middle text view
  • Fix: “Ours” & “Theirs” buttons were showing empty popovers in the merge tool.
  • Fix: Repository state description was missing during a rebase.
  • Fix: Potential crash when attempting to view or edit license key information.
  • Support for comparing files via juxta
  • Performance improvements.

Version 1.0.7

  • Workspace diffs update more quickly now. Especially for repos with many files.
  • Support for using the --dir-diff option with git difftool.
  • Text comparisons can now detect and display differences in newline characters.
  • Various performance improvements.

Version 1.0.6

  • Yet more performance improvements.
  • Fixed: commits were right-justified in the file history commit list.

Version 1.0.5

  • More performance improvements.
  • Fixed a crash that could occur when opening a repository.
  • Fixed a crash that could occur when using “Choose All from Left/Right” in the merge tool.
  • Fixed large diffs only partially loading when using git difftool.
  • Improved support for the various ways that git difftool can be called. E.g. using “..” notation to specify two revisions.

Known Issues

While support for git difftool has been improved, a couple of issues remain:

  • The --dir-diff argument is not yet supported.

    Workaround: Remove --dir-diff from your invocation of git difftool. JuxtaCode will still present a diff of the revisions that you passed in.

  • juxta does not yet support comparing 2 specific files (as opposed to revisions) via git difftool.

    Workaround: Open the files in JuxtaCode directly.

Version 1.0.4

⚡️ Lots of performance improvements ⚡️

And a bunch of fixes:

  • Fixed a crash that could occur when opening a diff.
  • Fixed a crash that could occur when scrolling through a list of commits.
  • Fixed visual glitches in commit list when there are a lot of branches.
  • Fixed file history not opening properly when the repository is already open.
  • Fixed File > Open… not offering to open files in file history.
  • Fixed: it wasn’t possible to select text from commit diffs.
  • Fixed: juxta would just show a repository in Finder instead of opening it in JuxtaCode.

Known Issues

Regrettably, using juxta with git difftool fails in a few scenarios:

  • the --dir-diff option isn’t currently supported,
  • .. notation for specifying ranges is only partially supported, and
  • diffs with a lot of files can get stuck after partially loading.

I intend to address these issues in an upcoming update.