From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Dauer <mick.dauer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: org-cut-special on inlinetask kill until point-max
Date: Thu, 17 Aug 2023 11:30:40 +0000 [thread overview]
Message-ID: <87fs4hrjmn.fsf@localhost> (raw)
In-Reply-To: <CAP7OBxKLZ7GqZ36LP4XjJD3K4-KT4s0xC_8OS+arwiu7feSAwQ@mail.gmail.com>
Michael Dauer <mick.dauer@gmail.com> writes:
> I probably mis-interpreted the code. Because then I would also fail for
> normal headings. Just thinking about the symptoms I think the issue Is that
> (org-end-of-subtree) works with type 'headline. And inlinetask is a
> different type, right?
Yes. Inlinetask is not considered a subtree of its own.
Just like other foldable elements (lists/drawers/blocks) are not considered subtrees.
> IMO org-mode should consistently treat inlinetasks including the END line
> as a branch. Then org-cut-special would do something useful on them, i.e.
> cutting the inlinetask includinging its contents and the END line.
It would not be consistent. We already do not treat, for example, lists
special in `org-cut-special'.
--
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:[~2023-08-17 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 11:14 BUG: org-cut-special on inlinetask kill until point-max Michael Dauer
2023-08-16 11:48 ` Ihor Radchenko
2023-08-16 11:57 ` Michael Dauer
2023-08-16 12:12 ` Ihor Radchenko
2023-08-16 15:55 ` Michael Dauer
2023-08-16 16:02 ` Ihor Radchenko
2023-08-17 8:42 ` Michael Dauer
2023-08-17 8:56 ` Ihor Radchenko
2023-08-17 9:00 ` Michael Dauer
2023-08-17 11:30 ` Ihor Radchenko [this message]
2023-08-17 13:05 ` Michael Dauer
2023-08-17 17:50 ` [POLL] Should org-copy/cut/paste-special handle inlinetasks specially? (was: BUG: org-cut-special on inlinetask kill until point-max) 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=87fs4hrjmn.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@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).