From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [fr] org-copy-subtree or so with no header
Date: Thu, 11 Jan 2024 15:57:56 +0000 [thread overview]
Message-ID: <87mstbj20r.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8vkH+kv3k7FftcaGShNdMVZH4poxtzhnRnSwoYTfdESxg@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> [there is more that could in principle be discussed as an /analogous/
> topic, perhaps for the picky sake of keeping orthogonality across org
> features in mind, but i don't have it in me to cover. to adumbrate:
> 1] allowing choosing exporting a subtree with or without the top
> header similar to the above and 2] allowing /forcing/ exporting
> subtrees, again with or without exporting the top header just as in
> [1], even when the todo kw on the header in conjunction with
> org-export-with-tasks has inhibited exporting the subtree. i have for
> many years waned both feaures also. but i might not be able to
> provide further clarification or particpate in the discussion for
> unrelated reasons. it is just an extraneous comment for those who get
> what i am talking about, if any.]
If I understand correctly, 1] is covered by body-only option.
2] is probably a bug. It would help if you provide a more clear example
illustrating the problem.
--
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-01-11 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 6:58 [fr] org-copy-subtree or so with no header Samuel Wales
2024-01-09 7:06 ` Samuel Wales
2024-01-09 22:04 ` Ihor Radchenko
2024-01-10 3:37 ` Samuel Wales
2024-01-11 15:53 ` Ihor Radchenko
2024-01-11 15:57 ` Ihor Radchenko [this message]
2024-01-12 2:18 ` Samuel Wales
2024-01-12 12:11 ` 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=87mstbj20r.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).