Julien Cubizolles writes:
> It's weird, both variables (org-link-abbrev-alist and
> org-link-abbrev-alist-local) are nil even though there is a #+LINK: line
> in the file.
Just a late closing message: I tried again today and everything is
working as it should.
Julien.
Nick Dokos writes:
> It works fine here. The relevant function is org-link-expand-abbrev and
> it depends on the variables org-link-abbrev-alist and
> org-link-abbrev-alist-local. The latter gets initialized from the
> former and any #+LINK lines in the buffer are added on to it. In my
> case,
Julien Cubizolles writes:
> Darlan Cavalcante Moreira writes:
>
>> I don't think you can change the behavior of a link type to take into
>> account somethink similar to graphicspath, but you can easily define
>> custom link types: For instance, put this in your org-file
>> #+LINK: fig file:my_fi
Darlan Cavalcante Moreira writes:
> I don't think you can change the behavior of a link type to take into
> account somethink similar to graphicspath, but you can easily define
> custom link types: For instance, put this in your org-file
> #+LINK: fig file:my_figure_path/%s
>
> Then you will be a
Darlan Cavalcante Moreira writes:
> I don't think you can change the behavior of a link type to take into
> account somethink similar to graphicspath, but you can easily define
> custom link types: For instance, put this in your org-file
> #+LINK: fig file:my_figure_path/%s
>
> Then you will be a
I don't think you can change the behavior of a link type to take into
account somethink similar to graphicspath, but you can easily define
custom link types: For instance, put this in your org-file
--8<---cut here---start->8---
#+LINK: fig file:my_figure_path/%s
Julien Cubizolles writes:
> Nick Dokos writes:
>
>> Julien Cubizolles writes:
>>
>>
>>> * in LaTeX you can use \graphicspath to define the directories in which
>>> to look for picture files. Does org mode offer the same possibility ?
>>>
>>
>> No special mechanism afaik, but there is a genera
Nick Dokos writes:
> Julien Cubizolles writes:
>
>
>> * in LaTeX you can use \graphicspath to define the directories in which
>> to look for picture files. Does org mode offer the same possibility ?
>>
>
> No special mechanism afaik, but there is a general one. Did you try
> adding something
Hello,
Nick Dokos writes:
> While we are talking about cosmetic whitespace issues, let me also point
> out that the default beamer class in ox-beamer contains unnecessary
> indentation. Clearly, it's there to make the lisp code look prettier but
> it makes the resulting latex code uglier. Should
Hello,
Julien Cubizolles writes:
> * What's the difference between BEAMER_ENV and BEAMER_env ?
Properties are case insensitive. Therefore there is none.
> * What is the best way to generate
> \only<2-3>{Some text of picture} without creating a new heading ?
You can use export snippets:
@
Julien Cubizolles writes:
> Nick Dokos writes:
>
>> Julien Cubizolles writes:
>>
>>> ...
>>> * All the headers I add end up on the same line when I define them like
>>> in the following (even with an empty line).
>>>
>>> #+LATEX_HEADER_EXTRA: \institute{My Institure}
>>>
>>> #+LATEX_HEAD
Julien Cubizolles writes:
> * in LaTeX you can use \graphicspath to define the directories in which
> to look for picture files. Does org mode offer the same possibility ?
>
No special mechanism afaik, but there is a general one. Did you try
adding something like
#+LATEX_HEADER: \graphicspa
Nick Dokos writes:
> Julien Cubizolles writes:
>
>> ...
>> * All the headers I add end up on the same line when I define them like
>> in the following (even with an empty line).
>>
>> #+LATEX_HEADER_EXTRA: \institute{My Institure}
>>
>> #+LATEX_HEADER:\usepackage{mypackage}
>>
>> The LaT
Julien Cubizolles writes:
> ...
> * All the headers I add end up on the same line when I define them like
> in the following (even with an empty line).
>
> #+LATEX_HEADER_EXTRA: \institute{My Institure}
>
> #+LATEX_HEADER:\usepackage{mypackage}
>
> The LaTeX file produced is not very read
I'm trying to switch all my LaTeX needs to orgmode but I'm still
confused by several little things I could not understand in the
manual. I'm not sure what the policy is on the mailing-list, let me know
if it's best to split this message into several ones.
* What's the difference between BEAMER_ENV
15 matches
Mail list logo
