Re: [O] Enumeration within environment block
On Saturday, 17 May 2014 at 21:24, Xavier Garrido wrote: [...] block. Is there a way to solve that issue or at least to force the item number ? (for instance, in LaTeX I can write \item[1],\item[2] and in html I can set the =ol= start value). Thanks in advance, Xavier Forcing the item number is easy: #+begin_src org ,* list numbering 1. this is the first item. some interrupting text 2. [@2] this is the second item. #+end_src This functionality is describer in [[info:org#Plain%20lists]]. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.6-937-g60502a
[O] Bug: org-beamer-select-environment (ox-beamer.el) should temporarily disable persistent tags
Hi, Having some persistent tags configured (in org-tag-persistent-alist) means those get added to the selection window for org-beamer-select-environment possibly interfering with the selection of beamer environments. These tags should be explicitly disabled in the let in org-beamer-select-environment: (org-tag-persistent-alist nil) Cheers, Anders Johansson
[O] [PATCH] Improve usage of odt content templates
Hi all, I have been using org-mode's odt exporter heavily for the last days with the attached patches. These scratch an itch I have and I submit them to this list in the hope of being useful to others. Rationale: I am using the odt exporter to fill in a project description document at work with has strict specified layout and template. Fortunately just using an existing empty document and org-mode's content template setting is sufficient for my needs to create the OO documents without having to touch OpenOffice. However the current master code misses two things I need: * Possibility to override the globally defined org-odt-content-template-file variable in the document * Avoid inserting the document title as the first thing in the document contents, as there already is a title set in a title page in the template. As org-mode already sets the title data tag this can be used in the template to generate the correct title. However inserting the title as text is not desireable in that scenario. I have attached patches that address these two issues. The latter adds yet another option to the exporter mode to suppress title insertion. I offer these patches as the base of a discussion as I am not sure whether these small changes fit the overall org-mode way. Or maybe there already is an easier way to achieve what I want, I don't know. As these are my first org-mode patches I hope I have read the guidelines for commit messages correctly. I am grateful for any comments or advise you may have. Kind regards, Christian -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. From a6a84ae372ce1d755292da7559afde1c9bfbfc7d Mon Sep 17 00:00:00 2001 From: Christian Kellermann ck...@pestilenz.org Date: Mon, 19 May 2014 12:11:28 +0200 Subject: [PATCH 1/2] ox-odt: Expose content template file setting * ox-odt.el (odt): Add ODT_CONTENT_TEMPLATE_FILE option. org-odt-content-template-file is not changeable in the org buffer. * ox-odt.el (org-odt-template): Prefer local content template Prefer the locally set #+ODT_CONTENT_TEMPLATE_FILE over the global org-odt-content-template-file variable. TINYCHANGE --- lisp/ox-odt.el | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el index 4d2f257..1d4e796 100644 --- a/lisp/ox-odt.el +++ b/lisp/ox-odt.el @@ -97,6 +97,7 @@ (org-open-file (org-odt-export-to-odt nil s v) 'system)) :options-alist '((:odt-styles-file ODT_STYLES_FILE nil nil t) +(:odt-content-template-file ODT_CONTENT_TEMPLATE_FILE nil nil t) ;; Redefine regular option. (:with-latex nil tex org-odt-with-latex))) @@ -1450,7 +1451,8 @@ original parsed data. INFO is a plist holding export options. '(%Y-%M-%d %a . %Y-%M-%d %a %H:%M (with-temp-buffer (insert-file-contents - (or org-odt-content-template-file + (or (plist-get info :odt-content-template-file) + org-odt-content-template-file (expand-file-name OrgOdtContentTemplate.xml org-odt-styles-dir))) ;; Write automatic styles. -- 1.9.2 From e1e171a12b0ad0d29881a27688d578fba1ac4a75 Mon Sep 17 00:00:00 2001 From: Christian Kellermann ck...@pestilenz.org Date: Mon, 19 May 2014 12:14:50 +0200 Subject: [PATCH 2/2] ox-odt: Optionally suppress title insertion * ox-odt.el (odt): Add ODT_INSERT_TITLE to option list. This allows the user to suppress the insertion of the document title in the openoffice document. * ox-odt.el (org-odt-template): optionally skip title insertion. If ODT_INSERT_TITLE is set to a false value, skip title insertion. As the odt exporter also sets the title metadata tag, this allows the user to use the title elsewhere, for example in a fancier title page. TINYCHANGE --- lisp/ox-odt.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/ox-odt.el b/lisp/ox-odt.el index 1d4e796..6268e51 100644 --- a/lisp/ox-odt.el +++ b/lisp/ox-odt.el @@ -97,6 +97,7 @@ (org-open-file (org-odt-export-to-odt nil s v) 'system)) :options-alist '((:odt-styles-file ODT_STYLES_FILE nil nil t) +(:odt-insert-title ODT_INSERT_TITLE nil nil t) (:odt-content-template-file ODT_CONTENT_TEMPLATE_FILE nil nil t) ;; Redefine regular option. (:with-latex nil tex org-odt-with-latex))) @@ -1504,7 +1505,7 @@ original parsed data. INFO is a plist holding export options. (email (and (plist-get info :with-email) email))) (concat ;; Title. - (when (org-string-nw-p title) + (when (and (plist-get info :odt-insert-title) (org-string-nw-p title)) (concat (format \ntext:p text:style-name=\%s\%s/text:p OrgTitle (format \ntext:title%s/text:title title)) -- 1.9.2
Re: [O] org-ref for biblatex
good news, I think org-ref works with biblatex pretty well now, see
http://kitchingroup.cheme.cmu.edu/blog/2014/05/19/Exporting-citations-with-biblatex/
org-ref also makes a reasonable html bibliography now too!
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, May 18, 2014 at 6:38 PM, Andreas Reuleaux andr...@a-rx.info wrote:
John,
thanks a lot, I will try them out, and let you know.
Never mind about the comfort (or lack thereof) of how to add an s or the
like in org. - I can easily do that by hand.
Working back ends (exporters) for the various citiation commands seem
much more important at this point.
-Andreas
John Kitchin jkitc...@andrew.cmu.edu writes:
I added the multicite commands. you have to use cites:foo,bar,baz, and it
will export to the format you suggested. org-ref is not smart enough to
automatically add the s to the link type if you add more than one
reference, you have to be smart enough to do that.
can you try it out and let me know if it does what you need?
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, May 18, 2014 at 1:16 PM, Andreas Reuleaux andr...@a-rx.info
wrote:
John,
to come back to org-ref, which basically runs fine for me now, thanks.
I am running biblatex (as opposed to bibtex) though, with meanwhile
biber as a backend.
The biblatex manual is very comprehensible and explains the different
citation commands from page 79 onwards.
http://ctan.mirrorcatalogs.com/macros/latex/contrib/biblatex/doc/biblatex.pdf
I just ran into this: Having added a few citations to an existing
one with C-u C-c d, I have something like
cite:foo,bar,baz
which gets exported to latex as
\cite{foo,bar,baz}
whereas biblatex expects
\cites{foo}{bar}{baz}
as I understand (note the plural s as well), and there are other config
tweekings I am doing for biblatex (that I intend to explain some other
time).
Maybe a switch (an org-ref variable) would be a good idea, that lets
one choose: use either biblatex or plain old bibtex?
thanks in advance
-Andreas
Re: [O] Bug: org-beamer-select-environment (ox-beamer.el) should temporarily disable persistent tags
Hello, Anders Johansson mejlaande...@gmail.com writes: Having some persistent tags configured (in org-tag-persistent-alist) means those get added to the selection window for org-beamer-select-environment possibly interfering with the selection of beamer environments. These tags should be explicitly disabled in the let in org-beamer-select-environment: (org-tag-persistent-alist nil) This should be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou
Re: [O] org-ref for biblatex
Thanks a lot, looks good!
(but I haven't had a chance yet to try it out myself,
will do so of course)
-Andreas
John Kitchin jkitc...@andrew.cmu.edu writes:
good news, I think org-ref works with biblatex pretty well now, see
http://kitchingroup.cheme.cmu.edu/blog/2014/05/19/Exporting-citations-with-biblatex/
org-ref also makes a reasonable html bibliography now too!
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, May 18, 2014 at 6:38 PM, Andreas Reuleaux andr...@a-rx.info wrote:
John,
thanks a lot, I will try them out, and let you know.
Never mind about the comfort (or lack thereof) of how to add an s or the
like in org. - I can easily do that by hand.
Working back ends (exporters) for the various citiation commands seem
much more important at this point.
-Andreas
John Kitchin jkitc...@andrew.cmu.edu writes:
I added the multicite commands. you have to use cites:foo,bar,baz, and it
will export to the format you suggested. org-ref is not smart enough to
automatically add the s to the link type if you add more than one
reference, you have to be smart enough to do that.
can you try it out and let me know if it does what you need?
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, May 18, 2014 at 1:16 PM, Andreas Reuleaux andr...@a-rx.info
wrote:
John,
to come back to org-ref, which basically runs fine for me now, thanks.
I am running biblatex (as opposed to bibtex) though, with meanwhile
biber as a backend.
The biblatex manual is very comprehensible and explains the different
citation commands from page 79 onwards.
http://ctan.mirrorcatalogs.com/macros/latex/contrib/biblatex/doc/biblatex.pdf
I just ran into this: Having added a few citations to an existing
one with C-u C-c d, I have something like
cite:foo,bar,baz
which gets exported to latex as
\cite{foo,bar,baz}
whereas biblatex expects
\cites{foo}{bar}{baz}
as I understand (note the plural s as well), and there are other config
tweekings I am doing for biblatex (that I intend to explain some other
time).
Maybe a switch (an org-ref variable) would be a good idea, that lets
one choose: use either biblatex or plain old bibtex?
thanks in advance
-Andreas
[O] Referring to results rather than code block
Hi,
I have a code block like this
#+NAME: users_per_month
#+HEADER: :results append
#+BEGIN_SRC sh :dir /root@sadmin:
sacct=/cm/shared/apps/slurm/current/bin/sacct
for y in {2014..2014}; do
for m in {03..04}; do
month=$y-$m
first=$y-$m-01
last=`date -d $first + 1 month - 1 day +%Y-%m-%d`
n=`$sacct -S $first -E $last -o user -X -n | sort | uniq | wc -l`
echo $month $n
done
done
#+END_SRC
which produces something like this
#+RESULTS: users_per_month
| 2012-01 | 1 |
| 2012-02 |10 |
| 2012-03 | 100 |
| 2012-04 | 1000 |
I'm using append because the generation of a datapoint takes a while.
I'd like to plot the data with something like:
#+NAME: plot_users_per_month
#+HEADER: var data=users_per_month
#+HEADER: :results output graphics
#+HEADER: :file ./users_per_month.pdf :exports both
#+HEADER: :session *r*
#+BEGIN_SRC R
library(ggplot2)
bar_colour - #69B4D8 # steely blue
month - data$V1
users - data$V2
df - data.frame(month,users)
p - ggplot(df,aes(x=month,y=users)) +
geom_bar(stat=identity,alpha=0.5,fill=bar_colour) +
xlab(date) +
ylab(users)
p
#+END_SRC
However, this is just generating a plot of the data generated by the
source block and not of the total results table.
Can I give the results block a different name to the source block, so
that I can refer to it directly, or should I be doing something
completely different?
Cheers,
Loris
--
This signature is currently under construction.
Re: [O] still seeing semi-regular lockups
Daimrod daim...@gmail.com writes: I have also semi-regular lockup with org-mode. I have opened a bug on debbugs and here is what Stefan told me to try to debug this: You can try `debug-on-event'. There's jit-lock-debug-mode but it doesn't disable inhibit-quit. So you'll need to additionally use (advice-add 'jit-lock--debug-fontify :around (lambda (fun rest args) (with-local-quit (apply fun args Of course sometimes this doesn't work because jit-lock-debug-mode changes the way things are executed and the bug may not manifest itself any more, but it's worth a try. Another source of info is to M-x trace-function RET org-adaptive-fill-function RET M-x trace-function RET org-element-at-point RET M-x trace-function RET org-element--cache-sync RET M-x trace-function RET org-element--cache-process-request RET Then reproduce the hang, then break the hang somehow (maybe with the jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g C-g, ...), then look at the *trace..* buffer. I'll try to see what I can find this week end and report back. Ok, so the good news is the `debug-on-event' trick works. If you got a lockup, you can get a classic elisp backtrace by sending the SIGUSR2 to the Emacs process. The bad news is that I don't know yet how to reproduce the lockup. It seems to happen mostly (if not only) when I use org-mode + visual-line-mode + adaptive-wrap-prefix-mode + an input-method like latin-postfix. And it probably has to do with the cache mechanism. I'll try to reproduce it with the cache disabled but it hard to test because, as I said, I don't know how to reproduce it yet. I'll keep testing and see if I can reproduce it reliably. Stay tuned! -- Daimrod/Greg
Re: [O] Error with org-mode-reftex-setup after upgrade
Hi Loris, Loris Bennett loris.benn...@fu-berlin.de writes: ,- | (defun org-mode-reftex-setup () | (interactive) | (load-library reftex) | (and (buffer-file-name) |(file-exists-p (buffer-file-name)) |(reftex-parse-all))) | | (add-hook 'org-mode-hook 'org-mode-reftex-setup) `- Following the update, this now seems to throw the error: , | Loading reftex...done | File mode specification error: (wrong-type-argument sequencep dwim) ` Any ideas? You need to use this defun instead: (defun org-mode-reftex-setup () (load-library reftex) (and (buffer-file-name) (file-exists-p (buffer-file-name)) (setq TeX-master t) (reftex-parse-all)) (define-key org-mode-map (kbd C-c )) 'reftex-citation)) setting TeX-master to t locally. HTH, -- Bastien
Re: [O] Referring to results rather than code block
Loris Bennett loris.benn...@fu-berlin.de writes:
Hi,
I have a code block like this
#+NAME: users_per_month
#+HEADER: :results append
#+BEGIN_SRC sh :dir /root@sadmin:
sacct=/cm/shared/apps/slurm/current/bin/sacct
for y in {2014..2014}; do
for m in {03..04}; do
month=$y-$m
first=$y-$m-01
last=`date -d $first + 1 month - 1 day +%Y-%m-%d`
n=`$sacct -S $first -E $last -o user -X -n | sort | uniq | wc -l`
echo $month $n
done
done
#+END_SRC
which produces something like this
#+RESULTS: users_per_month
| 2012-01 | 1 |
| 2012-02 |10 |
| 2012-03 | 100 |
| 2012-04 | 1000 |
I'm using append because the generation of a datapoint takes a while.
I'd like to plot the data with something like:
#+NAME: plot_users_per_month
#+HEADER: var data=users_per_month
#+HEADER: :results output graphics
#+HEADER: :file ./users_per_month.pdf :exports both
#+HEADER: :session *r*
#+BEGIN_SRC R
library(ggplot2)
bar_colour - #69B4D8 # steely blue
month - data$V1
users - data$V2
df - data.frame(month,users)
p - ggplot(df,aes(x=month,y=users)) +
geom_bar(stat=identity,alpha=0.5,fill=bar_colour) +
xlab(date) +
ylab(users)
p
#+END_SRC
However, this is just generating a plot of the data generated by the
source block and not of the total results table.
Can I give the results block a different name to the source block, so
that I can refer to it directly, or should I be doing something
completely different?
I believe so: the source name ties the source block to the same named
result block - that allows the source block to find the result block
and modify it appropriately. The results block can be named and then
that name can be used in the plotting block, e.g.
--8---cut here---start-8---
#+name: foo
#+BEGIN_SRC sh :results output table append :var n=5
for x in $(seq $n)
do
echo $x $(expr $x \* $x)
done
#+END_SRC
#+name: foo_results
#+RESULTS: foo
| 1 | 1 |
| 2 | 4 |
| 3 | 9 |
| 4 | 16 |
| 5 | 25 |
#+NAME: plot_foo_results
#+HEADER: :var data=foo_results
#+HEADER: :file ./foo.pdf :exports both
#+BEGIN_SRC gnuplot
plot data
#+END_SRC
--8---cut here---end---8---
Nick
Re: [O] [PATCH] Improve usage of odt content templates
Hello, Christian Kellermann ck...@pestilenz.org writes: I have been using org-mode's odt exporter heavily for the last days with the attached patches. These scratch an itch I have and I submit them to this list in the hope of being useful to others. Thank you for your patches. * Possibility to override the globally defined org-odt-content-template-file variable in the document It is already possible to override the varible file-wise with: #+BIND: org-odt-content-template-file somefile I'm not sure it is worth adding another keyword. OTOH, there's also ODT_STYLES_FILE and they are quite symmetric, so one could expect to be able to set both. But then, `org-odt-content-template-file''s docstring needs to be updated, and the feature should be documented in the manual. Also, it should be (:odt-content-template-file ODT_CONTENT_TEMPLATE_FILE nil org-odt-content-template-file t) * Avoid inserting the document title as the first thing in the document contents, as there already is a title set in a title page in the template. As org-mode already sets the title data tag this can be used in the template to generate the correct title. However inserting the title as text is not desireable in that scenario. I think this is a more general issue: should we implement an #+OPTIONS: title:nil feature? I think it makes some sense since we already have date:nil and author:nil. In any case, keywords are not meant to be used for booleans. This should be an OPTIONS item. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] Improve usage of odt content templates
Nicolas Goaziou n.goaz...@gmail.com writes: I think this is a more general issue: should we implement an #+OPTIONS: title:nil feature? I think it makes some sense since we already have date:nil and author:nil. In any case, keywords are not meant to be used for booleans. This should be an OPTIONS item. That's nicer than a blank title (#+TITLE: ). I prefer the earlier ox-behavior where no title would be printed if title was missing, rather than using the file-name. The file name is never interesting in my work flow. If introducing a title option it would be nice if an option is print title if present so that this can be set by default. —Rasmus -- El Rey ha muerto. ¡Larga vida al Rey!
Re: [O] [PATCH] Improve usage of odt content templates
Hi! * Nicolas Goaziou n.goaz...@gmail.com [140519 18:16]: It is already possible to override the varible file-wise with: #+BIND: org-odt-content-template-file somefile I'm not sure it is worth adding another keyword. OTOH, there's also ODT_STYLES_FILE and they are quite symmetric, so one could expect to be able to set both. But then, `org-odt-content-template-file''s docstring needs to be updated, and the feature should be documented in the manual. I first thought about using ODT_STYLES_FILE in the list form and pick out the content.xml from there, but maybe that's a bit unexpected as one might use a different content than from the style. But the control flow as it is now would need to be refactored to make this a nice patch too. I shall resend this patch with proper docstrings and manual patches if you like. Also, it should be (:odt-content-template-file ODT_CONTENT_TEMPLATE_FILE nil org-odt-content-template-file t) Ah of course. * Avoid inserting the document title as the first thing in the document contents, as there already is a title set in a title page in the template. As org-mode already sets the title data tag this can be used in the template to generate the correct title. However inserting the title as text is not desireable in that scenario. I think this is a more general issue: should we implement an #+OPTIONS: title:nil feature? I think it makes some sense since we already have date:nil and author:nil. In any case, keywords are not meant to be used for booleans. This should be an OPTIONS item. I don't feel qualified to decide on this. I can provide the needed patches though. Thanks for your review! Regards, Christian -- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease.
Re: [O] org-ref for biblatex
John,
yes they work fine for me, I have tested: cites and parencites.
Thanks a lot.
-Andreas
John Kitchin jkitc...@andrew.cmu.edu writes:
I added the multicite commands. you have to use cites:foo,bar,baz, and it
will export to the format you suggested. org-ref is not smart enough to
automatically add the s to the link type if you add more than one
reference, you have to be smart enough to do that.
can you try it out and let me know if it does what you need?
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, May 18, 2014 at 1:16 PM, Andreas Reuleaux andr...@a-rx.info wrote:
John,
to come back to org-ref, which basically runs fine for me now, thanks.
I am running biblatex (as opposed to bibtex) though, with meanwhile
biber as a backend.
The biblatex manual is very comprehensible and explains the different
citation commands from page 79 onwards.
http://ctan.mirrorcatalogs.com/macros/latex/contrib/biblatex/doc/biblatex.pdf
I just ran into this: Having added a few citations to an existing
one with C-u C-c d, I have something like
cite:foo,bar,baz
which gets exported to latex as
\cite{foo,bar,baz}
whereas biblatex expects
\cites{foo}{bar}{baz}
as I understand (note the plural s as well), and there are other config
tweekings I am doing for biblatex (that I intend to explain some other
time).
Maybe a switch (an org-ref variable) would be a good idea, that lets
one choose: use either biblatex or plain old bibtex?
thanks in advance
-Andreas
[O] Org based websites w/o export
I've just come across an interesting website generator that I think has potential for making Org websites. I have no affiliation with this project, but thought it might interest this community. I have an interest in an org-based website, but none of the existing ones have met my needs yet. Jr https://github.com/Xeoncross/jr is a static static (yes 2x) site generator. Most static site generators work by you writing markdown, then you converting to HTML locally, and then you uploading the static HTML pages. Existing Org site generators work like this to, I think - export to markdown and then convert again with Jekyll. Or of course you can convert Org to HTML directly. Jr works by having javascript render the markdown to HTML. That is, you write markdown, upload markdown w/o running a generator, and the generator runs in the browser of the viewer. This is efficient for the server (simpler pages) and author (no need to run a static site generator), but may be globally inefficient for a popular site (many browser doing rendering). If Jr or a fork rendered Org to HTML instead of Markdown to HTML, then we could have website that are directly written in Org. A starting place for this is the existing Javascript support for Org here http://orgmode.org/manual/JavaScript-support.html but that still requires you to export the Org file to HTML before uploading it to the web. Anyway... maybe of interest to some of y'all. I'll be watching that program develop and may be contributing to an Org port of it as I have time. -k.
[O] Bug ? Normal lines interpreted as list items
Hi all,
a Debian user, reports[0] the following problem :
When using Org within GNU Emacs, integers starting lines and followed
by a period are interpreted as the first items of ordered lists, even
when they are not. Take, for instance, the following text in Org
syntax and the corresponding part in a LaTeX export:
Org text:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
1998. Bla, bla bla bla bla, bla bla. Bla bla bla bla bla bla, bla
bla bla, bla bla bla bla, bla bla.
LaTeX export:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
\begin{enumerate}
\item Bla, bla bla bla bla, bla bla. Bla bla bla bla bla bla, bla
\end{enumerate}
bla bla, bla bla bla bla, bla bla.
I see the same thing here with 8.2.1, and was wondering if this was
indeed a bug ?
Cheers,
--Seb
[0] https://bugs.debian.org/644238
Re: [O] Bug ? Normal lines interpreted as list items
Sébastien Delafond sdelaf...@gmail.com writes:
Hi all,
a Debian user, reports[0] the following problem :
When using Org within GNU Emacs, integers starting lines and followed
by a period are interpreted as the first items of ordered lists, even
when they are not. Take, for instance, the following text in Org
syntax and the corresponding part in a LaTeX export:
Org text:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
1998. Bla, bla bla bla bla, bla bla. Bla bla bla bla bla bla, bla
bla bla, bla bla bla bla, bla bla.
LaTeX export:
Bla bla bla, bla bl, bla bla bla, bla bla, bla bla bla,
\begin{enumerate}
\item Bla, bla bla bla bla, bla bla. Bla bla bla bla bla bla, bla
\end{enumerate}
bla bla, bla bla bla bla, bla bla.
I see the same thing here with 8.2.1, and was wondering if this was
indeed a bug ?
Not in itself, but *how* the number got there *might* be a bug. See
the thread at
http://thread.gmane.org/gmane.emacs.orgmode/72902
Nick
