From: "Mark E. Shoulson" <mark@shoulson.com>
To: Ihor Radchenko <yantar92@gmail.com>,
org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-pop-mode
Date: Wed, 18 Mar 2020 15:57:21 -0400 [thread overview]
Message-ID: <68cc7a92-c382-3eb1-9417-9d0ac563d64a@kli.org> (raw)
In-Reply-To: <87blou171h.fsf@localhost>
On 3/18/20 3:00 AM, Ihor Radchenko wrote:
>> Any feedback?
> >From the first glance it does not look too different from inline
> headings. Could you highlight the difference?
>
> Best,
> Ihor
Well, it's true there is similarity. I even found in my notes where I
noticed inline tasks and their similarity, but all I wrote there was
"but mine is different," so maybe that isn't so helpful. I have not
used inline tasks, and was only barely familiar with them (I did know
they existed, though), so that is my excuse for having invented my own
wheel.
In terms of differences, let's see:
inline tasks are, from a strict outline point-of-view, a zillion levels
down (approximately), which makes them indent waaaay over if you're
using org-indent-mode. My org-pop is the "normal," expected single
level down.
inline tasks mark the end of the task with a special header at the same
level as the task. Org-pop marks the end of the digression with a
special header at the same level as the "base" (the surrounding text).
Your call as to what makes better sense.
inline tasks are well-integrated and worked deep into the innards of
org-mode, to the point that it seems from looking at code that they
cause something of a headache to developers with their exceptional
behavior. On the plus side, that means that many/most packages will Do
the Right Thing in the face of inline tasks. My org-pop is new and
non-standard, with hacks to make a few key things work right with it,
but doesn't have the support of... well, anything else. I'm pretty sure
exporting works well with inline tasks, but currently org-pop has no
special tweaks for it (I'm not even sure what they should be). This is
a reason to stick with inline tasks.
Both approaches sinfully break the underlying outline-mode structure,
which explicitly forbids exactly what we're trying to accomplish with
them. Inline tasks have (way) more seniority and support and indulgence
for doing so, though.
I haven't experimented much with inline tasks as regards the two or
three behaviors that I actually cared enough about to write org-pop;
have to see if they do something like I would have wanted.
Thanks!
~mark
next prev parent reply other threads:[~2020-03-18 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 2:33 org-pop-mode Mark E. Shoulson
2020-03-18 7:00 ` org-pop-mode Ihor Radchenko
2020-03-18 19:57 ` Mark E. Shoulson [this message]
2020-03-22 14:58 ` org-pop-mode Mark E. Shoulson
2020-03-22 18:15 ` org-pop-mode Ihor Radchenko
2020-03-18 19:15 ` org-pop-mode Adam Porter
2020-03-18 20:05 ` org-pop-mode Mark E. Shoulson
2020-03-18 20:24 ` org-pop-mode Adam Porter
2020-03-18 20:52 ` org-pop-mode Mark E. Shoulson
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=68cc7a92-c382-3eb1-9417-9d0ac563d64a@kli.org \
--to=mark@shoulson.com \
--cc=emacs-orgmode@gnu.org \
--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).