From: Konstantin Kliakhandler <kosta@slumpy.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug: \uline produced inside \section in latex export [8.2.5h (8.2.5h-30-gdd810b-elpa @ /home/user/.emacs.d/elpa/org-20140303/)]
Date: Sat, 22 Mar 2014 23:04:00 +0200 [thread overview]
Message-ID: <CAH+LVpkwoVrVa-VcLcXpYPHQbzNsD8e+e17573oJQz_-EFi5+A@mail.gmail.com> (raw)
In-Reply-To: <874n2qcgcx.fsf@yahoo.fr>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hello,
On Mar 22, 2014 7:06 PM, "Nicolas Richard" <theonewiththeevillook@yahoo.fr>
wrote:
> I'd go even a little further : assuming it makes sense to underline
> within a section header, does it also make sense to propagate that
> formatting to the toc and/or header of the document ? If not, I suggest
> exporting as:
> \section[not-so-plain text]{\uline{not-so-plain} \textbf{text}}
>
I think it sometimes does make sense to highlight in the TOC, for instance
if the highlight was intended to emphasize a specific word.
Also I don't know why there was underlining in the first place. If we're
> asking to underline all section titles, then it might make sense to
> redefine e.g. \section to do so (packages titlesec might help).
>
There was underlining because I wanted to emphasize a single word in the
heading (the example I posted was minimal for demonstration purposes), not
because all exported sections are underlined.
Cheers,
Kosta
[-- Attachment #2: Type: text/html, Size: 1617 bytes --]
prev parent reply other threads:[~2014-03-22 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 16:30 Bug: \uline produced inside \section in latex export [8.2.5h (8.2.5h-30-gdd810b-elpa @ /home/user/.emacs.d/elpa/org-20140303/)] Konstantin Kliakhandler
2014-03-21 23:32 ` Bastien
2014-03-22 8:01 ` Konstantin Kliakhandler
2014-03-22 8:02 ` Nicolas Goaziou
2014-03-22 8:27 ` Bastien
2014-03-22 11:19 ` Nicolas Goaziou
2014-03-22 11:38 ` Rasmus
2014-03-22 11:45 ` Konstantin Kliakhandler
2014-03-22 12:38 ` Nicolas Goaziou
2014-03-22 13:03 ` Bastien
2014-03-22 13:37 ` Nicolas Goaziou
2014-03-22 14:09 ` Bastien
2014-03-22 14:18 ` Nicolas Goaziou
2014-03-22 17:06 ` Nicolas Richard
2014-03-22 20:06 ` Rasmus
2014-03-22 21:04 ` Konstantin Kliakhandler [this message]
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=CAH+LVpkwoVrVa-VcLcXpYPHQbzNsD8e+e17573oJQz_-EFi5+A@mail.gmail.com \
--to=kosta@slumpy.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=theonewiththeevillook@yahoo.fr \
/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).