From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Konstantin Kliakhandler <kosta@slumpy.org>
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 09:27:37 +0100 [thread overview]
Message-ID: <87ppleiqo6.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87k3bmoe3o.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 22 Mar 2014 09:02:35 +0100")
Hi Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> I don't think this is the right fix. IIRC, I replaced "\ul" with
> "\uline" a while ago for some reason (maybe a problem with newline
> or unicode, I cannot remember). This would go backwards.
>
> There are probably other solutions (e.g., remove all underline markup in
> sections).
Yes, maybe there is a better fix.
If you can find why you used \uline instead of \ul that will help
spot possible problems with the current fix, of course.
I'm not for getting rid of the problem before we can tell for sure
why the current solution is wrong.
--
Bastien
next prev parent reply other threads:[~2014-03-22 8:27 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 [this message]
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
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=87ppleiqo6.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kosta@slumpy.org \
--cc=n.goaziou@gmail.com \
/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).