> On Jan 16, 2022, at 7:13 AM, Eric S Fraga wrote:
>
> On Sunday, 16 Jan 2022 at 00:36, Timothy wrote:
>>Hmm. Not sure about this. Keystroke wise we’re comparing $$
>>to \(. The latter can be completed by smartparens, but since
>>single dollars are reasonable Org conte
> On Mar 21, 2021, at 1:46 PM, Greg Minshall wrote:
>
> hi. i occasionally want to switch from the org package to a git
> version, then back again. and, i want to avoid the dread "mixed
> installation".
>
> i'm wondering is there a way people do this other than simply
> installing/deleting
Fraga, Eric writes:
> On Monday, 10 Feb 2020 at 23:20, Anthony Cowley wrote:
>> I am having trouble understanding how short captions are supposed to
>> work. Consider this org document:
>
> [...]
>
>> The first matches my expectations. The second is an exampl
I am having trouble understanding how short captions are supposed to work.
Consider this org document:
#+begin_src org
,#+title: Short Caption Test
,#+author: Org User
,#+label: table1
,#+caption[This is table1]: And here go on at length in a longer caption.
| Name | Favorite Number |
|--+--
Nicolas Goaziou writes:
> Hello,
>
> Anthony Cowley writes:
>
>> When I hit C-c C-c on a latex src block with a :file header,
>> I ultimately get an error from org-compile-file that the expected
>> output file in a temp directory was not produced. However, the file
Hello,
When I hit C-c C-c on a latex src block with a :file header, I ultimately get
an error from org-compile-file that the expected output file in a temp
directory was not produced. However, the file is produced in the current
directory.
For instance, evaluating the src block in the followin
Lawrence Bottorff writes:
> I'm guessing Haskell and org-mode Babel aren't really a great match? After
> installing haskell-mode, I've tried
>
> #+begin_src haskell
> doubleMe x = x + x
> #+end_src
>
> which isn't working . . . because it isn't allowed in the ghci?
>
> #+begin_src haskell
> let d
John Kitchin writes:
> I was looking into ob-ipython as a replacement for regular
> org-babel-python because it seems to be better at sessions. Also, you
> can use other kernels with it!
>
> For example:
>
> #+BEGIN_SRC ipython :session hy :results output :kernel hy
> (print "hello world")
> (imp
On Tuesday, May 24, 2016, Ista Zahn wrote:
> On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier
> > wrote:
>
> It this change is not going to be reversed than the doc string for
> org-export-babel-evaluate needs to be updated, and something should go
> in the NEWS file warning people (like me) wh
Charles C. Berry writes:
> On Wed, 9 Mar 2016, Anthony Cowley wrote:
>
>>
>> If I have org-export-babel-evaluate set to nil, source blocks are not
>> evaluated on export. However, if a source block has a :var header
>> argument that calls another source bloc
If I have org-export-babel-evaluate set to nil, source blocks are not evaluated
on export. However, if a source block has a :var header argument that calls
another source block, I am prompted if the callee should be evaluated.
Given that the caller is not to be evaluated, I'm not sure I see a r
Rasmus writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> Rasmus writes:
>>
>>> Thanks! I have added a TODO to my agenda regarding checking other
>>> backends, but I'd not hold grudges against anyone who beats me to it.
>>
>> I took care of ox-groff, ox-man and ox-texinfo.
>
> Thanks.
>
>> I
Rasmus writes:
> Nicolas Goaziou writes:
>
Eventually, I think at least ox-texinfo.el, ox-man.el and ox-groff.el
need a similar trick.
>>>
>>> Perhaps there should be an error check in ox-odt as well? I guess the
>>> only thing that could happen is that the zip/odt can’t be written, w
> On Jan 16, 2016, at 10:17 AM, Rasmus wrote:
>
> Hi Anthony and Nicolas,
>
> Anthony Cowley writes:
>
>> Thanks for taking a look, Rasmus! The bug is in Org, not Emacs. One
>> may perhaps assume the invariant that successive calls to
>> `current-time` wi
> On Jan 15, 2016, at 7:13 AM, Rasmus wrote:
>
> Hi Anthony,
>
> Thanks for raising this issue.
>
> Anthony Cowley writes:
>
>> I’ve had some trouble with toggling latex fragment previews in a
>> document on OS X. It would sometimes work, sometimes not
I’ve had some trouble with toggling latex fragment previews in a document on OS
X. It would sometimes work, sometimes not, so I could just try a few times
until it worked and get on with things. Looking into it more, the problem seems
to be with the HFS+ filesystem’s second granularity on file t
16 matches
Mail list logo
