Re: [Orgmode] Re: Bug: subtree export fails with src block

[Jörg Hagmann]

 On 10/4/10 5:06 PM, Eric Schulte wrote:

Similar,

I think this thread is also related
http://thread.gmane.org/gmane.emacs.orgmode/31312/focus=31392

either way the issue should be fixed in the latest Org-mode.  Please let
me know if that is not the case.

Yes, it works with today's org version.
Many thanks!
Jörg

Best -- Eric

Jörg Hagmann  writes:


  This might be the same problem I discussed recently?
See this thread:
http://thread.gmane.org/gmane.emacs.orgmode/31241/focus=31289

Jörg

On 10/4/10 3:48 PM, Eric Schulte wrote:

"Eric Schulte"   writes:

[...]

"Giovanni Moretti"   writes:


I'm just starting with Babel and have been puzzled about why one file
worked and another didn't.

I have been playing in a new file without any headers at all (no lines
starting with '*') and while I could execute the code in the buffer,
exporting to HTML always failed with:

 No such file: c:/org/babel-python-test.org::


Hmm, it looks like it's trying to find a file with "::" attached to the
end which is probably the source of the issue.  I wonder if this is a
windows specific problem?


a-ha,

I just noticed that while my test file "python.org" was exporting w/o
problem, it was opening a "python.org::" buffer in the process, so maybe
the reason this throws errors for you and not for me is just Unix's more
permissive file names.

I've just pushed up a change to the Babel exporter that will only concat
the "::" to the end of a file name, where there is actually a heading to
following it.  Hopefully this will fix the error you described, please
let me know if that is not the case.

Best -- Eric

___
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


___
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

Re: [Orgmode] arranging and publishing music with Org-mode and lilypond

[Christian Moe]

Hi,

I've only used Lilypond for play, but I'd appreciate a Babel module 
for Lilypond, if someone writes one.


My use case, for which I think Org is perfect, is maintaining simple 
song collections: short scores interspersed with lyrics, printable as 
a booklet. It is doable now but could clearly be done better with Babel.


So if someone's thinking about ob-lilypond, integration with 
lilypond-book as a post-processing step would be useful.


Yours,
Christian


On 10/4/10 4:31 AM, John Hendy wrote:



On Sun, Oct 3, 2010 at 8:24 PM, T.F. Torrey mailto:tftor...@tftorrey.com>> wrote:

Hello,

 > From: Stefan Vollmar mailto:voll...@nf.mpg.de>>
 > Date: Sun, 03 Oct 2010 00:26:39 +0200
 > Subject: [Orgmode] arranging and publishing music with Org-mode
and lilypond
 >
 > Dear all,
 >
 > I believe that many members of this list with an interest in
music (notation/composition) might find the http://lilypond.org
project "addictive" (in the nicest possible manner): the concept
is rather similar to writing TeX, there is very good Emacs support
(if you know where to look), it is all OpenSource, there is
extensive documentation (in LaTeX format with embedded lilypond
snippets), the print quality is excellent.
 >
 > I mention this because while arranging some piece of music
recently, I noticed that Org-mode might be helpful in this context
- it is probably already possible by tweaking org-babel a bit:
lilypond encourages the user to structure music in a way that
lends itself rather naturally to processing with Org-mode - you
can assign a theme, a few bar with notes or even whole voices to
variables and use them repeatedly. And imagine using Org-mode's
outline capabilities to structure a piece of music. Exporting an
org-file with lilypond-snippets in it to PDF or HTML might also be
an interesting option.
 >
 > I have not yet put any effort into it and just wanted to find
out if anybody apart from me finds the combination of Org-mode and
lilypond (potentially) exciting.

I think this is very exciting.


___
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

Re: [Orgmode] quotation marks in LaTeX (again)

[Carsten Dominik]

On Oct 4, 2010, at 10:00 PM, Don March wrote:


There's been some talk about quotation marks when exporting to LaTeX,
but I've noticed some issues in addition (I think) to those mentioned
by others.

"'a quote' inside a quote"
is exported to LaTeX as
``'a quote' inside a quote''
but should be
``\,`a quote' inside a quote''

Similarly,
"a quote that ends with 'a quote'"
is exported as
``a quote that ends with `a quote'''
but should be
``a quote that ends with `a quote'\,''

Implementing the \enquote solution proposed by Sven Bretfeld


Could you please point me to that earlier discussion?  I cannot
find it right now.

THanks!

- Carsten


would a
fix for this, but that would probably have to be optional.  So I was
working on a regexp fix for this, but then I realized that there's a
host of cases where the beginning quote isn't recognized as beginning
because there isn't whitespace in front of it, such as when a quote
starts a parenthetical ("like this").  Maybe the solution is to use
the list of "allowed chars in pre" from
org-emphasis-regexp-components?

Don

___
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



___
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

Re: [Orgmode] [PATCH] tag input separators

[Carsten Dominik]

On Oct 4, 2010, at 11:44 AM, Richard Riley wrote:



I dont know if it would be generally useful, but a tiny little tweak  
to
tag editing in order to allow "," as a seperator when typing in tags  
via

C-c C-q TAB "free entry" interface. "," is certainly easier for me to
use but I dont know about the ramifications of it as a legal character
in a tag name.


Sure, why not, this is not a problem.  I have applied this patch,
with a small extension that should also make it work in other
tag completion situations.

If you want to do me a favor, please identify one or two places in
the manual where this should be mentioned and make me a patch
for that file?

Cheers

- Carsten




--8<---cut here---start->8---
Modified lisp/org.el
diff --git a/lisp/org.el b/lisp/org.el
index 3f24ee8..fa3d364 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12792,6 +12792,8 @@ With prefix ARG, realign all tags in  
headings in the current buffer."

  ;; No boolean logic, just a list
  (setq tags (replace-match ":" t t tags

+  (setq tags (replace-regexp-in-string "[ ,]" ":" tags))
+
  (if org-tags-sort-function
  (setq tags (mapconcat 'identity
(sort (org-split-string tags (org-re 
"[^[:alnum:]...@#%]+"))
--8<---cut here---end--->8---

I replaced space too but that isnt currently allowed anyway.

regards

r.


___
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



___
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

Re: [Orgmode] Re: [PATCH] Alphabetical ordered lists

[Carsten Dominik]

On Oct 4, 2010, at 7:18 PM, Nicolas Goaziou wrote:


Carsten Dominik writes:



I think it would be appropriate in this case to simply throw an
error and let the user clean up with undo.


Certainly, but this still means that any 27+ items list will never be
able to complete a full bullet cycle as the user will have to undo
each time alphabetical bullets are reached. It could perhaps start
again at letter 'a'...


Ok, we could force the list to become numbered when someone tries to  
cycle it into
a,b,...  THis does not mean that you'd have to count in advance, you  
could simply
try the renumbering and when stepping over z throw an exception that  
will force the

list to move to the next state which would be numbers.




Nicolas, would you *object* against a patch by Nathaniel that
implements this? You are Mr lists now, so your green light will be
needed.


I wouldn't object against it as some people are finding it useful and
as it won't be turned on by default (if I remember correctly).


Yes, we sould not turn it on by default because it might bahave strange
under some circumstances.



But I can't help thinking this could lead to unexpected results in
some cases (admittedly less than when alpha bullets could be any size
long).


It definitely will.

Here is an alternative idea.  Nathaniel, what do you
think about this: We could keep the numbering as we
have it in the Org file, but introduce something like [...@a]
in the first item that will convert the numbering
into a,b,... upon export to ASCII, HTML, maybe even LaTeX
(even though I think LaTeX demands some consistency here
and prefers to have the global setup decide how lists work).
Hell, we could even use [...@a] for capitals and [...@i] and [...@i]
for roman numbering :)

- Carsten


___
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

Re: [Orgmode] quotation marks in LaTeX (again)

[Sven Bretfeld]

Hi Don

Don March  writes:

> Implementing the \enquote solution proposed by Sven Bretfeld would a
> fix for this, but that would probably have to be optional.  So I was
> working on a regexp fix for this, but then I realized that there's a
> host of cases where the beginning quote isn't recognized as beginning
> because there isn't whitespace in front of it, such as when a quote
> starts a parenthetical ("like this").  Maybe the solution is to use
> the list of "allowed chars in pre" from
> org-emphasis-regexp-components?

The different styles of quotation marks needed for different languages
might also be a problem for a regexp solution. I'm using the \enquote
method since quite a while and write English and German text in that way
without further user interference. \enquote just picks the correct
version in dependency of the babel environment.

Greetings,

Sven

___
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

[Accepted] [Orgmode] tag input separators

[Carsten Dominik]

Patch 297 (http://patchwork.newartisans.com/patch/297/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3Ci8c7me%24g3n%241%40dough.gmane.org%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode] tag input separators
> Date: Mon, 04 Oct 2010 14:44:44 -
> From: Richard Riley 
> X-Patchwork-Id: 297
> Message-Id: 
> To: emacs-orgmode@gnu.org
> 
> I dont know if it would be generally useful, but a tiny little tweak to
> tag editing in order to allow "," as a seperator when typing in tags via
> C-c C-q TAB "free entry" interface. "," is certainly easier for me to
> use but I dont know about the ramifications of it as a legal character
> in a tag name.
> 
> 
> --8<---cut here---start->8---
>   Modified lisp/org.el
> --8<---cut here---end--->8---
> 
> I replaced space too but that isnt currently allowed anyway.
> 
> regards
> 
> r.
> 
> 
> diff --git a/lisp/org.el b/lisp/org.el
> index 3f24ee8..fa3d364 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -12792,6 +12792,8 @@ With prefix ARG, realign all tags in headings in the 
> current buffer."
> ;; No boolean logic, just a list
> (setq tags (replace-match ":" t t tags
>  
> +  (setq tags (replace-regexp-in-string "[ ,]" ":" tags))
> +
>(if org-tags-sort-function
> (setq tags (mapconcat 'identity
>   (sort (org-split-string tags (org-re 
> "[^[:alnum:]...@#%]+"))
> 

___
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

Re: [Orgmode] ELPA Howto

[Jambunathan K]

Carsten 

Reworked the changes based on your feedback. Customize to your tastes.

Jambunathan K.

>From 1121461037e0308054afeabf8c67bd1a568dd9b1 Mon Sep 17 00:00:00 2001
From: Jambunathan K 
Date: Tue, 5 Oct 2010 15:33:08 +0530
Subject: [PATCH] Support for elpa-compatible tarballs

* Makefile (pkg): New target for creating elpa-compatible tarball.
---
 Makefile |   24 
 1 files changed, 24 insertions(+), 0 deletions(-)

diff --git a/Makefile b/Makefile
index 1c1f317..3b92534 100644
--- a/Makefile
+++ b/Makefile
@@ -164,6 +164,19 @@ CARDFILES   = doc/orgcard.tex doc/orgcard.pdf doc/orgcard_letter.pdf
 TEXIFILES   = doc/org.texi
 INFOFILES   = doc/org
 
+# Package Manager (ELPA)
+PKG_TAG = $(shell date +%Y%m%d)
+PKG_DOC = "Outline-based notes management and organizer"
+PKG_REQ = "nil"
+
+PKG_FILES = $(LISPFILES0)		\
+doc/dir doc/org		\
+doc/pdflayout.sty		\
+doc/org.pdf			\
+doc/orgguide.pdf		\
+doc/orgcard.tex		\
+doc/orgcard.pdf		\
+doc/orgcard_letter.pdf
 
 .SUFFIXES: .el .elc .texi
 SHELL = /bin/sh
@@ -325,6 +338,17 @@ distfile:
 	zip -r org-$(TAG).zip org-$(TAG)
 	gtar zcvf org-$(TAG).tar.gz org-$(TAG)
 
+pkg:
+	@if [ "X$(PKG_TAG)" = "X" ]; then echo "*** No tag ***"; exit 1; fi
+	touch doc/org.texi doc/orgcard.tex # force update
+	${MAKE} info
+	${MAKE} doc
+	rm -rf org-$(PKG_TAG) org-$(PKG_TAG).tar
+	$(MKDIR) org-$(PKG_TAG)
+	cp -r $(PKG_FILES) org-$(PKG_TAG)
+	echo "(define-package \"org\" \"$(PKG_TAG)\" \"$(PKG_DOC)\" $(PKG_REQ))" > org-$(PKG_TAG)/org-pkg.el
+	tar cf org-$(PKG_TAG).tar org-$(PKG_TAG) --remove-files
+
 makerelease:
 	@if [ "X$(TAG)" = "X" ]; then echo "*** No tag ***"; exit 1; fi
 	${MAKE} distfile
-- 
1.7.2.3

___
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

[Orgmode] Version string (was Re: ELPA Howto)

[Jambunathan K]

In the context of ELPA packages, I think there might be a need to
revisit how orgmode's version string is defined.

For example, 7.01h wouldn't be successfully parsed by (version-to-list
...) which the package manager uses internally.

So 7.01h could be mapped to 7.0.1.8 or 7.1.8.

,[ C-h f version-to-list RET ]
| version-to-list is a compiled Lisp function in `subr.el'.
| 
| (version-to-list VER)
| 
| Convert version string VER into an integer list.
| 
| The version syntax is given by the following EBNF:
| 
|VERSION ::= NUMBER ( SEPARATOR NUMBER )*.
| 
|NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+.
| 
|SEPARATOR ::= `version-separator' (which see)
|  | `version-regexp-alist' (which see).
| 
| The NUMBER part is optional if SEPARATOR is a match for an element
| in `version-regexp-alist'.
| 
| As an example of valid version syntax:
| 
|1.0pre2   1.0.7.5   22.8beta3   0.9alpha1   6.9.30Beta
| 
| As an example of invalid version syntax:
| 
|1.0prepre2   1.0..7.5   22.8X3   alpha3.2   .5
| 
| As an example of version convertion:
| 
|String VersionInteger List Version
|"1.0.7.5" (1  0  7 5)
|"1.0pre2" (1  0 -1 2)
|"1.0PRE2" (1  0 -1 2)
|"22.8beta3"   (22 8 -2 3)
|"22.8Beta3"   (22 8 -2 3)
|"0.9alpha1"   (0  9 -3 1)
|"0.9AlphA1"   (0  9 -3 1)
|"0.9alpha"(0  9 -3)
| 
| See documentation for `version-separator' and `version-regexp-alist'.
| 
| [back]
`

Jambunathan K.

___
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

[Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> Thanks for the patch! I would certainly have a better way to process these
> files.

Could you make your latest sentence more explicit?


> 1. Can we run bibtex only if we have an indication that it might be needed?
>Maybe by looking at the output of the first LaTeX run? Hmm, maybe this
>would not work if only the bibtex database file was changed.

I guess things in that direction are entirely possible. I don't use bibtex
yet, but will have a look at a better integration.


> 2. The contrill structures you are using, are they standard shell or is bash
>needed for this?

Good question!  Yes, I implicitly wrote in bash. That won't work for sure in
Windows...

But, then, how do we do for writing such shells in Emacs?  Go to Emacs's
builtin shell?  I have no experience with it, but I can have a look, except:
how would we be sure that the preferred shell of the user is that one?


> 3. Maybe we can extract a useful error message if the last PDFLaTeX run
>still contains problems? Maybe even load the log file in this case?

For sure, such behaviors would be a great, in case of failures.

Best regards,
  Seb

>> Here is my (much) better proposition:
>>
>> --8<---cut here---start->8---
>> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
>> index 9a62457..0a2c5fe 100644
>> --- a/lisp/org-latex.el
>> +++ b/lisp/org-latex.el
>> @@ -455,25 +455,35 @@ allowed.  The default we use here encompasses both."
>>   :group 'org-export-latex
>>   :group 'org-export)
>>
>> +(defcustom org-latex-pdf-max-runs 3
>> +  "Maximum number of times PDFLaTeX is run after BibTeX."
>> +  :group 'org-export-pdf
>> +  :type 'int)
>> +
>> (defcustom org-latex-to-pdf-process
>> -  '("pdflatex -interaction nonstopmode -output-directory %o %f"
>> -"pdflatex -interaction nonstopmode -output-directory %o %f")
>> +  `("pdflatex -interaction nonstopmode -output-directory %o %f"
>> +"bibtex %b"
>> +,(concat "let COUNTER=0; while (grep -e \"Rerun .* cross-
>> references\" %b.log > /dev/null); do if [ $COUNTER -eq "
>> + (int-to-string org-latex-pdf-max-runs)
>> + " ]; then break; fi; pdflatex -interaction nonstopmode
>> -output-directory %o %f; let COUNTER=COUNTER+1; done"))
>>   "Commands to process a LaTeX file to a PDF file.
>> This is a list of strings, each of them will be given to the shell
>> as a command.  %f in the command will be replaced by the full file name, %b
>> by the file base name (i.e. without extension) and %o by the base directory
>> of the file.
>> The reason why this is a list is that it usually takes several runs of
>> -pdflatex, maybe mixed with a call to bibtex.  Org does not have a clever
>> -mechanism to detect which of these commands have to be run to get to a
>> stable
>> -result, and it also does not do any error checking.
>> +pdflatex, mixed with a call to bibtex.  Org does now have a clever
>> mechanism
>> +to detect how many times the document has to be compiled to get to a stable
>> +result for the cross-references.  Moreover, the number of compilations
>> after
>> +bibtex is limited to 3 by default (see `org-latex-pdf-max-runs' for more).
>> +Though, it does not do any error checking.
>>
>> Alternatively, this may be a Lisp function that does the processing, so you
>> could use this to apply the machinery of AUCTeX or the Emacs LaTeX mode.
>> This function should accept the file name as its single argument."
>>   :group 'org-export-pdf
>>   :type '(choice (repeat :tag "Shell command sequence"
>> -  (string :tag "Shell command"))
>> + (string :tag "Shell command"))
>>   (function)))
>>
>> (defcustom org-export-pdf-logfiles
>> --8<---cut here---end--->8---
>>
>> Enhancements:
>>
>> - variable to limit the number of PDFLaTeX runs (3, by default)
>>
>>  Though, the way it is evaluated, you need to set it before calling
>> org-latex
>>  (before defining org-latex-to-pdf-process). Not a problem, IMHO. Maybe
>> there
>>  are better ways, though?
>>
>> - real standard sequence to compile the doc:
>>
>>  + one call to PDFLaTeX
>>  + one call to BibTeX
>>  + as many calls as needed to PDFLaTeX (max 3)

-- 
Sébastien Vauban


___
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

[Orgmode] [BUG] Table formula with org-hh:mm-string-to-minutes

[Sébastien Vauban]

Hello,

I use the following table and formulas to convert HH:MM times to fractional
times, so that I can sum up the times (and convert them to money...)

| Task   | *HH:MM* | *Frac* |
|+-+|
| Item 1 |   20:27 |  20.45 |
| Item 2 |2:25 |   2.42 |
| Item 3 |2:07 |   2.12 |
| Item 4 |0:19 |   0.00 |
| Item 5 |0:43 |   0.72 |
| Item 6 |0:05 |   0.08 |
| Item 7 |0:32 |   0.53 |
| Item 8 |0:16 |   0.27 |
|+-+|
|| |  26.59 |
#+TBLFM: $3='(/ (float (org-hh:mm-string-to-minutes $2)) 
60.);%.2f::@5$3=0.00;%.2f::@10$3=vsum(@-...@-ii)

Everything is fine... but the item 4: 19 minutes get converted to 0.00 hour...
Why!?

It's not even because it's a small figure that would be rounded, or some such,
as 0:05 is well converted (to 0.08 hour).

Do you have a hint?

Best regards,
  Seb

-- 
Sébastien Vauban


___
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

Re: [Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Matthew Leifer]

Hi,

I don't know if you are aware, but there is a utility called texi2dvi that
figures out how many times LaTeX, bibtex, etc. need to be run and
automatically runs them the correct number of times for you.  It also has an
option -p that uses pdflatex and generates pdf instead of dvi.  In my
opinion, it would be better to make use of this rather than writing new code
to do this, as they have thought about all the edge cases in far more detail
than is possible here.  It is possible that some LaTeX installations do not
come with texi2dvi, but it does come with the full TeXLive installation so
plenty of people are likely to have it installed.  If you want to avoid this
breaking on systems that do not have texi2dvi installed then you could just
check for it, use it if it is available and, if not, give the user a warning
message that they may get better results if they install texi2dvi whilst
using the existing code.

Best,

Matt Leifer

2010/10/5 Sébastien Vauban 

> Hi Carsten,
>
> Carsten Dominik wrote:
> > Thanks for the patch! I would certainly have a better way to process
> these
> > files.
>
> Could you make your latest sentence more explicit?
>
>
> > 1. Can we run bibtex only if we have an indication that it might be
> needed?
> >Maybe by looking at the output of the first LaTeX run? Hmm, maybe this
> >would not work if only the bibtex database file was changed.
>
> I guess things in that direction are entirely possible. I don't use bibtex
> yet, but will have a look at a better integration.
>
>
> > 2. The contrill structures you are using, are they standard shell or is
> bash
> >needed for this?
>
> Good question!  Yes, I implicitly wrote in bash. That won't work for sure
> in
> Windows...
>
> But, then, how do we do for writing such shells in Emacs?  Go to Emacs's
> builtin shell?  I have no experience with it, but I can have a look,
> except:
> how would we be sure that the preferred shell of the user is that one?
>
>
> > 3. Maybe we can extract a useful error message if the last PDFLaTeX run
> >still contains problems? Maybe even load the log file in this case?
>
> For sure, such behaviors would be a great, in case of failures.
>
> Best regards,
>  Seb
>
> >> Here is my (much) better proposition:
> >>
> >> --8<---cut here---start->8---
> >> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> >> index 9a62457..0a2c5fe 100644
> >> --- a/lisp/org-latex.el
> >> +++ b/lisp/org-latex.el
> >> @@ -455,25 +455,35 @@ allowed.  The default we use here encompasses
> both."
> >>   :group 'org-export-latex
> >>   :group 'org-export)
> >>
> >> +(defcustom org-latex-pdf-max-runs 3
> >> +  "Maximum number of times PDFLaTeX is run after BibTeX."
> >> +  :group 'org-export-pdf
> >> +  :type 'int)
> >> +
> >> (defcustom org-latex-to-pdf-process
> >> -  '("pdflatex -interaction nonstopmode -output-directory %o %f"
> >> -"pdflatex -interaction nonstopmode -output-directory %o %f")
> >> +  `("pdflatex -interaction nonstopmode -output-directory %o %f"
> >> +"bibtex %b"
> >> +,(concat "let COUNTER=0; while (grep -e \"Rerun .* cross-
> >> references\" %b.log > /dev/null); do if [ $COUNTER -eq "
> >> + (int-to-string org-latex-pdf-max-runs)
> >> + " ]; then break; fi; pdflatex -interaction nonstopmode
> >> -output-directory %o %f; let COUNTER=COUNTER+1; done"))
> >>   "Commands to process a LaTeX file to a PDF file.
> >> This is a list of strings, each of them will be given to the shell
> >> as a command.  %f in the command will be replaced by the full file name,
> %b
> >> by the file base name (i.e. without extension) and %o by the base
> directory
> >> of the file.
> >> The reason why this is a list is that it usually takes several runs of
> >> -pdflatex, maybe mixed with a call to bibtex.  Org does not have a
> clever
> >> -mechanism to detect which of these commands have to be run to get to a
> >> stable
> >> -result, and it also does not do any error checking.
> >> +pdflatex, mixed with a call to bibtex.  Org does now have a clever
> >> mechanism
> >> +to detect how many times the document has to be compiled to get to a
> stable
> >> +result for the cross-references.  Moreover, the number of compilations
> >> after
> >> +bibtex is limited to 3 by default (see `org-latex-pdf-max-runs' for
> more).
> >> +Though, it does not do any error checking.
> >>
> >> Alternatively, this may be a Lisp function that does the processing, so
> you
> >> could use this to apply the machinery of AUCTeX or the Emacs LaTeX mode.
> >> This function should accept the file name as its single argument."
> >>   :group 'org-export-pdf
> >>   :type '(choice (repeat :tag "Shell command sequence"
> >> -  (string :tag "Shell command"))
> >> + (string :tag "Shell command"))
> >>   (function)))
> >>
> >> (defcustom org-export-pdf-logfiles
> >> --8<---cut here---end--->8---
> >>
> >> Enhan

[Orgmode] Re: quotation marks in LaTeX (again)

[Don March]

"Sven Bretfeld"  writes:

> The different styles of quotation marks needed for different languages
> might also be a problem for a regexp solution. I'm using the \enquote
> method since quite a while and write English and German text in that way
> without further user interference. \enquote just picks the correct
> version in dependency of the babel environment.

Definitely--I agree that the csquotes solution is probably best, but
since Carsten said that would probably be an option there needs to be a
vanilla LaTeX solution too.


___
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

Re: [Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Carsten Dominik]

On Oct 5, 2010, at 2:46 PM, Sébastien Vauban wrote:


Hi Carsten,

Carsten Dominik wrote:
Thanks for the patch! I would certainly have a better way to  
process these

files.


I would certainly *like very much to have your* better way to process  
it.


Sorry about that confusing sentence...



Could you make your latest sentence more explicit?


1. Can we run bibtex only if we have an indication that it might be  
needed?
  Maybe by looking at the output of the first LaTeX run? Hmm, maybe  
this

  would not work if only the bibtex database file was changed.


I guess things in that direction are entirely possible. I don't use  
bibtex

yet, but will have a look at a better integration.


2. The contrill structures you are using, are they standard shell  
or is bash

  needed for this?


Good question!  Yes, I implicitly wrote in bash. That won't work for  
sure in

Windows...

But, then, how do we do for writing such shells in Emacs?  Go to  
Emacs's
builtin shell?  I have no experience with it, but I can have a look,  
except:

how would we be sure that the preferred shell of the user is that one?


I think the safe way would be to capture output of the run to an Emacs  
buffer and study it there.  this is what AUCTeX is doing, I think.


Anyway, I think your new way is already better than the old one.

Cheers.

- Carsten




3. Maybe we can extract a useful error message if the last PDFLaTeX  
run

  still contains problems? Maybe even load the log file in this case?


For sure, such behaviors would be a great, in case of failures.

Best regards,
 Seb


Here is my (much) better proposition:

--8<---cut here---start->8---
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 9a62457..0a2c5fe 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -455,25 +455,35 @@ allowed.  The default we use here  
encompasses both."

 :group 'org-export-latex
 :group 'org-export)

+(defcustom org-latex-pdf-max-runs 3
+  "Maximum number of times PDFLaTeX is run after BibTeX."
+  :group 'org-export-pdf
+  :type 'int)
+
(defcustom org-latex-to-pdf-process
-  '("pdflatex -interaction nonstopmode -output-directory %o %f"
-"pdflatex -interaction nonstopmode -output-directory %o %f")
+  `("pdflatex -interaction nonstopmode -output-directory %o %f"
+"bibtex %b"
+,(concat "let COUNTER=0; while (grep -e \"Rerun .* cross-
references\" %b.log > /dev/null); do if [ $COUNTER -eq "
+ (int-to-string org-latex-pdf-max-runs)
+ " ]; then break; fi; pdflatex -interaction nonstopmode
-output-directory %o %f; let COUNTER=COUNTER+1; done"))
 "Commands to process a LaTeX file to a PDF file.
This is a list of strings, each of them will be given to the shell
as a command.  %f in the command will be replaced by the full file  
name, %b
by the file base name (i.e. without extension) and %o by the base  
directory

of the file.
The reason why this is a list is that it usually takes several  
runs of
-pdflatex, maybe mixed with a call to bibtex.  Org does not have a  
clever
-mechanism to detect which of these commands have to be run to get  
to a

stable
-result, and it also does not do any error checking.
+pdflatex, mixed with a call to bibtex.  Org does now have a clever
mechanism
+to detect how many times the document has to be compiled to get  
to a stable
+result for the cross-references.  Moreover, the number of  
compilations

after
+bibtex is limited to 3 by default (see `org-latex-pdf-max-runs'  
for more).

+Though, it does not do any error checking.

Alternatively, this may be a Lisp function that does the  
processing, so you
could use this to apply the machinery of AUCTeX or the Emacs LaTeX  
mode.

This function should accept the file name as its single argument."
 :group 'org-export-pdf
 :type '(choice (repeat :tag "Shell command sequence"
- (string :tag "Shell command"))
+(string :tag "Shell command"))
 (function)))

(defcustom org-export-pdf-logfiles
--8<---cut here---end--->8---

Enhancements:

- variable to limit the number of PDFLaTeX runs (3, by default)

Though, the way it is evaluated, you need to set it before calling
org-latex
(before defining org-latex-to-pdf-process). Not a problem, IMHO.  
Maybe

there
are better ways, though?

- real standard sequence to compile the doc:

+ one call to PDFLaTeX
+ one call to BibTeX
+ as many calls as needed to PDFLaTeX (max 3)


--
Sébastien Vauban


___
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


- Carsten




___
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

[Orgmode] Re: quotation marks in LaTeX (again)

[Don March]

Carsten Dominik  writes:

> On Oct 4, 2010, at 10:00 PM, Don March wrote:
>
>> Implementing the \enquote solution proposed by Sven Bretfeld
>
> Could you please point me to that earlier discussion?  I cannot
> find it right now.
>

Sure--"[feature request] Quotation marks in LaTeX export", 2010-01-22,
http://article.gmane.org/gmane.emacs.orgmode/21588

>
>> So I was working on a regexp fix for this, but then I realized that
>> there's a host of cases where the beginning quote isn't recognized as
>> beginning because there isn't whitespace in front of it, such as when
>> a quote starts a parenthetical ("like this").  Maybe the solution is
>> to use the list of "allowed chars in pre" from
>> org-emphasis-regexp-components?
>>

I'd be happy to work on this, by the way, but don't want to start on a
solution that other people don't want.


___
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

Re: [Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Indraneel Majumdar]

 texi2dvi is also on my minimal MikTex system, I'd certainly love a 
patch that uses it instead of a shell script (although I also have 
cygwin too)..


On 2010-10-05 20:00, Matthew Leifer wrote:

Hi,

I don't know if you are aware, but there is a utility called texi2dvi 
that figures out how many times LaTeX, bibtex, etc. need to be run and 
automatically runs them the correct number of times for you.  It also 
has an option -p that uses pdflatex and generates pdf instead of dvi. 
 In my opinion, it would be better to make use of this rather than 
writing new code to do this, as they have thought about all the edge 
cases in far more detail than is possible here.  It is possible that 
some LaTeX installations do not come with texi2dvi, but it does come 
with the full TeXLive installation so plenty of people are likely to 
have it installed.  If you want to avoid this breaking on systems that 
do not have texi2dvi installed then you could just check for it, use 
it if it is available and, if not, give the user a warning message 
that they may get better results if they install texi2dvi whilst using 
the existing code.


Best,

Matt Leifer

2010/10/5 Sébastien Vauban >


Hi Carsten,

Carsten Dominik wrote:
> Thanks for the patch! I would certainly have a better way to
process these
> files.

Could you make your latest sentence more explicit?


> 1. Can we run bibtex only if we have an indication that it might
be needed?
>Maybe by looking at the output of the first LaTeX run? Hmm,
maybe this
>would not work if only the bibtex database file was changed.

I guess things in that direction are entirely possible. I don't
use bibtex
yet, but will have a look at a better integration.


> 2. The contrill structures you are using, are they standard
shell or is bash
>needed for this?

Good question!  Yes, I implicitly wrote in bash. That won't work
for sure in
Windows...

But, then, how do we do for writing such shells in Emacs?  Go to
Emacs's
builtin shell?  I have no experience with it, but I can have a
look, except:
how would we be sure that the preferred shell of the user is that one?


> 3. Maybe we can extract a useful error message if the last
PDFLaTeX run
>still contains problems? Maybe even load the log file in this
case?

For sure, such behaviors would be a great, in case of failures.

Best regards,
 Seb

>> Here is my (much) better proposition:
>>
>> --8<---cut here---start->8---
>> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
>> index 9a62457..0a2c5fe 100644
>> --- a/lisp/org-latex.el
>> +++ b/lisp/org-latex.el
>> @@ -455,25 +455,35 @@ allowed.  The default we use here
encompasses both."
>>   :group 'org-export-latex
>>   :group 'org-export)
>>
>> +(defcustom org-latex-pdf-max-runs 3
>> +  "Maximum number of times PDFLaTeX is run after BibTeX."
>> +  :group 'org-export-pdf
>> +  :type 'int)
>> +
>> (defcustom org-latex-to-pdf-process
>> -  '("pdflatex -interaction nonstopmode -output-directory %o %f"
>> -"pdflatex -interaction nonstopmode -output-directory %o %f")
>> +  `("pdflatex -interaction nonstopmode -output-directory %o %f"
>> +"bibtex %b"
>> +,(concat "let COUNTER=0; while (grep -e \"Rerun .* cross-
>> references\" %b.log > /dev/null); do if [ $COUNTER -eq "
>> + (int-to-string org-latex-pdf-max-runs)
>> + " ]; then break; fi; pdflatex -interaction
nonstopmode
>> -output-directory %o %f; let COUNTER=COUNTER+1; done"))
>>   "Commands to process a LaTeX file to a PDF file.
>> This is a list of strings, each of them will be given to the shell
>> as a command.  %f in the command will be replaced by the full
file name, %b
>> by the file base name (i.e. without extension) and %o by the
base directory
>> of the file.
>> The reason why this is a list is that it usually takes several
runs of
>> -pdflatex, maybe mixed with a call to bibtex.  Org does not
have a clever
>> -mechanism to detect which of these commands have to be run to
get to a
>> stable
>> -result, and it also does not do any error checking.
>> +pdflatex, mixed with a call to bibtex.  Org does now have a clever
>> mechanism
>> +to detect how many times the document has to be compiled to
get to a stable
>> +result for the cross-references.  Moreover, the number of
compilations
>> after
>> +bibtex is limited to 3 by default (see
`org-latex-pdf-max-runs' for more).
>> +Though, it does not do any error checking.
>>
>> Alternatively, this may be a Lisp function that does the
processing, so you
>> could use this to apply the machinery of AUCTeX or the Emacs
LaTeX mode.

Re: [Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Carsten Dominik]

Hi Matthew,

you are completely right, we are re-inventing wheels here.

I have just pushed a fix which will use texi2dvi when available.
The echo area will now also give an indication of the kinds
of errors that happened during the final pdflatex run.

This is a big improvement, thanks to Sebastian for kicking
off this discussion, and to all who contributed.

Please test the new processing and let me know if there
are problems.

- Carsten

On Oct 5, 2010, at 4:30 PM, Matthew Leifer wrote:


Hi,

I don't know if you are aware, but there is a utility called  
texi2dvi that figures out how many times LaTeX, bibtex, etc. need to  
be run and automatically runs them the correct number of times for  
you.  It also has an option -p that uses pdflatex and generates pdf  
instead of dvi.  In my opinion, it would be better to make use of  
this rather than writing new code to do this, as they have thought  
about all the edge cases in far more detail than is possible here.   
It is possible that some LaTeX installations do not come with  
texi2dvi, but it does come with the full TeXLive installation so  
plenty of people are likely to have it installed.  If you want to  
avoid this breaking on systems that do not have texi2dvi installed  
then you could just check for it, use it if it is available and, if  
not, give the user a warning message that they may get better  
results if they install texi2dvi whilst using the existing code.


Best,

Matt Leifer

2010/10/5 Sébastien Vauban 
Hi Carsten,

Carsten Dominik wrote:
> Thanks for the patch! I would certainly have a better way to  
process these

> files.

Could you make your latest sentence more explicit?


> 1. Can we run bibtex only if we have an indication that it might  
be needed?
>Maybe by looking at the output of the first LaTeX run? Hmm,  
maybe this

>would not work if only the bibtex database file was changed.

I guess things in that direction are entirely possible. I don't use  
bibtex

yet, but will have a look at a better integration.


> 2. The contrill structures you are using, are they standard shell  
or is bash

>needed for this?

Good question!  Yes, I implicitly wrote in bash. That won't work for  
sure in

Windows...

But, then, how do we do for writing such shells in Emacs?  Go to  
Emacs's
builtin shell?  I have no experience with it, but I can have a look,  
except:

how would we be sure that the preferred shell of the user is that one?


> 3. Maybe we can extract a useful error message if the last  
PDFLaTeX run
>still contains problems? Maybe even load the log file in this  
case?


For sure, such behaviors would be a great, in case of failures.

Best regards,
 Seb

>> Here is my (much) better proposition:
>>
>> --8<---cut here---start->8---
>> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
>> index 9a62457..0a2c5fe 100644
>> --- a/lisp/org-latex.el
>> +++ b/lisp/org-latex.el
>> @@ -455,25 +455,35 @@ allowed.  The default we use here  
encompasses both."

>>   :group 'org-export-latex
>>   :group 'org-export)
>>
>> +(defcustom org-latex-pdf-max-runs 3
>> +  "Maximum number of times PDFLaTeX is run after BibTeX."
>> +  :group 'org-export-pdf
>> +  :type 'int)
>> +
>> (defcustom org-latex-to-pdf-process
>> -  '("pdflatex -interaction nonstopmode -output-directory %o %f"
>> -"pdflatex -interaction nonstopmode -output-directory %o %f")
>> +  `("pdflatex -interaction nonstopmode -output-directory %o %f"
>> +"bibtex %b"
>> +,(concat "let COUNTER=0; while (grep -e \"Rerun .* cross-
>> references\" %b.log > /dev/null); do if [ $COUNTER -eq "
>> + (int-to-string org-latex-pdf-max-runs)
>> + " ]; then break; fi; pdflatex -interaction  
nonstopmode

>> -output-directory %o %f; let COUNTER=COUNTER+1; done"))
>>   "Commands to process a LaTeX file to a PDF file.
>> This is a list of strings, each of them will be given to the shell
>> as a command.  %f in the command will be replaced by the full  
file name, %b
>> by the file base name (i.e. without extension) and %o by the base  
directory

>> of the file.
>> The reason why this is a list is that it usually takes several  
runs of
>> -pdflatex, maybe mixed with a call to bibtex.  Org does not have  
a clever
>> -mechanism to detect which of these commands have to be run to  
get to a

>> stable
>> -result, and it also does not do any error checking.
>> +pdflatex, mixed with a call to bibtex.  Org does now have a clever
>> mechanism
>> +to detect how many times the document has to be compiled to get  
to a stable
>> +result for the cross-references.  Moreover, the number of  
compilations

>> after
>> +bibtex is limited to 3 by default (see `org-latex-pdf-max-runs'  
for more).

>> +Though, it does not do any error checking.
>>
>> Alternatively, this may be a Lisp function that does the  
processing, so you
>> could use this to apply the machinery of AUCTeX or the Emacs  
LaTeX mode.

>> This function should ac

[Orgmode] Re: custom postamble in HTML export

[Łukasz Stelmach]

Carsten Dominik  writes:

> On Oct 4, 2010, at 7:59 PM, Łukasz Stelmach wrote:
>
>> How about moving
>>
>>  (org-export-html-insert-plist-item opt-plist :postamble opt-plist)
>>
>> in org-html.el from line 1694 few lines up, just above the closing div
>> of the postamble. IMHO it makes more sense to put custom content into
>> the existing postamble than crating another one. There is usually only
>> one footer per page ;-)
>
> :postamble is meant to completely replace the automatic
> postamble Org creates,

But what if I like the information it puts there? Especially the
timestamp? there is the :timestamp option but honestly I couldn't figure
out how to use it. I puts some HTML with  in it
and that's all.

> so you would normally use it with
>
>:auto-postamble nil

How about putting this hint in the documentation or comments around the
code? Or maybe even a "XOR switch" that automaticall turns of one of
those options if the other is on.

-- 
Miłego dnia,
Łukasz Stelmach


___
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

[Orgmode] Re: Quoting formula "cookies" in table?

[Achim Gratz]

Carsten Dominik  writes:
[...]
> The best way to deal with this is:
>
> * Table Test
>
>  |-+--|
>  | unrelated 1 | ~>=~ |
>  | Test1   | ~=~  |
[...]

Ah, thank you -- I've settled for *bold* instead since that is a bit
more pleasing in the HTML output.  Now that I export the file to HTML
nobody gets to see the org file anymore, so while it looks a bit clumsy
in the source I can live with that.

It would still be nice if there was a way to quote without changing the
output or to just disable the formula mechanism entirely for a table,
but I recognize that these things are very deeply embedded into the
table code and not so easy to change...


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds


___
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

Re: [Orgmode] Re: Quoting formula "cookies" in table?

[Carsten Dominik]

On Oct 5, 2010, at 7:10 PM, Achim Gratz wrote:


Carsten Dominik  writes:
[...]

The best way to deal with this is:

* Table Test

|-+--|
| unrelated 1 | ~>=~ |
| Test1   | ~=~  |

[...]

Ah, thank you -- I've settled for *bold* instead since that is a bit
more pleasing in the HTML output.  Now that I export the file to HTML
nobody gets to see the org file anymore, so while it looks a bit  
clumsy

in the source I can live with that.

It would still be nice if there was a way to quote without changing  
the

output or to just disable the formula mechanism entirely for a table,
but I recognize that these things are very deeply embedded into the
table code and not so easy to change...


Don't forget that this is Org-mode, so pretty much everything can be  
changed.


:-)

(setq org-table-formula-evaluate-inline nil)

might do this - I am not completely sure


- Carsten


___
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

[Orgmode] [Feature Request] Cross headings in tables

[Achim Gratz]

Now that I've started exporting some org files (to HTML mostly), I run
into some limitations here and there.  I've worked around most of them,
but have not been able to do anything about this (other than editing the
resulting HTML):

I have some tables where I used (without thinking much about it)
cross headings like this:

|--+-+-|
| Header   | some more   | and more|
| actually | multi-line headings | just work!  |
|--+-+-|
| item | stuff   | things  |
| etc. | pp. | ad nauseam  |
|--+-+-|
| Header   | to keep | things together |
|--+-+-|
| ...  | | |
|  | ... | |
|  | | ... |
|--+-+-|

I don't want to rip these apart into separate tables since that causes
the different parts to all have different widths (both in the source and
the export) and I really need these to line up and be just a single
table.

I guess that I could somehow manage to use the "splicing" of tables to
get the HTML export done, but I'd have that problem again for each
export backend.  Also, this would interrupt the table in the source and
make a formatting mess unless I'd define the column width for each of
the table parts by hand (which is equally undesirable).

So I'd like to have first-class cross headings, maybe like this:

|--+---+-|
| Header   | some more | and more|
|--+---+-|
| item | stuff | things  |
| etc. | pp.   | ad nauseam  |
|--+---+-|
|> Header  | to keep   | things together |
|--+---+-|
|  | ...   | |
|--+---+-|

So, the first heading would be determined by the first horizontal
separator inside the table (for backwards compatibility) and any
following heading would need get some special syntax (like the "|>"
above, but anything that doesn't collide with existing syntax will just
be fine I think).  If there's a heading marker before the first
horizontal separation, it should probably take precedence over the
backwards-compatible markup.  That would also enable to have table
headings without a separator, something that's not possible today.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada


___
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

[Orgmode] Re: custom postamble in HTML export

[Achim Gratz]

Łukasz Stelmach  writes:
> But what if I like the information it puts there? Especially the
> timestamp? there is the :timestamp option but honestly I couldn't figure
> out how to use it. I puts some HTML with  in it
> and that's all.

I don't know what was the intention, but I recognize those particular
comments very well: if you'd use html-helper-mode on that file, it will
put the modification date between those two comments on each save.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


___
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

Re: [Orgmode] bug: babel: Export of temporary buffers fails

[Eric Schulte]

Hi,

This issue is fixed in the "combined-testing" branch of the repository,
I hope to merge that branch into the master branch soon.

If anyone is interested, some of my thoughts on this commit which has
caused these couple of recent problems...  It seems that by using
org-links to find the location of a headline in an Org-mode file during
export I have introduced a handful of little bugs in the export process.
I think these have now been fixed but the fixes are a little bit hacky,
however I think that relying on org-mode links for finding these
headlines is still preferable to implementing a Babel-specific method of
linking back to the original export file.

Best -- Eric

Hsiu-Khuern Tang  writes:

> Hi Eric,
>
>
> Are you also seeing the problem reported at
> http://thread.gmane.org/gmane.emacs.orgmode/30855?  I checked out the
> latest git version and that problem still exists.
>
>
> I don't know how closely it is related to the problem in this thread,
> but it was caused by the same commit
> (efdf78172d9f7c0070c781d136a9b49a2a56fcc4) -- hoping you can shed some
> light on this.  Thanks!

___
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

Re: [Orgmode] Re: custom postamble in HTML export

[Carsten Dominik]

On Oct 5, 2010, at 6:43 PM, Łukasz Stelmach wrote:


Carsten Dominik  writes:


On Oct 4, 2010, at 7:59 PM, Łukasz Stelmach wrote:


How about moving

(org-export-html-insert-plist-item opt-plist :postamble opt-plist)

in org-html.el from line 1694 few lines up, just above the closing  
div
of the postamble. IMHO it makes more sense to put custom content  
into
the existing postamble than crating another one. There is usually  
only

one footer per page ;-)


:postamble is meant to completely replace the automatic
postamble Org creates,


But what if I like the information it puts there?


Then you have a case which Org currently does not handle.
You would have to introduce a new variable, org-export-html-postamble- 
extra
and arrange for it to be handled correctly with publishing properties  
etc etc.


- Carsten


___
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

Re: [Orgmode] [PATCH] Removed unecessary invocations of org-agenda-show.

[Matt Lundin]

Hi Carsten

Carsten Dominik  writes:

> On Sep 16, 2010, at 6:22 AM, Matthew Lundin wrote:
>
>> Hi Carsten,
>>
>> Carsten Dominik  writes:
>>
>>> On Sep 13, 2010, at 6:48 PM, Matt Lundin wrote:
>>>

 lisp/org-agenda.el (org-agenda-set-tags): Remove org-agenda-show to
 prevent
 disrupting windows and changing point in original buffer.
 (org-agenda-set-property): Same
 (org-agenda-set-effort): Same
 (org-agenda-toggle-archive-tag): Same

 When setting a tag in the agenda, org-mode displays the
 corresponding
 entry in the original org buffer by calling org-agenda-show. This
 has
 the unwelcome side-effect of disrupting the current window
 arrangement
 and changing the position of the point in the original buffer. This
 behavior is inconsistent with the that of org-agenda-todo, which
 makes
 all its changes "silently."
>>>
>>> I agree, but I am sure I used to have problems with something
>>> which is why this was added.
>>> Have you been running this patch for some time already?
>>> Without any problems like the agenda jumping to a wrong place in a
>>> org
>>> file or so?
>>
>> I haven't yet encountered any deleterious side effects, but I agree
>> that
>> this patch needs further consideration. I will do some additional
>> research/testing and return with a report. :)
>
> Hi Matt,
>
> any new about this patch?
>

I've looked at the code and can't see anything that org-agenda-show adds
to org-agenda-set-tags, apart from making the original buffer visible.

The function org-agenda-show calls org-agenda-goto, which grabs the
value of org-marker, jumps to the corresponding buffer and position, and
shows the next heading. The function org-agenda-set-tags does exactly
the same things in the background, except that it uses org-hd-marker
instead of org-marker.

As a point of comparison, org-agenda-todo seems to works just fine
without invoking org-agenda-show.

Unfortunately, there haven't been substantial changes to
org-agenda-set-tags since 4.12a (the beginning of the git repository),
so I can't reconstruct why the hack was added. 

I've not run into any troubles with the patch. I've tried moving
headlines around behind the agenda's back, changing multiple lines
before refreshing the agenda buffer, etc., all without issue. That's not
to say there aren't problems lurking out there somewhere; but detecting
them is beyond my abilities. :)

Best,
Matt


___
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

[Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Achim Gratz]

Matthew Leifer  writes:
> I don't know if you are aware, but there is a utility called texi2dvi
> that figures out how many times LaTeX, bibtex, etc. need to be run and
> automatically runs them the correct number of times for you.
[...]

You know, I've been using LaTeX for so long, but it never occured to me
that texi2dvi could actually be used for something other than, well,
texinfo files (and the manual doesn't really make much fuzz about that
either).  But it just works... this is _great_ news, thank you!  Now
I'll have to make AucTeX use this.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


___
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

[Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Achim Gratz]

Commit 59ba4125 lisp/org-latex.el raises warning during byte-compile:

In org-export-as-pdf:
org-latex.el:882:28:Warning: assignment to free variable `errors'
org-latex.el:882:47:Warning: reference to free variable `errors'


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


___
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

Re: [Orgmode] Re: Testing --- again...

[Eric Schulte]

Sebastian Rose  writes:

> "Eric Schulte"  writes:
>> Hi,
>>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>> I wonder, can we commit to the combined-testing branch, and if so could
>> we fold it into the master branch?  It would make my test driven bug
>> fixing a much smoother process, and would remove the need to rebase the
>> combined-testing branch against master and "git push -f" the changes up
>> to repo.or.cz which just feels wrong.
>
>
> Yes,  commit to that branch.  And yes, fold it into master,  if there
> are no objections.  In the worst case there will be more contributions.
>
>

Great, I've just merged this into the master branch.

>
>
>
> Eric, can we keep track with the ERT development for a little while?
> That will not be done automatically, right? 

Right, but at our leasure we can
1) cd into the testing/ert directory
2) git pull the latest version of ert into that directory
3) and on our next git commit the update will be committed to the git
   submodules

> But, as you know, Christian is working on it to get it into Emacs, and
> we should use the version that finally will make it there.
>
>   git submodule update
>
> Should that be called once to avoid conflicts?
>

Most users need never run

  git submodule init

or

  git subomdule update

however for those of us writing and using tests, we will want to run

  git submodule init

at least once, and run

  git submodule update

from time to time, to pull down newer versions of ert which may have
been committed to the org-mode repo by the process described at the top
of this email.

Best -- Eric

>
>
>   Sebastian

___
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

[Orgmode] Re: [BUG] Table formula with org-hh:mm-string-to-minutes

[Achim Gratz]

[repost -- sorry if this turns out a duplicate]

Sébastien Vauban 
writes:
> Everything is fine... but the item 4: 19 minutes get converted to 0.00
> hour...  Why!?

Because you told it to: remove ";%.2f::@5$3=0.00" from the formula and
live a happier life.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


___
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

[Orgmode] Re: [BUG] Table formula with org-hh:mm-string-to-minutes

[Štěpán Němec]

Sébastien Vauban 
writes:

> Hello,
>
> I use the following table and formulas to convert HH:MM times to fractional
> times, so that I can sum up the times (and convert them to money...)
>
> | Task   | *HH:MM* | *Frac* |
> |+-+|
> | Item 1 |   20:27 |  20.45 |
> | Item 2 |2:25 |   2.42 |
> | Item 3 |2:07 |   2.12 |
> | Item 4 |0:19 |   0.00 |
> | Item 5 |0:43 |   0.72 |
> | Item 6 |0:05 |   0.08 |
> | Item 7 |0:32 |   0.53 |
> | Item 8 |0:16 |   0.27 |
> |+-+|
> || |  26.59 |
> #+TBLFM: $3='(/ (float (org-hh:mm-string-to-minutes $2))
> 60.);%.2f::@5$3=0.00;%.2f::@10$3=vsum(@-...@-ii)

I don't really understand Calc and Org table formulas, but the
"%.2f::@5$3=0.00;" in there looks pretty suspicious, and removing it
fixes it for me. ;-)

Štěpán


___
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

[Orgmode] Re: arranging and publishing music with Org-mode and lilypond

[Shelagh Manton]

Christian Moe  writes:

> Hi,
>
> I've only used Lilypond for play, but I'd appreciate a Babel module
> for Lilypond, if someone writes one.
>
> My use case, for which I think Org is perfect, is maintaining simple
> song collections: short scores interspersed with lyrics, printable as
> a booklet. It is doable now but could clearly be done better with
> Babel.
>
> So if someone's thinking about ob-lilypond, integration with
> lilypond-book as a post-processing step would be useful.
>
> Yours,
> Christian

I have had an ob-LilyPond on my list of things to do for quite a while
now. If I have the next few days off, I will seriously look into it. 
But post integration with LilyPond-book is probably more than I would be
able to handle in the short term. 

Cheers
Shelagh
>
>
> On 10/4/10 4:31 AM, John Hendy wrote:
>>
>>
>> On Sun, Oct 3, 2010 at 8:24 PM, T.F. Torrey > > wrote:
>>
>> Hello,
>>
>>  > From: Stefan Vollmar mailto:voll...@nf.mpg.de>>
>>  > Date: Sun, 03 Oct 2010 00:26:39 +0200
>>  > Subject: [Orgmode] arranging and publishing music with Org-mode
>> and lilypond
>>  >
>>  > Dear all,
>>  >
>>  > I believe that many members of this list with an interest in
>> music (notation/composition) might find the http://lilypond.org
>> project "addictive" (in the nicest possible manner): the concept
>> is rather similar to writing TeX, there is very good Emacs support
>> (if you know where to look), it is all OpenSource, there is
>> extensive documentation (in LaTeX format with embedded lilypond
>> snippets), the print quality is excellent.
>>  >
>>  > I mention this because while arranging some piece of music
>> recently, I noticed that Org-mode might be helpful in this context
>> - it is probably already possible by tweaking org-babel a bit:
>> lilypond encourages the user to structure music in a way that
>> lends itself rather naturally to processing with Org-mode - you
>> can assign a theme, a few bar with notes or even whole voices to
>> variables and use them repeatedly. And imagine using Org-mode's
>> outline capabilities to structure a piece of music. Exporting an
>> org-file with lilypond-snippets in it to PDF or HTML might also be
>> an interesting option.
>>  >
>>  > I have not yet put any effort into it and just wanted to find
>> out if anybody apart from me finds the combination of Org-mode and
>> lilypond (potentially) exciting.
>>
>> I think this is very exciting.
>
> ___
> 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
>



___
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

[Orgmode] [babel] creating simple vectors in R

[Dan Davison]

I'd appreciate opinions from R users on the following org-babel-R
details:

Currently, Org tables, and lisp lists, are converted into data frames
when they are sent from Org to R, and we have no way to create simple
vectors such as c(1,2). I'd like to know whether users of org and R
would approve of the following change that makes simple R vectors
possible, or have other suggestions related to these issues.

With the patch below, there would be two ways to create a simple vector
in R. The most direct way is to pass a non-nested lisp list:

#+begin_src R :var x='(1 2) :results output
str(x)
#+end_src

CURRENT OUTPUT:
#+results:
: 'data.frame': 1 obs. of  2 variables:
:  $ V1: int 1
:  $ V2: int 2

NEW OUTPUT:
#+results:
:  num [1:2] 1 2

In addition, because babel's table-indexing code produces a non-nested
list when taking a one-dimensional slice, this would be another
situation in which a vector rather than data frame is created:

#+tblname: input-tab
| 1 | 3 |
| 2 | 4 |

#+begin_src R :var x=input-tab[0,] :results output
str(x)
#+end_src

CURRENT OUTPUT:
#+results:
: 'data.frame': 1 obs. of  2 variables:
:  $ V1: int 1
:  $ V2: int 3

NEW OUTPUT:
#+results:
:  num [1:2] 1 3

There's a possible argument that that's slightly at odds with R, since,
in R, a single row slice of a data frame is still a data frame.

A related issue is translating an Org table into a matrix rather than a
data frame in R. This can be done explicitly with a call to as.matrix in
the user's code, but if anyone feels that it would be helpful for babel
to automate this then do say so.

Dan


diff --git a/lisp/ob-R.el b/lisp/ob-R.el
index c709064..4b49af5 100644
--- a/lisp/ob-R.el
+++ b/lisp/ob-R.el
@@ -141,16 +141,18 @@ This function is called by `org-babel-execute-src-block'."
 (defun org-babel-R-assign-elisp (name value colnames-p rownames-p)
   "Construct R code assigning the elisp VALUE to a variable named NAME."
   (if (listp value)
-  (let ((transition-file (org-babel-temp-file "R-import-")))
-;; ensure VALUE has an orgtbl structure (depth of at least 2)
-(unless (listp (car value)) (setq value (list value)))
-(with-temp-file transition-file
-  (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
-  (insert "\n"))
-(format "%s <- read.table(\"%s\", header=%s, row.names=%s, 
sep=\"\\t\", as.is=TRUE)"
-name (org-babel-process-file-name transition-file 'noquote)
-   (if (or (eq (nth 1 value) 'hline) colnames-p) "TRUE" "FALSE")
-   (if rownames-p "1" "NULL")))
+  (if (listp (car value))
+ (let ((transition-file (org-babel-temp-file "R-import-")))
+   (with-temp-file transition-file
+ (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
+ (insert "\n"))
+   (format "%s <- read.table(\"%s\", header=%s, row.names=%s, 
sep=\"\\t\", as.is=TRUE)"
+   name (org-babel-process-file-name transition-file 'noquote)
+   (if (or (eq (nth 1 value) 'hline) colnames-p) "TRUE" 
"FALSE")
+   (if rownames-p "1" "NULL")))
+   (format "%s <- %s"
+   name
+   (concat "c(" (mapconcat 'org-babel-R-quote-tsv-field value ",") 
")")))
 (format "%s <- %s" name (org-babel-R-quote-tsv-field value
 
 (defvar ess-ask-for-ess-directory nil)

___
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

Re: [Orgmode] Re: [PATCH] Compiling multiple times the LaTeX output

[Carsten Dominik]

On Oct 5, 2010, at 8:55 PM, Achim Gratz wrote:



Commit 59ba4125 lisp/org-latex.el raises warning during byte-compile:

In org-export-as-pdf:
org-latex.el:882:28:Warning: assignment to free variable `errors'
org-latex.el:882:47:Warning: reference to free variable `errors'


Fixed, thanks.

- Carsten




Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


___
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



___
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

Re: [Orgmode] [babel] creating simple vectors in R

[Erik Iverson]

Hello,

Dan Davison wrote:

I'd appreciate opinions from R users on the following org-babel-R
details:



I use R daily, with and without org-mode, but have never investigated
these features of passing tables and Lisp lists to source blocks, but
it looks interesting.  More below.


Currently, Org tables, and lisp lists, are converted into data frames
when they are sent from Org to R, and we have no way to create simple
vectors such as c(1,2). I'd like to know whether users of org and R
would approve of the following change that makes simple R vectors
possible, or have other suggestions related to these issues.

With the patch below, there would be two ways to create a simple vector
in R. The most direct way is to pass a non-nested lisp list:

#+begin_src R :var x='(1 2) :results output
str(x)
#+end_src

CURRENT OUTPUT:
#+results:
: 'data.frame': 1 obs. of  2 variables:
:  $ V1: int 1
:  $ V2: int 2

NEW OUTPUT:
#+results:
:  num [1:2] 1 2



What happens with "non-atomic" lists that contain mixed types?
They could either be turned into a vector of the lowest common
type, e.g., '(1 "hi") is turned into a character vector, or this
could be turned into an R list.  Then you'd be going from
Lisp List -> R list data types.


In addition, because babel's table-indexing code produces a non-nested
list when taking a one-dimensional slice, this would be another
situation in which a vector rather than data frame is created:

#+tblname: input-tab
| 1 | 3 |
| 2 | 4 |

#+begin_src R :var x=input-tab[0,] :results output
str(x)
#+end_src

CURRENT OUTPUT:
#+results:
: 'data.frame': 1 obs. of  2 variables:
:  $ V1: int 1
:  $ V2: int 3

NEW OUTPUT:
#+results:
:  num [1:2] 1 3

There's a possible argument that that's slightly at odds with R, since,
in R, a single row slice of a data frame is still a data frame.



Yes, only since data.frames may and almost always do contain
mixed types.  Which goes back to the first question about the
behavior of this code when there are mixed types.  I think for
this case, if you're taking a single row of an org-table,
turning it into a vector is an OK thing to do, and
is something I probably would rarely do.  For columns,
I definitely think it's an OK thing to do, and it's more likely
I'd be passing in a single column of an org-table as opposed
to a single row.

In R, for columns, subsets of data.frames only return data.frames
with certain indexing styles, and even then,
setting drop = TRUE will return a vector.

> df1 <- data.frame(a = 1:10, b = 2:11)

> is.vector(df1$a)
[1] TRUE

> is.vector(df1[["a"]])
[1] TRUE

> is.vector(df1[, "a"])
[1] FALSE

> is.vector(df1[, "a", drop = TRUE])
[1] TRUE


A related issue is translating an Org table into a matrix rather than a
data frame in R. This can be done explicitly with a call to as.matrix in
the user's code, but if anyone feels that it would be helpful for babel
to automate this then do say so.

Dan


diff --git a/lisp/ob-R.el b/lisp/ob-R.el
index c709064..4b49af5 100644
--- a/lisp/ob-R.el
+++ b/lisp/ob-R.el
@@ -141,16 +141,18 @@ This function is called by `org-babel-execute-src-block'."
 (defun org-babel-R-assign-elisp (name value colnames-p rownames-p)
   "Construct R code assigning the elisp VALUE to a variable named NAME."
   (if (listp value)
-  (let ((transition-file (org-babel-temp-file "R-import-")))
-;; ensure VALUE has an orgtbl structure (depth of at least 2)
-(unless (listp (car value)) (setq value (list value)))
-(with-temp-file transition-file
-  (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
-  (insert "\n"))
-(format "%s <- read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\", 
as.is=TRUE)"
-name (org-babel-process-file-name transition-file 'noquote)
-   (if (or (eq (nth 1 value) 'hline) colnames-p) "TRUE" "FALSE")
-   (if rownames-p "1" "NULL")))
+  (if (listp (car value))
+ (let ((transition-file (org-babel-temp-file "R-import-")))
+   (with-temp-file transition-file
+ (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
+ (insert "\n"))
+   (format "%s <- read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\", 
as.is=TRUE)"
+   name (org-babel-process-file-name transition-file 'noquote)
+   (if (or (eq (nth 1 value) 'hline) colnames-p) "TRUE" 
"FALSE")
+   (if rownames-p "1" "NULL")))
+   (format "%s <- %s"
+   name
+   (concat "c(" (mapconcat 'org-babel-R-quote-tsv-field value ",") 
")")))
 (format "%s <- %s" name (org-babel-R-quote-tsv-field value
 
 (defvar ess-ask-for-ess-directory nil)


___
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


___
Emacs-orgmode m

[Orgmode] Re: Testing --- again...

[Bernt Hansen]

"Eric Schulte"  writes:

> So, I've been using the framework in the combined-testing branch this
> morning writing tests to strap down my daily Babel bug fixes, and I'm
> really liking ERT.
>
> I wonder, can we commit to the combined-testing branch, and if so could
> we fold it into the master branch?  It would make my test driven bug
> fixing a much smoother process, and would remove the need to rebase the
> combined-testing branch against master and "git push -f" the changes up
> to repo.or.cz which just feels wrong.
>
> Thoughts?

Hi Eric and Sebastian,

There's no technical reason that you need to rebase the combined-testing
branch -- there is nothing wrong with making small commits and merging
master into it to fix any conflicts -- eventually when it gets merged
back to master the history will stay intact.

I personally only rebase local work that hasn't been published.  As soon
as the combined-testing branch is useful and public I think it should no
longer be rebased.

I'm really looking forward to getting my hands dirty in this testing
stuff for the clocking functions (since I seem to break those a lot :-P)

Thanks for all of your efforts so far and please keep up the great work!

Regards,
Bernt

___
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

[Orgmode] [org-babel] :no-expand header expands noweb refs

[aditya siram]

Hi all,
I may have understood the :no-expand header incorrectly, but I thought
it suppressed expanding noweb references while exporting but seems to
expand them.
For example I have an org file that looks like this (simplified) :
* Root
#+begin_src fundamental :noweb yes :no-expand :tangle Root.txt
  <>
  <>
#+end_src
* Chunk 1
#+source: Chunk1
#+begin_src fundamental
  code for chunk 1
#+end_src
* Chunk 2
#+source: Chunk2
#+begin_src fundamental
  code for chunk 2
#+end_src

When I 'org-export-as-ascii-to-buffer' I expect this :
 Root
 

Table of Contents
=


1 Root
~~~
 <>
 <>
...

But I get this:
 Root
 

Table of Contents
=
1 Root
2 ...


1 Root
~~~

  code for chunk 1
  code for chunk 2
...


Thanks for the help!
-deech

___
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

[Orgmode] [Dev] Org-mode Test Framework

[Eric Schulte]

A test framework based on ert [1] is now included in the testing
directory of the org-mode repository.  Directions for use are included
in testing/README.org.

This is based on work by Sebastian Rose and myself.

Enjoy -- Eric

Footnotes: 
[1]  http://github.com/ohler/ert


___
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

[Orgmode] Re: Testing --- again...

[Eric Schulte]

Bernt Hansen  writes:

> "Eric Schulte"  writes:
>
>> So, I've been using the framework in the combined-testing branch this
>> morning writing tests to strap down my daily Babel bug fixes, and I'm
>> really liking ERT.
>>
>> I wonder, can we commit to the combined-testing branch, and if so could
>> we fold it into the master branch?  It would make my test driven bug
>> fixing a much smoother process, and would remove the need to rebase the
>> combined-testing branch against master and "git push -f" the changes up
>> to repo.or.cz which just feels wrong.
>>
>> Thoughts?
>
> Hi Eric and Sebastian,
>
> There's no technical reason that you need to rebase the combined-testing
> branch -- there is nothing wrong with making small commits and merging
> master into it to fix any conflicts -- eventually when it gets merged
> back to master the history will stay intact.
>

Noted, I was just shying away from including too many commits in the
revision history.

>
> I personally only rebase local work that hasn't been published.  As
> soon as the combined-testing branch is useful and public I think it
> should no longer be rebased.
>

Ah, that's a good point.  Although this is all moot now as the testing
branch has now been merged into the master branch.

>
> I'm really looking forward to getting my hands dirty in this testing
> stuff for the clocking functions (since I seem to break those a lot :-P)
>

Great, I'm really looking forward to seeing how the test framework
develops as it gets more users.

Best -- Eric

>
> Thanks for all of your efforts so far and please keep up the great
> work!
>
> Regards,
> Bernt

___
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

[Orgmode] Header levels and section numbering > 3, in LaTeX export

[Kai]

With a .org file having headers 4-5 levels deep (e.g.  This 
Section), I'd like the LaTeX export to treat it as a subsubsubsection 
with numbering, e.g. 1.1.1.1.  But no luck, and I'm not sure whether I'm 
doing something wrong with org-mode, or need to customize my LaTeX 
template.  In the org file I have:


#+OPTIONS: H:5 num:t

...which does give the TeX markup of \label{sec-1_1_1_1} in the .tex 
file, but the header text is wrapped in a \paragraph{The Header}, 
instead of \subsubsubsection{The Header}.


Is there a way to have the org-mode LaTeX export mark that up as a 
subsubsubsection?  I'm using the org-mode trunk.  Thanks in advance for 
any help,


K


___
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

[Orgmode] Re: [org-babel] :no-expand header expands noweb refs

[aditya siram]

It appears I misread the manual. 'no-expand' works only for tangling -
but my original question stands. Is there a header that provides this
feature for weaving with links to the chunk like a noweb document?

-deech

On Tue, Oct 5, 2010 at 10:12 PM, aditya siram  wrote:
> Hi all,
> I may have understood the :no-expand header incorrectly, but I thought
> it suppressed expanding noweb references while exporting but seems to
> expand them.
> For example I have an org file that looks like this (simplified) :
> * Root
> #+begin_src fundamental :noweb yes :no-expand :tangle Root.txt
>  <>
>  <>
> #+end_src
> * Chunk 1
> #+source: Chunk1
> #+begin_src fundamental
>  code for chunk 1
> #+end_src
> * Chunk 2
> #+source: Chunk2
> #+begin_src fundamental
>  code for chunk 2
> #+end_src
>
> When I 'org-export-as-ascii-to-buffer' I expect this :
>                                 Root
>                                 
>
> Table of Contents
> =
> 
>
> 1 Root
> ~~~
>  <>
>  <>
> ...
>
> But I get this:
>                                 Root
>                                 
>
> Table of Contents
> =
> 1 Root
> 2 ...
>
>
> 1 Root
> ~~~
>
>  code for chunk 1
>  code for chunk 2
> ...
>
>
> Thanks for the help!
> -deech
>

___
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

Re: [Orgmode] Header levels and section numbering > 3, in LaTeX export

[Indraneel Majumdar]

 Hi,

If you're 4 levels down, it'll be a sub sub sub section, same as a paragraph
* Section
** Sub section
*** Sub Sub section
 Paragraph
* Sub paragraph

H:5 will give you the levels but you have to enable numbering explicitly 
with

\setcounter{secnumdepth}{5}

paragraph is actually a sectioning command. If you want to use it as sub 
sub sub section do this:


 Sub sub sub section heading
  Paragraph starts here...

If you simply want numbered paragraphs, do this:


  Paragraph starts here...
And \includepackage{titlesec} to iron out the redundant spaces that 
would otherwise appear.



HTH,
Indraneel

On 2010-10-06 9:06, Kai wrote:
With a .org file having headers 4-5 levels deep (e.g.  This 
Section), I'd like the LaTeX export to treat it as a subsubsubsection 
with numbering, e.g. 1.1.1.1.  But no luck, and I'm not sure whether 
I'm doing something wrong with org-mode, or need to customize my LaTeX 
template.  In the org file I have:


#+OPTIONS: H:5 num:t

...which does give the TeX markup of \label{sec-1_1_1_1} in the .tex 
file, but the header text is wrapped in a \paragraph{The Header}, 
instead of \subsubsubsection{The Header}.


Is there a way to have the org-mode LaTeX export mark that up as a 
subsubsubsection?  I'm using the org-mode trunk.  Thanks in advance 
for any help,


K


___
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



___
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

Re: [Orgmode] [Dev] Org-mode Test Framework

[Nick Dokos]

Eric Schulte  wrote:

> A test framework based on ert [1] is now included in the testing
> directory of the org-mode repository.  Directions for use are included
> in testing/README.org.
> 
> This is based on work by Sebastian Rose and myself.
> 
> Enjoy -- Eric
> 
> Footnotes: 
> [1]  http://github.com/ohler/ert
> 

Thanks to both of you for doing this!

A couple of small things for the README:

o I needed to add the testing directory to my load-path. Without it,
  org-test-load barfed in the (require 'org-test-ob-consts) when loading
  testing/lisp/test-ob-exp.el.

o I needed to create testing/contrib/lisp by hand. Again, org-test-load
  complained without it. Should that be part of the repository?

Thanks,
Nick

___
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

Re: [Orgmode] [Dev] Org-mode Test Framework

[Nick Dokos]

... and a typo on line 24 of README.org: just->jump.

Nick

___
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

Re: [Orgmode] Header levels and section numbering > 3, in LaTeX export

[Nick Dokos]

Kai  wrote:

> With a .org file having headers 4-5 levels deep (e.g.  This
> Section), I'd like the LaTeX export to treat it as a subsubsubsection
> with numbering, e.g. 1.1.1.1.  But no luck, and I'm not sure whether
> I'm doing something wrong with org-mode, or need to customize my LaTeX
> template.  In the org file I have:
> 
> #+OPTIONS: H:5 num:t
> 
> ...which does give the TeX markup of \label{sec-1_1_1_1} in the .tex
> file, but the header text is wrapped in a \paragraph{The Header},
> instead of \subsubsubsection{The Header}.
> 
> Is there a way to have the org-mode LaTeX export mark that up as a
> subsubsubsection?  I'm using the org-mode trunk.  Thanks in advance
> for any help,
> 

This is a LaTeX limitation (if you want to call it that), not an orgmode
one. See

 http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub

for some workarounds/comments/references (but be prepared for at least some
strangeness).

HTH,
Nick


___
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