From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems created by inlinetasks in agenda views
Date: Mon, 16 Apr 2018 14:08:06 +0200 [thread overview]
Message-ID: <87in8ricbd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23248.48530.817172.917300@frac.u-strasbg.fr> (Alain Cochard's message of "Fri, 13 Apr 2018 16:24:18 +0200")
Hello,
Alain.Cochard@unistra.fr writes:
> Hello. I have the file (with name 'bug.org'):
>
> * foo :foofoofoo:
> *************** TODO an inlinetask
> foo
> *************** END
> barXXX
>
>
> (1) 'C-c a m foofoofoo'
>
> gives be
>
> Headlines with TAGS match: foofoofoo
> Press `M-0 r' to search again with new search string
> bug: foo :foofoofoo:
> bug: ..............TODO an inlinetask :foofoofoo::
> bug: ..............END :foofoofoo::
>
> which I do not find really normal.
>
> (2) Similarly 'C-c a s barXXX'
>
> gives me
>
> Search words: barXXX
> Press `[', `]' to add/sub word, `{', `}' to add/sub regexp, `M-0 r' to edit
> bug: END :foofoofoo::
>
Fixed. Thank you.
> PS: Also, is that normal that inlinetaks are virtually not documented
> in the manual?
Inlinetasks has a lot of glitches like the one you noticed above. It is
not ready for prime time. Worse, I don't think its design is good,
either. Even if that sounds smart at first, inline tasks should not use
the same syntax as first-class headlines. This introduces too many
complications.
However, since inline tasks have been around for years, it may be a good
time to decide once and for all how, and if, they should be included in
Org proper. Note that last time this discussion happened, we couldn't
even agree on a set of features.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-04-16 12:08 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 [this message]
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
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=87in8ricbd.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Alain.Cochard@unistra.fr \
--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).