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

Re: How to make gitk not overwrite my selection?

From
JHJean-Luc Herren <jlh@gmx.ch>
Date
Mar 5, 2008, 22:44 UTC
Message-ID
<47CF223A.60507@gmx.ch>
In-Reply-To
<20080304230306.GA18246@sigill.intra.peff.net>
Jeff King wrote:
> On Tue, Mar 04, 2008 at 04:39:08PM +0100, Jean-Luc Herren wrote:
>> 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. 
> The patch below seems to work for me (see the "auto-select sha1" option
> under preferences). However, I don't actually know tcl, so I
> cargo-culted all of the option processing magic. Paul, if you want to
> take this patch, please read it carefully. ;)

Thanks, I don't know tcl either, but the patch seems to work great here.

jlh
Previous: Jeff KingNext: Martin Langhoff
Message 3 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.