Hi Eric,
Eric Fraga wrote:
> Sebastien Vauban writes:
>> I want to customize a bit the layout of a table, using the =align= parameter
>> as
>> explained on http://orgmode.org/manual/Tables-in-LaTeX-export.html.
>>
>> That works well for the first two common usages (see ECM) but not with
>> @-exp
Sebastien Vauban writes:
> Hello,
>
> I want to customize a bit the layout of a table, using the =align= parameter
> as
> explained on http://orgmode.org/manual/Tables-in-LaTeX-export.html.
>
> That works well for the first two common usages (see ECM) but not with
> @-expressions (see, for examp
"Sebastien Vauban"
writes:
> Regarding the new exporter (which I can't test -- I have problems when
> activating it, still have to look why with emacs -Q and dichotomic search...),
> IIRC Beamer is not supported (yet?).
Yes, it is not.
--
Bastien
Hello,
I want to customize a bit the layout of a table, using the =align= parameter as
explained on http://orgmode.org/manual/Tables-in-LaTeX-export.html.
That works well for the first two common usages (see ECM) but not with
@-expressions (see, for example, on
https://en.wikibooks.org/wiki/LaTeX
On 4.6.2012, at 08:14, Nick Dokos wrote:
> Sebastien Vauban wrote:
>
>> Hello,
>>
>> I'm trying to get numbered equations in Beamer, hence using the
>> begin_equation
>> block, but the formula is not correctly translated to LaTeX, and I have no
>> clue why...
>>
>> Here an ECM:
>> ...
>> -
Hey Seb,
On Mon, Jun 4, 2012 at 9:41 AM, Sebastien Vauban
wrote:
> Hi Nick,
>
> Nick Dokos wrote:
>> Sebastien Vauban wrote:
>>
>>> I'm trying to get numbered equations in Beamer, hence using the
>>> begin_equation
>>> block, but the formula is not correctly translated to LaTeX, and I have no
>
Hi Nick,
Nick Dokos wrote:
> Sebastien Vauban wrote:
>
>> I'm trying to get numbered equations in Beamer, hence using the
>> begin_equation
>> block, but the formula is not correctly translated to LaTeX, and I have no
>> clue why...
>>
>> Here an ECM:
>> ...
>> - These should be numbered:
>>
Hi Nick,
Nick Dokos wrote:
> Sebastien Vauban wrote:
>>
>> I'm trying to get numbered equations in Beamer, hence using the
>> begin_equation block, but the formula is not correctly translated to LaTeX,
>> and I have no clue why...
>
> Confirmed (except that I have to comment out hyperref in orde
Sebastien Vauban wrote:
> Hello,
>
> I'm trying to get numbered equations in Beamer, hence using the begin_equation
> block, but the formula is not correctly translated to LaTeX, and I have no
> clue why...
>
Confirmed (except that I have to comment out hyperref in order to
process the latex
Sebastien Vauban wrote:
> Hello,
>
> I'm trying to get numbered equations in Beamer, hence using the begin_equation
> block, but the formula is not correctly translated to LaTeX, and I have no
> clue why...
>
> Here an ECM:
> ...
> - These should be numbered:
>
> #+begin_equation
> \frac{1}{\
Hello,
I'm trying to get numbered equations in Beamer, hence using the begin_equation
block, but the formula is not correctly translated to LaTeX, and I have no
clue why...
Here an ECM:
--8<---cut here---start->8---
#+TITLE: ECM Equations
#+DATE: 2012
Jonathan BISSON gmail.com> writes:
>
> Hello,
>
> When I try to export my org file using latest git (1 month ago version
> got this problem too) to a tex file, I have problems with footnotes.
>
> * Orgfile
>
> Hello [fn:foo: bar]
>
> -> Latex Output
>
> Hello \footnote{bar
> }
>
> So I got
Hello,
When I try to export my org file using latest git (1 month ago version
got this problem too) to a tex file, I have problems with footnotes.
* Orgfile
Hello [fn:foo: bar]
-> Latex Output
Hello \footnote{bar
}
So I got a newline after bar, which causes big troubles in tables as the
On Wednesday, April 25, 2012, Achim Gratz wrote:
> Mike McLean writes:
> > So if I do not copy/move/link code from contrib/lisp/ to lisp/ I could
> > still be using old contrib code from my Emacs system directories?
>
> There is no contrib code in Emacs unless you yourself installed it
> there. T
Mike McLean writes:
> So if I do not copy/move/link code from contrib/lisp/ to lisp/ I could
> still be using old contrib code from my Emacs system directories?
There is no contrib code in Emacs unless you yourself installed it
there. The advantage of copying to lisp is that you don't need to add
On Wednesday, April 25, 2012, Achim Gratz wrote:
>
> Here's my chance to upsell the new build system to you: to use code from
> contrib, just link or copy it into lisp, then do whatever you let make
> normally do. You usually don't need any extra requires since the
> autoload cookies do their mag
Thomas S. Dye writes:
> On a practical note, using the new exporter is easy. I have these
> two lines (along with other configuration) in an Org-babel code block
> that I use to setup Org-mode:
>
> (require 'org-export)
> (require 'org-e-latex)
Here's my chance to upsell the new build sys
Jambunathan K writes:
> Karl Voit writes:
>
>> * Thomas S. Dye wrote:
>>> Karl Voit writes:
>>>
Maybe it might be a cool idea to work on this template together and
publish it on Worg? I can imagine that several people are trying to
meet those ACM template requirements ...
>>>
>>
Karl Voit writes:
> * Thomas S. Dye wrote:
>> Karl Voit writes:
>>
>>> Maybe it might be a cool idea to work on this template together and
>>> publish it on Worg? I can imagine that several people are trying to
>>> meet those ACM template requirements ...
>>
>> This seems like a good idea. Wou
* Thomas S. Dye wrote:
> Karl Voit writes:
>
>> Maybe it might be a cool idea to work on this template together and
>> publish it on Worg? I can imagine that several people are trying to
>> meet those ACM template requirements ...
>
> This seems like a good idea. Would it be possible to target N
Karl Voit writes:
> Hi!
>
> For a short demo at a conference I tried to configure Org-mode LaTeX
> export to generate a tex file which complies to the ACM SIG
> Proceedings format[1].
>
> The tutorial on [2] is great but unfortunately, I could not achieve
> several things :-(
>
> Maybe it might b
Hi!
For a short demo at a conference I tried to configure Org-mode LaTeX
export to generate a tex file which complies to the ACM SIG
Proceedings format[1].
The tutorial on [2] is great but unfortunately, I could not achieve
several things :-(
Maybe it might be a cool idea to work on this templat
Pedro Silva writes:
> Is it possible to insert text just before \end{document} on export,
> similarly to org-export-html-postamble?
>
> I'd like to do this on a capture target file that contains the following
> at the end:
>
> \bibliography{references}
>
> New capture entries keep getting i
Is it possible to insert text just before \end{document} on export,
similarly to org-export-html-postamble?
I'd like to do this on a capture target file that contains the following
at the end:
\bibliography{references}
New capture entries keep getting inserted below it, which makes the
r
I'm using orgmode version 7.8.06. Right now, whenever an org file is
exported to LaTeX, each heading is assigned an automatic label (e.g.
sec-1). All hyperlinks to the heading will also use this label.
There is a standard orgmode property for assigning custom ID to
headings for hyperlinks: CUSTOM
Achim Gratz wrote:
> Nick Dokos writes:
> >>
> >> Especially as this is a limitation of LaTeX, not the exporter.
> >>
> >> :-)
> >
> > Not true - the following compiles with no problems:
>
> Yes, LaTeX doesn't really enforce it, but it makes the assumption of
> "correct nesting". It's been a
Nick Dokos writes:
>>
>> Especially as this is a limitation of LaTeX, not the exporter.
>>
>> :-)
>
> Not true - the following compiles with no problems:
Yes, LaTeX doesn't really enforce it, but it makes the assumption of
"correct nesting". It's been a few years since I tried something like
y
Achim Gratz wrote:
> Nick Dokos writes:
> > The latex exporter is very rigid about what it will accept: it wants the
> > levels to be in strict sequence. So this has to be chalked down as a
> > fairly deeply ingrained limitation of the exporter. I don't see an easy way
> > to lift it.
>
> Espec
Nick Dokos writes:
> The latex exporter is very rigid about what it will accept: it wants the
> levels to be in strict sequence. So this has to be chalked down as a
> fairly deeply ingrained limitation of the exporter. I don't see an easy way
> to lift it.
Especially as this is a limitation of La
Nick Dokos wrote:
> Richard Stanton wrote:
>
> > Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
> > if you try to skip a header level. For example, to prevent my TODO items
> > being numbered, one method is to make them a lower-level heading, and then
> > make that l
> From: nicholas.do...@hp.com [mailto:nicholas.do...@hp.com]
> Sent: Tuesday, March 20, 2012 12:55 PM
> To: Richard Stanton
> Cc: emacs-orgmode@gnu.org; nicholas.do...@hp.com
> Subject: Re: [O] LaTeX export - can't skip a heading level
>
> Richard Stanton wrote:
&g
Richard Stanton wrote:
> Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
> if you try to skip a header level. For example, to prevent my TODO items
> being numbered, one method is to make them a lower-level heading, and then
> make that level un-numbered.
>
> However,
Using org-mode 7.8.03, I've found that exporting to LaTeX has a tough time
if you try to skip a header level. For example, to prevent my TODO items
being numbered, one method is to make them a lower-level heading, and then
make that level un-numbered.
However, if I try the following:
* To Do List
Ista Zahn wrote:
> Hi all,
>
> I'm having trouble modifying the example at
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
> to highlight R code blocks. The trouble seems to be that org-mode
> identifies R blocks using uppercase R, while pygments looks for
> lowercase r.
>
Ah, perfect! Thank you.
On Fri, Mar 16, 2012 at 5:13 PM, Christophe Pouzat
wrote:
> (add-to-list 'org-export-latex-minted-langs '(R "r"))
Ista Zahn writes:
> Hi all,
>
> I'm having trouble modifying the example at
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
> to highlight R code blocks. The trouble seems to be that org-mode
> identifies R blocks using uppercase R, while pygments looks for
> lowercase r.
>
Hi all,
I'm having trouble modifying the example at
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
to highlight R code blocks. The trouble seems to be that org-mode
identifies R blocks using uppercase R, while pygments looks for
lowercase r.
For example, org exports
\begin{
Daniel Schoepe writes:
> I have the following issue: If I write something like `$n$th' in an org
> file and then export it to LaTeX, it will produce `\$n\$th', whereas I
> would like it to export this as `$n$th'. Is there some way I can disable
> escaping of dollar signs entirely (Leaving it to me
Hi,
I have the following issue: If I write something like `$n$th' in an org
file and then export it to LaTeX, it will produce `\$n\$th', whereas I
would like it to export this as `$n$th'. Is there some way I can disable
escaping of dollar signs entirely (Leaving it to me to escape them, when
I don
Hi Jambunathan,
Jambunathan K writes:
> I think the problem is not with the latex or odt backends as such but in
> the export pre-processor.
Just to make sure: are you suggesting `org-export-preprocess-string'
should normalize comment lines like "^.+#header.*") and move them to
column 0 of the
Michael Bach writes:
> Eric S Fraga writes:
>
>> If so, I suggest you could achieve what you want by using the
>> org-export-* hooks to, for instance, save current position before export
>> and then jump to that position after export? Maybe
>> org-export-first-hook and org-export-latex-final-ho
Eric S Fraga writes:
> If so, I suggest you could achieve what you want by using the
> org-export-* hooks to, for instance, save current position before export
> and then jump to that position after export? Maybe
> org-export-first-hook and org-export-latex-final-hook could be used?
>
Thanks fo
Jambunathan K writes:
> Andreas Leha writes:
>
>> Andreas Leha writes:
>>
>>> "Sebastien Vauban"
>>> writes:
>>>
>>>
Hi Andreas,
Andreas Leha wrote:
> I am experiencing a problem with the latex exporter: #+header: lines
> are visible in the exported file.
>
> Ex
Andreas Leha writes:
> Andreas Leha writes:
>
>> "Sebastien Vauban"
>> writes:
>>
>>
>>> Hi Andreas,
>>>
>>> Andreas Leha wrote:
I am experiencing a problem with the latex exporter: #+header: lines
are visible in the exported file.
Example:
/==
Piotr Kaźmierczak writes:
> Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
>
>> Have you tried exporting a simple file to latex? Perhaps something as simple
>> as:
>>
>> ---
>> * Foo
>> Bar
>> ---
Wiadomość napisana przez Nick Dokos w dniu 17 sty 2012, o godz. 18:00:
> In that case, it seems like your orgmode install is hosed - have you tried
> reinstalling from scratch?
I did, but no luck. There must be something else I'm missing here, but I don't
have time to investigate now.
Thanks f
Piotr Kaźmierczak wrote:
> Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
>
> > Have you tried exporting a simple file to latex? Perhaps something as simple
> > as:
> >
> > ---
> > * Foo
> > Bar
> >
Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
> Have you tried exporting a simple file to latex? Perhaps something as simple
> as:
>
> ---
> * Foo
> Bar
> -
Hi Andreas,
Andreas Leha wrote:
> Andreas Leha writes:
>> "Sebastien Vauban" writes:
>>> Andreas Leha wrote:
I am experiencing a problem with the latex exporter: #+header: lines
are visible in the exported file.
Example:
/
Andreas Leha writes:
> Andreas Leha writes:
>
>> "Sebastien Vauban"
>> writes:
>>
>>
>>> Hi Andreas,
>>>
>>> Andreas Leha wrote:
I am experiencing a problem with the latex exporter: #+header: lines
are visible in the exported file.
Confirmation, exporting to latex. Also happens wit
Andreas Leha writes:
> "Sebastien Vauban"
> writes:
>
>
>> Hi Andreas,
>>
>> Andreas Leha wrote:
>>> I am experiencing a problem with the latex exporter: #+header: lines
>>> are visible in the exported file.
>>>
>>> Example:
>>>
>>> /==\
>>> * tes
"Sebastien Vauban"
writes:
> Hi Andreas,
>
> Andreas Leha wrote:
>> I am experiencing a problem with the latex exporter: #+header: lines
>> are visible in the exported file.
>>
>> Example:
>>
>> /==\
>> * test header tag
Hi Andreas,
Andreas Leha wrote:
> I am experiencing a problem with the latex exporter: #+header: lines
> are visible in the exported file.
>
> Example:
>
> /==\
> * test header tag
> #+caption: foo
Hi all,
I am experiencing a problem with the latex exporter: #+header: lines
are visible in the exported file.
Example:
/==\
* test header tag
#+caption: foo
#+label: fig:fig1
Michael Bach writes:
> Hello everyone,
>
> The way I am now doing LaTeX export is that I have the exported tex
> buffer below the org buffer. When I do an export via `C-c C-e l' the
> .tex buffer gets updated, but point jumps to beginning of buffer instead
> of staying where it was. (How) Can I
Hello everyone,
The way I am now doing LaTeX export is that I have the exported tex
buffer below the org buffer. When I do an export via `C-c C-e l' the
.tex buffer gets updated, but point jumps to beginning of buffer instead
of staying where it was. (How) Can I changed that so point stays near
Piotr Kaźmierczak wrote:
> I have a very strange problem: I can no longer process an org file
> with all my notes to LaTeX. I've been using org-mode this way for some
> time now, and I was always able to get a nice tex file I could later
> process to PDF. Now all I get is a TeX file with absolu
Hi,
I have a very strange problem: I can no longer process an org file with all my
notes to LaTeX. I've been using org-mode this way for some time now, and I was
always able to get a nice tex file I could later process to PDF. Now all I get
is a TeX file with absolutely no new-line symbols (
Carlos Russo writes:
> I suppose this means there are no plans of creating a variable containing
> the markup associated with a date range, right :-p?
Not that I know -- but beware of the conspiracy, as the LaTeX exporter
is currently being rewritten by Nicolas... see org-e-latex.el in the
EXP
Thanks, it seems that
(setq org-export-latex-timestamp-markup "\\printdate{%s}")
does half of the job already.
> Er.. forget this sentence -- perhaps my subconscious is trying
> to tell me there are too many variables in Org now :)
I suppose this means there are no plans of creating a variable
Bastien writes:
>> Is there a way to customize how a date is exported into LaTeX?
>
> You cannot do this right now.
Er.. forget this sentence -- perhaps my subconscious is trying
to tell me there are too many variables in Org now :)
--
Bastien
Hi Carlos,
Carlos Russo writes:
> Is there a way to customize how a date is exported into LaTeX?
You cannot do this right now.
See these variables:
org-export-latex-timestamp-markup:
"A printf format string to be applied to time stamps."
org-export-latex-timestamp-inactive-markup:
"A pri
Hello,
Is there a way to customize how a date is exported into LaTeX?
Google couldn't help me on this.
For example, if an org file contains a timestamp <2012-01-09 Mon>, I'm
getting an italicized version in the .tex file, i.e. \textit{2012-01-09
Mon}.
I would like to be able to change how dates
> Read Chapter 14 of the Org-mode manual. And go to
> http://orgmode.org/worg/ and search with the keyword "literate".
Thanks, I've read these already, they are helpful.
Happy New Year
York
>
> Hi Bastien,
>
> Thanks a lot, this really works, and it sounds like literate programming. Can
> you suggest some quick reading on using org-mode for literate programming?
>
> Happy new year,
>
> York
>
Read Chapter 14 of the Org-mode manual. And go to
http://orgmode.org/worg/ and search with t
> I would use code blocks tangling
>
> ,
> | #+TITLE: Test
> |
> | * Test headline
> |
> | #+begin_src tex :tangle yes
> | \documentclass{article}
> | \begin{document}
> | ...
> | \end{document}
> | #+end_src
> `
>
> `C-c C-v t' on the block will create a .tex file with the exact content
>
Hi York,
York Zhao writes:
> I'm wondering if there is a way to export ONLY the LaTeX code within
> "#+begin_latex" and "#+end_latex". I want the exact literal export without
> adding anything before and after my code. The result should be exactly the
> same
> as if I have copied the block betw
Hi there,
I'm wondering if there is a way to export ONLY the LaTeX code within
"#+begin_latex" and "#+end_latex". I want the exact literal export without
adding anything before and after my code. The result should be exactly the same
as if I have copied the block between "#+begin_latex" and "#+end
Michael Bach writes:
> Can someone give me a hint on where to look for a solution? Do I miss
> something obvious?
Indeed I missed something obvious. Once again: More thinking, less
typing.
Sorry for the noise
Hello,
I am having trouble controlling what org's LaTeX export does with my
keyword markup. I have set
org-export-latex-todo-keyword-markup (quote (("NEW" . "\\new{%s}")
("TODO" . "\\todo{%s}")
("DONE" . "
Hello,
l...@gnu.org (Ludovic Courtès) writes:
> The LaTeX exporter of Org 7.7 from a recent Emacs snapshot improperly
> interprets sequences with angle brackets in Babel snippets as if they
> were footnote references, as in:
>
> #+BEGIN_src C
> int array[2];
> #+END_src
>
> This leads to
Hello,
The LaTeX exporter of Org 7.7 from a recent Emacs snapshot improperly
interprets sequences with angle brackets in Babel snippets as if they
were footnote references, as in:
#+BEGIN_src C
int array[2];
#+END_src
This leads to a wrong-type-arg error in ‘org-export-latex-preprocess’.
Andrei Jirnyi wrote:
> Is there any way to see (in a temporary buffer) the log generated by
> pdflatex when compiling the exported document with C-e p ?
>
> --aj
>
>
It's in the buffer ``*Org PDF LaTeX Output*'' - just switch to it.
Nick
Is there any way to see (in a temporary buffer) the log generated by
pdflatex when compiling the exported document with C-e p ?
--aj
On Mon, Oct 17, 2011 at 8:31 PM, Nick Dokos wrote:
>
> As I pointed out in the subsequent message, that's not good enough: 7.7 came
> out
> on July 28 and the fix (at least what I *think* is the fix) did not go in
> until
> September 13.
Ah, I see - I was thinking 7.7 came out at the end of Sep
Nick Dokos wrote:
> Ken Williams wrote:
>
> > On Mon, Oct 17, 2011 at 4:52 PM, Nick Dokos wrote:
> > > Ken Williams wrote:
> > >
> > >> Here's a full stack trace, does this make it any more evident what's
> > >> going on?
> > >>
> > >
> > > Not really: you have not mentioned what version you
Ken Williams wrote:
> On Mon, Oct 17, 2011 at 4:52 PM, Nick Dokos wrote:
> > Ken Williams wrote:
> >
> >> Here's a full stack trace, does this make it any more evident what's going
> >> on?
> >>
> >
> > Not really: you have not mentioned what version you are using.
>
> I did post my complete
On Mon, Oct 17, 2011 at 4:52 PM, Nick Dokos wrote:
> Ken Williams wrote:
>
>> Here's a full stack trace, does this make it any more evident what's going
>> on?
>>
>
> Not really: you have not mentioned what version you are using.
I did post my complete config, which this message was a direct re
Nick Dokos wrote:
> Ken Williams wrote:
>
> > On Thu, Oct 13, 2011 at 4:48 PM, Ken Williams wrote:
> > > Hi, the following document makes a LaTeX export (C-c C-e d) crash with
> > > "Args out of range: "", -1, 0". After that, exporting (to any format)
> > > dies with the same error.
> > > [sn
Ken Williams wrote:
> On Thu, Oct 13, 2011 at 4:48 PM, Ken Williams wrote:
> > Hi, the following document makes a LaTeX export (C-c C-e d) crash with
> > "Args out of range: "", -1, 0". After that, exporting (to any format)
> > dies with the same error.
> > [snip]
>
> Then Sebastien Vauban wro
On Thu, Oct 13, 2011 at 4:48 PM, Ken Williams wrote:
> Hi, the following document makes a LaTeX export (C-c C-e d) crash with
> "Args out of range: "", -1, 0". After that, exporting (to any format)
> dies with the same error.
> [snip]
Then Sebastien Vauban wrote:
> Works for me, with Org-mode ve
Hi Ken,
Ken Williams wrote:
> Hi, the following document makes a LaTeX export (C-c C-e d) crash with "Args
> out of range: "", -1, 0". After that,
>
> --
> #+TITLE: Test doc
> #+AUTHOR: Ken Williams
>
> Some stuff.
>
> #+begin_src R
> 5+5
> #+end_src
> --
>
> Is thi
Hi, the following document makes a LaTeX export (C-c C-e d) crash with "Args
out of range: "", -1, 0". After that,
--
#+TITLE: Test doc
#+AUTHOR: Ken Williams
Some stuff.
#+begin_src R
5+5
#+end_src
--
Is this a known problem?
If I either omit the R source blo
Hi, the following document makes a LaTeX export (C-c C-e d) crash with
"Args out of range: "", -1, 0". After that, exporting (to any format)
dies with the same error.
--
#+TITLE: Test doc
#+AUTHOR: Ken Williams
Some stuff.
#+begin_src R
5+5
#+end_src
--
Is this
Thomas S. Dye wrote:
> Eric S Fraga writes:
>
> > Jakob Lombacher writes:
> >
> >> Hi,
> >>
> >> if I export a document to latex, the caption of a table is always on the
> >> top.
> >>
> >> How can I place it at the bottom? Is there a parameter to config it?
> >
> > No, the placement is (curr
Eric S Fraga writes:
> Jakob Lombacher writes:
>
>> Hi,
>>
>> if I export a document to latex, the caption of a table is always on the top.
>>
>> How can I place it at the bottom? Is there a parameter to config it?
>
> No, the placement is (currently) fixed to come before the tabular (or
> alter
Jakob Lombacher writes:
> Hi,
>
> if I export a document to latex, the caption of a table is always on the top.
>
> How can I place it at the bottom? Is there a parameter to config it?
No, the placement is (currently) fixed to come before the tabular (or
alternative) environment. Line 1970 or t
Hi,
if I export a document to latex, the caption of a table is always on the top.
How can I place it at the bottom? Is there a parameter to config it?
Thanks
Jakob
Examaple
#+LABEL: tbl:asdf
#+CAPTION: ?
| | |
"leads to:"
---
\begin{table}[htb]
\caption{?} \label{tbl:dat
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I've just browsed the Document Structure chapter of the Org-mode manual:
>> paragraphs aren't mentioned!
>
> They are in "11.1 Structural markup elements"
>
Yes, somewhat incongruously. To my mind, the markup elements are bla
t...@tsdye.com (Thomas S. Dye) writes:
> I've just browsed the Document Structure chapter of the Org-mode manual:
> paragraphs aren't mentioned!
They are in "11.1 Structural markup elements"
> I'm not trying to be pedantic here and hold out for the presence or
> absence of blank lines to indicat
Nicolas Goaziou writes:
> Hello,
>
> Eric S Fraga writes:
>
>> Latex does have the concept of lists within paragraphs in that
>> paragraph boundaries are defined by blank lines. So, if you have a
>> begin{itemize}...end{itemize} with no blank lines before and after, the
>> list implicitly is pa
Eric S Fraga writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>>
>>> Hello,
>>>
>>> t...@tsdye.com (Thomas S. Dye) writes:
>>>
Nicolas Goaziou writes:
> That raises an interesting question: can a list belong to a paragraph in
> Org? According to paragra
Eric S Fraga writes:
> Latex does have the concept of lists within paragraphs in that
> paragraph boundaries are defined by blank lines. So, if you have a
> begin{itemize}...end{itemize} with no blank lines before and after, the
> list implicitly is part of the enclosing paragraph.
It can probab
Hello,
Eric S Fraga writes:
> Latex does have the concept of lists within paragraphs in that
> paragraph boundaries are defined by blank lines. So, if you have a
> begin{itemize}...end{itemize} with no blank lines before and after, the
> list implicitly is part of the enclosing paragraph.
That
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>
>> Hello,
>>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Nicolas Goaziou writes:
That raises an interesting question: can a list belong to a paragraph in
Org? According to paragraph-related regexps, it can't, for n
On 07/29/2011 04:59 PM, Ista Zahn wrote:
> Hi Scott,
> Untested, but I think you can use
> #+LATEX_HEADER: \hypersetup{colorlinks=true,urlcolor=blue,linkcolor=blue}
That worked. Thanks.
Scott
>
> Best,
> Ista
>
> On Fri, Jul 29, 2011 at 4:55 PM, Scott Randby wrote:
>> The package hyperref is
Hi Scott,
Untested, but I think you can use
#+LATEX_HEADER: \hypersetup{colorlinks=true,urlcolor=blue,linkcolor=blue}
Best,
Ista
On Fri, Jul 29, 2011 at 4:55 PM, Scott Randby wrote:
> The package hyperref is one of the default packages listed in
> org-export-latex-default-packages-alist. I want
The package hyperref is one of the default packages listed in
org-export-latex-default-packages-alist. I want to add some options to
this package for some files but not for others.
I have tried adding the following to my file:
#+LATEX_HEADER:
\usepackage[colorlinks=true,urlcolor=blue,linkcolor=bl
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>>> That raises an interesting question: can a list belong to a paragraph in
>>> Org? According to paragraph-related regexps, it can't, for now. And your
>>> request is more a "LaTeXism" than
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>> That raises an interesting question: can a list belong to a paragraph in
>> Org? According to paragraph-related regexps, it can't, for now. And your
>> request is more a "LaTeXism" than an "Orgism" (!).
> I probably don'
301 - 400 of 462 matches
Mail list logo
