gitkraken is missing important feature from gitk











up vote
0
down vote

favorite












I'm a long time gitk user, and switching to gitkraken, I miss at least one important feature. I wonder if there's a way to do this with gitkraken?



In gitk, I can click the mouse on the commit/branch tree to see not only the file names but also the diff contents of that commit. Then I can simply press the up/down arrows to move through the tree and at each commit I see the diffs for THAT commit, (i.e, a single click of up/down).



In gitkraken, when I click on the branches graph, it shows me only the names of the files which changed, and I have to click only one of the files to see its diffs, but that obscures the branches graph. To move to a different commit, I have to kill that pane, and move the cursor, and repeat the tedious process.



Isn't there an easier way? For the moment, I run both gitkraken to do update operations easily, and also open gitk to easily pursue the history.










share|improve this question


























    up vote
    0
    down vote

    favorite












    I'm a long time gitk user, and switching to gitkraken, I miss at least one important feature. I wonder if there's a way to do this with gitkraken?



    In gitk, I can click the mouse on the commit/branch tree to see not only the file names but also the diff contents of that commit. Then I can simply press the up/down arrows to move through the tree and at each commit I see the diffs for THAT commit, (i.e, a single click of up/down).



    In gitkraken, when I click on the branches graph, it shows me only the names of the files which changed, and I have to click only one of the files to see its diffs, but that obscures the branches graph. To move to a different commit, I have to kill that pane, and move the cursor, and repeat the tedious process.



    Isn't there an easier way? For the moment, I run both gitkraken to do update operations easily, and also open gitk to easily pursue the history.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm a long time gitk user, and switching to gitkraken, I miss at least one important feature. I wonder if there's a way to do this with gitkraken?



      In gitk, I can click the mouse on the commit/branch tree to see not only the file names but also the diff contents of that commit. Then I can simply press the up/down arrows to move through the tree and at each commit I see the diffs for THAT commit, (i.e, a single click of up/down).



      In gitkraken, when I click on the branches graph, it shows me only the names of the files which changed, and I have to click only one of the files to see its diffs, but that obscures the branches graph. To move to a different commit, I have to kill that pane, and move the cursor, and repeat the tedious process.



      Isn't there an easier way? For the moment, I run both gitkraken to do update operations easily, and also open gitk to easily pursue the history.










      share|improve this question













      I'm a long time gitk user, and switching to gitkraken, I miss at least one important feature. I wonder if there's a way to do this with gitkraken?



      In gitk, I can click the mouse on the commit/branch tree to see not only the file names but also the diff contents of that commit. Then I can simply press the up/down arrows to move through the tree and at each commit I see the diffs for THAT commit, (i.e, a single click of up/down).



      In gitkraken, when I click on the branches graph, it shows me only the names of the files which changed, and I have to click only one of the files to see its diffs, but that obscures the branches graph. To move to a different commit, I have to kill that pane, and move the cursor, and repeat the tedious process.



      Isn't there an easier way? For the moment, I run both gitkraken to do update operations easily, and also open gitk to easily pursue the history.







      gitkraken gitk






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 8 at 11:19









      Jim Newton

      429




      429





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206699%2fgitkraken-is-missing-important-feature-from-gitk%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206699%2fgitkraken-is-missing-important-feature-from-gitk%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Guess what letter conforming each word

          Port of Spain

          Run scheduled task as local user group (not BUILTIN)