From: Ihor Radchenko <yantar92@posteo.net>
To: c.buhtz@posteo.jp
Cc: Emacs orgmode <Emacs-orgmode@gnu.org>
Subject: Re: Presenting Hyperorg version 0.1.0: The Org to HTML Converter
Date: Sun, 24 Mar 2024 13:31:31 +0000 [thread overview]
Message-ID: <87h6gvbvt8.fsf@localhost> (raw)
In-Reply-To: <4V28mv5Q3rz6tyS@submission01.posteo.de>
<c.buhtz@posteo.jp> writes:
> On 2024-03-23 13:58 Ihor Radchenko <yantar92@posteo.net> wrote:
>> Although I am actually more interested in other questions -
>> why custom parser and what is tailored for zettelkasten.
>
> What do you mean by "custom parser"?
Hmm. I thought that you implemented Org parser in python from scratch.
Now, I see that you are using orgparse.
Wondering what you are referring to when mentioning "resilient when
dealing with parser issues".
> Zettelkasten? Hyperorg handles the links between nodes out of the box
> including the backlinks. It also creates an index (nodes sorted by
> title, tags, etc pp).
>
> Of course with Emacs is everything possible even Coffee making. But the
> difference are the resources you have to invest into configure it. This
> is much even if you know Lisp.
index can be produced with minimal configuration via ox-publish.
Backlinks are certainly a novelty. I do not recall Org publishing
systems that produce backlinks automatically (not via dynamic block).
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-03-24 13:31 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 [this message]
2024-03-24 14:22 ` c.buhtz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6gvbvt8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=Emacs-orgmode@gnu.org \
--cc=c.buhtz@posteo.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.