From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:8:6d80::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 6KiqKLWdaWDT+gAAgWs5BA (envelope-from ) for ; Sun, 04 Apr 2021 13:06:29 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id KNeHI7WdaWD9JwAAB5/wlQ (envelope-from ) for ; Sun, 04 Apr 2021 11:06:29 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id A70DA28021 for ; Sun, 4 Apr 2021 13:06:28 +0200 (CEST) Received: from localhost ([::1]:51540 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lT0aI-00036s-Ky for larch@yhetil.org; Sun, 04 Apr 2021 07:06:26 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:50082) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lT0YY-00036e-C0 for emacs-orgmode@gnu.org; Sun, 04 Apr 2021 07:04:38 -0400 Received: from mail-wm1-x334.google.com ([2a00:1450:4864:20::334]:37418) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lT0YV-0002Rz-En for emacs-orgmode@gnu.org; Sun, 04 Apr 2021 07:04:38 -0400 Received: by mail-wm1-x334.google.com with SMTP id f22-20020a7bc8d60000b029010c024a1407so6303197wml.2 for ; Sun, 04 Apr 2021 04:04:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=VTd3JF6W4LmYJ6XupXR2RiGt24ltHqvm+fdpN04Hrco=; b=QAkO0zh0jVOeAgzPd9kBu+mT71AhmgiVmvg706ejbrrwBbdXUD7wJhZSe8QEcvMj3Y myaeYz4bOnH43TzsRqvCXJs/hZadnTlRNXBb4GjIs7DmY06+jdrrbRt/yD7Dv9TFB1eV Yb6yiN/sJ0b28WJfJpSHSU6J8qx2Dhquzken15RtDRwzdLNBnG2EOii5l0Q/a4JC+Q5m DYQQTfEfjQshUPO2K+FbyBFrSOXDl4RM0yJ50eWooKbEfjdgDjiWw91Hjkht0M6WIOAZ SEvJVboXlq82juOQHdrEaXmYH9sffT2aKJccqoGD81SBFIEIezNBnsFqhIcurg5VCmGV ew8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=VTd3JF6W4LmYJ6XupXR2RiGt24ltHqvm+fdpN04Hrco=; b=GoLl58B59JuwtWNkLjwZC4drGP4pQkVSMVtYEl4qlWKQCCAXuMAQsB5a+uX6quBQUI gJZ8ag7GoQnkg26ADvuVLpzWnQOBX9mP7Iyh2Y6Zr/HSIv40Z7s95od7CB5mv09PHwoq T8Bg/XYzL/GYMybKlzeLy+CoWeWFw1GRS7q0ARy39X4z/JR4COXWLc4zwbCpNGVnzrD2 iqMIyxKwQpnm+K/FI0hZdm1/I2IHFKSGp82cKflRnYZ/6ssEnx5vprIPJXpbG24AV8vW Tm2mr5ysFAqoNs4VAq2e4TukEsaT96DCfqNuTnqElLabTaCEIp0/l4oJkif8/fQFNCCn 8/YQ== X-Gm-Message-State: AOAM530qYbldsPS1eomQ3opXEGLSrtON6dICm6LS/Q90nOUbqNBjUsjT G6M23jf2UkoFSLSZL+DTG8M= X-Google-Smtp-Source: ABdhPJy7GMuSDRpUje6p0AjD5uF8/8+oEtNHlr0ic180ZPmYqaLDEo0C75PZXcpya77ZCXI7msvVGw== X-Received: by 2002:a05:600c:289:: with SMTP id 9mr20934665wmk.135.1617534273377; Sun, 04 Apr 2021 04:04:33 -0700 (PDT) Received: from [192.168.0.97] ([87.125.178.230]) by smtp.gmail.com with ESMTPSA id c8sm19168516wmb.34.2021.04.04.04.04.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 04 Apr 2021 04:04:32 -0700 (PDT) Subject: Re: First steps exporting to tex To: emacs-orgmode@gnu.org References: <86im538yip.fsf@login.ifi.uio.no> From: Ypo Message-ID: <5d1bbedb-0332-d584-c6ef-9ca0d8351003@gmail.com> Date: Sun, 4 Apr 2021 13:04:31 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: <86im538yip.fsf@login.ifi.uio.no> Content-Type: multipart/alternative; boundary="------------2696DEE63D17EE08901C6839" Content-Language: en-GB Received-SPF: pass client-ip=2a00:1450:4864:20::334; envelope-from=ypuntot@gmail.com; helo=mail-wm1-x334.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1617534388; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=VTd3JF6W4LmYJ6XupXR2RiGt24ltHqvm+fdpN04Hrco=; b=F+U4J8v9PxYvfFdsm3AXrW5ARdoQhd2JEBzm6JQEs07mcX7spYQo1ajQLHFiTaBuE1F2LT 71rA/ZxGUFhLV8jXoclpg2rNBLu2lb5LlVH0OlWTkupV9qFsKoiZ1GLDmNnCW0sKLOMRlS EpWXUwsXwJ1ln+uHg1mnxdAoiz/1Odp4xMeq/+88awTmTdkTcSJ1lUpYCDJC9MozqSbftt xXr5YTPdmtouZjGauZyhOUU1RDG6uBSiMUTrMakUTZXahLxXIyQA5S1AMjwnMNql9ps2kj x+G0Fp7IZzChG0mhYnfQ99mtdrP/U2g0thJvkBLJrRpp7B0vWZQ0TN3G9VEJbQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1617534389; a=rsa-sha256; cv=none; b=KDb/Sz7BO4+AEIPs0QP0TrcUZXPceCK43qSttWHNpopi5OaZo7NuvZZ3i4vfR+uJw9A6gx aDVHSPFKEyB5trRRTRlJKmU6capvKp19moHWX/wI5M3A2iN+W67r59I0DD5XAHHtLu5VmC xXODWlyQ81IuMDWVCu/BC7yAfQ59EPFW2i3pDwb6ZBoayUXNcY3+RyjIhDQeP3AQNZa2I1 z0PTLP2ftHMZcpHxTl9S2QCV61joc8PoDWqMHTnPa/mJjLC344zZz4XNWALI7IEjP5SOsB Q/IcUhThWIQ4u12mfa1P7+s/O5XNE9LZzOIOJOG6deM+2YmEkgFcBwvMHCZgOA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=QAkO0zh0; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Spam-Score: -3.14 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=QAkO0zh0; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: A70DA28021 X-Spam-Score: -3.14 X-Migadu-Scanner: scn0.migadu.com X-TUID: pTURQxt4WJWU This is a multi-part message in MIME format. --------------2696DEE63D17EE08901C6839 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit >>>>>>> El 03/04/2021 a las 18:00, emacs-orgmode-request@gnu.org escribió: > Message: 34 > Date: Sun, 04 Apr 2021 00:31:24 +1100 > To:emacs-orgmode@gnu.org > Subject: Re: First steps exporting to tex > Message-ID:<871rbr7ag1.fsf@gmail.com> > Content-Type: text/plain; charset=utf-8 > > > Why do you think you need any of this for your 'first steps'. Start by > just writing your org file and exporting it to LaTeX or pdf. Then, once > you have your first document, see what you think needs changing and come > back and ask advice on what you need to do to make the changes you want. > In your first document, don't use any LaTeX commands, header options or > anything else - just write your document using standard org mode. > > Org already sets up a reasonable starting default. Once you know what > the default is, then we can discuss what you may need to change. For > many documents, you may not need to change much at all and you may not > need any templates - for example, you will likely want to change the > margin sizes (this is a common request) or you may want to see what some > of the other 'standard' LaTeX document classes are like. All of this can > be achieved with just minor configuration of org mode. > > The org export to LaTeX only needs to be as complicated as you need it > to be. Org has variables which can be used to add/remove things from the > preamble and once you have those configured, you don't have to put > anything in the org file itself. Start simple and add as you find a need > rather than try to start with something complex which might not be > necessary. > > -- Tim Cross Hi Tim I have been exporting from orgmode to PDF time ago, but very basic PDFs, playing with some basic options of orgmode. When I tried to produce a meeting minute with a logo in the heading, I decided that I should learn better a way of exporting, because the minute meeting was a first challenge, but many more would come. For example, for that task I started with this code, which I think it goes far beyond what the "LaTeX Defaults" can offer (I must yet "play around" a lot with it): #+BEGIN_SRC #+options: toc:nil #+options: num:1 #+options: d:nil #+export_file_name: BORRAR #+options: broken-links:mark #+LaTeX_header_extra: \usepackage{fancyhdr} #+begin_export LaTeX \thispagestyle{fancy} \lhead{\includegraphics[width=4cm]{//192.168.1.2/f/LOGO-IMAGEN CORPORATIVA/IMAGEN CORPORATIVA 2018/DEFINITIVO ANAGRAMAS/SELLO1_grueso.png}} \rhead{Student Name: John Doe\\ Student ID: 1234\\ Course: IDB 601 (Fall 2020)} #+end_export #+END_SRC The buffer I exported my meeting notes from has much more information which is not related with meetings nor with the logo. So I foresaw 3 things: 1. A fast cluttering of the buffers with LaTeX headings would happen, as I will learn more about LaTeX and I will want to add more and more packages. 2. A need for flexibility to be able to export different kinds of documents from the same buffer, ideally achieved just by changing a line (or few lines) in the buffer. Although, from my example, it seems that ~#+begin_export...~ contents can't be added in that way. 3. A great potential if it were possible to use already existing, and well curated, LaTeX templates frictionless through orgmode. I find quite useful to analyse the default generated TeX file though. Best regards >>>>>>> El 03/04/2021 a las 12:15, Martin Steffen escribió: Good morning, Martin > For the "preamble" of a latex document, the general setup that comes > _before_ \begin{document} and before any output is generated, I use > native latex using  instructions like > > #+BEGIN_SRC > #+latex_header: \input{switches} > #+latex_header: \input{preamble} > #+latex_header: \input{style/style-common} > #+latex_header: \input{macros} > #+END_SRC Thanks for your input. I'll keep with that. > As far controlling input is concerned, I also rely on latex-specific > setting (outside org, also outside emacs), things like environment > settings like $TEXINPUT, a path-specification, where one can control > where LaTeX finds (additional) stylefiles, outside of the standard > ``load-path''. > > Thus, I often try to avoid to use hardcoded things, like > > >>> \input{~//export//template.tex} > > I would use \input{template} (".tex" is not needed) and I make sure, the > templatex.tex file is included in the $TEXINPUTS-path. Typically, the > current directory "./"  should be included by default (and stuff from > the latex-installation is also routinely found) Thanks. But I can read in this post: https://tex.stackexchange.com/questions/93712/definition-of-the-texinputs-variable that ~$TEXINPUT~ could give some problems with LuaLaTeX, could it be? It seems important, since LuaLaTeX is the safe recommendation of our mailing list pal Juan Manuel Macías [maciaschain@...]. >>>>>>> El 03/04/2021 a las 12:43, Dr. Arne Babenhauserheide escribió: A pleasure, Arne. > Alternatively you can use #+INCLUDE: template.org > to grab more than just the org-setup. And there you show me a different way: ~#+INCLUDE,~ "competing" with ~\input{}~. What would be the difference? > Have a look at \DeclareUnicodeCharacter: > https://www.draketo.de/light/english/emacs/char-not-setup-latex Does that mean that some symbols must be declared one by one in order to be exported using LaTeX? >>>>>>> El 03/04/2021 a las 14:10, Juan Manuel Macías escribió: Hi, Juan Manuel :-) > The correct way is \input{~/export/template.tex} I've already tried that. But it doesn't seem to understand the HOME directory ~~/~. At least at Windows. > A *.sty file is what is known in LaTeX jargon as a "package", and it > would come to be the equivalent of what is a *.el file in Emacs, > /mutatis mutandis/. In a sty file you can put whatever you want, but a > different syntax must be used and these files are subject to a series of > good practices. Therefore, a sty file is more indicated to introduce > 'heavy' code that you want reuse in other documents (defined commands > and macros, etc.). In short, what comes to be a package ;-) At the user > level, and unless you want to write your own package (see: > https://www.overleaf.com/learn/latex/Writing_your_own_package), it is > almost never necessary. So I will keep myself far away from .sty by now. > Great care must be taken here. One thing is a LaTeX class, which is > something laborious and complex to write, and another thing what Org > understands for a LaTeX class :-) Classen and the class concept are a > essential component for LaTeX, as a class is the first thing you must > declare in a preamble with the command \documentclass{}. There are the > standard classes (article, book and others) and other ones, more > specialized. A class changes globally the behavior of the document and > all LaTeX commands as \section, \subsection and many more, and add its > own commands. > > A 'LaTeX class' for Org is a light translation of the above. It is > actually "what type of LaTeX document you want to get". > > You can easily define your own LaTeX 'classes' for Org documents. For > example: I have an 'empty class', to be able to add the entire preamble, > without Org charging me anything before the \begin{document} > (add-to-list 'org-latex-classes >       '("empty" >          "[NO-DEFAULT-PACKAGES] >          [PACKAGES] >          [EXTRA]" >          ("\\section{%s}" . "\\section*{%s}") >          ("\\subsection{%s}" . "\\subsection*{%s}") >          ("\\subsubsection{%s}" . "\\subsubsection*{%s}") >          ("\\paragraph{%s}" . "\\paragraph*{%s}") >          ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))) > > And I have in my ~/.emacs: > > (setq org-latex-default-class "empty") > (setq org-latex-default-packages-alist nil) > (setq org-latex-packages-alist nil) > (setq org-latex-hyperref-template nil) Thanks for your class. I suppose that "nulls" the orgmode LaTeX export defaults, so you can control it completely. Thank you all --------------2696DEE63D17EE08901C6839 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

>>>>>>> El 03/04/2021 a las 18:00, emacs-orgmode-request@gnu.org escribió:

Message: 34
Date: Sun, 04 Apr 2021 00:31:24 +1100
To: emacs-orgmode@gnu.org
Subject: Re: First steps exporting to tex
Message-ID: <871rbr7ag1.fsf@gmail.com>
Content-Type: text/plain; charset=utf-8


Why do you think you need any of this for your 'first steps'. Start by
just writing your org file and exporting it to LaTeX or pdf. Then, once
you have your first document, see what you think needs changing and come
back and ask advice on what you need to do to make the changes you want.
In your first document, don't use any LaTeX commands, header options or
anything else - just write your document using standard org mode. 

Org already sets up a reasonable starting default. Once you know what
the default is, then we can discuss what you may need to change. For
many documents, you may not need to change much at all and you may not
need any templates - for example, you will likely want to change the
margin sizes (this is a common request) or you may want to see what some
of the other 'standard' LaTeX document classes are like. All of this can
be achieved with just minor configuration of org mode.

The org export to LaTeX only needs to be as complicated as you need it
to be. Org has variables which can be used to add/remove things from the
preamble and once you have those configured, you don't have to put
anything in the org file itself. Start simple and add as you find a need
rather than try to start with something complex which might not be
necessary.


-- 
Tim Cross

Hi Tim

I have been exporting from orgmode to PDF time ago, but very basic PDFs, playing with some basic options of orgmode. When I tried to produce a meeting minute with a logo in the heading, I decided that I should learn better a way of exporting, because the minute meeting was a first challenge, but many more would come. For example, for that task I started with this code, which I think it goes far beyond what the "LaTeX Defaults" can offer (I must yet "play around" a lot with it):

#+BEGIN_SRC

#+options: toc:nil
#+options: num:1
#+options: d:nil
#+export_file_name: BORRAR
#+options: broken-links:mark

#+LaTeX_header_extra: \usepackage{fancyhdr}

#+begin_export LaTeX
\thispagestyle{fancy}
\lhead{\includegraphics[width=4cm]{//192.168.1.2/f/LOGO-IMAGEN CORPORATIVA/IMAGEN CORPORATIVA 2018/DEFINITIVO ANAGRAMAS/SELLO1_grueso.png}}
\rhead{Student Name: John Doe\\
Student ID: 1234\\
Course: IDB 601 (Fall 2020)}
#+end_export
#+END_SRC

The buffer I exported my meeting notes from has much more information which is not related with meetings nor with the logo. So I foresaw 3 things:

  1. A fast cluttering of the buffers with LaTeX headings would happen, as I will learn more about LaTeX and I will want to add more and more packages.
  2. A need for flexibility to be able to export different kinds of documents from the same buffer, ideally achieved just by changing a line (or few lines) in the buffer. Although, from my example, it seems that ~#+begin_export...~ contents can't be added in that way.
  3. A great potential if it were possible to use already existing, and well curated, LaTeX templates frictionless through orgmode.

I find quite useful to analyse the default generated TeX file though.

Best regards

>>>>>>> El 03/04/2021 a las 12:15, Martin Steffen escribió:

Good morning, Martin

For the "preamble" of a latex document, the general setup that comes
_before_ \begin{document} and before any output is generated, I use
native latex using  instructions like

#+BEGIN_SRC
#+latex_header: \input{switches}
#+latex_header: \input{preamble}
#+latex_header: \input{style/style-common}
#+latex_header: \input{macros}
#+END_SRC

Thanks for your input. I'll keep with that.

As far controlling input is concerned, I also rely on latex-specific
setting (outside org, also outside emacs), things like environment
settings like $TEXINPUT, a path-specification, where one can control
where LaTeX finds (additional) stylefiles, outside of the standard
``load-path''.

Thus, I often try to avoid to use hardcoded things, like

>>> \input{~//export//template.tex}

I would use \input{template} (".tex" is not needed) and I make sure, the
templatex.tex file is included in the $TEXINPUTS-path. Typically, the
current directory "./"  should be included by default (and stuff from
the latex-installation is also routinely found)
Thanks. But I can read in this post:

https://tex.stackexchange.com/questions/93712/definition-of-the-texinputs-variable

that ~$TEXINPUT~ could give some problems with LuaLaTeX, could it be? It seems important, since LuaLaTeX is the safe recommendation of our mailing list pal Juan Manuel Macías [maciaschain@...].


>>>>>>> El 03/04/2021 a las 12:43, Dr. Arne Babenhauserheide escribió:

A pleasure, Arne.

Alternatively you can use #+INCLUDE: template.org
to grab more than just the org-setup.
And there you show me a different way: ~#+INCLUDE,~ "competing" with ~\input{}~. What would be the difference?


Have a look at \DeclareUnicodeCharacter:
https://www.draketo.de/light/english/emacs/char-not-setup-latex
Does that mean that some symbols must be declared one by one in order to be exported using LaTeX?


>>>>>>> El 03/04/2021 a las 14:10, Juan Manuel Macías escribió:

Hi, Juan Manuel :-)

The correct way is \input{~/export/template.tex}
I've already tried that. But it doesn't seem to understand the HOME directory ~~/~. At least at Windows.


A *.sty file is what is known in LaTeX jargon as a "package", and it
would come to be the equivalent of what is a *.el file in Emacs,
/mutatis mutandis/. In a sty file you can put whatever you want, but a
different syntax must be used and these files are subject to a series of
good practices. Therefore, a sty file is more indicated to introduce
'heavy' code that you want reuse in other documents (defined commands
and macros, etc.). In short, what comes to be a package ;-) At the user
level, and unless you want to write your own package (see:
https://www.overleaf.com/learn/latex/Writing_your_own_package), it is
almost never necessary.
So I will keep myself far away from .sty by now.

Great care must be taken here. One thing is a LaTeX class, which is
something laborious and complex to write, and another thing what Org
understands for a LaTeX class :-) Classen and the class concept are a
essential component for LaTeX, as a class is the first thing you must
declare in a preamble with the command \documentclass{}. There are the
standard classes (article, book and others) and other ones, more
specialized. A class changes globally the behavior of the document and
all LaTeX commands as \section, \subsection and many more, and add its
own commands.

A 'LaTeX class' for Org is a light translation of the above. It is
actually "what type of LaTeX document you want to get".

You can easily define your own LaTeX 'classes' for Org documents. For
example: I have an 'empty class', to be able to add the entire preamble,
without Org charging me anything before the \begin{document}
(add-to-list 'org-latex-classes
      '("empty"
         "[NO-DEFAULT-PACKAGES]
         [PACKAGES]
         [EXTRA]"
         ("\\section{%s}" . "\\section*{%s}")
         ("\\subsection{%s}" . "\\subsection*{%s}")
         ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
         ("\\paragraph{%s}" . "\\paragraph*{%s}")
         ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

And I have in my ~/.emacs:

(setq org-latex-default-class "empty")
(setq org-latex-default-packages-alist nil)
(setq org-latex-packages-alist nil)
(setq org-latex-hyperref-template nil)
Thanks for your class. I suppose that "nulls" the orgmode LaTeX export defaults, so you can control it completely.


Thank you all

--------------2696DEE63D17EE08901C6839--