From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views]
Date: Mon, 23 Apr 2018 14:31:22 -0700 [thread overview]
Message-ID: <87bme9obit.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 871sf5pr4t.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Carsten Dominik <dominik@uva.nl> writes:
>
>> I would be interested to discuss a better solution. It would be nice is
>> list items could be TODO's, but I though long and har about this back when,
>> and over allo those years, I could not think of anything that could be
>> implemented with reasonable effort.
>
> I think we have to make inline tasks more limited, yet still useful.
>
> One major technical drawback stems from the fact that they allow
> contents.
>
>
> *************** Foo
> ...
> *************** END
>
> It means that they allow, e.g., properties (it hurts inheritance), or
> clocks that do not belong to the containing headline but to the inline
> task itself... It would be a major pain if we had to handle this
> seriously, as a core feature.
>
> Now, if we allow them to have no contents, it becomes much more
> manageable. It means we can still have TODO, tags, priority, but no
> clock, no properties, no log...
Would there be any consideration for an inline syntax that looks more
like a link? Personally, when I want inline TODOs, I want them because
there's a particular chunk of text that I need to do something with.
What about something that looks like:
In 2005 there were approximately [[TODO: Verify this; SCHEDULED:
<tomorrow>; :statistics:][4,500]] Confucius Institutes in operation
worldwide.
That's kind of made-up, but the one-line syntax seems like it would be
well suited to providing tags, priority, scheduling, etc., but none of
the more bulky attributes that are part of a proper headline.
WDYT?
Eric
next prev parent reply other threads:[~2018-04-23 21:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 14:24 Problems created by inlinetasks in agenda views Alain.Cochard
2018-04-16 12:08 ` Nicolas Goaziou
2018-04-16 14:01 ` Eric S Fraga
2018-04-16 16:39 ` Nicolas Goaziou
2018-04-16 17:01 ` Eric S Fraga
2018-04-16 17:25 ` Berry, Charles
2018-04-16 17:33 ` Nicolas Goaziou
2018-04-23 13:50 ` Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views] Alain.Cochard
2018-04-23 14:21 ` Eric S Fraga
2018-04-23 16:03 ` Carsten Dominik
2018-04-23 21:08 ` Nicolas Goaziou
2018-04-23 21:31 ` Eric Abrahamsen [this message]
2018-04-24 11:47 ` Kaushal Modi
2018-04-24 16:01 ` Eric Abrahamsen
2018-04-24 20:22 ` Rasmus
2018-04-25 5:43 ` Carsten Dominik
2018-04-26 23:34 ` Bastien
2018-04-27 7:27 ` Eric S Fraga
2018-04-27 7:46 ` Bastien
2018-04-27 7:57 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bme9obit.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.