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

Potentially bless a file extension? #2

Open
rdmurphy opened this issue Mar 7, 2020 · 1 comment
Open

Potentially bless a file extension? #2

rdmurphy opened this issue Mar 7, 2020 · 1 comment

Comments

@rdmurphy
Copy link

rdmurphy commented Mar 7, 2020

Would love to add this as a reader to quaff, but would need some way to say “treat this as a Betty file.”

If it passes all ArchieML tests and returns the same thing I could also potentially include a flag that uses Betty instead.

Great work!

@thomaswilburn
Copy link
Collaborator

thomaswilburn commented Mar 7, 2020

This parser just takes a string as input, so I don't think the file extension actually matters. Our rig just reads *.txt this way. I don't have any strong opinions about picking a "real" file extension for it.

The NYT tests are checked in, and apart from the ones that would conflict with the multiline:: ... ::multiline syntax, they all pass as of today. I think a flag would be fine. This is basically a superset of ArchieML, not a true fork.

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

2 participants