Source files in lispusers>talk all contain only NUL characters

[MattHeffron]

This looks like the same problem that affected the lispusers>proofreader> files.
It seems that no one actually looked inside the files moved before approving the PR.

[rmkaplan]

They look good to me, when I fetch the current master.

[MattHeffron]

Strange. When I look at what github has for the file (master branch) it has length but no content.

[nbriggs]

I agree - I pulled the current master and these files are all NULs, except for TALK.TEDIT, which appears to be OK.

/Users/briggs/Projects/medley/lispusers/TALK
briggs@macrobiotic TALK % od -c TALK
0000000   \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0107200   \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0        
0107216

We'll have to try and recover them from previous commits -- files can be retrieved individually with

git show <commit-id>:path/to/file

so for example:

 medley % git show f4fd00f8b8376fd8a490a79fcbdd2b13063adfb1:lispusers/TEDITTALK >/tmp/TEDITTALK

and then put it back in place of the current NUL filled one. I wonder if we got burned by deleting the lispusers/TALK file and then creating a directory named talk, in the same commit, when many of us have case-insensitive file systems.

[rmkaplan]

I think COPYFILE is where things go wrong. (COPYFILE 'FOO;1 'FOO;1) for any FOO wipes out the contents. The same version number must have slipped in on both sides when I did the copies. I think that's a glitch in COPYFILE, I'll make an issue.

…

On Jul 31, 2025, at 5:33 PM, Nick Briggs ***@***.***> wrote: nbriggs left a comment (Interlisp/medley#2236) <#2236 (comment)> I agree - I pulled the current master and these files are all NULs, except for TALK.TEDIT, which appears to be OK. /Users/briggs/Projects/medley/lispusers/TALK ***@***.*** TALK % od -c TALK 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0107200 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0107216 We'll have to try and recover them from previous commits -- files can be retrieved individually with git show <commit-id>:path/to/file so for example: medley % git show f4fd00f:lispusers/TEDITTALK >/tmp/TEDITTALK and then put it back in place of the current NUL filled one. I wonder if we got burned by deleting the lispusers/TALK file and then creating a directory named talk, in the same commit, when many of us have case-insensitive file systems. — Reply to this email directly, view it on GitHub <#2236 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJKQ3TEGR6ZGOUJ6JED3LKYUPAVCNFSM6AAAAACCYK3RESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBRG4ZTSNBTHE>. You are receiving this because you were assigned.