From: Ihor Radchenko <yantar92@gmail.com>
To: "Mark E. Shoulson" <mark@shoulson.com>, emacs-orgmode@gnu.org
Subject: Re: org-pop-mode
Date: Mon, 23 Mar 2020 02:15:48 +0800 [thread overview]
Message-ID: <87r1xkgsrv.fsf@localhost> (raw)
In-Reply-To: <7f5a3798-9128-ac69-c0b2-8f0b9844ab81@shoulson.com>
> Inline tasks seem to be limited to just body text; you
> can't put sub-headings inside them, etc. Org-pop digressions can
> contain sub-headings and whatever other structure, even further
> digressions and "pop"s. So that's something significant that inline
> headings lack.
Thanks for clarifying. Do you actually use this feature? It was hard for
me to come out with anything fitting my workflow.
I tried to play very little with org-pop just now. Generally it looks a
lot like inline tasks, but indeed a lot less integrated with standard
org features.
Some observations:
- the visual appearance looks same as normal org structure. While, as
you said, inline tasks are generally indented too much, the org-pop
approach shows little indication that "inline" headlines are actually
any different from normal org subheadings. Yes, you have cycling, but it
will not be really useful for entries having more than a screen full of
text. Probably, the "inline" headlines should be highlighted in some
way.
- refiling does not touch the :contd: heading
- org-metaright and similar functions mess up the :contd: part
- creating the :contd: headline feels too manual for me. A command to
create the :contd: headline would be useful, I think.
- Archiving does not work
In summary, my impression is that hacking the existing inlinetask
functionality to change visual appearance of inlinetasks (maybe less
indentation) and to allow subtasks could be easier if you really want to
integrate the whole thing with org-mode.
Best,
Ihor
"Mark E. Shoulson" <mark@shoulson.com> writes:
> 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
>
> Oh! And I forgot a crucial feature that org-pop has over inline tasks:
> you can put any amount of org-mode tree-structure inside an org-pop
> digression. Inline tasks seem to be limited to just body text; you
> can't put sub-headings inside them, etc. Org-pop digressions can
> contain sub-headings and whatever other structure, even further
> digressions and "pop"s. So that's something significant that inline
> headings lack.
>
> ~mark
>
>
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next prev parent reply other threads:[~2020-03-22 18:19 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 ` org-pop-mode Mark E. Shoulson
2020-03-22 14:58 ` org-pop-mode Mark E. Shoulson
2020-03-22 18:15 ` Ihor Radchenko [this message]
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=87r1xkgsrv.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mark@shoulson.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).