{"thread":{"id":"59238","subject":"Gitk : When the number of commits is small, you can roll up excessively","startedAt":"2023-02-14T06:02:55Z","lastAt":"2023-02-28T06:35:49Z","messageCount":4,"participants":["L2750558108@outlook.com","Philip Oakley","Johannes Sixt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"472049","messageId":"BY5PR14MB3560879E6CBDD493C873DB18B1A29@BY5PR14MB3560.namprd14.prod.outlook.com","threadId":"59238","inReplyTo":null,"subject":"Gitk : When the number of commits is small, you can roll up excessively","fromName":"L2750558108@outlook.com","fromEmail":"l2750558108@outlook.com","sentAt":"2023-02-14T06:02:49Z","receivedAt":"2023-02-14T06:02:55Z","isPatch":false,"sender":{"key":"l2750558108@outlook.com","avatar":"https://gravatar.com/avatar/d660aedf7309af6cb004f0f08cf6946c8dd674b9a777699fa4857e0bdf2e0c58?d=mp&s=160"},"body":"Gitk : When the number of commits is small, you can roll up excessively\n\n\n\n\n\n\n\nReduce :\n\n\n\n1.Create a new respository\n2.Make 2 Commit\n3.Go to Gitk to see them\n4.Scroll up in the commit list and you can see the error"},{"id":"472752","messageId":"3f11a4d5-6774-ddd9-060e-3e95acb84c69@iee.email","threadId":"59238","inReplyTo":"BY5PR14MB3560879E6CBDD493C873DB18B1A29@BY5PR14MB3560.namprd14.prod.outlook.com","subject":"Re: Gitk : When the number of commits is small, you can roll up excessively","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2023-02-26T12:26:08Z","receivedAt":"2023-02-26T12:26:15Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"A bit of a late response..\nOn 14/02/2023 06:02, L2750558108@outlook.com wrote:\n> Gitk : When the number of commits is small, you can roll up excessively\n>\n> Reduce :\n>\n> 1.Create a new respository\n> 2.Make 2 Commit\n> 3.Go to Gitk to see them\n> 4.Scroll up in the commit list and you can see the error\nI cannot replicate this problem (on Git-for-Windows git version\n2.39.2.windows.1).\n\nWhat OS, Git and gitk versions are you on?\n\nI created the repo with the commands\nphili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src (main)\n$ git init gitkfault\n$ cd gitkfault/\n$ echo test>file;git add file;git commit -mfirst\n$ echo test2>file;git add file;git commit -msecond\n$ gitk &\n[1] 1021\n\nI was visualising the commits (lower gitk window) with the \"Diff\" and\n\"Patch\" settings.\n \nAt your step 4, I tried 'scrolling up' both by mouse clicking on the two\ncommits in the top left window that displays the history, and by using\nthe left/right arrows displayed just right of the \"SHA1 ID\" value. No\nerrors were shown.\n\n(those sha1 arrows are distinct from the 'Find' selection and navigation\ncapability immediately below the \"SHA1 ID\" line.\n\nWhat were the exact errors shown at your step 4?\n\n--\nPhilip\n"},{"id":"472776","messageId":"15d5c6c5-091a-63b1-979a-5aaa64c9e717@iee.email","threadId":"59238","inReplyTo":"CH2PR14MB35637B8C5593D5F17076E7EEB1AF9@CH2PR14MB3563.namprd14.prod.outlook.com","subject":"Re: Gitk : When the number of commits is small, you can roll up excessively","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2023-02-27T10:00:45Z","receivedAt":"2023-02-27T10:00:55Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"On 27/02/2023 05:01, L2750558108@outlook.com wrote:\n> You can scroll up via the scroll wheel or the right column button and\n> see the white space in front of the first row, and in this case, the\n> collision box for each row is misaligned, which prevents me from\n> selecting the commit by clicking. If you stll not understand, I can\n> send a picture or video to show the situation I am experiencing,\n\nI see the space above (which I guess is for 'uncommitted changes',\nshould they exist) and a small space below when scrolling.\nI'm unsure what the 'collision box' refers to as I don't see any\n'misalignment'. But I maybe just too familiar with gitk's quirks.\n\n> but I don't know where to put them\n>\n\nThe https://groups.google.com/g/git-users does allow (If I remember\ncorrectly) the inclusion of photos. Please do annotate/label the screen\nshots. Plain text doesn't always carry the expected nuances...\n>  \n> ------------------------------------------------------------------------\n> L2750558108@outlook.com\n>\n>  \n> From: Philip Oakley \n> Date: 2023-02-26 20:26\n> To: L2750558108@outlook.com; git \n> Subject: Re: Gitk : When the number of commits is small, you can\n> roll up excessively\n> A bit of a late response..\n> On 14/02/2023 06:02, L2750558108@outlook.com wrote:\n> > Gitk : When the number of commits is small, you can roll up\n> excessively\n> >\n> > Reduce :\n> >\n> > 1.Create a new respository\n> > 2.Make 2 Commit\n> > 3.Go to Gitk to see them\n> > 4.Scroll up in the commit list and you can see the error\n> I cannot replicate this problem (on Git-for-Windows git version\n> 2.39.2.windows.1).\n>\n> What OS, Git and gitk versions are you on?\n>\n> I created the repo with the commands\n> phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src (main)\n> $ git init gitkfault\n> $ cd gitkfault/\n> $ echo test>file;git add file;git commit -mfirst\n> $ echo test2>file;git add file;git commit -msecond\n> $ gitk &\n> [1] 1021\n>\n> I was visualising the commits (lower gitk window) with the \"Diff\" and\n> \"Patch\" settings.\n>  \n> At your step 4, I tried 'scrolling up' both by mouse clicking on\n> the two\n> commits in the top left window that displays the history, and by\n> using\n> the left/right arrows displayed just right of the \"SHA1 ID\" value. No\n> errors were shown.\n>\n> (those sha1 arrows are distinct from the 'Find' selection and\n> navigation\n> capability immediately below the \"SHA1 ID\" line.\n>\n> What were the exact errors shown at your step 4?\n>\n> -- \n> Philip\n>\n\n"},{"id":"472840","messageId":"75afffcd-65f8-e8e2-1cd9-51806194e4b3@kdbg.org","threadId":"59238","inReplyTo":"15d5c6c5-091a-63b1-979a-5aaa64c9e717@iee.email","subject":"Re: Gitk : When the number of commits is small, you can roll up excessively","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2023-02-28T06:35:41Z","receivedAt":"2023-02-28T06:35:49Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 27.02.23 um 11:00 schrieb Philip Oakley:\n> On 27/02/2023 05:01, L2750558108@outlook.com wrote:\n>> You can scroll up via the scroll wheel or the right column button and\n>> see the white space in front of the first row, and in this case, the\n>> collision box for each row is misaligned, which prevents me from\n>> selecting the commit by clicking. If you stll not understand, I can\n>> send a picture or video to show the situation I am experiencing,\n> \n> I see the space above (which I guess is for 'uncommitted changes',\n> should they exist) and a small space below when scrolling.\n> I'm unsure what the 'collision box' refers to as I don't see any\n> 'misalignment'. But I maybe just too familiar with gitk's quirks.\n\nThe issue is this: When there is vertical space for a list of, say, 10\ncommits, but there are only 3 commits, then you can scroll the display\nsuch that the 3 commit lines are at the bottom of the list and there is\nblank space above the lines. Now, when you click on one of the lines,\nnothing happens; but when you click into the void near the top, one of\nthe lines is selected as if the lines were displayed at the top.\nClearly, the click hitbox for the lines is not aligned with how the\nlines are displayed.\n\nIMHO, this is a case of \"if it hurts, don't do it\".\n\n-- Hannes\n\n"}]}