From: David Masterson <dsmasterson92630@outlook.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org,
Sebastian Miele <sebastian.miele@gmail.com>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Empty headline titles unsupported: Bug?
Date: Thu, 27 May 2021 15:35:02 -0700 [thread overview]
Message-ID: <SJ0PR03MB545521ACAC91A60238E31E399B239@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87bl8wyhun.fsf@localhost> (Ihor Radchenko's message of "Thu, 27 May 2021 11:29:36 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> David Masterson <dsmasterson92630@outlook.com> writes:
>
>> Could an extensible pre-hook that runs a list of functions take care of
>> the inconsistencies where each function recognizes one change to the
>> standard grammar and adjusts the input accordingly?
>
> Could you elaborate? For now, this sounds like unnecessary
> over-complication. Why would we need to introduce deviations from
> grammar in different functions?
Testing the usefulness of extensions to the grammar before they're added
to the grammar..?
Thinking about it, though, I'm not sure how you could "pre-parse" a
section of the file, make changes to the file via an extension, then
roll back the file pointer and let the regular parser take over. I was
thinking of a "hook" approach where, when the parser gets to a certain
point (beginning of a header?), it could call the hooks with the current
spot as input. If the hooks try to "extract" something from the input
(to process it and hide it from the regular grammar), I have a feeling
that would mess up the base parser.
It was just an idea... ;)
--
David Masterson
next prev parent reply other threads:[~2021-05-27 22:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 11:15 Empty headline titles unsupported: Bug? Sebastian Miele
2021-05-22 12:21 ` Nicolas Goaziou
2021-05-23 4:45 ` Ihor Radchenko
2021-05-23 14:06 ` Nicolas Goaziou
2021-05-23 14:33 ` Ihor Radchenko
2021-05-23 14:55 ` Nicolas Goaziou
2021-05-23 15:22 ` Ihor Radchenko
2021-05-24 11:01 ` Sebastian Miele
2021-05-24 10:37 ` Sebastian Miele
2021-09-26 9:04 ` Bastien
2021-09-26 23:47 ` Tom Gillespie
2021-09-27 19:59 ` Nicolas Goaziou
2021-09-29 11:26 ` Bastien
2021-05-24 10:46 ` Sebastian Miele
2021-05-24 22:17 ` David Masterson
2021-05-25 10:43 ` Sebastian Miele
2021-05-25 11:43 ` Sebastian Miele
2021-05-25 16:10 ` Nicolas Goaziou
2021-05-25 21:04 ` David Masterson
2021-05-25 23:06 ` Tim Cross
2021-05-26 23:37 ` David Masterson
2021-05-26 14:07 ` Ihor Radchenko
2021-05-26 23:42 ` David Masterson
2021-05-27 3:29 ` Ihor Radchenko
2021-05-27 22:35 ` David Masterson [this message]
2021-05-28 5:36 ` Tom Gillespie
2021-05-29 6:21 ` David Masterson
2021-05-29 6:54 ` Tom Gillespie
2021-05-29 8:04 ` Ihor Radchenko
2021-05-29 19:33 ` Tom Gillespie
2021-05-30 4:06 ` Ihor Radchenko
2021-05-29 14:09 ` Ihor Radchenko
2021-05-30 2:19 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR03MB545521ACAC91A60238E31E399B239@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson92630@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=sebastian.miele@gmail.com \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).