# gitk - fails to highlight commits

3 messages from 2007-07-04 to 2007-07-04. Participants: Mark Levedahl, Paul Mackerras.
Thread: https://gitlist.dev/t/8849

## Mark Levedahl, 2007-07-04 00:44

Subject: gitk - fails to highlight commits
Message-ID: <468AED7C.5040507@verizon.net>
URL: https://gitlist.dev/e/468AED7C.5040507%40verizon.net

```
Using gitk on master (281404ca1db4c921ac162f3c0 in the gitk) gitk's 
highlighting is sporadic. Running gitk from a gitk sandbox and typing 
'gitk' into the 'Highlight Commits' box shows nothing highlighted, but 
all commits should be highlighted. After doing this, many of the commits 
revealed by scrolling down the list are highlighted, just not the ones 
visisble at the top nor the first few below.

This problem first appears in commit 322a8cc ("gitk: New algorithm for 
drawing the graph lines).

Mark

```

## Paul Mackerras, 2007-07-04 12:02

Subject: Re: gitk - fails to highlight commits
Message-ID: <18059.35942.150086.936853@cargo.ozlabs.ibm.com>
URL: https://gitlist.dev/e/18059.35942.150086.936853%40cargo.ozlabs.ibm.com
In-Reply-To: <468AED7C.5040507@verizon.net>

```
Mark Levedahl writes:

> Using gitk on master (281404ca1db4c921ac162f3c0 in the gitk) gitk's 
> highlighting is sporadic. Running gitk from a gitk sandbox and typing 
> 'gitk' into the 'Highlight Commits' box shows nothing highlighted, but 
> all commits should be highlighted. After doing this, many of the commits 
> revealed by scrolling down the list are highlighted, just not the ones 
> visisble at the top nor the first few below.

This is fixed by a commit I just pushed out ("gitk: Fix the find and
highlight functions").

Paul.

```

## Mark Levedahl, 2007-07-04 13:34

Subject: Re: gitk - fails to highlight commits
Message-ID: <468BA1E2.5040509@verizon.net>
URL: https://gitlist.dev/e/468BA1E2.5040509%40verizon.net
In-Reply-To: <18059.35942.150086.936853@cargo.ozlabs.ibm.com>

```
Paul Mackerras wrote:
> This is fixed by a commit I just pushed out ("gitk: Fix the find and
> highlight functions").
>
> Paul.
>   
Thanks - that fixed the problem.

Mark

```