Hi again,
I'm separating the Org document concept from the document property drawer to
not block the document property drawer by syntax changes.
New RFC coming in a moment. Now only for the document property drawer
functionality.
/G
> -Original Message-
> From: Nicolas Goaziou
> Sen
Hello,
Gustav Wikström writes:
> I'm starting out slow by making this a non-breaking change. At least
> I'm trying to. I.e. everything that worked before should continue to
> work.
This still is a syntax change, which is not to be taken lightly. Since
Org 9.3 is way overdue (I'm not blaming any
(Resending this mail due to formatting-issues. Sorry!)
> From: Adam Porter
> Subject: Re: [O] [RFC] Org document concept + document property drawers
> Date: Sun, 01 Sep 2019 11:11:22 -0500
>
> > #+begin_src org
> > :PROPERTIES:
> > :DIR: ~/
> > :ID:
> From: Adam Porter
> Gustav Wikström writes:
>
> > Previous tree:
> > (org-data nil CONTENTS)
> >
> > With this patch:
> > (org-data nil (document (doc-props) CONTENTS))
> >
> > Yeah.. The structure changed a bit. But it's a fairly trivial change
> > in my opinion. Everything else works as be
> From: Adam Porter
> > #+begin_src org
> > :PROPERTIES:
> > :DIR: ~/
> > :ID: 730e0151-8e34-4dd9-b978-187c3c81e6b4
> > :CATEGORY: Test
> > :END:
> >
> > Section 1 before first headline.
> >
> > ,* TODO Headline 1
> > Section 1 in first headline.
> >
> > ,** TODO Sub-
Gustav Wikström writes:
Hi Gustav,
Thanks for your reply. I sent my most recent message, which reiterated
my question, before this message of yours came through.
>> This is a very interesting idea, and I don't want to dismiss your work,
>> but I am concerned about how much third-party code wil
Hi Adam,
> This is a very interesting idea, and I don't want to dismiss your work,
> but I am concerned about how much third-party code will likely break by
> changing the results returned by org-element for parsing an Org buffer.
> I haven't thoroughly studied all of the code in your patches, so
Gustav Wikström writes:
> Nicolas requested a more thorough introduction to the patch so here it
> comes.
Thank you, this is helpful.
> The first patch deals with formalities. It introduces one new greater
> element called "document". Parsers and everything around it are
> modified to work with
Hi again,
Nicolas requested a more thorough introduction to the patch so here it
comes.
To start with, this relates to the topic presented here:
- https://lists.gnu.org/archive/html/emacs-orgmode/2019-06/msg0.html
The first patch deals with formalities. It introduces one new greater
element
Hi Nicolas,
> -Original Message-
> From: Nicolas Goaziou
>
> > I'm continuing on my proposal to introduce a "document" element in
> > org-mode and the idea of seeing everything before the first headline
> > as the base level 0 outline for a file. I've attached two patches that
> > I'd li
Hello,
Gustav Wikström writes:
> I'm continuing on my proposal to introduce a "document" element in
> org-mode and the idea of seeing everything before the first headline
> as the base level 0 outline for a file. I've attached two patches that
> I'd like some public review of before pushing to m
Gustav Wikström writes:
> I'm continuing on my proposal to introduce a "document" element in
> org-mode and the idea of seeing everything before the first headline
> as the base level 0 outline for a file. I've attached two patches that
> I'd like some public review of before pushing to master.
>
Hi!
I'm continuing on my proposal to introduce a "document" element in
org-mode and the idea of seeing everything before the first headline
as the base level 0 outline for a file. I've attached two patches that
I'd like some public review of before pushing to master.
Patch 0001 introduces the doc
13 matches
Mail list logo
