Re: [O] Feature Request: allow export yes/no for blocks that are valid babel inputs

2019-04-16 Thread Fraga, Eric
I missed your original query. Have you considered using drawers? I use these instead of inline tasks for "inputs" of the type you describe. You can control their export using the d: option. -- Eric S Fraga via Emacs 27.0.50, Org release_9.2.3-327-g3375f0

Re: [O] Feature Request: allow export yes/no for blocks that are valid babel inputs

2019-04-16 Thread Carlos Pita
Hi Berry, sorry for the late reply, I was pretty busy lately. I didn't know about inline tasks, thanks for let me know. The idea is cool but I think that regarding the use case I'm suggesting, they are a more or less hackish workaround and not a proper solution. I'm saying this because: 1) They

Re: [O] Converting tags to TODO states

2019-04-16 Thread garjola
On Tue 16-Apr-2019 at 15:26:16 +02, Bernt Hansen wrote: > garj...@garjola.net writes: > >> Hi, >> >> For my GTD implementation with org-mode, I have been using the :next: >> tag for my next actions. I would like now to use a "NEXT" TODO keyword, >> which means that I need to convert all :next: ta

[O] org-mode table to elisp script

2019-04-16 Thread f . nikolakopoulos
I like to export org-table and calculations as an elisp function. I was thinking I can use some cells as variables to calculate rest of the table. Table can be as complicated as possible Function shall return as value another table Procedure shall be: 1) get a table like variable, 2) chan

Re: [O] Converting tags to TODO states

2019-04-16 Thread Bernt Hansen
garj...@garjola.net writes: > Hi, > > For my GTD implementation with org-mode, I have been using the :next: > tag for my next actions. I would like now to use a "NEXT" TODO keyword, > which means that I need to convert all :next: tags with "TODO" headlines > into "NEXT" headlines without the :next