Hi John,
John Hendy wrote:
> Something's still not right. This:
> --
> * Top headline
> Some notes about this stuff to see how this custom export works! Some
> notes about
> this stuff to see how this custom export works!
>
> *** An inline section
> Here's some text inside an inlin
2011/4/7 John Hendy :
> I can't have something set up right. I was doubtful that I was going
> this source block thing right when Eric posted his suggestion for
> notes in code blocks. So, I pasted this into my org-mode file and
> evaluated it. Is that not what I'm supposed to do? At the top of the
2011/4/7 Sébastien Vauban :
> Hi Jeff,
>
>
> This is my current config for nice styling:
>
> #+begin_src emacs-lisp
>
> #+end_src
>
> Customize to your own taste (and report back!)...
I can't have something set up right. I was doubtful that I was going
this source block thing right when Eric po
Hello,
Jeff Horn writes:
> AFAIK, "inline-tasks" don't have to have headlines. For instance:
>
> ,[ org-inlinetask example ]
> | *** NOTES
> | Test note with a headline word.
> | *** END
> |
> | ***
> | Test note with blank headline.
> | *** EN
Hi Jeff,
Jeff Horn wrote:
> No problem. As a note for others searching on this, I'll just go ahead and
> re-iterate that if you don't want a particular inline-task to be printed,
> just add the :noexport: tag to the headline.
Better to say it twice!
> Sebastian, or others: One is able to add pro
On Tue, Apr 5, 2011 at 11:14 PM, Samuel Wales wrote:
> I agree this is interesting.
>
> Another option is an annotation mechanism with unbreakable
> bidirectional links -- ID markers work for this. You can stick the
> markers anywhere.
Heck yes -- this sounds *awesome*. Could you give an example
Hi Jeff,
Jeff Horn wrote:
> Have you tried using org-inline-task without a TODO keyword? These
> super-deep "headlines" aren't treated as headlines, so they don't
> break doc structure, but they are foldable, and unlike COMMENT keyword
> headlines, they're printable.
I second this approach, and a
I agree this is interesting.
Another option is an annotation mechanism with unbreakable
bidirectional links -- ID markers work for this. You can stick the
markers anywhere.
If the thing to be annotated is read-only, I have other ideas.
Samuel
--
The Kafka Pandemic:
http://thekafkapandemic.
Jeff Horn wrote
> Have you tried using org-inline-task without a TODO keyword? These super-deep
> "headlines" aren't
> treated as headlines, so they don't break doc structure, but they are
> foldable, and unlike COMMENT keyword headlines,
> they're printable. The only problem I've run into is hav
