On this page we have this statement
-
15.11 Context Dependent Documentation
C-c C-x C-i in an Org file tries to open a suitable section of the Org info
documentation
I believe that this should be C-c C-x I
org-info-find-node
--
=
Ian Garmaise
Consultant
Phorix Solutions Group
ia...@
Hello,
Felix Wiemuth writes:
> Start with an empty buffer in org-mode and add the following content:
>
> * A
> - L1
> - L2
> * B
>
> If we execute `org-list-make-subtree` on any position within the list (the
> two lines with L1/L2), we get
>
> * A
> ** L1
> ** L2* B
>
> So the conversion "eats"
Hello,
Ernesto Alfonso writes:
> The following URLs fail to get inlined as an html image:
>
> https://travis-ci.org/erjoalgo/emacs-buttons.svg?branch=master
> https://travis-ci.org/erjoalgo/emacs-buttons.png?branch=master
>
> But this one does:
>
> https://travis-ci.org/erjoalgo/emacs-buttons.pn
* lisp/ob-emacs-lisp.el (org-babel-execute:emacs-lisp,
org-babel-emacs-lisp-lexical): Factor out the conversion of the
:lexical source block argument to a form that is appropriate for
`lexical-binding' and the LEXICAL argument to `eval'.
* lisp/ob-emacs-lisp.el (org-babel-edit-prep:emacs-lis
David Masterson writes:
> Is there a documented requirement of the order of things in a Org
> outline? For instance, do these things have to come directly after the
> headline and, if so, in what order? Will Org get confused otherwise?
> * PROPERTY drawer
> * Timestamp
> * SCHEDULED and DEADLIN