> On Dec 24, 2017, at 3:16 PM, Nicolas Goaziou wrote:
>
> I fixed it in maint.
>
Yes, indeed. Thank you!
Chuck
Hi,
On Sat, Dec 23, 2017 at 11:12 PM, Kaushal Modi wrote:
> The only minor issue is that it loads the whole manual as a single HTML
> page, so it takes a while to load. Do you know if there's a way to set it up
> so that it shows a single page per node as orgmode.org does?
I've looked around the
2017-12-24 16:05 GMT+01:00 Nicolas Goaziou :
> Contents mean "data in Org syntax". There are no such contents in source
> blocks. Therefore, the parser does not provide :contents-begin
> and :contents-end for them.
Thanks for your quick response As I understand from your reply,
:contents-begin/end
Hello,
"Berry, Charles" writes:
> I can execute this src block with no problems:
>
> #+begin_src emacs-lisp :wrap src latex :exports results
> "some-text"
> #+end_src
>
>
> and it will produce the expected result:
>
> #+RESULTS:
>
> #+begin_src latex
> some-text
> #+end_src
>
> and if I then exp
I can execute this src block with no problems:
#+begin_src emacs-lisp :wrap src latex :exports results
"some-text"
#+end_src
and it will produce the expected result:
#+RESULTS:
#+begin_src latex
some-text
#+end_src
and if I then export as (say) `C-c C-e C-b l L n y', I get just `some-text' in
Hi all,
Org 9.1.5, a bugfix release, is out.
Many thanks to Nicolas and all the contributors.
Merry chrismas and happy hacking to everyone!
--
Bastien
Hello stardiviner,
I actually don't mind using absoute paths in my org files, and I think that
using something like that header var and expansion is more trouble than it
is worth.
If I wanted to move the org file to another folder, I would just do a
*replace-string* of the old path with the new pa
> Here is a quick test:
>
> * Test tangle will auto expand and substitute :var
>
> #+begin_src js :tangle kk.js
> console.log("hello, world!");
> #+end_src
>
> #+begin_src js :var name="chris" :tangle require-kk.js
> // require("kk.js");
> console.log("Hi, ", name);
> #+end_src
>
> #+RESULTS:
> : H
Hello,
Rasmus writes:
> The first patches adds string keys to snippet expansion. For tempo, this
> is straight-forward.
>
> For the interactive prompt there’s an org-mks interface. It limited to at
> most two keys (this shouldn’t be much of a limitation TBH). So for
> instance if the key is "
Hello,
"Somelauw ." writes:
> Here is a simple patch that makes it possible to find the inner
> contents of a src-code block.
Contents mean "data in Org syntax". There are no such contents in source
blocks. Therefore, the parser does not provide :contents-begin
and :contents-end for them.
HTH,
Here is a simple patch that makes it possible to find the inner
contents of a src-code block.
In the function called "defun org-element-src-block-parser (limit affiliated)":
- First find contents-begin and contents-end using the following:
#+BEGIN_SRC emacs-lisp
(contents-begin (save-e
11 matches
Mail list logo
