Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

2018-05-02 Thread Rasmus Pank Roulund
Aaron Ecay  writes:

> I would also question the decision to change the format of
> org-structure-template-alist.  That has caused some errors (in the sense
> of calls to the elisp ‘error’ function) for me because a third
> party-library (ox-reveal) still uses the old format.  The change also
> seems orthogonal to the switch from  Finally, irrespective of which options are chosen, I think that org-tempo
> would be better implemented in terms of a minor mode.  This would allow
> it to be autoloaded, turned on/off for different buffer(s) in an emacs
> session, and avoid duplicating the logic for activating global minor
> modes.  Patch attached.

I agree.


The right to be left alone is a human right

Re: [O] Upstream synchronization documentation

2017-07-03 Thread Rasmus Pank Roulund
Kyle Meyer  writes:

>> Whereas in your text I think it is the other way round, isn't it?
>> (I.e. the Emacs branch is more stable, and you are talking about
>> porting a fix that someone has made in that branch to the Org master.)
>> So perhaps 'forward port' would be clearer?
> I suspect that Org's maint (where the Emacs changes land) is generally
> more stable than the Org in Emacs's master, but, yes, Emacs's version is
> the older version.  (Well, with v9.0.9 just synced the versions match,
> but maint still has quite a few more commits.)
> Since before I took over "backporting" changes from the Emacs repo, it's
> been referred to as this.  Although I agree it isn't great word choice,
> I'd prefer that we remain consistent so that, for example, "git log -i
> --grep=backport" remains informative.
> But if people think using "backport" is too confusing, I'm OK switching
> to another term.  Of "forward port" and "propagate" (suggested in this
> thread by Eric), I prefer "propagate"---or maybe just "port", though
> grepping for that might lead to too many false positives.  And if we
> stick with "backport", it still might be a good idea to clarify in
> README_maintainer that we're abusing the term.

So at least I’m not crazy for "coming up with" it backporting!

So I will keep calling it "backporting" but explain that it is more like
propagating changes from the Emacs repository (back) to the Org


Dung makes an excellent fertilizer

Re: [O] Use headings in sitemap

2016-10-12 Thread Rasmus Pank Roulund
Nicolas Goaziou  writes:

> Hello,
> Thibault Marin  writes:
>> I would like to generate a sitemap for a published website and use
>> it to extract
>> the last few entries in a specific folder to put on the main page.
>> The site structure looks like:
>> .
>> ├──
>> ├── posts
>> │   ├──
>> │   ├──
>> │   └──
>> ├── misc
>> │   ├──
>> │   └──
>> └──
>> In, I would have:
>> #+begin_src org
>> #+INCLUDE:*posts :lines "-10" :only-contents t
>> #+end_src
>> to include links to the 10 most recent pages in =posts= (I use
>> :sitemap-sort-files anti-chronologically in the project setup).  If I am not
>> missing anything, this requires the file to have a
>> =posts= heading,
>> but the `org-publish-org-sitemap' function only produces a list of pages.
>> If there is no better way to get this to work, I would like to propose a 
>> patch
>> to `org-publish-org-sitemap' to produce headings in the sitemap file
>> when a new
>> parameter is passed and non-nil.  The attached patch is my first
>> attempt at it,
>> it works for my tests.
>> I would be interested to hear people's opinion on this:
>> - Is there a better way to achieve what I want?
>> - Is the proposed patch acceptable?  Any comments would be appreciated.
> This reminds me of a patch Rasmus (Cc'ed) is working on (thread starting
> at: ).

This is still WIP.  I guess we were discussing the "hows" in that thread
as well.

> I'd like to propose here a slightly different, hopefully simpler
> approach so as to get flexibility without entering keyword hell.
> The first thing to note is that :sitemap-function is, IMO, unusable,
> because it puts too much work on the hands of the user. Indeed, they
> have to generate the title of the sitemap page, get the list of files in
> the project, walk that list, handle sorting according to style...

It’s not quite that complicated in my patch/WIP.  You specify an ordering
function.  E.g. the plain list is:

 (defun org-publish-org-sitemap-as-list (files project-plist)
   "Insert FILES as simple list separated by newlines.
 PROJECT-PLIST holds the project information."
(lambda (file) (org-publish-format-file-entry
   file project-plist))
files "\n"))

If you don’t have the full flexibility of a function I guess someone will
always run into trouble eventually...

> I suggest to let :sitemap-function operate on the lists of files
> included in the sitemap (i.e., the list of files in the project),
> already ordered, and formatted according to
> `org-publish-sitemap-file-entry-format'.

Isn’t that’s what my patch does?  The file sorting function call the
formater, providing these arguments.  We could move the formatting back in
the "main" sitemap publishing function, to hide it from users, if that’s

 `((?t . ,(and (not (directory-name-p file)) (org-publish-find-title 
file t)))
   (?s . ,(and (not (directory-name-p file)) (org-publish-find-subtitle 
file t)))
   (?f . ,filename)
   (?F . ,(directory-file-name
(if (directory-name-p filename)
 dirname (org-publish--dir-parent dirname))
  (file-relative-name filename dirname
   (?l . ,link)
   (?h . ,(concat (make-string depth ?*)))
   (?i . ,(concat (make-string (* 2 depth) ? ) "-"))
   (?d . ,(and (not (directory-name-p file))
(or (plist-get project-plist :sitemap-date-format)
(org-publish-find-date file

> The list would be provided in the same format as the return value from
> `org-list-to-lisp', so that, e.g., `org-list-to-subtree' can be directly
> called on it.

> Also, I suggest to make `org-publish-sitemap-file-entry-format'
> a function instead of a string, so as to get more power, i.e., to not
> limit ourselves to the list of placeholders allowed in the format
> string. In particular, we could provide a public function
> org-publish-get-keyword (file keyword  backend), much like what
> Rasmus does in his patchset, but with a back-end so as to get the value
> of any export keyword. Also, this would make
> `org-publish-sitemap-dir-entry-format' unnecessary.

I like that, but AFAIK the backend is not known at the time the sitemap is
generated.  And it might not be deducible from the publishing function.

> Eventually, we could run a hook at the end of `org-publish-org-sitemap',
> which would now always be called, in order to give the opportunity to
> modify the 

Re: [O] [PATCH] ox-koma-letter.el: Add support for 'location' koma variable

2016-03-31 Thread Rasmus Pank Roulund

Is :with-location something you feel strongly about?  I'm not sure I find
that it makes sense...

I would like to apply the following patch on top of yours.


I almost cut my hair, it happened just the other day
>From 43a26688870f6861747a1d333a5844348d3a1749 Mon Sep 17 00:00:00 2001
From: Rasmus 
Date: Tue, 29 Mar 2016 18:08:09 +0200
Subject: [PATCH 1/2] ox-koma-letter: Changes to LOCATION handling

* ox-koma-letter.el (options): Parse LOCATION and remove
  :with-location and :inbuffer-with-location.
  (org-koma-letter--get-tagged-contents): Change string handling.
  (org-koma-letter--get-value): Simplify function.
  (org-koma-letter-use-location): remove
 contrib/lisp/ox-koma-letter.el | 63 --
 1 file changed, 24 insertions(+), 39 deletions(-)

diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index d36e817..a76033d 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -376,13 +376,6 @@ This option can also be set with the OPTIONS keyword, e.g.:
   :group 'org-export-koma-letter
   :type 'boolean)
-(defcustom org-koma-letter-use-location t
-  "Non-nil prints the contents of the letter's extension below the header.
-This option can also be set with the OPTIONS keyword, e.g.:
-  :group 'org-export-koma-letter
-  :type 'boolean)
 (defcustom org-koma-letter-default-class "default-koma-letter"
   "Default class for `org-koma-letter'.
 The value must be a member of `org-latex-classes'."
@@ -436,7 +429,7 @@ e.g. \"title-subject:t\"."
 (:email "EMAIL" nil (org-koma-letter--get-value org-koma-letter-email) t)
 (:to-address "TO_ADDRESS" nil nil newline)
 (:place "PLACE" nil org-koma-letter-place)
-(:location "LOCATION" nil org-koma-letter-location)
+(:location "LOCATION" nil org-koma-letter-location parse)
 (:subject "SUBJECT" nil nil parse)
 (:opening "OPENING" nil org-koma-letter-opening parse)
 (:closing "CLOSING" nil org-koma-letter-closing parse)
@@ -453,7 +446,6 @@ e.g. \"title-subject:t\"."
 (:with-foldmarks nil "foldmarks" org-koma-letter-use-foldmarks)
 (:with-phone nil "phone" org-koma-letter-use-phone)
 (:with-place nil "place" org-koma-letter-use-place)
-(:with-location nil "location" org-koma-letter-use-location)
 (:with-subject nil "subject" org-koma-letter-subject-format)
 (:with-title-as-subject nil "title-subject" org-koma-letter-prefer-subject)
 (:with-headline-opening nil nil org-koma-letter-headline-is-opening-maybe)
@@ -472,7 +464,6 @@ e.g. \"title-subject:t\"."
 (:inbuffer-with-foldmarks nil "foldmarks" 'koma-letter:empty)
 (:inbuffer-with-phone nil "phone" 'koma-letter:empty)
 (:inbuffer-with-place nil "place" 'koma-letter:empty)
-(:inbuffer-with-location nil "location" 'koma-letter:empty))
   :translate-alist '((export-block . org-koma-letter-export-block)
 		 (export-snippet . org-koma-letter-export-snippet)
 		 (headline . org-koma-letter-headline)
@@ -767,42 +758,36 @@ a communication channel."
   (format "\\KOMAoption{fromphone}{%s}\n"
   (if (plist-get info :with-phone) "true" "false")))
  ;; Signature.
- (let* ((head-opening (plist-get info :with-headline-opening))
-	(signature (funcall heading-or-key-value
-(if head-opening 'closing nil)
-(if head-opening 'signature nil
-   (and signature
-	(format "\\setkomavar{signature}{%s}\n" signature)))
+ (let* ((heading-val
+	 (and (plist-get info :with-headline-opening)
+		  (org-string-nw-p
+		   (org-trim
+		(org-export-data
+		 (org-koma-letter--get-tagged-contents 'closing)
+		 info)
+	(signature (org-string-nw-p (plist-get info :signature)))
+	(signature-scope (funcall check-scope 'signature)))
+   (and (or (and signature signature-scope)
+		heading-val)
+	(not (and (eq scope 'global) heading-val))
+	(format "\\setkomavar{signature}{%s}\n"
+		(if signature-scope signature heading-val
  ;; Back address.
  (and (funcall check-scope 'with-backaddress)
   (format "\\KOMAoption{backaddress}{%s}\n"
   (if (plist-get info :with-backaddress) "true" "false")))
  ;; Place.
- (let ((place-scoped (funcall check-scope 'with-place))
+ (let ((with-place-set (funcall check-scope 'with-place))
 	   (place-set (funcall check-scope 'place)))
-   (when (or (and place-scoped place-set)
-		 (and (eq scope 'buffer)
-		  (or place-scoped place-set)))
-	 (format "\\setkomavar{place}{%s}\n"
-		 (if (plist-get info :with-place) (plist-get info :place)
-		   ""
+   (and (or (and with-place-set place-set)
+		(and (eq scope 'buffer) (or with-place-set place-set)))
+	(format "\\setkomavar{place}{%s}\n"
+		(if (plist-get info :with-place) (plist-get info :place)
+		  ""
  ;; Location.
- (let ((heading-val

Re: [O] Some projects

2015-10-27 Thread Rasmus Pank Roulund

Ista Zahn  writes:

> I disagree. pandoc supports conversion to and from org-mode.

I fail to see how this is relevant for the discussion at hand.

> Making pandoc a requirement will enable other useful features (e.g.,
> "Import documents from...", alternative pandoc-based exporters etc.

AFAIK, nobody is working on this.

> IMO pandoc is easy on Windows and OSX. It is easy on some Linux distros
> but not all.

> I use Arch LInux, where getting pandoc requires some work, but I think
> that is an issue that the Linux distros need to work out.

No it doesn't: pacman -S pandoc.

The relevant question here is whether we can accept to rely on pandoc for
CSL support.  Any other feature is irrelevant.

At 25MB, a static, precompiled pandoc is probably fine, but for users of
some OSs, such as Archlinux or even worse some OS where pandoc is not
generally available as a precompiled package, it’s a really, really big
dependency.  I may still be the best option, though.


And when I’m finished thinking, I have to die a lot

Re: [O] [patch] extend org-meta-return to keywords

2014-11-22 Thread Rasmus Pank Roulund

Thanks for the comments.

Nicolas Goaziou writes:

 Rasmus writes:

 Attached is a new version of the patch that will respect the variables
 that also govern `org-insert-headline'.  It's smarter and preserves the
 layout better.

 Thanks for the patch. However there are already mechanisms to complete
 keywords faster (e.g., M-TAB, yasnippet).

Personally, I never figured out how to use yasnippet.  M-TAB is for
completion of new lines, not for continuation of ongoing work.

 Of course, yours is more efficient, but also very specific.

So say you do
#+LATEX_HEADER: \usepackage{biblatex}
Now you need to add a bib resource.  It's nice to quickly be able to get
a new #+LATEX_HEADER-line.  It's specific, but it's meant as a
continuation of the M-RET logic.

 It makes sense on very few keywords.  I have no strong opinion here,
 but I don't think it is general enough to go into core.

OK.  Hopefully some more people will chime in so we can make an educated

 Moreover, it can get in the way of expected M-RET behaviour, as in the
 following example

   - item

   | #+caption: test
 where M-RET is expected to insert an item.

Sure. . .  I'm not sure expected behavior is what I'd like here.  But
that's the initial point, I guess.

 Anyway, some comments follow.

Thanks for those.


The second rule of Fight Club is: You do not talk about Fight Club

Re: [O] [PATCH][ox-koma-letter] changed-in-buffer, subject, minor fixes

2014-02-04 Thread Rasmus Pank Roulund
 Would you give the attached patches a spin?  I think they work nicely;
 only the second patch is non-trivial.  Basically, one can ignore
 subject and title differences as now by setting
 org-koma-letter-prefer-subject to t and not use the SUBJECT keyword.

 I have set the default of -prefer-subject to nil per the discussion
 with Alan and Michael Strey.

 It should apply against master.

 It looks good. Thank you.

 A few minor remarks below.

 +(defcustom org-koma-letter-use-title t
 +  Non-nil means use a title in the letter if present.
 +See also `org-koma-letter-prefer-subject' for the handling of
 +title versus subject.
 +  :group 'org-export-koma-letter
 +  :type 'boolean)

 You should also talk about the OPTIONS item, i.e., title:nil, as in
 other defcustoms.

 +(defcustom org-koma-letter-prefer-subject nil
 +  Non-nil means title should be interpret as subject if subject is 
 +This may be useful for older documents where the SUBJECT keyword
 +was not present.
 +:group 'org-export-koma-letter
 +:type 'boolean)


 -   ;; Subject
 -   (let ((with-subject (plist-get info :with-subject)))
 +   ;; Subject and title
 +   (let ((with-subject (plist-get info :with-subject))
 +(title-as-subject (plist-get info :with-title-as-subject))
 +(subject (org-string-nw-p (org-export-data (plist-get info :subject) 
 +(title (org-string-nw-p (org-export-data (plist-get info :title) 

 `title-as-subject', `subject' and `title' belong to the `let' below, not
 this one.

   (when with-subject
 (unless (eq with-subject t)
   (format \\KOMAoption{subject}{%s}\n
   (if (symbolp with-subject) with-subject
 (mapconcat #'symbol-name with-subject ,
 -   (let ((subject (org-export-data (plist-get info :title) info)))
 - (and (org-string-nw-p subject)
 -  (format \\setkomavar{subject}{%s}\n\n subject))
 +   (let ((subject (if title-as-subject (or subject title) subject))
 + (title (if title-as-subject (and subject title) title)))
 + (concat
 +  (and (org-string-nw-p subject)
 +   (format \\setkomavar{subject}{%s}\n subject))
 +  (and (org-string-nw-p title)
 +   (format \\setkomavar{title}{%s}\n title))
 +  (when (or (org-string-nw-p title) (org-string-nw-p subject)) 

 Rasmus: do you want to change these, or should I do it and apply the
 patch? (The former would be simpler, I have to say.)

Yes, but I didn't manged to do it in the weekend.  I'll try to find
time during the week.  My apology. 


When the facts change, I change my mind. What do you do, sir?

Re: [O] [ANN] Improved Flyspell check

2013-11-22 Thread Rasmus Pank Roulund
Nicolas Goaziou writes:

 Nicolas Goaziou writes:

 Updated patch.

I've been using this patch without issues for at least two week.  I
haven't experienced any slowdowns over wcheck other than that
associated with the design of Flyspell (e.g. flyspell-buffer moves the
cursor over all words).

Quick question: does ISpell/Flyspell feature options to:

  1. Move the ispell suggestion window to the bottom of the window
 (rather than the top)

  2. Select the first suggestion with 1 rather than 0?  The latter is
 harder to press on my keyboard.


There are known knowns; there are things we know that we know.

Re: [O] Best practices for literate programming [was: Latex export of tables]

2013-04-21 Thread Rasmus Pank Roulund

Dear Tom,

 I suppose this depends on what is meant by reproducible.

 My goal is to produce a compendium as defined by Gentleman and Lang
 (see Gentleman R, Lang DT (2004). Statistical Analyses and Reproducible
 Research. Technical report, Bioconductor Project. URL  

 I keep the init.el file as a babel source block with the reproducible
 document, so it can be tangled. I also have an editing setup in a babel
 source block that activates many of the same features handled by the
 init.el file, but also configures the new exporter to look for init.el
 (which might have a different name). The filters are all part of the Org
 document, too, and get pulled into the init.el file with noweb

My issue here is that this approach might lead to copy-paste
preambles which may or may not be desirable.  I can certainly see
the attraction in being able to just tangle the setup.  In fact for my
thesis I also had a preamble.tex blog in my file.  Your proposed setup
here is perhaps better in that it uses emacs-lisp.

Still, say I'm working on two files A and B.  If I fix a bug in
preamble A I would have to manually copy it over to B.  

Thus, the main question is how to distribute updates?  I guess one
could keep a separate file, but then we are back at square one in a
way. . .

One possibility might be a file structure like this

where A and B both has a block like
* Preamlbe:noexport:
#+INCLUDE: ../

To ship it off one would only have to write a command to replacing
#+INCLUDE with its content.  The exporter could likely be used for
this and one could produce an archive version when signing off a

Even more robust, #+INCLUDE: would look for files in org-directory (it
might already do, I didn't check).

Am I missing something obvious (probably?) in the above stream of
random thoughts?  It's kind of a LaTeX-ish way of dealing with it, I

 I am able to distribute the compendium, typically as a single
 document (sometimes with associated data files produced by an
 on-line service that can't be used programmatically), which I
 believe is a good step toward reproducibility.



Send from my Emacs

Re: [O] [ox-latex] Bad default value for image width?

2013-04-07 Thread Rasmus Pank Roulund

In general this auto width code seems super annoying.  Consider this 

From ox-latex.el:
#+BEGIN_SRC emacs-lisp
 (width (cond ((plist-get attr :width))
  ((plist-get attr :height) )
  ((eq float 'figure) 0.7\\textwidth)
  ((eq float 'wrap) 0.48\\textwidth)
  (t org-latex-image-default-width)))

Consider the following example: 


#+BEGIN_SRC emacs-lisp
(make-local-variable 'org-latex-image-default-width)
(setq org-latex-image-default-width )

#+CAPTION: test

no caption


This exports as:


no caption

To me it is not intuitive why a certain width is imposed on me because
I add a caption. . .

Could we consider removing:

#+BEGIN_SRC emacs-lisp
 ((eq float 'figure) 0.7\\textwidth)
 ((eq float 'wrap) 0.48\\textwidth)

and maybe changing the default value of org-latex-image-default-width
to something non-intruding? 

Powered by magic pixies!

Re: [O] org-exp-bibtex missing in git?

2013-03-07 Thread Rasmus Pank Roulund
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.

Achim Gratz writes:

 Do you mean using something like this


 for the file: protocol

 This is a prime example of how _not_ to do this, IMHO.  The file
 protocol is an established protocol that you shouldn't bolt any extra
 parameters on.  

I very much agree.  The current hacks using links are annoying and
ugly, and if we were to do citations properly in Org—and I think we
should—it should NOT be using links (as Nicolas also pointed out).
It's a hack and shouldn't be made official.

In my book it would seem 'natural' to strive towards the following:

  1. It should be Bibtex-based.  I.e. Bibtex should be the 'database'
 or storage for citation information.  It may be stored in
 Org-Bibtex-whatever, but Bibtex should be the natural base.
  2. Citation selection should be possible via Reftex.
  3. It should look nice in the buffer.  For instance, with the
 current link hacks I am shown the pre or post notes in place of
 the citation.  Ideally, it should be able to specify a
 reftex-cite-format string on how to display stuff in the buffer.
 Notes should be viewable in an non-disturbing way.
 Ideally, I would want to see something like:
   (POSTFIX, Jensen, 1906, SUFFIX)
   Jensen (POSTFIX, 1906, SUFFIX)
 (If my memory serves me correctly this is how BibLatex places
 (4. If we are to adopt LaTeX terminology we should adopt the
 terminology of BibLatex as opposed to Natbib). 


Dung makes an excellent fertilizer

Re: [O] Export tables as matrices (change tbl-export function on the fly)

2012-11-17 Thread Rasmus Pank Roulund
Nicolas Goaziou writes:

 I'm doing some stuff where the natural output of my tables are
 matrices.  I found a decent translation function here ¹.  However,
 I'm not very successful in making org use it. 

 Using the new exporter, something like should replace any table using
 default environment (i.e. no special attribute) and without horizontal
 rules with bmatrix environment. It should also insert it in math mode

I didn't manage to get your (Nicolas') or my own attempt working
correctly for exporting matrices.  I still think it would be nice.

I tried to use the regexp 
   (not (string-match |[\\+-]+|  table))
to identify tables without heading separators, but it didn't work

Thinking about it, it might be nice to be able to specify table export
function more generally.  For instance, I might have a matrix with
labels (in LaTeX a bordermatrix or kbordermatrix).  Likewise, it might
also be nice to specify a header argument to tables s.t. I can specify
a name, e.g.

#+NAME: P 
#+TBLOPTIONS: :prefix P= :type matrix
| a| b|
| c| d|

would export to 


May the Force be with you

Re: [O] nbsp and /italics/

2012-10-16 Thread Rasmus Pank Roulund
Rasmus writes:

 Can anyone think of a clever regexp that recognizes the above pattern?
 I tried, \\.[ ]\{1\} but it didn't work.  And without the \{1\} it's
 too strong. . .

Here's one that seems to work in the primitive cases, but not when
there's a link. 

Tested on 
   test of tilde. small space fig. [[latex:ref][test]].  But here's a large 

the regexp recognizes both small spaces, but does not insert the
tilde between fig. and [[.

Could I add it to an earlier hook or something similar to make it

#+begin_src emacs-lisp
(defun ngz-latex-filter-nobreaks-double-space (text backend info)
  Tries to export \S1. S2\ as \S1.~S2\ while letting \S1.  S2\ be 
exported without tilde
  (when (memq backend '(e-beamer e-latex))
(replace-regexp-in-string \\.[ ]\\{1\\}\\([^ ]\\) .~\\1 text)))

(add-to-list 'org-export-filter-plain-text-functions


I almost cut my hair, it was happened just the other day

Re: [O] Publish HTML Without Title

2011-11-27 Thread Rasmus Pank Roulund
Hi Nick,

Thanks for you answer and your verification. 

 Thanks for providing your setup. I think you are right about the code
 and I don't see any way to turn it off.

 It looks like another band-aid to me (and org-html definitely has more
 than its fair share of those), particularly given the comment about
 org-infojs: presumably, after org-infojs is fixed to look for it in
 the preamble, then the h1 header can be deleted from the content
 (although anything I say about HTML should be taken with a large grain
 of salt).

The thing is, this is a 'new' thing, as the git blame log also
suggests.  Which is bothersome.  But okay.

 Next question: can't you get rid of the instance in your preamble at
 temporarily? Does it have to be in the top div?

Well, you know, I would have to redesign my website.  It is possible,
but I like it. . .

The header on each side is something like:

| Title| | Menu  |
| Left aligned | empty space | Right aligned |

Which is rather neat IMO.

It used to work.  I don't know under which version of Org I wrote
(probably mostly stole :) the original CSS but I am guessing 7.6.

I had hoped for some command I could #+BIND to have Org behave as
before, (e.g. similar to the BIND for removing \maketitle in LaTeX).

Thanks for the help,

Sent from my Emacs

Re: [O] [PATCH] Add tikzDevice support to ob-R

2011-11-27 Thread Rasmus Pank Roulund

Aloha Thomas,

 The attached patch adds tikzDevice support to ob-R.  It requires that
 the tikzDevice package be available to R, so it must be installed and
 loaded.  Something like the following code in .Rprofile will load the
 package by default:

Thanks a bunch.  I always use pgfSweave and thus I haven't really
managed to move from Rnw (LaTeX + R files) to Org file.

Are you aware of the very handy pgfsweave bin?  In the Arch R package it
is located in


First, you don't have to load tikzDevice. Second, It makes this very
nice notation valid in Rnw files:

#+begin_src latex
\caption{Time series $x$ and $y$}\label{fig:ts1}
ts3xy-plot, echo=FALSE, fig=T, tikz=T, external=T, cache=F, echo=F, width=7, 
height=3, sanitize=T=

which translates to the following automatically:
#+begin_src latex
\caption{Time series $x$ and $y$}\label{fig:ts1}

It also adds nice formatting of R chucks without the need other R

Thus, using pgfSweave over regular Sweave is just wonderful.  However, I
don't know whether it can integrate with Babel.

Thanks again.


Sent from my Emacs

Re: [O] Publish HTML Without Title

2011-11-26 Thread Rasmus Pank Roulund
Nick Dokos writes:

 Rasmus wrote:


 I publish my website with Org. have defined my title in
 org-publish-project-alist under the :html-preamble.

 However, it seems that recent Orgs have become 'smart' and now I don't
 know how to disable the publishing of title and I have the title printed
 twice.  As I recall this was not an issue before.

 It seems to stem from org-html. el around 1358:

 #+begin_src emacs-lisp
  ;; begin wrap around body
  (insert (format \ndiv id=\%s\
  ;; FIXME org-export-html-content-div is obsolete since 
  (or org-export-html-content-div
  (nth 1 org-export-html-divs)))
  ;; FIXME this should go in the preamble but is here so
  ;; that org-infojs can still find it
  \nh1 class=\title\ title /h1\n))

 Are there any known solutions to this at the moment?

 I spent 10 minutes trying to recreate the problem, and decided that I
 have no idea what you are talking about.

 So in my role as the official and perpetual nag on this list: can you
 please post your org-publish-project-list -or at least the relevant
 and (unless, as I suspect, the org file is completely trivial) an ECM
 exhibiting the problem?

In my publish file I have (Warning: 'destructive' example that setq
rather than add-to-list).

#+begin_src emacs-lisp
(setq org-publish-project-alist
:base-directory ~/test
:publishing-directory ~/test
div id=\top\
h1 class=\title\%t/h1
div id=\menu\
 a href=\index.html\ Home/a |
 a href=\emacs.html\ Emacs/a |

Now use ~/test/
#+begin_src org

* First head
  1. point
  2. two
  3. three

Publish it as HTML.  Here is relevant snips from the sourced code.
#+begin_src html

div id=preamble

div id=top
h1 class=titleTEST/h1
div id=menu
 a href=index.html Home/a |
 a href=emacs.html Emacs/a |

div id=content
h1 class=titleTEST/h1

Note, I never asked for the second title and this is the one I want to
go away, but I don't know how.  As I pointed out in the previous case,
it seems that it may be hardcoded, but I don't know.

I use Emacs-bzr 106282 and Org-git of 2026.


Sent from my Emacs

Re: [O] Cdlatex questions

2011-10-19 Thread Rasmus Pank Roulund
Carsten Dominik writes:
 Hi Rasmus,

 you need to set these variables before cdlatex.el has been loaded, or you need
 run (cdlatex-reset-mode) after you have changed them.  THis is not documented 

Thanks Carsten.

For the reference I use the following snip now which and it works as I
want it to work.

#+begin_src emacs-lisp

(add-to-list 'cdlatex-math-modify-alist
 '(98 \\boldsymbol \\textbf t nil nil))

(add-to-list 'cdlatex-math-modify-alist
 '(115 \\mathbb nil t nil nil))

(org-defkey org-cdlatex-mode-map ¨ 'cdlatex-math-symbol)
(setq cdlatex-math-symbol-prefix 168)

(require 'cdlatex)



Sent from my Emacs

Re: [O] Put result output in different type of code block than original

2011-10-11 Thread Rasmus Pank Roulund
Niels Giesen writes:


 Say I've got a sh code block invoking curl to some json api, is it possible
 some way to specify that the format of the output when :results output code
 is in a json code block and *not* a sh code block?

Does this help you?  (Lacking a relevant example)

#+begin_src R :results output latex

[1] 2


Sent from my Emacs

[O] Beamer and non-frames

2011-05-29 Thread Rasmus Pank Roulund

How do I put text between frames in an Org-Beamer document? 
What I really want to do is something like:

#+begin_src LaTeX

But there is /plenty/ of use of being able to write in-between frames. 

I imagine two ways this could be archived,
  a. Use a special property for a headline
  b. Have a '#+LaTeX_Beamer:' option.

Are anybody aware of any quick fixes?


Sent from my Emacs

Re: [O] Beamer and non-frames

2011-05-29 Thread Rasmus Pank Roulund

 I am sorry I have no solution for you just now.
 This behavior you're seeking is something I long for as well, to
 insert a this frame only custom background, to be precise.

So many great things can be put in-between 


in Beamer

 The issue lies in the org-beamer.el way of divvying up the file into
 frames (if memory servers me, it's the org-beamer-sectioning function,
 but I can be mistaken), it's a  big function that handles most of
 org-beamers functionality. For the behavior that we seek we need to
 implement a function that can encapsulate the \begin{frame}
 ... \end{frame} code. However, this is not trivial.

Yeah, I gussed it was something like that..

However, maybe something like to the following could be implemented.
I note the following in my file:

** Frame

#+latex_beamer_outside_frame: \againframe2{overview.fig} %(1) 

** Next frame

The 'Org-exporter' notices (1) and stores it in a list L.  Each time it
writes \end{frame} it also checks L and if L is non-empty the exporter
will dump whatever currently exists in L after \end{frame}.

I do, however, not know whether this is easily implemented.

 It has my interest, but don't expect anything useful from me in the
 short term, as I am an elisp noob and I am just getting acquainted
 with the org api.

I am neither good at lisp nor programming in general, although I do need
the command for a Python presentation. I guess I'll have to fix the Beamer
code 'by hand'.


Sent from my Emacs

Re: [O] Questions on LaTeX Exporter

2011-03-07 Thread Rasmus Pank Roulund

 (setq org-export-latex-hyperref-format \\ref{%s}) then you can
 refer to sections by their numbers with as we see in section
 [[section]] and it works nicely.

Wow; it works! Lawrence, in your experience, how fragile is this? The
bliss of LaTeX labels is that they are independent of the printed
headings so I can change the title and retain a sensible \ref.

Eric, thanks for your point. I still think it less than ideal, as
illustrate by this snip.

| \section{Introduction}
| \label{sec-1}
| \label{sec:into}

Org has a /really/ bad habit of inserting blank lines! Here is an
example of a fix from a beamer presentation:

| *** Stiglitz  :B_quotation:
| :BEAMER_env: quotation
| :END:
| \noindent
| Social capital is a concept with a short and already confused history.
| #+latex:  \\\hfill\citep[pp. 59]{stiglitz99}

And the output:

| \begin{quotation} % Stiglitz
| \label{sec-2_1_1}
| \noindent
| Social capital is a concept with a short and already confused history.
| \\\hfill\citep[pp. 59]{stiglitz99}
| \end{quotation}


Re: [O] Questions on LaTeX Exporter

2011-03-07 Thread Rasmus Pank Roulund


But Latex doesn't care?  =sec:into= will still be fine so I don't see
why this is not suitable *and* it is not fragile as far as I can tell.
I've used this approach for a long time.
No, using \label's is never fragile! The /only/ theoretical possibility 
is that the \label is placed on a new page, but this would only be an 
issue in perverse cases as vanilla-LaTeX would not place a heading alone 
(i.e. just before a page break). It is an aesthetic issue. I can't help 
my scrutinizing of the .tex-output :)

 beamer quote

I am not sure what point you are trying to make in this case?
It inserts a blank line which will cause the text to be indented. So I 
need to add a \noindent to avoid the indent. I never asked for a blank 
line. I apologize for obscurity.

(i.e. no need for the #+latex directive...)

I know. I a later quote in the same document I actually didn't use it, 
so my best guess is that it was an experiment to see whether there were 
any differences.


PS: I might go to UCL next semester. I haven't decided yet.

Re: [O] Questions on LaTeX Exporter

2011-03-07 Thread Rasmus Pank Roulund

I think what Eric is asking is why does the empty line matter?  I just

realize that the undesirable behavior is caused by the fact that the
quotation rather than the quote environment is used. Sorry for the

All I need to do is call `C-c C-e p' and I get a publication quality
pdf. But of course that is not always the case when we start out with
a document, but as we approach completion I would expect to reach that
ideal state.  Isn't that how you view it?

Sure, but when undesirable results are obtained I will go to the LaTeX
code since I can determine the problem in the LaTeX code.

I am in no way unthankful. Rather, I try to share criticism that might
be useful in improving the exporter, such as not being able to demand
ordinary space rather than full stop after 'e.g.'. On the other hand, it
may be that I just add noise :)


Re: [Orgmode] Agenda and one-line diary display

2011-02-11 Thread Rasmus Pank Roulund

Hi Bastien,

Thanks for your reply.

   Bill B. visits Princeton today
   2pm Cognitive Studies Committee meeting

Sounds interesting.

   2:30-5:30 Liz at Lawrenceville
   4:00pm Dentist appt
   7:30pm Dinner at George's
   8:00-10:00pm concert

Busy day :)

Here is an example of a diary going all wrong

| Friday 11 February 2011
|   10:00.. 
|   12:00.. 
|   14:00.. 
|   Diary:  14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum 
i statens tjeneste

|   16:00.. 
|   18:00.. 
|   Diary:  18:00-23:55 Fest
|   20:00.. 
|   overview:   In   3 d.:  TODO 
[[file:institutions/assignment2.tex][Assignment 2]]
|   overview:   In   7 d.:  TODO 
[[file:growth/assignment1.tex][Assignment 1]]

|   overview:   In   7 d.:  TODO [[file:labor/lab/lab1.Rnw][Lab1]]
|   Diary:  Location: Sabina
|   Diary:  Status: CONFIRMED		(UID:
|   Diary:  Desc: 1. Politisk økonomi - Fra ADAM til DREAM:  Jesper 

|   Diary:  2. Politisk rådgivning:fhv. departementschef Jørgen Rosted
|   Diary:  3. Politisk praksis:fhv. økonomiminister Marianne Jelved, MF
|   Diary:  Location: Roskilde Universitet (RUC) hus 25.2
|   Diary:  Status: CONFIRMED		(UID:


It is a bit of a SNAFU. Here is the diary

| 2/11/2011 18:00-23:55 Fest
|Location: Sabina
| [...] omitting 22 lines [...]
| 2/11/2011 14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum i 
statens tjeneste

|Desc: 1. Politisk økonomi - Fra ADAM til DREAM:  Jesper Jespersen
|  2. Politisk rådgivning:fhv. departementschef Jørgen Rosted
|  3. Politisk praksis:fhv. økonomiminister Marianne Jelved, MF
|Location: Roskilde Universitet (RUC) hus 25.2

| Friday 11 February 2011
|   10:00.. 
|   12:00.. 
|   14:00.. 
|   Diary:  14:00-15:30 Professor Jesper Jespersen – 40 års jubilæum 
i statens tjeneste

|   16:00.. 
|   18:00.. 
|   Diary:  18:00-23:55 Fest
|   overview:   In   3 d.:  TODO 
[[file:institutions/assignment2.tex][Assignment 2]]
|   overview:   In   7 d.:  TODO 
[[file:growth/assignment1.tex][Assignment 1]]

|   overview:   In   7 d.:  TODO [[file:labor/lab/lab1.Rnw][Lab1]]

So what I'd want was just to display. If I'd want more info I'd just RET
the line.

The fuss might be caused by an auto-generated diary. I don't know.

So I'd say for now no, you cannot reduce your diary entry to just one

Too bad.

Have a nice weekend.


Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

Re: [Orgmode] LaTeX exporter #+INCLUDE bug

2011-01-16 Thread Rasmus Pank Roulund

Yes. This is a bug and a bit hard to fix.
I only happens if the #+include line is before the
first headline in the buffer.

I am afraid I do not have a simple solution.

It is fairly simple to make a work-around:




Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

[Orgmode] Agenda and one-line diary display

2011-01-15 Thread Rasmus Pank Roulund

I have finally found a tolerable solution to include Google calendars
into Emacs and thus Org using emacs-google[1].

However, one thing is bothering me about the way Org agenda view handles
my newly populated diary file. It shows too much information! Basically,
I want /one line per entry/. If I want more info I'll just hit the
entry. The reason is that I will often include a lot of extra
information for each calendar/diary entry. When needed, I will fetch it
but it usually preclude the overview that I wish to obtain in the agenda

Here is a simple agenda example: 

|   Diary:  Semester start
|   Diary:  Location: Lund University
|   Diary:  Status: CONFIRMED   (UID:

And the corresponding diary code:

| %%(and (diary-block 1 17 2011 1 17 2011)) Semester start
|Location: Lund University

What I want to agenda view to show is merely: 

|   Diary:  Semester start

Or, even better:

|   Diary:  Semester start (Lund University)

I.e. no other information than the event and if possible the
location. If time is available this should also be displayed, but all in
one line. 

Is this possible in one way or the other? If so I'd appreciate any hints
on getting there. 

Thanks a bunch,


Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

Re: [Orgmode] Bug: \log and friends are not recognized as math [6.34b]

2010-01-30 Thread Rasmus Pank Roulund

Hi Carsten,

can you make me a list of macros that should be treated in this way?

If you load AUCTeX with math key bindings
  M-x latex-mode RET
  M-x latex-math-mode RET

You will get a list of symbols under Math--Log-like. It is defined in 

Here is a list of log-like functions according to AUCTeX.

(nil arccos Log-like)
(nil arcsin Log-like)
(nil arctan Log-like)
(nil arg Log-like)
(?\C-c cos Log-like)
(nil cosh Log-like)
(nil cot Log-like)
(nil coth Log-like)
(nil csc Log-like)
(nil deg Log-like)
(?\C-d det Log-like)
(nil dim Log-like)
(?\C-e exp Log-like)
(nil gcd Log-like)
(nil hom Log-like)
(?\C-_ inf Log-like)
(nil ker Log-like)
(nil lg Log-like)
(?\C-l lim Log-like)
(nil liminf Log-like)
(nil limsup Log-like)
(nil ln Log-like)
(nil log Log-like)
(nil max Log-like)
(nil min Log-like)
(nil Pr Log-like)
(nil sec Log-like)
(?\C-s sin Log-like)
(nil sinh Log-like)
(?\C-^ sup Log-like)
(?\C-t tan Log-like)
(nil tanh Log-like)

Is that sufficient?

I guess we can simply add these to org-html-entities t=and that might
already solve the issue.

You are probably right :)


Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

[Orgmode] Bug: \log and friends are not recognized as math [6.34b]

2010-01-17 Thread Rasmus Pank Roulund

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

Your bug report will be posted to the Org-mode mailing list.

It seems a bit extravagant to include all of the system-info so I removed
most of it . . .

Anyhow Org does not recognized \log and friends as math when using the 

Try the following minimal example

\log is math. so is \ln

The LaTeX result is:


\title{\log is math. so is \ln}
% It should have been $\log$ and $\ln$
\date{17 January 2010}





Would it be possible to adopt \log-like functions as math? \cos, \tan,
\sin are also affected.
It is so convenient to write \log-like but I have to fix the exported
latex file manually afterward.

BTW: I created a very complex econometric note in org. Once I had
squeezed the LaTeX-related bugs (math typos) the export was /perfect/!
(except for the \log's). Good work!


Emacs  : GNU Emacs (i686-pc-linux-gnu, GTK+ Version 2.18.5)
 of 2010-01-15 on pank
Package: Org-mode version 6.34b

Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

[Orgmode] Re: Fully featured Web publishing

2009-03-19 Thread Rasmus Pank Roulund
 Why not us preamble?

I am not sure I understand you question, but:
Because the OP wants to include the same menu on every page. If you
input the file you will only have to update one file and the other files
will be updated. 

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: The most important project for org developers?

2009-03-19 Thread Rasmus Pank Roulund

 If you have access to a server that supports WebDav you can create a
 Google Calendar that reads your org ics file directly.
phpicalendar has a module called publish.php than can write to a ics
file via http. I use it with multiple shared calendars in Thunderbird. 

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: Fully featured Web publishing

2009-03-18 Thread Rasmus Pank Roulund
I have done something similar. I have a single menu file which I
include on every page.

Would that solve you problem?


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: Bug and feature request in HTML export

2009-02-12 Thread Rasmus Pank Roulund
Hello Sebastian,

 M-x customize-variable RET org-empty-line-terminates-plain-lists
 will do what you need.

Thank you so much. It worked like a charm. Have a nice weekend.

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: LaTeX Export

2009-02-12 Thread Rasmus Pank Roulund
Carsten Dominik writes:

 Some time ago I added a new matcher $1 for single
 charactersbetween dollars like in this case.  People who
 havecustomized this option unfortunately do not get to see it.
That was probably the problem. It works a lot better now! Thanks. 

 That said, Giovanni's proposal to use \(\) is excellentadvice, at least
 in cases where using $..$ causes trouble.- Carsten

Acctually, at first I used \(...\) but at that time Org had a harder
time picking up \(...\) than $...$ which caused a lot of \($...$\). I
have not checked whether it works better now.


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: LaTeX Export

2009-02-10 Thread Rasmus Pank Roulund
Sorry for the late reply. This is regarind a bug in LaTeX export.
The trouble seems to happen when autofill is used. It
might be caused by something else. I am not sure. The thing is
that Org sometimes misintpretate $ as the currency symbolar
rather than math as in LaTeX-lingu. IMO the use of $ as a
currency symbol should be optional.

Here is an example of the error:

Org source: 

   - Funktioner findes ved at sætte funktionen lige en given konstant
 $k$. Dermed bestemmes indifferentfunktion. Det ses nemt at
 $u(x_1, x_2)=k$.

LaTeX export: 

   \item Funktioner findes ved at sætte funktionen lige en given konstant
 \$k\$. Dermed bestemmes indifferentfunktion. Det ses nemt at
 $u(x_1, x_2)=k$.

I have pulled the newest revision of Org. The version is 6.22b.


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Bug and feature request in HTML export

2009-02-10 Thread Rasmus Pank Roulund
There seems to be a bug in HTML export.
I am using Org for making a (fancy) web site.
I define the top menu via a list which is made fancy via CSS.

The Org file looks like this:

#+HTML: div id=topbar

  - [[][Forside]]
  - [[][Eksempler]]

#+HTML: /div

The corrosponding HTML code looks like this:

div id=navbar

a href=index.htmlForside/a
a href=eksempler.htmlEksempler/a


Thus, when I try to validate the site it gets errors! It should look


I tried to insert a comment (#) after the list but Org still ended div
before ul.

I also have a couple of feature request/bug reports for html export:

First: it would be nice if one could specify the location of the title
similar to the [TABLE-OF-CONTENTS] option. At the moment it seems to
always be placed in the top of the page, which might not be desirable. 

Second: I do not know if this is a feature, but * Heading (i.e. a first
level heading) is marked as a h2 heading. It should probably be
h1. At least one should be able to define it as a h1 heading.

Third (bug): Sometimes links are rendered wrong: 
 is rendered as a 
 notice the sub-tags!

Forth: Sometimes it is desirable to be able to #+HTML in links and
titles. This is not possible.
For example:
 #+TITLE:  #+HTML: span class=latexTsubE/subX/span
#+HTML: span class=latexXsub#398;/subTsube/subX/span


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: Bug and feature request in HTML export

2009-02-10 Thread Rasmus Pank Roulund
Carsten Dominik writes:


 Org cannot know that you do want to end the list here, the HTML
 insertion might be part of the list.

 I do not know how to fix this.
I see your point. But if i have a lot of blank lines it probably should
not be included. Somehow one needs to signal to Org that this is not
part of the list. The most obvious signal seems to be a lot of blank
lines, or does that solution contain undesirable sideeffects?  

 It seems to me quite reasonable to put it at the top of the page.
Sure, but it might be useful to have the title several places on the
site. Sometimes it might be useful to place it elsewhere than the top.

 Don't forget that Org is not a full HTML editor, it just tried to do a
 good job at converting your file.

I know :-) But it is still the best HTML editor/parser I have used in
a looong time! The publish feature is fantanstic. Good job BTW!

 You do not have a recent version of Org-mode.  Please always try the
 latest version before reporting bugs.
I have 6.22b but the page had not been refreshed with the new
version. Sorry!

 This is not supported currently, and I am not sure we will get there.
Maybe one day :-)

 For this specific case you will get away with ...

 However, if you need this much or more control, maybe Muse will be a
 better option.
Org rocks. 'Nuff said :-)

BTW: Is it possible make part of a word italicized. I.e. Ti/k/Z where
the 'k' is italicized?

Thanks for Org.

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: LaTeX Export

2009-01-08 Thread Rasmus Pank Roulund
 I have tried to fix the issues with dollars, please download the
 latest GIT version and check if your stuff is now converted better.

I have gotten the newest git version from today. I have Org v6.17trans.

There is still something funny with $-signs.

Here are a couple of examples:
LaTeX output: 
  \item Hvis en vare har input \$x\$ \dots

  - Hvis en vare har input $x$ \dots
LaTeX output:
   \$M\$ er bestemt af centralbanken, og det eneste den bestemmer er

 - Produktionsfunktionen brugt af monetarister:
   $M$ er bestemt af centralbanken, og det eneste den bestemmer er
LaTeX output (this one is particuarily troublesome):
  \item På arbejdsmarkedet bestemmes ligevægten imellem $L_d$ og $L_s\$
   Her ud fra findes ligevægten i udbudet.

 - På arbejdsmarkedet bestemmes ligevægten imellem $L_d$ og $L_s$
   Her ud fra findes ligevægten i udbudet.
LaTeX (also troublesome):
  \item Givet ved $y=f(l, k)\$

 - Givet ved $y=f(l, k)$
There are lots of \$ in the end of math even though there is no line


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] Re: LaTeX Export

2009-01-05 Thread Rasmus Pank Roulund

 First of all, org 3.16c is very old indeed so *maybe* this works
 better in a more recent version?
Sorry, it is 6.16c :-) (Thanks Matthew!)
I believe it is the version bundled with the latest Emacsw32 from I am using a Emacsw32 from December 2008.
Since I use win32 I am not able to use the provided update-script. 
Is is okay to overwrite the el files in the Emacs folder and recompile

 Second, you could help with an example which demonstrates the problem.
Sorry. I should have included examples in the first post.
Here is an example from the notes I am working on.
The LaTeX output is:

\item Indtegnes i et $x_1/x_2$-diagram, evt. med indifferentkurver.
\item Kurve, der sammensætte alle de bedste løsninger \$(x_1^{*},
  x_2^{*})$ ved varierende indkomst $m$.

Notice the \$ in the second item. Since I rarely use $ as a symbol but
use it all the time as math delimiter it would be more efficient to use
\$ when I actually need a $-sign.

Here is the corresponding Org code:

- Indtegnes i et $x_1/x_2$-diagram, evt. med indifferentkurver.
- Kurve, der sammensætte alle de bedste løsninger $(x_1^{*},
  x_2^{*})$ ved varierende indkomst $m$.

The trouble is probably caused by my auto-fill-mode hook, but I really
cannot stand long lines, and I absolutely love auto-fill-mode.

Here is an example of the information I would like to have washed out.
The LaTeX code contains the following:
  \texttt{SCHEDULED:} \texttt{2008-12-30 ti}
\texttt{CLOCK:} [2008-12-30 ti 13:42]--[2008-12-30 ti 15:47] =  2:05

Here is the corresponding Org code:
 * DONE Forbrugeroverskud
   SCHEDULED: 2008-12-30 ti
 CLOCK: [2008-12-30 ti 13:42]--[2008-12-30 ti 15:47] =  2:05

I have (setq org-export-with-timestamps t) btw.
With #+OPTIONS: :nil time stamps are still present (after refreshing
and re-exporting).

Another thing on LaTeX Export: Why so much \texttt{}? Org stamps (and
tags) such as CLOSED are written with \texttt{}. I am not sure why.

On check boxes: Can their look be customized? I would rather use
\CheckedBox and \Square from the Wasysym package. It is LaTeX so there
is no reason to use ASCII persudo boxes (IMO, of course). 

Long post. Sorry. 

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

[Orgmode] LaTeX Export

2009-01-05 Thread Rasmus Pank Roulund
I have got two questions.
I am using Org-mode v. 3.16c. I usually use LaTeX but Org has been
really nice. However, I want to export to LaTeX.
Two features are bugging me though.
  1. Timestambs are really nice, but I don't want them in my final
 print (the LaTeX output). Is there an easy way to remove these? 
  2. The interpretation of $ is probably nice for American but for me
 it creates a lot of undesirable results, since a lot of math is
 not recognized as math for unknown reasons. It would be nice to
 be able to turn the $-feature off [1]. When I need a $-sign I
 would much rather use \$. Maybe the universal currency-symbol ¤
 could be used as a replacement, if the user desire.

If either of these are already possible I appoligize. I was not able
to find an answear to my questions in the manual.

[1] To avoid conflicts with currency specifications, single '$'
 characters are only recognized as math delimiters if the enclosed
 text contains at most two line breaks, is directly attached to
 the '$' characters with no whitespace in between, and if the
 closing '$' is followed by whitespace or punctuation. 
 --From the Org manual.


Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.