emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <esflists@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Carsten Dominik <dominik@uva.nl>,
	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 08:27:46 +0100	[thread overview]
Message-ID: <87604drtvx.fsf@gmail.com> (raw)
In-Reply-To: <87po2lsfsg.fsf@bzg.fr> (Bastien's message of "Fri, 27 Apr 2018 01:34:39 +0200")

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Friday, 27 Apr 2018 at 01:34, Bastien wrote:

[...]

> 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".

I agree with all of the above, as somebody who uses inline tasks all the
time.  I would prefer the syntax to be very simple and would find, for
instance, a line starting with optional whitespace and "! " as a task
marker, akin to comments.  Nicolas proposed !! but I see no need for
more than one...

Using *s seems confusing as they are intended for headlines.  From a
font lock point of view, I would have thought that ! at the start of the
line would be easier as well.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-474-g92785f

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2018-04-27  7:27 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
2018-04-27  7:27               ` Eric S Fraga [this message]
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=87604drtvx.fsf@gmail.com \
    --to=esflists@gmail.com \
    --cc=Alain.Cochard@unistra.fr \
    --cc=bzg@gnu.org \
    --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).