From: c.buhtz@posteo.jp
To: Emacs orgmode <Emacs-orgmode@gnu.org>
Subject: Re: Presenting Hyperorg version 0.1.0: The Org to HTML Converter
Date: Sun, 24 Mar 2024 14:22:03 +0000 [thread overview]
Message-ID: <9e466e7e9d9de12103df770ace706d21@posteo.de> (raw)
In-Reply-To: <87h6gvbvt8.fsf@localhost>
Dear Ihor,
thanks for your reply.
Am 24.03.2024 14:31 schrieb Ihor Radchenko:
> Hmm. I thought that you implemented Org parser in python from scratch.
> Now, I see that you are using orgparse.
The orgparse package do not parse much of on org file. IT does parse the
meta infos (property drawers, etc) but not the content of an orgfile. In
the long run I might replay orgparse to reduce dependencies.
Beside orgparse yes I implement an org parser.
> Wondering what you are referring to when mentioning "resilient when
> dealing with parser issues".
Orgparse do throw exceptions e.g. UnicodeDecodeError or when timestamps
are invalid. Hyperorg catch that exceptions and go on with the next node
without interrupting the whole process.
Other things are "invalid" links, e.g. unknown orgids, unknown roam
links, unsupported "link kinds" ("protocols" in org syntax?; e.g.
"inkscape:").
Additionally there are multiple fancy but not supported org features
(e.g. tables) currently not supported. Hyperorg shouldn't stop or crash
at this point.
> index can be produced with minimal configuration via ox-publish.
"minimal" is a subjective term here. Again I don't blame the tools or
the Emacs universe.
But for me it is not even minimal to get ox-publish run in the first
place. Not speaking about further modifications, e.g. an index.
Emacs, Lisp and its "documentation" is a special thing not everybody can
or want to handle. I would have to invest so much resources into basics
like Lisp just to understand the documentation in a way that I would be
able to modify the publishing feature in a (for me) satisfying way. I am
the problem not Emacs and Co. ;)
Kind
Christian Buhtz
next prev parent reply other threads:[~2024-03-24 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:23 Presenting Hyperorg version 0.1.0: The Org to HTML Converter c.buhtz
2024-03-20 13:09 ` Ihor Radchenko
2024-03-23 13:50 ` c.buhtz
2024-03-23 13:58 ` Ihor Radchenko
2024-03-23 19:45 ` c.buhtz
2024-03-24 13:31 ` Ihor Radchenko
2024-03-24 14:22 ` c.buhtz [this message]
2024-03-24 14:40 ` Ihor Radchenko
2024-03-24 16:59 ` c.buhtz
2024-03-24 18:15 ` Ihor Radchenko
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=9e466e7e9d9de12103df770ace706d21@posteo.de \
--to=c.buhtz@posteo.jp \
--cc=Emacs-orgmode@gnu.org \
/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).