From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: [bug] two bugs: one with comments and with exporting inline tasks
Date: Tue, 02 Nov 2010 10:46:19 +0000 [thread overview]
Message-ID: <87iq0gknpg.fsf@pinto.chemeng.ucl.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Hello,
I have run into two problems. The first is one which has existed for a long time as
is somewhat minor: a line consisting of just #+ will be treated as part
of the text. The regex for comments requires a space but it would be
nice if this weren't required.
The second problem is more serious: exporting to latex when there are
inline tasks does not work. I believe the problem is due to a
combination of headings being treated as list entries and the
introduction of the new list handling code.
Please see attached files for a full example (org, tex and pdf) and
which includes the version information (org up-to-date as of an hour ago
basically).
Thanks,
eric
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example org file --]
[-- Type: text/org, Size: 2350 bytes --]
# -*- coding: utf-8; -*-
#+TITLE: examplebug.org
#+AUTHOR: Eric S Fraga
#+EMAIL: e.fraga@ucl.ac.uk
#+DATE: 2010.08.30 14:14:04
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
* comments in latex export
This is some text that should appear normally. The next few lines are
a comment which should not be exported.
#+ this line will be ignored, as it should be
#+
#+ as will this one but the one in between will not
*Immediately* before this sentence is the appearance of =#+= which should
not be there. I believe the regex requires a space after the plus
sign but maybe a check for end of line =$= as an alternative to a space
could be used? I.e. something like =#\+\( |$\)= although I don't know if
that type of expression will work...
* problem exporting to latex with inline tasks
I often use inline tasks to help me organise my thoughts as I am
writing long documents. However, exporting these no longer seems to
work.
***************************** TODO figure out why this doesn't work
***************************** END
There are two problems with exporting inline tasks:
1. If the whole document is exported, the inline task headline text is
inserted into the =[ ]= optional argument for an =\item=, generating
something like this:
: \item[@<span class="todo TODO"> TODO figure out why this doesn't work]
Further, this text in the =[]= appears in subsequent items as well!
See the attached =pdf= document.
2. If only the current subtree is exported, the exported latex ends
just before the inline task.
I believe both of these problems are related to the new list handling
as I used to be able to export inline tasks perfectly fine in
September.
* version information
#+begin_src emacs-lisp :results output :exports results
(format "%s\n%s" (org-version) (emacs-version))
#+end_src
#+results:
: Org-mode version 7.01trans (release_7.01h.514.g878d)
: GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
: of 2010-08-14 on raven, modified by Debian
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: latex generated by org exporter --]
[-- Type: text/x-tex, Size: 2536 bytes --]
% Created 2010-11-02 Tue 10:41
\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{xcolor}
\usepackage{listings}
\providecommand{\alert}[1]{\textbf{#1}}
\title{examplebug.org}
\author{Eric S Fraga}
\date{2010.08.30 14:14:04}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{comments in latex export}
\label{sec-1}
This is some text that should appear normally. The next few lines are
a comment which should not be exported.
\textbf{Immediately} before this sentence is the appearance of \verb=#+= which should
not be there. I believe the regex requires a space after the plus
sign but maybe a check for end of line \verb=$= as an alternative to a space
could be used? I.e. something like \verb=#\+\( |$\)= although I don't know if
that type of expression will work\ldots{}
\section{problem exporting to latex with inline tasks}
\label{sec-2}
I often use inline tasks to help me organise my thoughts as I am
writing long documents. However, exporting these no longer seems to
work.
\begin{enumerate}
\item[@<span class="todo TODO"> TODO figure out why this doesn't work]
There are two problems with exporting inline tasks:
\item[@<span class="todo TODO"> TODO figure out why this doesn't work]If the whole document is exported, the inline task headline text is
inserted into the \verb=[ ]= optional argument for an \verb=\item=, generating
something like this:
\begin{verbatim}
\item[@<span class="todo TODO"> TODO figure out why this doesn't work]
\end{verbatim}
Further, this text in the \verb=[]= appears in subsequent items as well!
See the attached \verb=pdf= document.
\item[@<span class="todo TODO"> TODO figure out why this doesn't work]If only the current subtree is exported, the exported latex ends
just before the inline task.
\end{enumerate}
I believe both of these problems are related to the new list handling
as I used to be able to export inline tasks perfectly fine in
September.
\section{version information}
\label{sec-3}
\begin{verbatim}
Org-mode version 7.02trans (release_7.3.5.g1197)
GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
of 2010-08-14 on raven, modified by Debian
\end{verbatim}
\end{document}
[-- Attachment #4: examplebug.pdf --]
[-- Type: application/pdf, Size: 72085 bytes --]
[-- Attachment #5: Type: text/plain, Size: 156 bytes --]
--
Eric S Fraga, GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
using Org-mode version 7.02trans (release_7.3.5.g1197) in Emacs version 23.2.1
[-- Attachment #6: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-11-02 13:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 10:46 Eric S Fraga [this message]
2010-11-02 19:27 ` [bug] two bugs: one with comments and with exporting inline tasks Nicolas Goaziou
2010-11-02 20:51 ` Eric S Fraga
2010-11-02 23:11 ` Eric S Fraga
2010-11-04 7:41 ` Nicolas Goaziou
2010-11-04 7:51 ` [patch] " Nicolas Goaziou
2010-11-04 8:01 ` Nicolas Goaziou
2010-11-04 10:24 ` Eric S Fraga
2010-11-04 14:05 ` Nicolas Goaziou
2010-11-04 14:21 ` Eric S Fraga
2010-11-04 14:42 ` Nicolas Goaziou
2010-11-04 15:22 ` Eric S Fraga
2010-11-04 15:28 ` Nicolas Goaziou
2010-11-04 16:17 ` Eric S Fraga
2010-11-04 16:32 ` Sébastien Vauban
2010-11-04 17:45 ` Nicolas Goaziou
2010-11-05 8:01 ` Sébastien Vauban
2010-11-05 8:58 ` Sébastien Vauban
2010-11-05 12:50 ` Eric S Fraga
2010-11-05 12:50 ` Eric S Fraga
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=87iq0gknpg.fsf@pinto.chemeng.ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--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).