[O] Org-mode using enumerate properties to export to LaTeX
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
In my LaTeX export I like to have it look like
R1. This
R2. is
R3. a
R4. numbered
R5. list
In my latex-document I would do something like this:
\documentclass{article}
\usepackage{enumerate}
\begin{document}
\begin{enumerate}[{\bfseries R1.}]
\item This
\item is
\item a
\item numbered
\item list
\end{enumerate}
\end{document}
--
aagaard
Re: [O] Org-mode using enumerate properties to export to LaTeX
Søren Mikkelsen sorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.7 (release_7.7.271.gbae8)
Re: [O] Org-mode using enumerate properties to export to LaTeX
On 2011-09-11 15:18, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
Thanks, I thought something like renewing a command could do the job.
However it could be nice, if it was possible to export a list with a
generic prefix on the lists.
---
/aagaard
[O] ATTN: Working on the HTML exporter and links (Spaghetti alarm)
Hi, I did some changes to Org's HTML exporter and link functionality. Please double check the exporting results, I hope I didn't mess up things too much this time. Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgp2LO5slycpf.pgp Description: PGP signature
Re: [O] Question about org-mode compilation
On 9/11/11 Sep 11 -12:52 AM, David Maus wrote: At Sat, 10 Sep 2011 12:08:45 -0500, Robert Goldman wrote: Today I was trying to push to mobile org after an update from git, and got an invalid function error on org-eval-in-environment. This macro is defined in org-macs.el and is used in org-agenda.el. I note that the makefile has org-agenda depending on org.el, but /not/ on org-macs.el. Is that an error? Adding that dependency, then making clean and making all fixes things. But I may not have properly cleaned before my last build, so I'm not sure. Hi Robert, I checked and don't think the missing dependency in Makefile was cause of the problem. When org-agenda.el is compiled it requires org.el which in turn requires org-macs.el -- thus the macro definition is loaded. Otherwise the compiler would stop. An invalid function error with a macro is according to my experience an indicator of mixing up of old and new files. Thus, the make clean was the action that fixed the issue. I byte compiled Org and ran a batch-agenda (which uses org-eval-in-environment) with no error. Thanks, I noticed that org.el dependency, but I wasn't sure how transitive these dependencies were. I will try to remember to always make clean! best, R
Re: [O] FYI: Org mode testing framework, Emacs 23 and 22
At Fri, 02 Sep 2011 07:50:02 -0600, Eric Schulte wrote: Hi David, David Maus dm...@ictsoc.de writes: Just FYI: I've tried to get the testing framework running on Emacs 23 and Emacs 22 and succeeded to 50%: - copying ert.el and ert-x.el from Emacs24 Git repository at git://git.savannah.gnu.org/emacs.git with master on 231bffa3e6c37164fa40ad18bd27249cc7704e30 and installing jump.el is sufficient to get the test suit running again - not so much luck with Emacs22: Recent ERT requires `special-mode', defined in simple.el from 23.x upwards. Would it be possible to load a more recent version of simple.el in Emacs22 to define special mode, and then see if ert loads successfully? Next on my list. Also, did all tests pass successfully in Emacs23? Currently on my system using Emacs24 all tests pass but those related to fortran code block support, all of which are failing. The test result with failing tests for Emacs23 is attached. , | Passed: 101 | Failed: 8 (8 unexpected) | Total: 109/109 | | Started at: 2011-09-11 19:53:46+0200 | Finished. | Finished at: 2011-09-11 19:53:51+0200 ` 7 of the 8 are fortran-tests, the 8th is `org-babel-get-inline-src-block-matches'. Once we have all tests running for Emacs=22 it would be very nice (and not too difficult) to add a post-update hook to the Org-mode git repository which could run the test suite and record the results for every version of Emacs with something like the following emacs23 -Q --batch -l $ORGTESTSTUFF --eval (progn (org-test-run-all-tests) (htmlize-buffer) (write-file commit-id-23.html)) +1 Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgplKGyAeCOTP.pgp Description: PGP signature
Re: [O] Org-mode using enumerate properties to export to LaTeX
Søren Mikkelsen sorenaamikkel...@gmail.com writes:
On 2011-09-11 15:18, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
Thanks, I thought something like renewing a command could do the
job. However it could be nice, if it was possible to export a list
with a generic prefix on the lists.
---
/aagaard
I'm not sure what you mean? Doesn't what I posted above do the job?
This is the standard latex means of doing this, at least with the
default latex enumeration environment.
You may wish to check out other list environments; there are a few out
there, e.g. paralist. However, I am not sure how the latex exporter
could be configured to pass the extra information that some of these
need to achieve what you want.
HTH,
eric
Re: [O] Org-mode using enumerate properties to export to LaTeX
On 2011-09-11 21:06, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
On 2011-09-11 15:18, Eric S Fraga wrote:
Søren Mikkelsensorenaamikkel...@gmail.com writes:
I am currently struggling with enumerating my numbered list with a
prefix. In org-mode I have
1. This
2. is
3. a
4. numbered
5. list
Try putting the line
#+latex: \renewcommand{\theenumi}{R\arabic{enumi}}
before the start of the list. This changes how latex outputs the first
level (i) enumeration counter. Set it back afterwards to the same thing
*without* the =R= to get the default behaviour.
This is obviously a latex issue not specific to org. For these cases,
there are some very good resources online. e.g.
https://secure.wikimedia.org/wikibooks/en/wiki/LaTeX/
and my all time favourite:
http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf
one of the best things about org as a writing mode is that you still
have access to most latex (and other export target) features in a
straightforward manner!
HTH,
eric
Thanks, I thought something like renewing a command could do the
job. However it could be nice, if it was possible to export a list
with a generic prefix on the lists.
---
/aagaard
I'm not sure what you mean? Doesn't what I posted above do the job?
This is the standard latex means of doing this, at least with the
default latex enumeration environment.
You may wish to check out other list environments; there are a few out
there, e.g. paralist. However, I am not sure how the latex exporter
could be configured to pass the extra information that some of these
need to achieve what you want.
HTH,
eric
Yes, it works perfectly when I export it into latex (and thank you for
that). Just wondering if it was possible to do something similar within
org-mode; a enumerate list with a prefix, e.g.:
R1. One
R2. Two
--
---
Søren Mikkelsen
[O] [patch] fix 22.x compatibility test issue
Replace left-char with backward-char for backward compatibility in =test-org-babel/org-babel-get-inline-src-block-matches= From 08bfac66d69ed6ce739d58710f06444b6f43fb94 Mon Sep 17 00:00:00 2001 From: Martyn Jago martyn.j...@btinternet.com Date: Sun, 11 Sep 2011 21:17:40 +0100 Subject: [PATCH] Replace left-char with backward-char for backward compatibility * testing/lisp/test-ob.el (test-org-babel/org-babel-get-inline-src-block-matches): --- testing/lisp/test-ob.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el index a78bf1e..3a68328 100644 --- a/testing/lisp/test-ob.el +++ b/testing/lisp/test-ob.el @@ -226,9 +226,9 @@ (should (re-search-forward echo nil t)) ;; 2 (should (org-babel-get-inline-src-block-matches)) (should (re-search-forward blocks nil t)) ;; 3 - (left-char 8) ;; 3 + (backward-char 8) ;; 3 (should (org-babel-get-inline-src-block-matches)) - (right-char 1) ;;3 + (forward-char 1) ;;3 (should-not (org-babel-get-inline-src-block-matches)) (should (re-search-forward :results nil t)) ;; 4 (should (org-babel-get-inline-src-block-matches)) -- 1.7.3.4 Best, Martyn
[O] [OFFTOPIC] Happy Birthday!
Dear Carsten, Van harte gefeliciteerd met je verjaardag! :) -- Manish
Re: [O] FYI: Org mode testing framework, Emacs 23 and 22
Hi David David Maus dm...@ictsoc.de writes: [...] F test-org-babel/org-babel-get-inline-src-block-matches (void-function left-char) I've pushed a patch to the mailing-list which should fix the above test in Emacs 22. I will take a look at the fortran related tests when I get a chance. Best, Martyn
Re: [O] [patch] fix 22.x compatibility test issue
I've applied this same change. Thanks -- Eric Martyn Jago martyn.j...@btinternet.com writes: Replace left-char with backward-char for backward compatibility in =test-org-babel/org-babel-get-inline-src-block-matches= From 08bfac66d69ed6ce739d58710f06444b6f43fb94 Mon Sep 17 00:00:00 2001 From: Martyn Jago martyn.j...@btinternet.com Date: Sun, 11 Sep 2011 21:17:40 +0100 Subject: [PATCH] Replace left-char with backward-char for backward compatibility * testing/lisp/test-ob.el (test-org-babel/org-babel-get-inline-src-block-matches): --- testing/lisp/test-ob.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el index a78bf1e..3a68328 100644 --- a/testing/lisp/test-ob.el +++ b/testing/lisp/test-ob.el @@ -226,9 +226,9 @@ (should (re-search-forward echo nil t)) ;; 2 (should (org-babel-get-inline-src-block-matches)) (should (re-search-forward blocks nil t)) ;; 3 - (left-char 8) ;; 3 + (backward-char 8) ;; 3 (should (org-babel-get-inline-src-block-matches)) - (right-char 1) ;;3 + (forward-char 1) ;;3 (should-not (org-babel-get-inline-src-block-matches)) (should (re-search-forward :results nil t)) ;; 4 (should (org-babel-get-inline-src-block-matches)) -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] FYI: Org mode testing framework, Emacs 23 and 22
The test result with failing tests for Emacs23 is attached. , | Passed: 101 | Failed: 8 (8 unexpected) | Total: 109/109 | | Started at: 2011-09-11 19:53:46+0200 | Finished. | Finished at: 2011-09-11 19:53:51+0200 ` 7 of the 8 are fortran-tests, the 8th is `org-babel-get-inline-src-block-matches'. I would imagine that the fortran tests are failing because you do not have the gfortran executable in your path. I had to apt-get install fortran for these tests to pass. The eighth test should not be passing. I've getting all tests passing on Emacs24. Once we have all tests running for Emacs=22 it would be very nice (and not too difficult) to add a post-update hook to the Org-mode git repository which could run the test suite and record the results for every version of Emacs with something like the following emacs23 -Q --batch -l $ORGTESTSTUFF --eval (progn (org-test-run-all-tests) (htmlize-buffer) (write-file commit-id-23.html)) +1 I suppose the next step here would be to talk to Bastien about setting up such a system on the org-mode server. Cheers -- Eric Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de -- Eric Schulte http://cs.unm.edu/~eschulte/
