From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Cheong Yiu Fung <mail@yiufung.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org.el (org-show-context-detail): add option 'ancestors-with-entry
Date: Mon, 19 Apr 2021 10:21:16 +0200 [thread overview]
Message-ID: <87y2ded6rn.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878s5inyb2.fsf@yiufung.net> (Cheong Yiu Fung's message of "Fri, 16 Apr 2021 21:39:29 +0800")
Hello,
Cheong Yiu Fung <mail@yiufung.net> writes:
> Hi, I'm proposing a new option in `org-show-context-detail', which shows
> current headline, its ancestors, *and the entry itself*. This is useful
> when export matched subtrees and their contents quickly with least
> manual intervention.
>
> Consider when working on different aspects of a project and taking notes
> as we go:
>
> * Project
> A project tree
> ** Task1
> ** Task2
> *** ASK Something to align
> Something for discussion
> ** Task3
> ** Task4
> *** ASK Something else to align
> Something else.
>
> At some point, we may wish to export only certain contents. For example,
> to export headings with TODO keyword of "ASK", along with the task
> context (ancestors TASK<N> heading name), and their own content for
> discussion with colleagues. Ideally, this can be done by
> org-sparse-tree, followed by org-export with visible-only + subtree-only
> option.
>
> Expected output:
> * Project
> ** Task2
> *** ASK Something to align
> Something for discussion
> ** Task4
> *** ASK Something else to align
> Something else.
>
> Current options, though, either require manual expansion to show both
> ancestors AND entry, which becomes tedious soon;
>
> * Project
> ** Task2
> *** ASK Something to align
> ** Task4
> *** ASK Something else to align
>
> or it shows extra contents (`local' will include the *next* heading, in
> this example, the non-related Task3)
>
> * Project
> *** ASK Something to align
> Something for discussion
> ** Task3
> *** ASK Something else to align
> Something else.
>
> `ancestor-with-entries' is a long name that pose some difficulties to
> updating documentations, so I wish to have some feedbacks before moving
> on. Is there better way to achieve this effect? Am I overlooking
> something?
Don't you need to simply move point within the entry and use `ancestors'
view?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-04-19 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 13:39 [PATCH] org.el (org-show-context-detail): add option 'ancestors-with-entry Cheong Yiu Fung
2021-04-19 8:21 ` Nicolas Goaziou [this message]
2021-04-19 16:03 ` Cheong Yiu Fung
2021-04-20 13:15 ` Nicolas Goaziou
2021-04-20 13:38 ` Cheong Yiu Fung
2021-04-21 9:15 ` Cheong Yiu Fung
2021-04-21 9:51 ` Cheong Yiu Fung
2021-04-22 13:32 ` Nicolas Goaziou
2021-04-22 15:31 ` Cheong Yiu Fung
2021-04-27 20:31 ` Nicolas Goaziou
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=87y2ded6rn.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@yiufung.net \
/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).