Thanks all for the ideas, i will try them over the next few days
best
Z
On Tue, Dec 27, 2016 at 12:36 PM, Marcin Borkowski wrote:
> ש
> > On Thursday, 22 Dec 2016 at 13:01, Xebar Saram wrote:
> >> Hi all
> >>
> >> i recently had some projects where i would define the overall project
> >> as a
shripad sinari writes:
> Thanks for the suggestion. The proposed solution does not work since
> the recent org versions generate their own labels and the label
> value cannot be predetermined.
C-h v org-latex-prefer-user-labels RET
--
Nick
Thanks John,
Setting the variable org-latex-prefer-user-labels to "t" solves the issue.
Regards,
Shripad
Tucson, AZ
On Tue, Dec 27, 2016 at 11:42 AM, John Kitchin
wrote:
> Set a variable like org-latex-prefer-user-labels to t. I am away from my
> computer to look up the actual name but it is s
Hi Charles,
I think I found precisely the issue I'm having.
When I use your example, and adjust it slightly:
#+NAME: block-1
#+BEGIN_SRC shell :var x="X"
echo ">>>" $x "<<<"
#+END_SRC
#+BEGIN_SRC shell :var c="test" y=block-1(c)
echo $y
#+END_SRC
#+RESULTS:
Hello John,
Thanks for the suggestion. The proposed solution does not work since the
recent org versions generate their own labels and the label value cannot be
predetermined. See the LaTeX code generated by the above example with your
suggestion included:
x-x
\section{Sec
On Tue, 27 Dec 2016, daimrod wrote:
Hi,
I've found what I think is a bug in orgmode parsing.
When the following file is parsed :
* Test
#+BEGIN_SRC emacs-lisp :exports results :results raw drawer
(format "- Test2")
#+END_SRC
#+RESULTS:
:RESULTS:
- Test2
:END:
[snip]
That is, it generate
Hello,
daimrod writes:
> #+RESULTS:
> :RESULTS:
> * Test2
> :END:
>
[...]
> (paragraph
> (:begin 98 :end 119 :contents-begin 109 :contents-end 119 :post-blank 0
> :post-affiliated 109 :results
> (\"\")
> :parent #2)
> #(\":RESULTS:\\n\" 0 10
>(:parent #3)))
>
> That is,
On Tue, 27 Dec 2016, Zack Piper wrote:
Hi all,
Hopefully the below can explain better:
[deleted]
This is a workable idiom. C-c C-c on the second block produces the
output shown.
#+NAME: block-1
#+BEGIN_SRC shell :var x="X"
echo ">>>" $x "<<<"
#+END_SRC
#+BEGIN_SRC shell :var y=block-1(
Can you pass \ref{fig:image} in? I think that is what you would do in
Latex.
On Mon, Dec 26, 2016 at 7:00 PM shripad sinari
wrote:
> Hello all,
> I would like to know if there is a way to pass a reference for a figure to
> a source block as in the following example:
>
> x---x---
>
>
inf-ruby (melpa stable) has recently been updated to v2.5. The library has
been significantly re-factored, and `run-ruby` no longer accepts `nil` has
the command name. The following patch updates ob-ruby so that it continues
to work w/ inf-ruby v2.5. It should still (untested) work with the previou
Dushyant Juneja writes:
> Hi all,
>
> I was trying to wrap ox-latex in a use-package configuration. My
> use-package statement is super simple:
>
> (use-package ox-latex
> :defer t)
ox-latex is part of org, which ships with Emacs. You should be able to
just use:
,
| (require 'ox-latex)
`--
Hi,
I've found what I think is a bug in orgmode parsing.
When the following file is parsed :
* Test
#+BEGIN_SRC emacs-lisp :exports results :results raw drawer
(format "- Test2")
#+END_SRC
#+RESULTS:
:RESULTS:
- Test2
:END:
The truncated result of `org-element-parse-buffer' is :
(src-block
(:l
Hi all,
Hopefully the below can explain better:
#+NAME: abc
#+BEGIN_SRC shell :noweb yes :var a="b" :results output
echo <>
1
EOF
#+END_SRC
#+RESULTS: def
:
Pressing `C-c C-c' on the second block returns:
org-babel-ref-resolve: Reference ‘c’ not found in this
Hi all,
I was trying to wrap ox-latex in a use-package configuration. My
use-package statement is super simple:
(use-package ox-latex
:defer t)
However, emacs cribs on this at startup as follows:
package-compute-transaction: Package ‘ox-latex-’ is unavailable
Any ideas of what could be going w
On 2016-12-23, at 12:47, Eric S Fraga wrote:
> On Thursday, 22 Dec 2016 at 13:01, Xebar Saram wrote:
>> Hi all
>>
>> i recently had some projects where i would define the overall project
>> as a TODO and then add some more sub headers with TODOS. the problem
>> is that i dont want to see all the
Hi folks,
This fixes bug where you sometimes can't immediately see tags that were
just set. And to reveal them you need to go through global visibility
cycle.
Best,
Alexey
>From d81f5be08c83fb31adfd36dc97dcf92268c898ed Mon Sep 17 00:00:00 2001
From: Alexey Lebedeff
Date: Sun, 25 Dec 2016 13:24
16 matches
Mail list logo