From: Bastien <bzg@altern.org>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: inline tasks behave strange with respect to visibility cycling within plain lists [7.9.2 (release_7.9.2-646-g664217 @ /home/grfz/src/org-mode/lisp/)]
Date: Sat, 29 Dec 2012 11:06:44 +0100 [thread overview]
Message-ID: <871ue9f9zf.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20121225132619.GA29757@boo.workgroup> (Gregor Zattler's message of "Tue, 25 Dec 2012 14:26:19 +0100")
Hi Gregor,
thanks for the detailed report.
Gregor Zattler <telegraph@gmx.net> writes:
> Summary:
>
> 1) With respect to visibility cycling I would expect to see
> inline tasks as normal text or plainlist item. I would not
> expect the display of children or subtrees to be cut of
> immediately after an inline task.
>
> This is my main concern. (Hierarchical) plain lists are so
> useful. Tasks are useful. One workaround to combine the
> two would be to use headings instead of plain lists. But this
> looks terrible even with the `hidestars' option and and
> especially in all kinds of exports.
>
> 2) I would not expect to see an error when doing org-cycle with
> certain variable settings. If org-mode is not able to handle
> this situation it should tell so in a way the user is able to
> act upon.
It might disappoint you, but by take on this is very simple: you
should not try to use inline tasks within plain lists.
I added this note in the comment header of org-inlinetask.el:
;; Note that you should not try to use inline tasks within plain list,
;; visibility cycling is known to be problematic when doing so.
If anyone is willing to support inline tasks within plain list,
please send a patch.
Thanks,
--
Bastien
prev parent reply other threads:[~2012-12-29 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 17:32 Bug: inline tasks behave strange with respect to visibility cycling within plain lists [7.9.2 (release_7.9.2-646-g664217 @ /home/grfz/src/org-mode/lisp/)] Gregor Zattler
2012-12-24 8:50 ` Bastien
2012-12-25 13:26 ` Gregor Zattler
2012-12-28 12:08 ` mostely my fault, only a minor bug remains (was: Re: Bug: inline tasks behave strange with respect to visibility cycling within plain lists) Gregor Zattler
2012-12-29 10:06 ` Bastien [this message]
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=871ue9f9zf.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).