Thanks a lot!
-- Christian
---
On Mon, May 06 2019, William Denton wrote:
On 6 May 2019, Christian Lynbech wrote:
> What determines at what level LaTeX export goes from sections to
> enumerations?
According to this, by default it's three
On 6 May 2019, Christian Lynbech wrote:
What determines at what level LaTeX export goes from sections to
enumerations?
According to this, by default it's three levels of sections, then it turns into
lists:
https://orgmode.org/org.html#LaTeX-header-and-sectioning
But H in the export
What determines at what level LaTeX export goes from sections to
enumerations?
I am using `report', the definition of which looks like this:
("report" "\\documentclass[11pt]{report}"
("\\part{%s}" . "\\part*{%s}")
("\\chapter{%s}" . "\\chapter*{%s}")
Am 22.04.19 um 21:13 schrieb Nick Dokos:
Jakob Schöttl writes:
Hi, I want to use code blocks to generate and include images of sheet music:
#+BEGIN_SRC lilypond :file test.png :exports results
\header{tagline=""}
{ a b c }
#+END_SRC
When doing a latex export the result is:
\begin{center}
Jakob Schöttl writes:
> Hi, I want to use code blocks to generate and include images of sheet music:
>
> #+BEGIN_SRC lilypond :file test.png :exports results
> \header{tagline=""}
> { a b c }
> #+END_SRC
>
>
> When doing a latex export the result is:
>
> \begin{center}
>
Hi, I want to use code blocks to generate and include images of sheet music:
#+BEGIN_SRC lilypond :file test.png :exports results
\header{tagline=""}
{ a b c }
#+END_SRC
When doing a latex export the result is:
\begin{center}
\includegraphics[width=.9\linewidth]{test.png}
\end{center}
Is
Hello mailing list,
when I use org-download to take a screenshot and automatically import the
image into my org document it often contains spaces (because the overlying
headline contains spaces and the image gets saved in a folder with the same
name).
org-download seems to use URL encoding when
Hello,
Dominik Schrempf writes:
> I tried to follow your suggestions. Please let me know, if the patch
> is OK like this.
Applied, with some changes to the commit message. Thank you.
> The patch only adds one footnote. It is unfortunate, that all
> subsequent footnotes are changed too.
This
Hello,
I tried to follow your suggestions. Please let me know, if the patch is OK like
this.
The patch only adds one footnote. It is unfortunate, that all subsequent
footnotes are changed too.
Best,
Dominik
>From 4b97952b0d6d218de7d7cab6f7017f87b68b966c Mon Sep 17 00:00:00 2001
From: Dominik
Hello,
Dominik Schrempf writes:
> Oh thanks,
>
> I thought it would be good to add a comment to the Org mode manual although it
> is of course not really Org mode related.
>
> I decided that a good location would be
>
Oh thanks,
I thought it would be good to add a comment to the Org mode manual although it
is of course not really Org mode related.
I decided that a good location would be
https://orgmode.org/manual/Math-formatting-in-HTML-export.html#Math-formatting-in-HTML-export
A proposed patch is
Dominik Schrempf writes:
> so I found the reason. Both Org versions behave the same, sorry for the
> confusion. The original equation that does not get exported correctly
> contained
> angles:
>
> \begin{equation}
> = \frac{\sum_i w_i k_{eff}(i)}{\sum_i w_i}.
> \end{equation}
>
> This
Am 13.09.18 um 15:31 schrieb Dominik Schrempf:
> so I found the reason. Both Org versions behave the same, sorry for the
> confusion. The original equation that does not get exported correctly
> contained
> angles:
>
> \begin{equation}
> = \frac{\sum_i w_i k_{eff}(i)}{\sum_i w_i}.
>
Hi,
so I found the reason. Both Org versions behave the same, sorry for the
confusion. The original equation that does not get exported correctly contained
angles:
\begin{equation}
= \frac{\sum_i w_i k_{eff}(i)}{\sum_i w_i}.
\end{equation}
This equation is correctly rendered when using a
Hi,
I have the following document:
\begin{equation}
foobar
\end{equation}
I perform an HTML export.
The equation is not rendered with MathJax when using Org Mode 9.1.14
(Spacemacs).
The equation is correctly rendered with =emacs -Q=; then, Org Mode 9.1.9 is
used.
I am sure that Spacemacs
Hello,
I'm very sorry I hope this version is parsed correctly:
When I use a multiline caption without a label everythings is
correct, the two lines are both indented by the same amount
#+BEGIN_SRC org #+LATEX_HEADER: \usepackage{caption}
#+LATEX_HEADER: \captionsetup{format=hang}
Hello,
Max Beutelspacher writes:
> I have a problem when I'm exporting a figure with a multiline caption
> and a label to pdf via latex.
>
> Here is an example
> #+BEGIN_SRC org +LATEX_HEADER: \usepackage{caption} +LATEX_HEADER:
> #\captionsetup{format=hang} +NAME: test +CAPTION:Cras placerat
Hi,
I have a problem when I'm exporting a figure with a multiline
caption and a label to pdf via latex.
Here is an example
#+BEGIN_SRC org +LATEX_HEADER: \usepackage{caption} +LATEX_HEADER:
#\captionsetup{format=hang} +NAME: test +CAPTION:Cras placerat
#accumsan nulla. Aliquam posuere.
>
>
>
>>
>>> (while (string-match
>>> "\\(<\\([0-9]+\\)cid\\([0-9]+\\)?>[[:blank:]]*\\([^&]+\\)\\)" row)
>>
>> Could it be that you need to change the last + to *?
>> Haven't tried it, mind you.
>> --
>
> That does not change the result. Still pick only two.
>
> Vikas
>
>
>>
>>
>>>
(while (string-match
"\\(<\\([0-9]+\\)cid\\([0-9]+\\)?>[[:blank:]]*\\([^&]+\\)\\)" row)
>>>
>>> Could it be that you need to change the last + to *?
>>> Haven't tried it, mind you.
>>> --
>>
>
> The problem is in this part of the code:
>
> (while
On Saturday, 24 Mar 2018 at 22:24, Vikas Rawal wrote:
> I am trying to write a LaTeX export filter that should replace all
> table rows with cells having entries such as <3cid4> by
> \cmidrule{lr}{3-4}
[...]
> (while (string-match
>
Let me start by confessing my limited knowledge of lisp.
I am trying to write a LaTeX export filter that should replace all table rows
with cells having entries such as <3cid4> by \cmidrule{lr}{3-4}
The idea is to have a table row of this kind
| <2cid3> | <4cid5> |<6cid7>
On 08/10/2017 11:35 AM, Richard Lawrence wrote:> Hi Scott,
>
> Scott Randby writes:
>
>> I tried this in the properties associated with a subtree:
>> :export_latex_header:
>>
Hi Scott,
Scott Randby writes:
I tried this in the properties associated with a subtree:
:export_latex_header:
\hypersetup{pdfauthor={foo},pdftitle={foo},pdfsubject={foo},pdfkeywords={foo},pdfproducer={foo},pdfcreator={foo}}
Unfortunately, all the other LaTeX headers
I have a file with a large number of top-level headlines. Each subtree
corresponding to a top-level headline is exported to its own PDF file. The
subtrees all use the same LaTeX headers except for \hypersetup. Right now, I
have to uncomment the \hypersetup manually whenever I export a subtree.
Does this code from the backed-up .emacs interfere with TeX not working with
MINTED in the body of the .tex file? Should I eliminate it?
I'm thinking of posting all the bits of code where `minted' is mentioned, in
the hopes that some of you experts can tell me whether I could eliminate/edit
Not an answer to the issue you are seeing, but I noticed that you are using
Emacs 24.x and Org-mode 8.2.x. The Org-mode version especially is too old.
I can only suggest that you update to the latest version of Org-mode mode
(9.0.5) (and also that of Emacs (25.2) if you get a chance), so that the
Hello again, I'm still trying to find out why emacs doesn't pick up MINTED
instead of LISTINGS to handle code blocks when exporting files from .org to
.pdf, via .tex.
I backed-up my previous .emacs file (which had a lot of customization for
Beamer, AUCTeX etc.), loaded Nick Dokos' minimal init
"vendo.li...@libero.it" writes:
> Hello there!
> I'm having a bit of a problem telling emacs to use MINTED instead of LISTINGS
> to handle code blocks
> enclosed within #+BEGIN_SRC and #+END_SRC when exporting from an org file.
>
> I've had to Customize Org Groups using
Hello there!I'm having a bit of a problem telling emacs to use MINTED instead
of LISTINGS to handle code blocks enclosed within #+BEGIN_SRC and #+END_SRC
when exporting from an org file.
I've had to Customize Org Groups using the GUI menu `Org' but as soon as I
close and restart emacs, it goes
Hello,
Justen Rickert writes:
> LaTeX export for five dashes - exports from org as
> \rule{\linewidth}{0.5pt}
> which then produces a pdf with a horizontal line having the width of the
> paragraph but indented. This means the line extends into the margin by the
>
Hello,
LaTeX export for five dashes - exports from org as
\rule{\linewidth}{0.5pt}
which then produces a pdf with a horizontal line having the width of the
paragraph but indented. This means the line extends into the margin by the
width
of the indent.
If I do
Hello Takeshi,
On Sat, Mar 04 2017, Takeshi Teshima wrote:
> I have a question regarding latex export.
>
> When I export an org-mode to a latex file, a directory named "auto" is
> created in the same folder as the tex file.
>
> However, I couldn't find what line in the source code of org-mode
>
On 03/03/17 15:55, Takeshi Teshima wrote:
I have a question regarding latex export.
When I export an org-mode to a latex file, a directory named "auto" is
created in the same folder as the tex file.
However, I couldn't find what line in the source code of org-mode
creates this directory.
Does
Dear Colin,
Thank you for that detailed information!
I'll try them.
Best regards,
Takeshi
On 2017/03/04 1:37, Colin Baxter wrote:
Hello Takeshi,
On Sat, Mar 04 2017, Takeshi Teshima wrote:
I have a question regarding latex export.
When I export an org-mode to a latex file, a directory
Hi Tom,
Thank you for the immediate and useful answer!
You've saved me a lot of time. Thank you!
Best regards,
Takeshi
On 2017/03/04 1:06, Thomas S. Dye wrote:
Aloha Takeshi Teshima,
Takeshi Teshima writes:
I have a question regarding latex export.
When I export an org-mode to a latex file,
Aloha Takeshi Teshima,
Takeshi Teshima writes:
> I have a question regarding latex export.
>
> When I export an org-mode to a latex file, a directory named "auto" is
> created in the same folder as the tex file.
>
> However, I couldn't find what line in the source code of org-mode
> creates this
I have a question regarding latex export.
When I export an org-mode to a latex file, a directory named "auto" is
created in the same folder as the tex file.
However, I couldn't find what line in the source code of org-mode
creates this directory.
Does anyone know what causes this, or
Hello Mr. Goaziou,
Thank you for the reply!
Wow, thank you. It worked. The problem seems to stem from my own config.
It worked as I turned my personal settings off.
Best,
Takeshi
On 2017/01/19 7:38, Nicolas Goaziou wrote:
Hello,
Takeshi Teshima writes:
Hello,
Takeshi Teshima writes:
> When I try to export an org-mode file **that contains a figure with
> a caption** with `#+OPTIONS: \n:t`, (See minimal example files)
>
> to a pdf via latex-export, the exported latex file doesn't compile and
> I get the following
Hi all,
A happy new year!
I have a problem with org-export-to-latex.
# What happens
## [1]
When I try to export an org-mode file **that contains a figure with a
caption** with `#+OPTIONS: \n:t`, (See minimal example files)
to a pdf via latex-export, the exported latex file doesn't
Hello,
Scott Otterson writes:
> Hi Nicolas, thanks for trying to replicate this on Linux. What happens for
> you if it doesn't crash? Does the latex export just work and produce a pdf
> with a set of properly nested lists?
It produces a pdf with improperly nested lists
Hi Nicolas, thanks for trying to replicate this on Linux. What happens for
you if it doesn't crash? Does the latex export just work and produce a pdf
with a set of properly nested lists?
Would you be willing to sent me .tex your latex export produces? It seems
unlikely, but maybe org use a
Hello,
Scott Otterson writes:
> If a plain list has more than four levels, org-mode will produce latex that
> crashes. See attached. On the other hand, html export works fine, even
> for much deeper lists.
>
> In a large org file, this export error is pretty time
If a plain list has more than four levels, org-mode will produce latex that
crashes. See attached. On the other hand, html export works fine, even
for much deeper lists.
In a large org file, this export error is pretty time consuming for a naive
user (me) to isolate, so I'd like to suggest
On Friday, 2 Dec 2016 at 10:35, Alan Schmitt wrote:
> Thank you for the suggestion. With macros that makes for a quite elegant
> solution.
You're welcome. And, yes, with macros, many LaTeX aspects can be
incorporated easily without making everything look a mess.
--
: Eric S Fraga
Hi Eric,
On 2016-12-02 09:52, Eric S Fraga writes:
> I know you've had some answers but if you want exactly what you
> specified in LaTeX, the following will do it:
>
> * intro
> This is a list
> - @@latex:[\(\checkmark\)]@@ and so on
> - normal item
Thank you for the
On Thursday, 1 Dec 2016 at 09:04, Alan Schmitt wrote:
> Hello,
>
> I would like to generate the following latex export:
>
> \begin{itemize}
> \item[\Checkmark] foo
> \end{itemize}
>
> I tried both
>
> -[\Checkmark]
>
> and
>
> - [\Checkmark]
>
> but neither works.
>
> Is this possible with
Hello Richard,
On 2016-12-01 11:36, Richard Lawrence writes:
>> I would like to generate the following latex export:
>>
>> \begin{itemize}
>> \item[\Checkmark] foo
>> \end{itemize}
>
> It's not exactly pretty, but you can use a description list while
> resetting
Hi Alan,
Alan Schmitt writes:
> I would like to generate the following latex export:
>
> \begin{itemize}
> \item[\Checkmark] foo
> \end{itemize}
It's not exactly pretty, but you can use a description list while
resetting it to the itemize environment, like:
Hello,
I would like to generate the following latex export:
\begin{itemize}
\item[\Checkmark] foo
\end{itemize}
I tried both
-[\Checkmark]
and
- [\Checkmark]
but neither works.
Is this possible with org-mode?
Best,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂,
Nicolas Goaziou writes:
> All your "Effort" values are expressed as HH:MM so Org does its best to
> produce a HH:MM summary. If you write at least one value as a duration,
> e.g., "10 h", the summary will also be expressed as a duration.
I see, thank you!
ciao, lele.
--
Lele Gaifax writes:
> This is the equivalent, made with current master development org-mode:
>
> # -*- coding: utf-8 -*-
>
> #+TITLE: Test with current master revision of org-mode
> #+COLUMNS: %40ITEM(Item) %13Effort(Effort){:} %CLOCKSUM(Work)
>
>
> * This
Nicolas Goaziou writes:
> Lele Gaifax writes:
>
>> One minor issue: previously I used a custom setting for the variable
>> `org-time-clocksum-format`, to print something like "2gg 03:10" instead of
>> "2d
>> 03:10". With the version currently
Hello,
Lele Gaifax writes:
> One minor issue: previously I used a custom setting for the variable
> `org-time-clocksum-format`, to print something like "2gg 03:10" instead of "2d
> 03:10". With the version currently distributed with Emacs 25.1 it was used for
> both the
Nicolas Goaziou writes:
>> Do you know if/when it will be merged into Emacs?
>
> I don't know, but that will not happen before Emacs 25.1 release.
Thanks anyway, I installed latest development sources and I appreciate the
work that has been done in this (and many other)
Hello,
Lele Gaifax writes:
> Do you know if/when it will be merged into Emacs?
I don't know, but that will not happen before Emacs 25.1 release.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Lele Gaifax writes:
>
>> I know this is an ancient thread, but it seems the problem is still there, in
>> Emacs 25.
>
> "org-colview" was rewritten recently. IIRC, this is fixed in development
> version of Org.
Great,
Hello,
Lele Gaifax writes:
> I know this is an ancient thread, but it seems the problem is still there, in
> Emacs 25.
"org-colview" was rewritten recently. IIRC, this is fixed in development
version of Org.
Regards,
--
Nicolas Goaziou
Hi all,
I know this is an ancient thread, but it seems the problem is still there, in
Emacs 25.
FWIW, this is my quick and dirty fix, that at least produce a readable output,
in Emacs as well as in the PDF output.
(require 'org-colview)
;; Quick workaround to
Hello!
I use some calc in my org document:
#+begin_SRC calc :var x=5 :var y=2 :exports both
2 + a * x ** y
#+end_SRC
When I export this to LaTeX the listings package complains about an unknown
language calc.
To fix this I simply define a language:
#+LATEX_HEADER: \usepackage{listings}
On Saturday, 13 Feb 2016 at 16:35, Axel Kielhorn wrote:
> Hello!
>
> I use some calc in my org document:
>
> #+begin_SRC calc :var x=5 :var y=2 :exports both
> 2 + a * x ** y
> #+end_SRC
>
> When I export this to LaTeX the listings package complains about an
> unknown language calc.
>
> To fix
John Kitchin writes:
>> I do something like this with custom link types.
> Aha! I am not the only one ;)
>
>>
>> First of all, have a look at the variable
>>
>> org-latex-prefer-user-labels
>
> Is this a new 8.3 variable? It doesn't seem to be in my 8.2.10 MELPA
>
> 03.12.2015, 16:31, "John Kitchin" :
>
> Try this.
>
> * Chapter 1
> ** Section 1.1 \label{manual-section-1}
> :PROPERTIES:
> :CUSTOM_ID: section-1
> :END:
> * Chapter 2
> ** Section 2.1
> I want reference to Section 1.1 from here
Hi Ilya,
Ilya writes:
> I export my Org-Mode notes with internal links to LaTeX and I want it to
> look like this ''Section 1.1 [Section name], page 99'' (Like in the Org
> Manual). I use this construction:
>
> #+BEGIN_EXAMPLE
> * Chapter 1
> ** Section 1.1
>
> I do something like this with custom link types.
Aha! I am not the only one ;)
>
> First of all, have a look at the variable
>
> org-latex-prefer-user-labels
Is this a new 8.3 variable? It doesn't seem to be in my 8.2.10 MELPA
version.
>
> if you haven't already. Setting it will cause Org
Thank you, it is work, but I hope to use something like (setq org-export-latex-hyperref-format "\\ref{%s}") for hyperref customization. (I want join \\ref{%s} and \\pageref{%s} for org-export-latex-hyperref-format). If it will be work we may simple use [[#section-1]] to different templates for
I export my Org-Mode notes with internal links to LaTeX and I want it to look
like this ''Section 1.1 [Section name], page 99'' (Like in the Org Manual). I
use this construction:
#+BEGIN_EXAMPLE
* Chapter 1
** Section 1.1
:PROPERTIES:
:CUSTOM_ID: section-1
:END:
* Chapter 2
**
On Thursday, 26 Nov 2015 at 16:26, Fatma Başak Aydemir wrote:
> Hi all,
>
> I'm trying to write a conference paper which has multiple authors from
> multiple institues. I tried to insert author infor by adding the
> following block
>
> #+BEGIN_LaTeX
> \author{First Author\inst{1}, Second
I have also done something like this for different journals here:
https://github.com/jkitchin/jmax/blob/master/ox-manuscript.el#L64
Eric S Fraga writes:
> On Thursday, 26 Nov 2015 at 16:26, Fatma Başak Aydemir wrote:
>> Hi all,
>>
>> I'm trying to write a conference paper which has multiple
I export my Org-Mode notes with internal links to LaTeX and I want it to
look like this ''Section 1.1 [Section name], page 99'' (Like in the Org
Manual). I use this construction:
#+BEGIN_EXAMPLE
* Chapter 1
** Section 1.1
:PROPERTIES:
:CUSTOM_ID: section-1
:END:
* Chapter 2
**
Try this.
* Chapter 1
** Section 1.1 \label{manual-section-1}
:PROPERTIES:
:CUSTOM_ID: section-1
:END:
* Chapter 2
** Section 2.1
I want reference to Section 1.1 from here (See Section
\ref{manual-section-1} on page \pageref{manual-section-1})
John
Hi all,
I'm trying to write a conference paper which has multiple authors from
multiple institues. I tried to insert author infor by adding the
following block
#+BEGIN_LaTeX
\author{First Author\inst{1}, Second Author\inst{1}, Third Author\inst{2}}
\authorrunning{Author et al.}
Envoyé de mon iPhone
> Le 26 nov. 2015 à 16:26, Fatma Başak Aydemir a écrit :
>
> Hi all,
>
> I'm trying to write a conference paper which has multiple authors from
> multiple institues. I tried to insert author infor by adding the following
> block
>
> #+BEGIN_LaTeX
Aloha Fatma Başak Aydemir,
Fatma Başak Aydemir writes:
> Hi all,
>
> I'm trying to write a conference paper which has multiple authors from
> multiple institues. I tried to insert author infor by adding the
> following block
>
> #+BEGIN_LaTeX
> \author{First
Aloha!
Both solutions work for me. I went for adding the code line by line
using #+LATEX_HEADER for I do not collaborate with the same co-authors
all the time so I did not want to permanenetly add the configuration to
my setup.
Thanks!
26/11/15 16:59 tarihinde Thomas S. Dye yazdı:
Aloha
On Mon, 27 Apr 2015, Lawrence Bottorff wrote:
In a previous post I was getting at the issue of whether I should just do
regular export or use latex code blocks for what I wanted in a final
document. What I want is the ability to create a big, rambling, annotated
org file -- with keeper stuff
In a previous post I was getting at the issue of whether I should just do
regular export or use latex code blocks for what I wanted in a final
document. What I want is the ability to create a big, rambling, annotated
org file -- with keeper stuff inside the latex babel blocks -- then
tangle the
I would use LaTeX code blocks when I need to write something in LaTeX
that isn't easy to write in org mode, not to distinguish what is a
note and what is part of the draft. For that I recommend comments,
e.g.,
### Start example ###
* Section 1
** COMMENT Some rough draft notes to myself
yadda
Leonard Avery Randall wrote:
Serge Cohen writes:
Is this normal, if so is there another way to obtain the same results
as what is proposed in the documentation ?
The behaviour you are explaining is not normal. The setup you described
should work.
To complete the post : I am using Aquamacs
Hello list,
When using hte org to LaTeX exporter, I would like to use the link-type
capabilities described here :
http://orgmode.org/worg/org-contrib/babel/examples/article-class.html#sec-3
To follow the instruction, I have added the lines to my ~/.emacs.el
(org-add-link-type
ltx nil
(lambda
Hi Serge,
Serge Cohen writes:
Is this normal, if so is there another way to obtain the same results
as what is proposed in the documentation ?
The behaviour you are explaining is not normal. The setup you described
should work.
To complete the post : I am using Aquamacs (MacOSX
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]: Structural effects of
false transitives with the stratigraphic
Aloha Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]:
Aloha all,
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]: Structural effects of
false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:
When exporting to LaTeX, fourth-level headings become \enumerate. In
LaTeX, the item below \subsubsection is \paragraph, not \enumerate.
Here is what happens:
* Top becomes \section
** Second becomes \subsection
*** Third becomes \subsubsection
Fourth becomes \enumerate
Is there a way to
Aloha Ken,
Ken Mankoff mank...@gmail.com writes:
When exporting to LaTeX, fourth-level headings become \enumerate. In
LaTeX, the item below \subsubsection is \paragraph, not \enumerate.
Here is what happens:
* Top becomes \section
** Second becomes \subsection
*** Third becomes
* On 2014-07-10 at 17:08, Thomas S. Dye wrote:
Aloha Ken,
Ken Mankoff mank...@gmail.com writes:
When exporting to LaTeX, fourth-level headings become \enumerate. In
LaTeX, the item below \subsubsection is \paragraph, not \enumerate.
Here is what happens:
* Top becomes \section
**
Ken Mankoff mank...@gmail.com writes:
* On 2014-07-10 at 17:08, Thomas S. Dye wrote:
Aloha Ken,
Ken Mankoff mank...@gmail.com writes:
When exporting to LaTeX, fourth-level headings become \enumerate. In
LaTeX, the item below \subsubsection is \paragraph, not \enumerate.
Here is what
Thanks for the kind words, Martin. I hope you stay inspired since making a
few homemade paperbacks sounds like something I'd like to try.
Cheers,
Alan
On 31 May 2014 17:25, Martin Schöön martin.sch...@gmail.com wrote:
On 28 May 2014 06:31, Alan Tyree typh...@aanet.com.au wrote:
Hi Steven,
On 28 May 2014 06:31, Alan Tyree typh...@aanet.com.au wrote:
Hi Steven,
You want to learn more about LaTeX, but it's not too much.
I wrote a little book called Self-publishing with LyX that will help you
set up the title page as well as some of your other problems. This is not a
sales pitch
Hi Alan,
I downloaded the book and went through it--thank you for putting that
together! It was a valuable overview. Nonetheless, some confusions
persist for me since I'm using emacs org-mode and not LyX. Should I be
putting LaTeX markup into my org-mode doc, for instance, for formatting
the
Am 28.05.2014 um 08:07 schrieb Steven Arntson ste...@stevenarntson.com:
Hi Alan,
I downloaded the book and went through it--thank you for putting that
together! It was a valuable overview. Nonetheless, some confusions
persist for me since I'm using emacs org-mode and not LyX. Should I be
On 2014-05-27 23:25, Steven Arntson wrote:
Nick Dokos ndo...@gmail.com writes:
Igor Sosa Mayor joseleopoldo1...@gmail.com writes:
Steven Arntson ste...@stevenarntson.com writes:
Hi, I'm trying to export an org-mode doc to LaTex and subsequently to
PDF. This is a literary novel, written in
Hi Steven,
Steven Arntson ste...@stevenarntson.com writes:
Hi, I'm trying to export an org-mode doc to LaTex and subsequently to
PDF. This is a literary novel, written in prose. Right now when I run
the export command, the resulting file is incorrectly formatted for the
literary world, and
What kind of deadlines are you facing to accomplish this?
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
g...@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been
Rick,
Your google search to find the sffms style package seems like it could
be the perfect answer to my quandary. I'm trying now to get my head
around acquiring it. I don't have a great track record with installing
things, and try to use package management systems when I can.
Sffms is located
Steven Arntson ste...@stevenarntson.com writes:
Rick,
Your google search to find the sffms style package seems like it could
be the perfect answer to my quandary. I'm trying now to get my head
around acquiring it. I don't have a great track record with installing
things, and try to use
Nick Dokos ndo...@gmail.com writes:
Steven Arntson ste...@stevenarntson.com writes:
Rick,
Your google search to find the sffms style package seems like it could
be the perfect answer to my quandary. I'm trying now to get my head
around acquiring it. I don't have a great track record with
Steven Arntson ste...@stevenarntson.com writes:
Nick Dokos ndo...@gmail.com writes:
Steven Arntson ste...@stevenarntson.com writes:
Rick,
Your google search to find the sffms style package seems like it could
be the perfect answer to my quandary. I'm trying now to get my head
around
1 - 100 of 456 matches
Mail list logo