# gitk run from subdir and "find commit touching paths" 3 messages from 2009-01-27 to 2009-01-30. Participants: Sitaram Chamarty, Matt Graham. Thread: https://gitlist.dev/t/17395 ## Sitaram Chamarty, 2009-01-27 17:14 Subject: gitk run from subdir and "find commit touching paths" Message-ID: URL: https://gitlist.dev/e/slrngnug78.877.sitaramc%40sitaramc.homelinux.net ``` If I run gitk from a subdirectory, and then try to find a commit touching a path, it doesn't work. No movement of cursor on "Next/Prev". Running from the main project directory makes it work ok -- you can go "Next" or "Prev" finding other commits that touched the same path. Is this a known problem? I couldn't find it in the mailing list archives. Thanks, Sitaram ``` ## Matt Graham, 2009-01-30 05:56 Subject: Re: gitk run from subdir and "find commit touching paths" Message-ID: <1c5969370901292156k2456b585r8e79889db516bc59@mail.gmail.com> URL: https://gitlist.dev/e/1c5969370901292156k2456b585r8e79889db516bc59%40mail.gmail.com In-Reply-To: ``` On Tue, Jan 27, 2009 at 12:14, Sitaram Chamarty wrote: > If I run gitk from a subdirectory, and then try to find a > commit touching a path, it doesn't work. No movement of > cursor on "Next/Prev". > > Running from the main project directory makes it work ok -- > you can go "Next" or "Prev" finding other commits that > touched the same path. > > Is this a known problem? I couldn't find it in the mailing > list archives. Hi, I get this too. My repos are small enough that I'm usually able to just cd to the root dir and rerun gitk. ``` ## Sitaram Chamarty, 2009-01-30 13:39 Subject: Re: gitk run from subdir and "find commit touching paths" Message-ID: URL: https://gitlist.dev/e/slrngo60pf.l0k.sitaramc%40sitaramc.homelinux.net In-Reply-To: <1c5969370901292156k2456b585r8e79889db516bc59@mail.gmail.com> ``` On 2009-01-30, Matt Graham wrote: > On Tue, Jan 27, 2009 at 12:14, Sitaram Chamarty wrote: > I get this too. My repos are small enough that I'm usually able to > just cd to the root dir and rerun gitk. Mine are too; and if they weren't I'd alias it in bash, no sweat. It was just a question to see if it was a known problem, and really all I wanted was to confirm what I am seeing. I'm not even saying it needs to be fixed :-) ```