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

transcripts: don’t require tags to be in specific order #5494

Open
sellout opened this issue Dec 10, 2024 · 0 comments
Open

transcripts: don’t require tags to be in specific order #5494

sellout opened this issue Dec 10, 2024 · 0 comments
Labels

Comments

@sellout
Copy link
Contributor

sellout commented Dec 10, 2024

A transcript like

```unison :error :hide
this is a parse failure, right?
```

isn’t valid because the info string parser expects :hide to come before :error.

I don’t think the parser should care which order the tags appear in.

However, in the case of unison blocks in particular, there is an optional scratch file name at the end. It isn’t marked by a tag. I think this probably should still have to be last.

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

No branches or pull requests

1 participant