Sorry for delay. I expected that a next step with inline raw AST
fragments would be easier, but I have got working example for parser
tests grouped in single file earlier.
Certainly org files may be source for parser tests. They are readable
enough to be convenient for developers and, I hope,
Max Nikulin writes:
> On 11/12/2021 21:39, Ihor Radchenko wrote:
>>
>> The attached patch is an attempt to create something like shared repo
>> for Org element parser tests.
>
> "[PATCH]" prefix in the subject might be a reason why you message
> received less attention than it should.
Well. I
Tim Cross writes:
I have nothing to say about licence question. Replying to the other part
> ... On
> the other hand, I guess there could be cases where people want to just
> checkout these samples to use to validate their own library/parser etc.
> I tend towards putting them in the org-mode rep
Max Nikulin writes:
> On 11/12/2021 21:39, Ihor Radchenko wrote:
>
> Since these tests will unlikely become a part of some software, I do not think
> that GPL may be an obstacle for any project. Requirement of signed consent
> will
> likely prevent contributing of new cases from some developer
On 11/12/2021 21:39, Ihor Radchenko wrote:
The attached patch is an attempt to create something like shared repo
for Org element parser tests.
"[PATCH]" prefix in the subject might be a reason why you message
received less attention than it should.
The test set is essentially a series of .
Dear all,
The attached patch is an attempt to create something like shared repo
for Org element parser tests.
The idea is moving the tests out from Elisp into a set of text files.
That way, anyone interested in developing Org syntax support can use our
tests and potentially contribute more test f
