From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ngor Subject: Re: Fwd: Questions about org-element Date: Wed, 29 May 2019 19:06:15 -0400 Message-ID: References: <87ef4l599r.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000dd44d2058a0ed39c" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:58036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hW7eB-00066N-6d for emacs-orgmode@gnu.org; Wed, 29 May 2019 19:06:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hW7e9-0005R7-Ma for emacs-orgmode@gnu.org; Wed, 29 May 2019 19:06:15 -0400 Received: from mail-vk1-xa34.google.com ([2607:f8b0:4864:20::a34]:40789) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hW7e9-0005Qb-Gr for emacs-orgmode@gnu.org; Wed, 29 May 2019 19:06:13 -0400 Received: by mail-vk1-xa34.google.com with SMTP id v140so368796vkd.7 for ; Wed, 29 May 2019 16:06:13 -0700 (PDT) In-Reply-To: <87ef4l599r.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --000000000000dd44d2058a0ed39c Content-Type: text/plain; charset="UTF-8" Hi Org community. I am re-posting my questions here according to Nicolas' recommendation. I am working on a standalone parser implementation for Org which is basically a translation of elisp program to Rust https://github.com/org-rs/org-rs There are couple of things I wanted to ask about: 1) I have discovered several inconsistencies and errors in the Syntax/API documentation https://orgmode.org/worg/dev/org-element-api.html vs https://orgmode.org/worg/dev/org-syntax.html vs elisp source And I don't know the right way to report them. 2) I think I have found a bug in the algorithm (org-element-collect affiliated keywords does not take granularity into accound and seems to be always parsing objects in Caption keyword) 3) I have a question regarding the elisp source source (specifically about the :parent of the parsed objects of the keyword) I can elaborate on each point but I don't want to overwhelm everybody with details right from the start. I guess the meta-question is where and how should I discuss these points? - I never used mailing lists before (If I did something incorrectly or do not follow the established rituals/traditions please do not judge me harshly. ) Thanks Ihor On Sun, May 26, 2019 at 3:02 PM Nicolas Goaziou wrote: > Hello, > > Ngor writes: > > > Sorry to bother you. Just want to make sure that you've received my > > email.. > > I confirm I received this one. However, I suggest to communicate through > to the Org mailing list (). > > >> I am working on a standalone parser for Org > >> https://github.com/org-rs/org-rs/tree/master > >> > >> I closely follow the original elisp algorithm and read > >> - https://orgmode.org/worg/dev/org-element-api.html > >> - https://orgmode.org/worg/dev/org-syntax.html > >> > >> I have discovered several inconsistencies and errors in the > >> Syntax/API documentation, as well as I think I have found a bug in > >> the algorithm. > > Please report them. > > Note that the cache is currently known as buggy. Help is welcome to fix, > or re-implement it. > > >> Also I have some questions regarding some aspects of the algorithm. > > Feel free to ask questions. I'll do my best to help you. However, I am > very busy at the moment, so do not expect too much from me. > > Regards, > > -- > Nicolas Goaziou > --000000000000dd44d2058a0ed39c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Org community.
<= br>
I am re-posting my questions here according to Nicolas' r= ecommendation.

I am working on a standalone parser= implementation for Org which is basically a translation of elisp program t= o Rust
=
There are couple of things I wanted to ask about:
=
1) I have discovered several inconsistencies and errors in t= he Syntax/API documentation
And I do= n't know the right way to report them.

2) I th= ink I have found a bug in the algorithm (org-element-collect affiliated key= words does not take granularity into accound and seems to be always parsing= objects in Caption keyword)

3) I have a quest= ion regarding the elisp source source (specifically about the :parent of th= e parsed objects of the keyword)

I can elabora= te on each point but I don't want to overwhelm everybody with details r= ight from the start. I guess the meta-question is where and how
s= hould I discuss these points? - I never used mailing lists before (If I did= something incorrectly or do=20 not follow the established rituals/traditions please do not judge me=20 harshly. )

Thanks
Ihor


On Sun, May 26, 2019 at 3:02 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wr= ote:
Hello,

Ngor <ngortheo= ne@gmail.com> writes:

> Sorry to bother you. Just want to make sure that you've received m= y
> email..

I confirm I received this one. However, I suggest to communicate through to the Org mailing list (<mailto:emacs-orgmode@gnu.org>).

>> I am working on a standalone parser for Org
>> https://github.com/org-rs/org-rs/tree/master
>>
>> I closely follow the original elisp algorithm and read
>> - https://orgmode.org/worg/dev/org-element= -api.html
>> - https://orgmode.org/worg/dev/org-syntax.html<= /a>
>>
>> I have discovered several inconsistencies and errors in the
>> Syntax/API documentation, as well as I think I have found a bug in=
>> the algorithm.

Please report them.

Note that the cache is currently known as buggy. Help is welcome to fix, or re-implement it.

>> Also I have some questions regarding some aspects of the algorithm= .

Feel free to ask questions. I'll do my best to help you. However, I am<= br> very busy at the moment, so do not expect too much from me.

Regards,

--
Nicolas Goaziou
--000000000000dd44d2058a0ed39c--