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

invalid command name "listrefs"

From
Junio C Hamano <junkio@cox.net>
Date
Jun 11, 2006, 16:50 UTC
Message-ID
<7vu06rfxg8.fsf@assigned-by-dhcp.cox.net>

Starting gitk, "File->Reread references" results in an error dialog.

This patch resurrects the procedure from an older version, and it seems to work for me, but with the updated code it might be that you wanted to use a different mechanism to implement rereadrefs procedure -- I dunno.

-- >8 -- gitk: rereadrefs wants listrefs

The listrefs procedure was removed during the course of development, but there is still a user of it, so resurrect it.

Signed-off-by: Junio C Hamano <junkio@cox.net>
---
diff --git a/gitk b/gitk
index 9be10a4..ba4644f 100755
--- a/gitk
+++ b/gitk
@@ -5196,6 +5196,24 @@ proc rereadrefs {} {
     }
 }
 
+proc listrefs {id} {
+    global idtags idheads idotherrefs
+
+    set x {}
+    if {[info exists idtags($id)]} {
+	set x $idtags($id)
+    }
+    set y {}
+    if {[info exists idheads($id)]} {
+	set y $idheads($id)
+    }
+    set z {}
+    if {[info exists idotherrefs($id)]} {
+	set z $idotherrefs($id)
+    }
+    return [list $x $y $z]
+}
+
 proc showtag {tag isnew} {
     global ctext tagcontents tagids linknum
 
Next: Paul Mackerras
Message 1 of 2 in “invalid command name "listrefs"”
  1. Junio C HamanoJun 11, 2006
  2. Paul MackerrasJun 11, 2006

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.