emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Eduardo Mercovich <eduardo@mercovich.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org is exporting to tex an asterisk between "section" and "{"
Date: Thu, 10 Mar 2016 08:56:58 +0000	[thread overview]
Message-ID: <8737ry90dh.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <87si015ezq.fsf@mercovich.net> (Eduardo Mercovich's message of "Tue, 08 Mar 2016 09:30:17 -0300")

On Tuesday,  8 Mar 2016 at 09:30, Eduardo Mercovich wrote:

[...]

> Being a total newbie I can't say that the resulting syntax is incorrect
> (is it?), but at least in the case of latex, *not expressing this
> specific option creates a non-functional latex file*. 
>
> Shouldn't the exporter take care of this? Or at least, never export the
> asterisk between the "section" and the brace (just in case, "{" since
> I'm not an English native speaker).

The * between section and the brace indicates an unnumbered section
heading and is perfectly valid LaTeX syntax for the article class.  I am
not sure why you think the syntax is incorrect.

num:t tells org to export numbered headlines so the * won't be there in
that case.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-535-g7213aa

  reply	other threads:[~2016-03-10 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 19:15 Org is exporting to tex an asterisk between "section" and "{" Eduardo Mercovich
2016-03-04 19:45 ` Eric S Fraga
2016-03-04 21:26   ` Eduardo Mercovich
2016-03-05 10:10     ` Eric S Fraga
2016-03-08 12:30       ` Eduardo Mercovich
2016-03-10  8:56         ` Eric S Fraga [this message]
2016-03-15 16:07           ` Eduardo Mercovich
2016-03-15 17:11             ` Eric S Fraga
2016-03-10  9:57         ` Nicolas Goaziou
2016-03-15 16:02           ` Eduardo Mercovich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737ry90dh.fsf@delle7240.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=eduardo@mercovich.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).