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

RE: Question on textconv

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Aug 4, 2026, 21:45 UTC
Message-ID
<01ac01dd245a$8b64f990$a22eecb0$@nexbridge.com>
In-Reply-To
<CALnO6CD+LmWNffptqp4bsoJQaq7Ah8VaKHjTTu6m-Zfm2uN+9w@mail.gmail.com>
On August 4, 2026 4:53 PM, D. Ben Knoble wrote:
Show 41 quoted lines
> On Tue, Aug 4, 2026 at 2:52 PM <rsbecker@nexbridge.com> wrote:
> >
> > I experienced a change in how textconv works since about 2.50 and it
> > is hard to get past. I would appreciate advice:
> >
> > When I define an external binary textconv, roughly like:
> >
> > .gitattributes:
> > simple binary diff=enscr
> >
> > .gitconfig
> > [diff "enscr"]
> >         textconv = run -debug ../../enscribe-conv --verbose
> >         binary = true
> >
> > The supplied file going to the textconv program looks like
> > /tmp/git-blob-GFtIhK/simple and is always empty regardless of the file
> > contents.
> 
> That's strange. Over here (2.53.0), I get the temp file, but it has the expected
> contents.
> 
> (For example, I can debug a bit by using the shell form 'textconv =
> "f() { echo $@; cat $@; <stuff>; }; f"'. NB those $@ need quoted in production, but
> for my little test case that was more hassle than it was worth. We can also see the
> invocation using GIT_TRACE2=1.)
> 
> This was true for me even after setting "binary = true" in the diff driver block, which
> I thought was a bit unusual.
> 
> > When there is only one file named simple in the repository I can find
> > it, but otherwise any ambiguity in the name makes textconv processing
> > impractical. Somewhere prior to this I was supplied with the actual
> > file in the working index instead of a temp file.
> >
> > Am I missing something?
> >
> > Thanks,
> > Randall
> 
> I'm not sure :/

Curiously, I get this only on binary files. It is almost as if leading nulls is causing an issue. If I try on a text file or an ELF format file, the above works - ELF does not begin with a NULL.

Previous: D. Ben KnobleNext: Jeff King
Message 3 of 7 in “Question on textconv”
  1. rsbecker@nexbridge.comAug 4, 2026
  2. D. Ben KnobleAug 4, 2026
  3. rsbecker@nexbridge.comAug 4, 2026
  4. Jeff KingAug 5, 2026
  5. D. Ben KnobleAug 5, 2026
  6. rsbecker@nexbridge.comAug 5, 2026
  7. Jeff KingAug 6, 2026

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.