[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DISCUSSION] Re-design of inlinetasks
From: |
Alain . Cochard |
Subject: |
Re: [DISCUSSION] Re-design of inlinetasks |
Date: |
Wed, 30 Aug 2023 16:06:51 +0200 |
Russell Adams writes on Wed 30 Aug 2023 14:36:
> On Wed, Aug 30, 2023 at 01:49:26PM +0200, Alain.Cochard@unistra.fr wrote:
> > Russell Adams writes on Tue 29 Aug 2023 15:00:
> > > On Sat, Aug 26, 2023 at 08:01:16PM +0200, Russell Adams wrote:
> > > > Why not just put the TODO heading in a code block with type org?
> > > >
> > > > Then you get all the toys, ignored by the main file.
> > >
> > > If inline tasks are supposed to be Org enabled headings, but
> > > NOT treated like headings in the current file, why not put
> > > them in a src block?
> > >
> > > Doesn't this allow the same functionality without any new syntax
> > > elements, or silly long *'s?
> >
> > Are regular Org tags allowed in this scenario? If not, I'd be
> > miserable.
>
> It's a source block of type Org. That means *everything* that works in
> Org works inside that block. You might open it with C-c C-' to open it
> in an indirect buffer to enable everything.
Sorry, that's not enough for me to understand. What would be the
equivalent of:
* head :foo:
*************** inlt :bar:
*************** END
where the 'bar' tag could be used in exactly the same way as the 'foo'
tag.
Thanks.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
- Re: [DISCUSSION] Re-design of inlinetasks, (continued)
- Re: [DISCUSSION] Re-design of inlinetasks, Ihor Radchenko, 2023/08/26
- Re: [DISCUSSION] Re-design of inlinetasks, Juan Manuel Macías, 2023/08/26
- Re: [DISCUSSION] Re-design of inlinetasks, Ihor Radchenko, 2023/08/26
- Re: [DISCUSSION] Re-design of inlinetasks, Juan Manuel Macías, 2023/08/26
- Re: [DISCUSSION] Re-design of inlinetasks, Ihor Radchenko, 2023/08/27
- Re: [DISCUSSION] Re-design of inlinetasks, Juan Manuel Macías, 2023/08/27
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/26
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/29
- Re: [DISCUSSION] Re-design of inlinetasks, Alain . Cochard, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks,
Alain . Cochard <=
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks, Alain . Cochard, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks, Russell Adams, 2023/08/30
- Re: [DISCUSSION] Re-design of inlinetasks, Ihor Radchenko, 2023/08/30
- Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?, Russell Adams, 2023/08/24
- Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?, Ihor Radchenko, 2023/08/24
- Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?, Russell Adams, 2023/08/24
- Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?, Ihor Radchenko, 2023/08/24
- Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading?, Russell Adams, 2023/08/24