emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: in beamer export non-beamer tags exported as part of header
Date: Wed, 01 Jun 2016 15:23:43 +0200	[thread overview]
Message-ID: <m260ttvy8w.fsf@krugs.de> (raw)
In-Reply-To: <87bn3lqeum.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 01 Jun 2016 14:21:37 +0200")

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Rasmus <rasmus@gmx.us> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Rainer M Krug <Rainer@krugs.de> writes:
>>
>>> \section[Level 1]{Level 1\hfill{}\textsc{andHereIsTheTag}}
>>
>> IIUC, according to this line, tags should be removed from the toc.
>>
>> This issue may be related to Beamer.
>
> From the Beamer manual, 10.2 (latest TL version): 
>
>      \section<⟨mode specification⟩>[⟨short section name⟩]{⟨section name⟩}
>
>      Starts a section. No heading is created. The ⟨section name⟩ is shown in
>      the table of contents and in the navigation bars, except if ⟨short section
>      name⟩ is specified. In this case, ⟨short section name⟩ is used in the
>      navigation bars instead. If a ⟨mode specification⟩ is given, the command
>      only has an effect for the specified modes.
>
> I guess the most sane solution is to not support tags:not-in-toc in
> ox-beamer (or in general).

I agree - that might be the easiest solution.

Rainer


>
> A latex hack might be something like this (untested):
>
>     \section{title}
>     \section<beamer>*{title \hfill :tags:} % to not mess up if someone uses article mode
>
>
> Here’s another hack that can be applied in a org latex document class.
>
>     http://tex.stackexchange.com/questions/203105/short-section-name-in-toc
>
> Rasmus

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  reply	other threads:[~2016-06-01 13:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 10:48 BUG: in beamer export non-beamer tags exported as part of header Rainer M Krug
2016-05-24 12:08 ` Rasmus
2016-05-24 12:27   ` Rainer M Krug
2016-05-24 20:32     ` Nicolas Goaziou
2016-05-24 21:02       ` Rasmus
2016-05-25  7:39         ` Rainer M Krug
2016-05-25  7:37       ` Rainer M Krug
2016-05-25 20:29         ` Nicolas Goaziou
2016-05-27  9:01           ` Rainer M Krug
2016-05-27 11:58             ` Nicolas Goaziou
2016-05-27 16:15               ` Rainer M Krug
2016-05-31 19:53                 ` Nicolas Goaziou
2016-06-01  8:06                   ` Rainer M Krug
2016-06-01 11:08                     ` Nicolas Goaziou
2016-06-01 12:21                       ` Rasmus
2016-06-01 13:23                         ` Rainer M Krug [this message]
2016-06-01 17:40                           ` Nicolas Goaziou
2016-05-31 20:07                 ` John Hendy
2016-06-01  8:12                   ` Rainer M Krug

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=m260ttvy8w.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).