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:57:55 +0100 [thread overview]
Message-ID: <87po2lqdx8.fsf@gmail.com> (raw)
In-Reply-To: <87in8df5x0.fsf@gnu.org> (Bastien's message of "Fri, 27 Apr 2018 09:46:19 +0200")
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On Friday, 27 Apr 2018 at 09:46, Bastien wrote:
[...]
> Does that make sense to you?
It does. Thanks.
In any case, getting rid of the ***** END bit will be nice. And I've
already moved to using drawers for a large number of my inline task use
cases, the ones that weren't really tasks!
--
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 --]
prev parent reply other threads:[~2018-04-27 7:58 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
2018-04-27 7:46 ` Bastien
2018-04-27 7:57 ` Eric S Fraga [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=87po2lqdx8.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).