From: Bastien <bzg@gnu.org>
To: Carsten Dominik <dominik@uva.nl>
Cc: org-mode list <emacs-orgmode@gnu.org>,
Alain.Cochard@unistra.fr,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views]
Date: Fri, 27 Apr 2018 01:34:39 +0200 [thread overview]
Message-ID: <87po2lsfsg.fsf@bzg.fr> (raw)
In-Reply-To: CADn3Z2+ktm9aCJboVQsAkf7HvmdCxXj2fd94eSquUXYvRYXWRA@mail.gmail.com
Hi Nicolas and Carsten,
Carsten Dominik <dominik@uva.nl> writes:
> Either we keep it as the hack, or use the limitation you
> mention and get rid of the END line.
I think getting rid of the END line goes in the right direction...
> But I am not sure it is really with the trouble to replace a bad
> hack with a slightly better hack.
... but I'm definily not sure neither.
I'd favor a solution where inline tasks are really simple:
0. Prevent cycling for tasks with a high number of stars
("high" being defined by the user as an option).
1. Allow TODO keywords, priority, tags, SCHEDULED and DEADLINE
but nothing else.
2. Archiving and refiling DTRT.
3. ... and we move org-inlinetask.el outside of Org's core.
******************** is really too much clutter and we can simplify
things by saying "more than X stars are going to be inline tasks by
default".
WDYT?
--
Bastien
next prev parent reply other threads:[~2018-04-26 23: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
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 [this message]
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
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=87po2lsfsg.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=Alain.Cochard@unistra.fr \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).