git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bug in gitk search box

From
Brian Downing <bdowning@lavos.net>
Date
Jul 25, 2007, 13:56 UTC
Message-ID
<20070725135621.GC21692@lavos.net>
To reproduce:
* Open gitk in any repository, the Git one seems to work fine.
* Type a string that it won't find into the search box, like 'asdfasdf'.
* Click find.
You'll get:
can't read "commitdata(e83c5163316f89bfbde7d9ab23ca2e25604af290)": no such element in array
can't read "commitdata(e83c5163316f89bfbde7d9ab23ca2e25604af290)": no such element in array
    while executing
"doesmatch $commitdata($id)"
    (procedure "findmore" line 21)
    invoked from within
"findmore"
    ("eval" body line 1)
    invoked from within
"eval $script"
    (procedure "dorunq" line 9)
    invoked from within
"dorunq"
    ("after" script)

Where the SHA1 is always the earliest SHA1 in the rev-list gitk is examining.

After this happens you get a "busy cursor" when hovering over most of gitk, and you can't search again until gitk is restarted.

-bcd
Next: Paul Mackerras
Message 1 of 6 in “Bug in gitk search box”
  1. Brian DowningJul 25, 2007
  2. Paul MackerrasJul 26, 2007
  3. Junio C HamanoJul 26, 2007
  4. Paul MackerrasJul 26, 2007
  5. Junio C HamanoJul 26, 2007
  6. Marco CostalbaJul 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.