Giovanni Moretti writes:
> There's something weird with headings that can cause unfolding to fail.
> Headings can
> be folded with TAB refuse to unfold - they need Shift-TAB to see the
> contents. This
> is scary as it looks like content has been accidentally deleted whereas it's
> really
>
There's something weird with headings that can cause unfolding to fail. Headings can
be folded with TAB refuse to unfold - they need Shift-TAB to see the contents. This
is scary as it looks like content has been accidentally deleted whereas it's really
just hidden.
The TAB-cycling worked as ex
a little more information in case it is useful:
in emacs25 -Q with recent maint, this code fails to export; it errors
if there is an org-id link anywhere in the tree.
(org-export-as 'html 'subtree nil 'body-only nil)
the same bug arises with ascii export.
it seems like a bug that a link shoul
Hello,
ed...@openmail.cc writes:
> My comment for today is that I have something like this:
>
> this-file.org
> ..
> * Fancy header 1
>
> #+NAME: blk1
> #+begin_src python
>
>import numpy as np #+end_src
>
> ** Fancy subheader 2
>
> Res 1
>
> #+include: "this-file.
>>> "ESF" == Eric S Fraga writes:
> On Tuesday, 13 Oct 2020 at 14:56, Uwe Brauer wrote:
> "DZ" == Diego Zamboni writes:
>>> #+begin_src octave :exports results :results output raw
>>
>> That's it. That solves it, thanks so my function is not necessary. Good
>> to know
> The problem with =r
I was recently working with `org-refile` and wanted to use a custom
target. There is the `rfloc` argument which is documented as:
> RFLOC can be a refile location obtained in a different way.
There's no documentation as to how `rfloc` should be structured. To
figure that out one has to read thr
On Tuesday, 13 Oct 2020 at 14:56, Uwe Brauer wrote:
"DZ" == Diego Zamboni writes:
>> #+begin_src octave :exports results :results output raw
>
> That's it. That solves it, thanks so my function is not necessary. Good
> to know
The problem with =raw= is that you may find you have to manually
>>> "DZ" == Diego Zamboni writes:
Hi Diego
> Uwe,
> In my testing (using octave since I don't have matlab, but I hope it's
> similar), using = :exports none :results output raw= seems to produce the
> desired output:
> #+begin_src octave :exports results :results output raw
That's it. That so
Uwe,
In my testing (using octave since I don't have matlab, but I hope it's
similar), using = :exports none :results output raw= seems to produce the
desired output:
#+begin_src octave :exports results :results output raw
close all
N = 3; % number of chebyshev nodes
n = 1; % polytropic index
iter
>>> "AB" == Arne Babenhauserheide writes:
> Uwe Brauer writes:
>> That did not work: I tried
>> #+begin_src matlab :results output
>>
>> But when I exported the org file to latex, the matlab code was also
>> exported. Strange
> Do you use :exports results?
> :results output switches to sh
>>> "ESF" == Eric S Fraga writes:
> On Tuesday, 13 Oct 2020 at 09:26, Uwe Brauer wrote:
>> That did not work: I tried
>> #+begin_src matlab :results output
>> But when I exported the org file to latex, the matlab code was also
>> exported. Strange
> If you want the output only, you also need
On Tuesday, 13 Oct 2020 at 11:01, Dr. Arne Babenhauserheide wrote:
> Don’t you get a "do you want to revert file" warning then?
You might not be visiting that file and/or you might have auto-revert
mode set (which I do as I like living dangerously ;-)).
--
: Eric S Fraga via Emacs 28.0.50, Org r
Eric S Fraga writes:
> On Tuesday, 13 Oct 2020 at 09:27, Greg Minshall wrote:
>> yes, but. the first time i 'C-c C-v t' in the base file onto a
>> changed-but-uncommitted tangled file, even git will provide me no
>> succor.
>
> True. :-(
Don’t you get a "do you want to revert file" warning th
Uwe Brauer writes:
> That did not work: I tried
> #+begin_src matlab :results output
>
> But when I exported the org file to latex, the matlab code was also
> exported. Strange
Do you use :exports results?
:results output switches to show what is printed to stdout
Best wishes,
Arne
--
Unp
On Tuesday, 13 Oct 2020 at 09:26, Uwe Brauer wrote:
> That did not work: I tried
> #+begin_src matlab :results output
> But when I exported the org file to latex, the matlab code was also
> exported. Strange
If you want the output only, you also need to add ":exports results".
--
: Eric S Fra
> That did not work: I tried
> #+begin_src matlab :results output
> But when I exported the org file to latex, the matlab code was also
> exported. Strange
The only solution I am aware is to have something like this
(defun my-latex-filter-src-blocks (text backend info)
"Remove source
On Tuesday, 13 Oct 2020 at 09:27, Greg Minshall wrote:
> yes, but. the first time i 'C-c C-v t' in the base file onto a
> changed-but-uncommitted tangled file, even git will provide me no
> succor.
True. :-(
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4-57-g8402c4
On Monday, 12 Oct 2020 at 20:52, Dr. Arne Babenhauserheide wrote:
> Do you use org-mode to document stuff after you wrote it?
Before, during, and after!
> I often use it to start small tools that I need right now — for example
I do as well. I have little snippets of code and data throughout my
Hi Diego
Thanks for the quick answer
> Hi Uwe,
> 1. Is there any equivalent to org-update-all-dblocks for the source
> I think you want org-babel-execute-buffer:
Right, thanks!!!
> Documentation
> Call org-babel-execute-src-block on every source block in
> the current buffer.
> 2.
Hi,
On Mon, Oct 12 2020, Eric S Fraga wrote:
> On Monday, 12 Oct 2020 at 10:22, Christian Moe wrote:
>> I think I was thinking about adding mode flags for unit computations,
>> like in the imagined example above (`$3=$2+$1;u'), similar to what has
>> been done for duration computations.
>
> Thi
Hi Uwe,
1. Is there any equivalent to org-update-all-dblocks for the source
> blocks?
>
I think you want org-babel-execute-buffer:
Documentation
Call org-babel-execute-src-block on every source block in
the current buffer.
2. I want to export the org file to latex, in the current set
21 matches
Mail list logo