Hi Nick.
[...]
>> Excuse me if this sounds almost philosophical, but in which situation an
>> indirect buffer may be better that just focusing on the same (original)
>> buffer? For example, when you are toying with potentially big
>> modifications and don't want to replace the original? Is it
Hi Adam. Porter writes:
>> Excuse me if this sounds almost philosophical, but in which situation an
>> indirect buffer may be better that just focusing on the same (original)
>> buffer? [...]
> [...]
> So by jumping to an entry in an indirect buffer, I see only that entry,
Eduardo Mercovich mercovich.net> writes:
> Excuse me if this sounds almost philosophical, but in which situation an
> indirect buffer may be better that just focusing on the same (original)
> buffer? For example, when you are toying with potentially big
> modifications and don't want to replace
Eduardo Mercovich writes:
> Hi Adam.
>
>>> Also less known that it deserves, for focusing I do use narrowing a
>>> lot: [...]
>
>> Yeah, that's basically what tree-to-indirect does, it makes an indirect
>> buffer and then narrows it. So you can widen the indirect buffer
Hi Adam.
>> Also less known that it deserves, for focusing I do use narrowing a
>> lot: [...]
> Yeah, that's basically what tree-to-indirect does, it makes an indirect
> buffer and then narrows it. So you can widen the indirect buffer and get
> another view of the whole buffer. [...]
Excuse me
Eduardo Mercovich mercovich.net> writes:
> Also less known that it deserves, for focusing I do use narrowing a lot:
Yeah, that's basically what tree-to-indirect does, it makes an indirect
buffer and then narrows it. So you can widen the indirect buffer and get
another view of the whole buffer.
Hi Adam.
> Just a note, you mentioned that you find the folding very useful, so you
> might want to try out the org-tree-to-indirect-buffer command. It's very
> helpful when you're working on a large Org file and only want to work on
> certain parts of it. [...]
I didn't knew it, thank you. :)
Hi Eduardo,
Just a note, you mentioned that you find the folding very useful, so you
might want to try out the org-tree-to-indirect-buffer command. It's very
helpful when you're working on a large Org file and only want to work on
certain parts of it. I don't see it mentioned often, so I'm not
Hi Eric.
>> This linking capacity is great and I'm using it a lot.
>> The only detail remaining here that I'm still searching is how to
>> include the table/figure # also with the link. This is because if
>> someone prints the report, the link becomes unusable without a number.
> Well, if you
On Thursday, 31 Mar 2016 at 21:39, Eduardo Mercovich wrote:
[...]
> This linking capacity is great and I'm using it a lot.
>
> The only detail remaining here that I'm still searching is how to
> include the table/figure # also with the link. This is because if
> someone prints the report, the
Hi Christian.
>> ... place the abstract and #+LATEX: commands for frontmatter before the
>> first exported headline, e.g.,
>> #+BEGIN_abstract
>> [Abstract here]
>> #+END_abstract
> Originally my fault for pointing out that this was possible (for latex
> and html backends, anyway) without any
Aloha Tom.
>> I'm using org-mode as a writer and it is simply fantastic. One of the
>> things I enjoy more is the folding. [...]
>> However, I don't know how to integrate that with some semantic markup
>> and the latex exporter at the same time (BTW, org+latex=awesomness!).
>> I'll use the
Eduardo Mercovich writes:
>
> ... place the abstract and #+LATEX: commands for frontmatter before the
> first exported headline, e.g.,
> #+BEGIN_abstract
> [Abstract here]
> #+END_abstract
Originally my fault for pointing out that this was possible (for latex
and html backends, anyway) without
Aloha Eduardo,
You might find Aaron Ecay's ox-extra.el in contrib useful. It defines
an :ignore: tag that instructs the exporter to ignore the headline it
tags, but still export the text, etc. under the headline.
So,
,
| * Abstract :ignore:
|
Dear all.
I'm using org-mode as a writer and it is simply fantastic. One of the
things I enjoy more is the folding. A huge report like the one I'm
working on seems sooo easy... ;)
However, I don't know how to integrate that with some semantic markup
and the latex exporter at the same time (BTW,
15 matches
Mail list logo