Hello, alain.coch...@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