Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the extension of the DINFO files from TEDIT, for HCFILES? #1904

Open
rmkaplan opened this issue Dec 12, 2024 · 1 comment
Open

Change the extension of the DINFO files from TEDIT, for HCFILES? #1904

rmkaplan opened this issue Dec 12, 2024 · 1 comment

Comments

@rmkaplan
Copy link
Contributor

The DINFO files say they are Tedit files, and some segments of the those are in fact Tedit. But the files themselves are not well-formed, and they cause errors if not opened in a special DINFO way.

So code like HCFILES doesn't keep tripping over them, what about changing them to a more indicative extension, like .DINFO ?

@rmkaplan
Copy link
Contributor Author

Continuing on this, I think then that DINFO should have its own hardcopy-type entry. If we then figure out how it makes sense to hard copy a dinfo file, we can put that in its own hardcopy function.

It may not even make sense to hardcopy a DINFO file, if it is just a hodge-podge of snippets in a random order. Or it may be that the file contains an indexing tree that could be put out as a kind of table-of-contents.

But meanwhile, it would remove confusion and clean up the HCFILES transcript--these are not Tedit files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant