You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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.
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 ?
The text was updated successfully, but these errors were encountered: