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

How to make gitk not overwrite my selection?

From
JHJean-Luc Herren <jlh@gmx.ch>
Date
Mar 4, 2008, 15:39 UTC
Message-ID
<47CD6D1C.1080202@gmx.ch>
Hi list!

In gitk, whenever I select a commit in the tree, the SHA1 field gets automatically selected, putting its hash into the current selection for easy pasting into other applications. I wonder if I can disable this, because I find it rather annoying; if I do happen to want to paste the hash somewhere, I can easily double click the SHA1 field.

This is specially annoying when I select a hash in xterm and then start gitk to paste it in the SHA1 field. But immediately after gitk opens, it preselects the current HEAD, overwriting my previous selection from xterm.

Generally I think an application should not replace the selection unless the user explicitely marks something. Although I can understand that it can be useful sometimes with gitk. Therefore it should maybe be optional.

Thanks, jlh

Next: Jeff King
Message 1 of 6 in “How to make gitk not overwrite my selection?”
  1. Jean-Luc HerrenMar 4, 2008
  2. Jeff KingMar 4, 2008
  3. Jean-Luc HerrenMar 5, 2008
  4. Martin LanghoffMar 5, 2008
  5. Paul MackerrasMar 6, 2008
  6. gitk: make autoselect optionalJeff King, Mar 6, 2008

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.