[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] org-element.el: Fix properties being upcased by parser
From: |
Nicolas Goaziou |
Subject: |
Re: [PATCH] org-element.el: Fix properties being upcased by parser |
Date: |
Mon, 08 Jun 2020 21:43:36 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Leo Vivier <leo.vivier+dev@gmail.com> writes:
> I understand, but I think the function is also used to modify
> file-parameters like `#+title`. If you run `org-element-parse-buffer`
> on a buffer with the following content:
>
> --------------------------------[START]--------------------------------
> #+title: Foo
> ---------------------------------[END]---------------------------------
>
>
> Here’s what you get:
>
> --------------------------------[START]--------------------------------
> (org-data
> nil
> (section
> (:begin 1
> :end 14
> :contents-begin 1
> :contents-end 14
> :post-blank 0
> :post-affiliated 1
> :parent #0)
> (keyword
> (:key "TITLE" ; <----------
Keywords are stored in a normalized form. In this case, this is
uppercase, for reasons. I don't see an issue here. The docstring could
specify it, tho.
> Ultimately, it’s not changing anything for the users, but I did find it
> a little counterintuitive.
IMO, this is not worth changing. Besides, I'm quite sure it will break
some code elsewhere. Why bother?