re-exporting a web site

re-exporting a web site

[Eric S Fraga]

Hello,

I've been through the manual and the faq but just cannot seem to find
the answer to a very simple question:  I need to re-publish
(i.e. re-export) a website that is written in org-mode because I've
changed some of the style information that is "included" by each .org
file.  Although I can force a re-export on individual files (C-u C-c C-e
F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
export the project simply skips all the unmodified files.  Trying C-u
C-c C-e X gives 

,----
| org-publish-get-base-files: Wrong type argument: stringp, nil
`----

Is this a bug?  I am running the latest org-mode version from git (as of
yesterday evening, in any case) on emacs version 23.0.93.1.

I know I can delete all the files in .org-timestamps/ but this is rather
a sledgehammer approach (as it will cause unnecessary re-publishing for
other projects).

Is there an easy way to re-export a project?

Thanks,
eric

-- 
MC .  -.. --- -  ..-. .-. .- --. .-  .- -  ..- -.-. .-..  .- -.-.  ..- -.-
NL Professor Eric S Fraga, UCL, http://www.homepages.ucl.ac.uk/~ucecesf/
BF >++++++++++[>++++++++++>+++++++++++[<]>-]>++.>++++.<-----.++++++.------.

Re: re-exporting a web site

[Manish]

On Tue, May 19, 2009 at 5:06 PM, Eric S Fraga wrote:
> Hello,
>
> I've been through the manual and the faq but just cannot seem to find
> the answer to a very simple question:  I need to re-publish
> (i.e. re-export) a website that is written in org-mode because I've
> changed some of the style information that is "included" by each .org
> file.  Although I can force a re-export on individual files (C-u C-c C-e
> F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
> export the project simply skips all the unmodified files.  Trying C-u
> C-c C-e X gives
>
> ,----
> | org-publish-get-base-files: Wrong type argument: stringp, nil
> `----
>
> Is this a bug?  I am running the latest org-mode version from git (as of
> yesterday evening, in any case) on emacs version 23.0.93.1.
>
> I know I can delete all the files in .org-timestamps/ but this is rather
> a sledgehammer approach (as it will cause unnecessary re-publishing for
> other projects).
>
> Is there an easy way to re-export a project?

Does publishing with a prefix not work?

-- 
Manish

Re: re-exporting a web site

[Eric S Fraga]

Manish <mailtomanish.sharma@gmail.com> writes:

> On Tue, May 19, 2009 at 5:06 PM, Eric S Fraga wrote:
>> Hello,
>>
>> I've been through the manual and the faq but just cannot seem to find
>> the answer to a very simple question:  I need to re-publish
>> (i.e. re-export) a website that is written in org-mode because I've
>> changed some of the style information that is "included" by each .org
>> file.  Although I can force a re-export on individual files (C-u C-c C-e
>> F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
>> export the project simply skips all the unmodified files.  Trying C-u
>> C-c C-e X gives
>>
>> ,----
>> | org-publish-get-base-files: Wrong type argument: stringp, nil
>> `----
>>
>> Is this a bug?  I am running the latest org-mode version from git (as of
>> yesterday evening, in any case) on emacs version 23.0.93.1.
>>
>> I know I can delete all the files in .org-timestamps/ but this is rather
>> a sledgehammer approach (as it will cause unnecessary re-publishing for
>> other projects).
>>
>> Is there an easy way to re-export a project?
>
> Does publishing with a prefix not work?

Thanks Manish.  But unfortunately that's what I tried: 
  C-u C-c C-e X projectname 
and the error message I've given above results!

Publishing to a file, with prefix, works perfectly, however.

-- 
MC .  -.. --- -  ..-. .-. .- --. .-  .- -  ..- -.-. .-..  .- -.-.  ..- -.-
NL Professor Eric S Fraga, UCL, http://www.homepages.ucl.ac.uk/~ucecesf/
BF >++++++++++[>++++++++++>+++++++++++[<]>-]>++.>++++.<-----.++++++.------.

Re: re-exporting a web site

[Matthew Lundin]

Hi Eric,

Eric S Fraga <ucecesf@ucl.ac.uk> writes:

> Hello,
>
> I've been through the manual and the faq but just cannot seem to find
> the answer to a very simple question:  I need to re-publish
> (i.e. re-export) a website that is written in org-mode because I've
> changed some of the style information that is "included" by each .org
> file.  Although I can force a re-export on individual files (C-u C-c C-e
> F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
> export the project simply skips all the unmodified files.  Trying C-u
> C-c C-e X gives 
>
> ,----
> | org-publish-get-base-files: Wrong type argument: stringp, nil
> `----
>

I receive the same error when I try to export using C-u C-c C-e X.

As a temporary fix, you can use C-u C-c C-e P while visiting one of the
org files in the project. That's the method I use to update an entire
website.

- Matt

Re: re-exporting a web site

[Nick Dokos]

Matthew Lundin <mdl@imapmail.org> wrote:

> Hi Eric,
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> 
> > Hello,
> >
> > I've been through the manual and the faq but just cannot seem to find
> > the answer to a very simple question:  I need to re-publish
> > (i.e. re-export) a website that is written in org-mode because I've
> > changed some of the style information that is "included" by each .org
> > file.  Although I can force a re-export on individual files (C-u C-c C-e
> > F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
> > export the project simply skips all the unmodified files.  Trying C-u
> > C-c C-e X gives 
> >
> > ,----
> > | org-publish-get-base-files: Wrong type argument: stringp, nil
> > `----
> >
> 
> I receive the same error when I try to export using C-u C-c C-e X.
> 
> As a temporary fix, you can use C-u C-c C-e P while visiting one of the
> org files in the project. That's the method I use to update an entire
> website.
> 

As a workaround for the skipping of unmodified files: does setting

    org-publish-use-timestamps-flag

to nil temporarily do the deed? I'm not sure what that will do to
the timestamps: they will probably be completely out of sync afterwards;
but that's exactly what Matt's method does (for the current project
only), so it could not be *too* bad !-)

You can also try to blow away (or move aside) the time stamps directory
(~/.org-timestamps by default, or the value of
org-publish-timestamp-directory) and try publishing again.

HTH,
Nick

Re: re-exporting a web site

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> As a workaround for the skipping of unmodified files: does setting
> 
>     org-publish-use-timestamps-flag
> 
> to nil temporarily do the deed? I'm not sure what that will do to
> the timestamps: they will probably be completely out of sync afterwards;
> but that's exactly what Matt's method does (for the current project
> only), so it could not be *too* bad !-)
> 

D'oh - never mind. I need more coffee.

Nick

Re: re-exporting a web site

[Eric S Fraga, Eric S Fraga]

Nick Dokos writes:
> As a workaround for the skipping of unmodified files: does setting
>
>     org-publish-use-timestamps-flag
>
> to nil temporarily do the deed? I'm not sure what that will do to
> the timestamps: they will probably be completely out of sync afterwards;
> but that's exactly what Matt's method does (for the current project
> only), so it could not be *too* bad !-)

I guess that would work.  In the end, I used Matt's method (having
re-ordered my project list first so that org-mode would choose the
right project by default with the P option...).

> You can also try to blow away (or move aside) the time stamps directory
> (~/.org-timestamps by default, or the value of
> org-publish-timestamp-directory) and try publishing again.

Duh!  I did think of blowing it away as I've done that in the past but
never thought of simply moving it out of the way and then moving it
back again afterwards which would at least have retained the time
stamps for other projects.  Sigh.  I'll remember this for next time
however!

Many thanks all!

eric

Re: re-exporting a web site

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> Nick Dokos writes:
> > As a workaround for the skipping of unmodified files: does setting
> >
> >     org-publish-use-timestamps-flag
> >
> > to nil temporarily do the deed? I'm not sure what that will do to
> > the timestamps: they will probably be completely out of sync afterwards;
> > but that's exactly what Matt's method does (for the current project
> > only), so it could not be *too* bad !-)
> 
> I guess that would work.  In the end, I used Matt's method (having
> re-ordered my project list first so that org-mode would choose the
> right project by default with the P option...).
> 

I did not try the experiment, but as I indicated in my "D'oh" response
to me :-), I think you would run into the same bug that you ran into
originally: org-publish with a prefix arg sets
org-publish-use-time-stamps-flag to nil around the subordinate
org-publish-projects call, so these methods are (probably) equivalent. Can
you get a stack trace? 

Thanks,
Nick

Re: Re: re-exporting a web site

[Manish]

  On Tue, May 19, 2009 at 7:19 PM, Eric S Fraga wrote:
  > Manish <mailtomanish.sharma@gmail.com> writes:
  >
  >> On Tue, May 19, 2009 at 5:06 PM, Eric S Fraga wrote:
  >>> Hello,
  >>>
  >>> I've been through the manual and the faq but just cannot seem to find
  >>> the answer to a very simple question: I need to re-publish
  >>> (i.e. re-export) a website that is written in org-mode because I've
  >>> changed some of the style information that is "included" by each .org
  >>> file. Although I can force a re-export on individual files (C-u C-c C-e
  >>> F), I cannot force a re-export on a "project" (C-c C-e X). Asking to
  >>> export the project simply skips all the unmodified files. Trying C-u
  >>> C-c C-e X gives
  >>>
  >>> ,----
  >>> | org-publish-get-base-files: Wrong type argument: stringp, nil
  >>> `----
  >>>
  >>> Is this a bug? I am running the latest org-mode version from git (as of
  >>> yesterday evening, in any case) on emacs version 23.0.93.1.
  >>>
  >>> I know I can delete all the files in .org-timestamps/ but this is rather
  >>> a sledgehammer approach (as it will cause unnecessary re-publishing for
  >>> other projects).
  >>>
  >>> Is there an easy way to re-export a project?
  >>
  >> Does publishing with a prefix not work?
  >
  > Thanks Manish. But unfortunately that's what I tried:
  > C-u C-c C-e X projectname
  > and the error message I've given above results!

Sorry about that.  Lesson learnt: never respond while half-asleep. :-/

-- 
Manish

Re: re-exporting a web site

[Carsten Dominik]

Thanks to everyone who contributed to this thread.

This was a stupid bug, fixed now.

- Carsten

On May 19, 2009, at 1:36 PM, Eric S Fraga wrote:

> Hello,
>
> I've been through the manual and the faq but just cannot seem to find
> the answer to a very simple question:  I need to re-publish
> (i.e. re-export) a website that is written in org-mode because I've
> changed some of the style information that is "included" by each .org
> file.  Although I can force a re-export on individual files (C-u C-c  
> C-e
> F), I cannot force a re-export on a "project" (C-c C-e X).  Asking to
> export the project simply skips all the unmodified files.  Trying C-u
> C-c C-e X gives
>
> ,----
> | org-publish-get-base-files: Wrong type argument: stringp, nil
> `----
>
> Is this a bug?  I am running the latest org-mode version from git  
> (as of
> yesterday evening, in any case) on emacs version 23.0.93.1.
>
> I know I can delete all the files in .org-timestamps/ but this is  
> rather
> a sledgehammer approach (as it will cause unnecessary re-publishing  
> for
> other projects).
>
> Is there an easy way to re-export a project?
>
> Thanks,
> eric
>
> -- 
> MC .  -.. --- -  ..-. .-. .- --. .-  .- -  ..- -.-. .-..  .-  
> -.-.  ..- -.-
> NL Professor Eric S Fraga, UCL, http://www.homepages.ucl.ac.uk/~ucecesf/
> BF >++++++++++[>++++++++++>+++++++++++[<]>-]>++.>++++.<-----.+++++ 
> +.------.
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: re-exporting a web site

[Sebastian Rose]

I do

for f in $(find ~/org/ -name '*.org'); do touch "${f}"; done

    Sebastian


Eric S Fraga <ucecesf@ucl.ac.uk>, Eric S Fraga <ucecesf@ucl.ac.uk>
writes:
> Nick Dokos writes:
>> As a workaround for the skipping of unmodified files: does setting
>>
>>     org-publish-use-timestamps-flag
>>
>> to nil temporarily do the deed? I'm not sure what that will do to
>> the timestamps: they will probably be completely out of sync afterwards;
>> but that's exactly what Matt's method does (for the current project
>> only), so it could not be *too* bad !-)
>
> I guess that would work.  In the end, I used Matt's method (having
> re-ordered my project list first so that org-mode would choose the
> right project by default with the P option...).
>
>> You can also try to blow away (or move aside) the time stamps directory
>> (~/.org-timestamps by default, or the value of
>> org-publish-timestamp-directory) and try publishing again.
>
> Duh!  I did think of blowing it away as I've done that in the past but
> never thought of simply moving it out of the way and then moving it
> back again afterwards which would at least have retained the time
> stamps for other projects.  Sigh.  I'll remember this for next time
> however!
>
> Many thanks all!
>
> eric
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

Re: re-exporting a web site

[Eric S Fraga, Eric S Fraga]

Carsten Dominik writes:
> Thanks to everyone who contributed to this thread.
> 
> This was a stupid bug, fixed now.

Thanks Carsten!

Re: re-exporting a web site

[Eric S Fraga, Eric S Fraga]

Sebastian Rose writes:
> I do
>
> for f in $(find ~/org/ -name '*.org'); do touch "${f}"; done

That would definitely work!  I think I got stuck in rut, but a good
one this time: org-mode!  I should have thought of using the rest of
the system to solve my problem.

Again, thanks to all.

LaTeX export bugs?

[Sébastien Vauban]

Hello,

To make things clear, I love Org-mode (yes, I voted) and its LaTeX export.
More than you can imagine: I now look for avoiding writing any LaTeX document,
and have the export do all the work for me...

BTW, any solution for exporting to a Beamer presentation?  I'd be very very
very interested by anything in that direction. That's the last piece of the
whole puzzle, IMHO.

Though, working more and more in that direction (Org-mode -> LaTeX), I've seen
a couple of weird things that I've compiled into an ECM, for ease of use:

--8<---------------cut here---------------start------------->8---
* Org

  - If you have a level 3 item under a level 1 item, the level 3 doesn't get
    exported to LaTeX. I know this is not a normal situation, but it happens
    when restructuring some text, and you loose it in the exported view...

***** THIS SECTION WILL DISAPPEAR!!

      This text is not exported. Though, I'm not always aware of it, when
      sections are long (spreading over more than one screen page)...

*** Level 2 -- is there a level 3 above?

    - Table with formulas and environment /framed/ :

      The following table will be framed, but TBL formulas do not work
      anymore.

        #+ATTR_LaTeX: align=lrrr
        #+LaTeX: \begin{framed}
        | Code      | \euro{} |  \% | \euro{} |
        |-----------+---------+-----+---------|
        | GSM       |         |     |    0.00 |
        | Internet  |  168.45 | 100 |  168.45 |
        | Matériel  |  295.99 | 100 |  295.99 |
        | Publicité |  214.25 |  33 |   70.70 |
        | Autres    |         |     |    0.00 |
        |-----------+---------+-----+---------|
        | Total     |         |     |  535.14 |
        #+LaTeX: \end{framed}
        #+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)

      Swapping these two last lines gives LaTeX errors... What's the solution
      for having both: an environment around the table and formulas that work?

      Why do I have to escape the sign symbol as soon as I put LaTeX commands
      (and not BEGIN..END_LaTeX) near it?

    - Hyperlink to other sections: see [[To be referenced]]. Looking in the
      produced LaTeX code, it always link to the current section instead!

    - Quotes are sometimes exported in a weird /fashion/ : see "Industriels,
      et commerçants". And compare with the quotes in the next sample
      ("Industriels et commerçants").

      See as well that /fashion/ is not in italic above. Apparently because of
      the special non-breaking space following the second slash... BTW, a
      possibility would be to translate the "non-breaking space" to its LaTeX
      equivalent syntax (the "tilde" sign).

* To be referenced

  This should be the landing point for the hyperreference above.
--8<---------------cut here---------------end--------------->8---

Once again, thanks to all of you that provide us with those wonderful
features...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi all,

> To make things clear, I love Org-mode (yes, I voted) and its LaTeX export.
> More than you can imagine: I now look for avoiding writing any LaTeX document,
> and have the export do all the work for me...
>
> BTW, any solution for exporting to a Beamer presentation?  I'd be very very
> very interested by anything in that direction. That's the last piece of the
> whole puzzle, IMHO.
>
> Though, working more and more in that direction (Org-mode -> LaTeX), I've seen
> a couple of weird things that I've compiled into an ECM, for ease of use:
>
> * Org
>
>   - If you have a level 3 item under a level 1 item, the level 3 doesn't get
>     exported to LaTeX. I know this is not a normal situation, but it happens
>     when restructuring some text, and you loose it in the exported view...
>
> ***** THIS SECTION WILL DISAPPEAR!!
>
>       This text is not exported. Though, I'm not always aware of it, when
>       sections are long (spreading over more than one screen page)...
>
> *** Level 2 -- is there a level 3 above?
>
>     - Table with formulas and environment /framed/ :
>
>       The following table will be framed, but TBL formulas do not work
>       anymore.
>
>         #+ATTR_LaTeX: align=lrrr
>         #+LaTeX: \begin{framed}
>         | Code      | \euro{} |  \% | \euro{} |
>         |-----------+---------+-----+---------|
>         | GSM       |         |     |    0.00 |
>         | Internet  |  168.45 | 100 |  168.45 |
>         | Matériel  |  295.99 | 100 |  295.99 |
>         | Publicité |  214.25 |  33 |   70.70 |
>         | Autres    |         |     |    0.00 |
>         |-----------+---------+-----+---------|
>         | Total     |         |     |  535.14 |
>         #+LaTeX: \end{framed}
>         #+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
>
>       Swapping these two last lines gives LaTeX errors... What's the solution
>       for having both: an environment around the table and formulas that work?
>
>       Why do I have to escape the sign symbol as soon as I put LaTeX commands
>       (and not BEGIN..END_LaTeX) near it?
>
>     - Hyperlink to other sections: see [[To be referenced]]. Looking in the
>       produced LaTeX code, it always link to the current section instead!
>
>     - Quotes are sometimes exported in a weird /fashion/ : see "Industriels,
>       et commerçants". And compare with the quotes in the next sample
>       ("Industriels et commerçants").
>
>       See as well that /fashion/ is not in italic above. Apparently because of
>       the special non-breaking space following the second slash... BTW, a
>       possibility would be to translate the "non-breaking space" to its LaTeX
>       equivalent syntax (the "tilde" sign).
>
> * To be referenced
>
>   This should be the landing point for the hyperreference above.
>
> Once again, thanks to all of you that provide us with those wonderful
> features...

Anybody commenting on the above?

Other things I've noticed:

- Even with version 6.28, the `#+TBLNAME' tag must be located in column 0 (at
  least, for the highlighting features to work)

- Remote references to other tables are great, but they only work with
  absolute references, not with named cells. On the wishlist (easy to
  say ;-)), I image it'd be utmost useful to be able to name a cell and reuse
  its name in a remote ref.

Thanks for any commentary on the above...

Thank you very much Carsten, Bastien and Co...
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Nick Dokos]

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

=?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> wrote:

> >
> > BTW, any solution for exporting to a Beamer presentation?  I'd be
> > very very  very interested by anything in that direction. That's
> > the last piece of the whole puzzle, IMHO.
> >

I did a beamer presentation in org-mode last month (1 hour, about 20 slides).
Here is a simplified version (I'll talk about some problems at the end).

o org-export-latex-classes is augmented with a beamer element as follows:

,----
| (add-to-list 'org-export-latex-classes
|                '("beamer"
|                  "\\documentclass[11pt]{beamer}\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\\usepackage{hyperref}\n\\usepackage{verbatim}\n\\setbeameroption{show notes}\n\\usetheme{Goettingen}\n\\useoutertheme{infolines}"
|                  ("\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}"
|                   "\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}")
|                  ("\\item{%s}" . "\\item*{%s}")
|                  ("\\end{itemize}\\note{" "}")))
`----

o Here is an input file:

,----
| #+LaTeX_CLASS: beamer
| #+TITLE: Example presentation
| #+AUTHOR: Nick Dokos \\ $<$\href{mailto:nicholas.dokos@hp.com}{nicholas.dokos@hp.com}$>$
| #+EMAIL: nicholas.dokos@hp.com
| 
| * Why
| ** Reason 1.
|    Text explaining reason 1.
| ** Reason 2.
|    ... more explanations.
| ** Reason 3.
|    Blah, blah, blah.
|  
| ** Reason 4.
|    Why not?
| 
| * What
| ** First piece.
| ** Second piece.
| ** Third piece.
| ** Fourth piece.
`----

o Export it to latex (and zap the TOC - see below):


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: TeX file produced by exporting the org file (and zapping the TOC) --]
[-- Type: text/x-tex, Size: 976 bytes --]

% Created 2009-07-01 Wed 21:19
\documentclass[11pt]{beamer}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{hyperref}
\usepackage{verbatim}
\setbeameroption{show notes}
\usetheme{Goettingen}
\useoutertheme{infolines}


\title{Example presentation}
\author{Nick Dokos \\ $<$\href{mailto:nicholas.dokos@hp.com}{nicholas.dokos@hp.com}$>$}
\date{01 July 2009}

\begin{document}

\maketitle

\begin{frame}\frametitle{Why}\begin{itemize}
\label{sec-1}

\item{Reason 1.}
\label{sec-1.1}

   Text explaining reason \#1.
\item{Reason 2.}
\label{sec-1.2}

   \ldots{} more explanations.
\item{Reason 3.}
\label{sec-1.3}

   Blah, blah, blah.
 
\item{Reason 4.}
\label{sec-1.4}

   Why not?

\end{itemize}\end{frame}
\begin{frame}\frametitle{What}\begin{itemize}
\label{sec-2}

\item{First piece.}
\label{sec-2.1}

\item{Second piece.}
\label{sec-2.2}

\item{Third piece.}
\label{sec-2.3}

\item{Fourth piece.}
\label{sec-2.4}



\end{itemize}\end{frame}

\end{document}

[-- Attachment #3: Type: text/plain, Size: 48 bytes --]


and pdflatex it to produce the following pdf:


[-- Attachment #4: PDF produced by pdflatex --]
[-- Type: application/pdf, Size: 62868 bytes --]

[-- Attachment #5: Type: text/plain, Size: 1379 bytes --]



Some notes:

o Level 1 headlines become slide titles.

o Level 2 headlines become items in the slide and the text under the level
  2 headlines ends up as text in the item.

o Level 3 headlines (not shown in the sample document) were supposed to
  become notes, but this obviously will not work this way. I don't know
  how to make it work. In the end, I edited the tex file by hand in
  order to get the notes right.

o Moreover (and I think this is a bug in the latex exporter), I had to
  rearrange the notes by hand: they ended up in the wrong slides.
  I have had zero time to chase this however, so I am not really sure
  why this happened.

o There was a problem with the table of contents (it's empty and it pushes
  the title of the first slide down), so I manually zapped it from
  the tex file.

o Latex had some peculiar objections to the labels and I did not care
  about them, so I preprocessed them out of existence in the tex file.

After a little practice, I could edit the tex file to take care of all
the problems in about 5 minutes. Even so, after getting the bulk of the
contents of the presentation done, I did a final production of the tex
file and did the final touchups on that. One of these days, I'll have to
go back and figure out some of the problems. For now, this zeroth
approximation to a solution will have to suffice.

HTH.

Thanks,
Nick






[-- Attachment #6: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: LaTeX export bugs?

[Carsten Dominik]

On Jun 26, 2009, at 3:34 PM, Sébastien Vauban wrote:

> Hello,
>
> To make things clear, I love Org-mode (yes, I voted) and its LaTeX  
> export.
> More than you can imagine: I now look for avoiding writing any LaTeX  
> document,
> and have the export do all the work for me...
>
> BTW, any solution for exporting to a Beamer presentation?  I'd be  
> very very
> very interested by anything in that direction. That's the last piece  
> of the
> whole puzzle, IMHO.
>
> Though, working more and more in that direction (Org-mode -> LaTeX),  
> I've seen
> a couple of weird things that I've compiled into an ECM, for ease of  
> use:
>
> --8<---------------cut here---------------start------------->8---
> * Org
>
>  - If you have a level 3 item under a level 1 item, the level 3  
> doesn't get
>    exported to LaTeX. I know this is not a normal situation, but it  
> happens
>    when restructuring some text, and you loose it in the exported  
> view...

Yes, the parser currently requires the structure to be consistent
and does not fail gracefully if not.....

>
> ***** THIS SECTION WILL DISAPPEAR!!
>
>      This text is not exported. Though, I'm not always aware of it,  
> when
>      sections are long (spreading over more than one screen page)...
>
> *** Level 2 -- is there a level 3 above?
>
>    - Table with formulas and environment /framed/ :
>
>      The following table will be framed, but TBL formulas do not work
>      anymore.
>
>        #+ATTR_LaTeX: align=lrrr
>        #+LaTeX: \begin{framed}
>        | Code      | \euro{} |  \% | \euro{} |
>        |-----------+---------+-----+---------|
>        | GSM       |         |     |    0.00 |
>        | Internet  |  168.45 | 100 |  168.45 |
>        | Matériel  |  295.99 | 100 |  295.99 |
>        | Publicité |  214.25 |  33 |   70.70 |
>        | Autres    |         |     |    0.00 |
>        |-----------+---------+-----+---------|
>        | Total     |         |     |  535.14 |
>        #+LaTeX: \end{framed}
>        #+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
>
>      Swapping these two last lines gives LaTeX errors... What's the  
> solution
>      for having both: an environment around the table and formulas  
> that work?

This is a hard problem.  It is on my list, but will not be fixed soon.

>
>      Why do I have to escape the sign symbol as soon as I put LaTeX  
> commands
>      (and not BEGIN..END_LaTeX) near it?

I do not understand what you mean here.

>
>    - Hyperlink to other sections: see [[To be referenced]]. Looking  
> in the
>      produced LaTeX code, it always link to the current section  
> instead!

Have not yet looked into this.  Use IDs or custom IDs to links to
sections, that is much better.

>
>    - Quotes are sometimes exported in a weird /fashion/ : see  
> "Industriels,
>      et commerçants". And compare with the quotes in the next sample
>      ("Industriels et commerçants").

Fixed.

>
>      See as well that /fashion/ is not in italic above.

It is for me

> Apparently because of
>      the special non-breaking space following the second slash...

Looks like the non-breaking space did not make it through
the mailing process.  What exactly are you using?

> BTW, a
>      possibility would be to translate the "non-breaking space" to  
> its LaTeX
>      equivalent syntax (the "tilde" sign).
>
> * To be referenced
>
>  This should be the landing point for the hyperreference above.
> --8<---------------cut here---------------end--------------->8---
>
> Once again, thanks to all of you that provide us with those wonderful
> features...
>
> Best regards,
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Carsten Dominik]

On Jul 1, 2009, at 10:21 PM, Sébastien Vauban wrote:
> Other things I've noticed:
>
> - Even with version 6.28, the `#+TBLNAME' tag must be located in  
> column 0 (at
>  least, for the highlighting features to work)

Fixed, thanks.

>
> - Remote references to other tables are great, but they only work with
>  absolute references, not with named cells.

They actually do work fine.  A call like remote(mytbl,$name) will work
in this table

| _ | name |
|   | value |

- Carsten

> On the wishlist (easy to
>  say ;-)), I image it'd be utmost useful to be able to name a cell  
> and reuse
>  its name in a remote ref.
>
> Thanks for any commentary on the above...
>
> Thank you very much Carsten, Bastien and Co...
>  Seb
>
> -- 
> Sébastien Vauban
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> Sébastien Vauban wrote:
>> Other things I've noticed:
>>
>> - Even with version 6.28, the `#+TBLNAME' tag must be located in column 0
>> (at least, for the highlighting features to work)
>
> Fixed, thanks.

Euh, no, *I* am supposed to answer: "Fixed, thanks", and I'm doing it... ;-)


>> - Remote references to other tables are great, but they only work with
>>  absolute references, not with named cells.
>
> They actually do work fine.  A call like remote(mytbl,$name) will work
> in this table
>
> | _ | name |
> |   | value |

OK. I did not understand from the doc (section 3.5.1) that I had to prefix the
name of the cell with $:

   "REF is an absolute field [...] as described above."

I admit that, knowing it, I understand the above text better. Maybe is such
an example missing?

Now, more important question, one of the few that's not answered from my
previous post: how can I shade or frame a table? For me, inserting #+LaTeX
tags is different from inserting #+BEGIN_LaTeX and #+END_LaTeX tags: the first
one should have no impact on the rest of the text.

Though, it isn't as you can see with my following example:

--8<---------------cut here---------------start------------->8---
#+LaTeX: \begin{framed}
#+ATTR_LaTeX: align=lrrr
| Code      | \euro{} |  \% | \euro{} |
|-----------+---------+-----+---------|
| GSM       |         |     |    0.00 |
| Internet  |  168.45 | 100 |  168.45 |
| Matériel  |  295.99 | 100 |  295.99 |
| Publicité |  214.25 |  33 |   70.70 |
| Autres    |         |     |    0.00 |
|-----------+---------+-----+---------|
| Total     |         |     |  535.14 |
#+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
#+LaTeX: \end{framed}
--8<---------------cut here---------------end--------------->8---

Am I misunderstanding section 12.7.2 or is this a feature?

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Carsten Dominik]

On Jul 2, 2009, at 10:40 PM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Carsten Dominik wrote:
>> Sébastien Vauban wrote:
>>> Other things I've noticed:
>>>
>>> - Even with version 6.28, the `#+TBLNAME' tag must be located in  
>>> column 0
>>> (at least, for the highlighting features to work)
>>
>> Fixed, thanks.
>
> Euh, no, *I* am supposed to answer: "Fixed, thanks", and I'm doing  
> it... ;-)

The "thanks" is short for "thanks for your report/idea" :-)

>
>
>>> - Remote references to other tables are great, but they only work  
>>> with
>>> absolute references, not with named cells.
>>
>> They actually do work fine.  A call like remote(mytbl,$name) will  
>> work
>> in this table
>>
>> | _ | name |
>> |   | value |
>
> OK. I did not understand from the doc (section 3.5.1) that I had to  
> prefix the
> name of the cell with $:
>
>   "REF is an absolute field [...] as described above."
>
> I admit that, knowing it, I understand the above text better. Maybe  
> is such
> an example missing?

Fixed, thanks.

>
> Now, more important question, one of the few that's not answered  
> from my
> previous post: how can I shade or frame a table? For me, inserting # 
> +LaTeX
> tags is different from inserting #+BEGIN_LaTeX and #+END_LaTeX tags:  
> the first
> one should have no impact on the rest of the text.
>
> Though, it isn't as you can see with my following example:
>
> --8<---------------cut here---------------start------------->8---
> #+LaTeX: \begin{framed}
> #+ATTR_LaTeX: align=lrrr
> | Code      | \euro{} |  \% | \euro{} |
> |-----------+---------+-----+---------|
> | GSM       |         |     |    0.00 |
> | Internet  |  168.45 | 100 |  168.45 |
> | Matériel  |  295.99 | 100 |  295.99 |
> | Publicité |  214.25 |  33 |   70.70 |
> | Autres    |         |     |    0.00 |
> |-----------+---------+-----+---------|
> | Total     |         |     |  535.14 |
> #+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
> #+LaTeX: \end{framed}
> --8<---------------cut here---------------end--------------->8---
>
> Am I misunderstanding section 12.7.2 or is this a feature?

This does not work.  What is happening here is that during
LaTeX export, these begin/end lines are inserted into the buffer.
Then the LaTeX exporter marks the entire content of this environment
as something that should be exported literally to LaTeX, this is
why you can write

\begin{equation}
a=b
\end{equation}

and it will all be exported literally to LaTeX.

The fact that the table is transformed into a LaTeX table at
all is actually a bug which I will fix.

So there is not really a standard way to do what you want.

However, you could take a look as Chris Gray's contributes package
org-special-blocks.el

    http://orgmode.org/worg/org-contrib/org-special-blocks.php

which was made just for this use case.

Another workaround (hack, really) would be

#+LATEX_HEADER: \def\noop{}

\noop\begin{framed}
...
\noop\end{framed}

This will trick Org-mode by not having the \begin macro at
the beginning of a line, so it will not protect the content
of the environment.  Dirty, but works.

HTH

- Carsten

Re: LaTeX export bugs?

[Sébastien Vauban]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 5541 bytes --]

Hi Carsten,

Carsten Dominik wrote:
> Sébastien Vauban wrote:
>>
>>  - If you have a level 3 item under a level 1 item, the level 3 doesn't get
>>    exported to LaTeX. I know this is not a normal situation, but it happens
>>    when restructuring some text, and you loose it in the exported view...
>
> Yes, the parser currently requires the structure to be consistent and does
> not fail gracefully if not.....

OK.


>>    - Table with formulas and environment /framed/ :
>>
>>      The following table will be framed, but TBL formulas do not work
>>      anymore.
>>
>>        #+ATTR_LaTeX: align=lrrr
>>        #+LaTeX: \begin{framed}
>>        | Code      | \euro{} |  \% | \euro{} |
>>        |-----------+---------+-----+---------|
>>        | GSM       |         |     |    0.00 |
>>        | Internet  |  168.45 | 100 |  168.45 |
>>        | Matériel  |  295.99 | 100 |  295.99 |
>>        | Publicité |  214.25 |  33 |   70.70 |
>>        | Autres    |         |     |    0.00 |
>>        |-----------+---------+-----+---------|
>>        | Total     |         |     |  535.14 |
>>        #+LaTeX: \end{framed}
>>        #+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
>>
>>      Swapping these two last lines gives LaTeX errors... What's the
>>      solution for having both: an environment around the table and formulas
>>      that work?
>
> This is a hard problem.  It is on my list, but will not be fixed soon.

I had not seen this reply yet, when re-sending my question yesterday night.
I've got the solution from Chris to test...


>>      Why do I have to escape the sign symbol as soon as I put LaTeX
>>      commands (and not BEGIN..END_LaTeX) near it?
>
> I do not understand what you mean here.

I don't understand the details of the export process. For me, if I have such a
table:

| Item     |  % |
|----------+----|
| Sample 1 | 20 |

and I want it framed, adding `#+LaTeX: \begin{framed}' and `#+LaTeX:
\end{framed}' should be transparent for the Org -> LaTeX conversion process.

It is not: as soon as I do such a thing, I need to escape the `%' sign:

| Item     | \% |
|----------+----|
| Sample 1 | 20 |

For me, the `%' should be escaped independently of whether I add or not such a
LaTeX tag.


>>    - Hyperlink to other sections: see [[To be referenced]]. Looking in the
>>      produced LaTeX code, it always link to the current section instead!
>
> Have not yet looked into this. Use IDs or custom IDs to links to sections,
> that is much better.

OK.


>>    - Quotes are sometimes exported in a weird /fashion/ : see "Industriels,
>>      et commerçants". And compare with the quotes in the next sample
>>      ("Industriels et commerçants").
>
> Fixed.

Thanks that *you* fixed it ;-)


>>      See as well that /fashion/ is not in italic above.
>
> It is for me

I guess you talk to someone else? ;-)


>>      Apparently because of the special non-breaking space following the
>>      second slash...
>
> Looks like the non-breaking space did not make it through
> the mailing process.  What exactly are you using?

Here is one non-breaking space: ` ', and here is what Emacs tells me about it
(when `C-u C-x ='):

--8<---------------cut here---------------start------------->8---
        character:   (160, #o240, #xa0)
preferred charset: unicode (Unicode (ISO10646))
       code point: 0xA0
           syntax: . 	which means: punctuation
         category: .:Base, b:Arabic, j:Japanese, l:Latin
      buffer code: #xC2 #xA0
        file code: #xC2 #xA0 (encoded by coding system utf-8-emacs-unix)
          display: by display table entry [?øŽ€‚·] (see below)

The display table entry is displayed by these fonts (glyph codes):
øŽ€‚·: -- no font --
 face: `bold'

Character code properties: customize what to show
  name: NO-BREAK SPACE
  old-name: NON-BREAKING SPACE
  general-category: Zs (Separator, Space)
  decomposition: (noBreak 32) (noBreak ' ')

There are text properties here:
  fontified            t
--8<---------------cut here---------------end--------------->8---

I insert them when I have a colon (for example) preceded by a space: that
space is automagically converted to non-breaking one, thanks to the following
code in my `.emacs' file:


--8<---------------cut here---------------start------------->8---
(defun my-insert-colon ()
  (interactive)
  (if (eq (char-before) ?\ ) ; normal space
      (progn
        (backward-delete-char 1)
        (if (equal mode-name "PDFLaTeX")
            (insert "~:") ; for LaTeX-only
          (insert " :"))) ; non-breaking space
    (insert ":")))

(defun my-double-keys ()
  "Specific keys."
  (interactive)
  (local-set-key ":" 'my-insert-colon))

(add-hook 'text-mode-hook 'my-double-keys)
(add-hook 'message-mode-hook 'my-double-keys)
--8<---------------cut here---------------end--------------->8---


>>      BTW, a possibility would be to translate the "non-breaking space" to
>>      its LaTeX equivalent syntax (the "tilde" sign).

If you don't mind, this is on my wishlist of Org-mode features... You see my
Emacs code handles it when I write LaTeX myself, something I wanna avoid like
pest now that I'm more than delighted with the powerful possibilities and nice
reading presentation environment of Org.

Best regards... and thank you very much once again!
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi Nick,

Nick Dokos wrote:
> Sebastien Vauban wrote:
>
>> > BTW, any solution for exporting to a Beamer presentation? I'd be very
>> > very very interested by anything in that direction. That's the last piece
>> > of the whole puzzle, IMHO.
>> >
>
> I did a beamer presentation in org-mode last month (1 hour, about 20 slides).
> Here is a simplified version (I'll talk about some problems at the end).
>
> o org-export-latex-classes is augmented with a beamer element as follows:
>
> ,----
> | (add-to-list 'org-export-latex-classes
> |                '("beamer"
> |                  "\\documentclass[11pt]{beamer}\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\\usepackage{hyperref}\n\\usepackage{verbatim}\n\\setbeameroption{show notes}\n\\usetheme{Goettingen}\n\\useoutertheme{infolines}"
> |                  ("\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}"
> |                   "\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}")
> |                  ("\\item{%s}" . "\\item*{%s}")
> |                  ("\\end{itemize}\\note{" "}")))
> `----

Excellent idea...


> o Here is an input file:
>
> ,----
> | #+LaTeX_CLASS: beamer
> | #+TITLE: Example presentation
> | #+AUTHOR: Nick Dokos \\ $<$\href{mailto:nicholas.dokos-VXdhtT5mjnY@public.gmane.org}{nicholas.dokos-VXdhtT5mjnY@public.gmane.org}$>$
> | #+EMAIL: nicholas.dokos-VXdhtT5mjnY@public.gmane.org
> | 
> | * Why
> | ** Reason 1.
> |    Text explaining reason 1.
> | ** Reason 2.
> |    ... more explanations.
> | ** Reason 3.
> |    Blah, blah, blah.
> |  
> | ** Reason 4.
> |    Why not?
> | 
> | * What
> | ** First piece.
> | ** Second piece.
> | ** Third piece.
> | ** Fourth piece.
> `----
>
> o Export it to latex (and zap the TOC - see below):

Weird. Having done the above `add-to-list' in Emacs (with `C-x C-e'), I got a
different exported file than yours. But really different:

--8<---------------cut here---------------start------------->8---
% Created 2009-07-03 Fri 10:32
\documentclass[11pt]{beamer}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{hyperref}
\usepackage{verbatim}
\setbeameroption{show notes}
\usetheme{Goettingen}
\useoutertheme{infolines}


\title{Example presentation}
\author{Nick Dokos \\ $<$\href{mailto:nicholas.dokos-VXdhtT5mjnY@public.gmane.org}{nicholas.dokos@hp.com}$>$}
\date{03 July 2009}

\begin{document}

\maketitle

\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}

\begin{frame}\frametitle{Why}\begin{itemize}
\label{sec-1}

\end{itemize}\end{frame}
\begin{frame}\frametitle{What}\begin{itemize}
\label{sec-2}

\end{itemize}\end{frame}

\end{document}
--8<---------------cut here---------------end--------------->8---

There is no text, in fact...
Don't understand why...


> Some notes:
>
> o Level 1 headlines become slide titles.
>
> o Level 2 headlines become items in the slide and the text under the level
>   2 headlines ends up as text in the item.
>
> o Level 3 headlines (not shown in the sample document) were supposed to
>   become notes, but this obviously will not work this way. I don't know
>   how to make it work. In the end, I edited the tex file by hand in
>   order to get the notes right.
>
> o Moreover (and I think this is a bug in the latex exporter), I had to
>   rearrange the notes by hand: they ended up in the wrong slides.
>   I have had zero time to chase this however, so I am not really sure
>   why this happened.
>
> o There was a problem with the table of contents (it's empty and it pushes
>   the title of the first slide down), so I manually zapped it from
>   the tex file.
>
> o Latex had some peculiar objections to the labels and I did not care
>   about them, so I preprocessed them out of existence in the tex file.
>
> After a little practice, I could edit the tex file to take care of all the
> problems in about 5 minutes. Even so, after getting the bulk of the contents
> of the presentation done, I did a final production of the tex file and did
> the final touchups on that. One of these days, I'll have to go back and
> figure out some of the problems. For now, this zeroth approximation to a
> solution will have to suffice.

I think as well we can live with such minor troubles for the moment. And still
take advantage of Org...

Though, I have a bigger problem getting to there.

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Nick Dokos]

=?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> wrote:

> 
> Weird. Having done the above `add-to-list' in Emacs (with `C-x C-e'),
>  I got a different exported file than yours. But really different:
> 
> --8<---------------cut here---------------start------------->8---
> ...
> --8<---------------cut here---------------end--------------->8---
> 
> There is no text, in fact...
> Don't understand why...
> 
> 

I don't understand why either, but it may be some setting in my setup
or your setup that leads to the different behavior. In case it matters,
I use the following versions:

GNU Emacs 23.0.93.1 (i686-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-05-11 on gamaville.dokosmarshall.org
Org-mode version 6.28trans - git latest (more or less).

Here is an even more simplified version, using a variation of Bernt
Hansen's minimal .emacs. This version of slides.org takes care of the
zapping of the TOC at the org level, and the beamer section in
minimal.emacs gets rid of the third level Notes headlines (which cannot
work this way, in any case). I checked with

       emacs -Q -l minimal.emacs slides.org

exported to latex, and ran the latex file through pdflatex a couple of
times. The resulting PDF file seems to work for me. Can you try it out?

Thanks,
Nick

Here's the minimal.emacs - you'll need to adjust the load path for your
setup:

,----
| (add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
| (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
| (require 'org-install)
| (global-set-key "\C-cl" 'org-store-link)
| (global-set-key "\C-ca" 'org-agenda)
| (global-set-key "\C-cb" 'org-iswitchb)
| (setq org-log-done (quote time))
| (setq org-log-into-drawer t)
| 
| (load "org-exp")
| (load "org-latex")
| 
| (add-to-list 'org-export-latex-classes
|              '("beamer"
|                "\\documentclass[11pt]{beamer}
| \\usepackage[utf8]{inputenc}
| \\usepackage[T1]{fontenc}
| \\usepackage{hyperref}
| \\usepackage{verbatim}
| \\setbeameroption{show notes}
| \\usetheme{Goettingen}
| \\useoutertheme{infolines}"
|                ("\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}"
|                 "\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}")
|                ("\\item{%s}" . "\\item*{%s}")
|                )
|              )
`----

and here's slides.org:

,----
| #+LaTeX_CLASS: beamer
| #+TITLE: Example presentation
| #+AUTHOR: Nick Dokos \\ $<$\href{mailto:nicholas.dokos@hp.com}{nicholas.dokos@hp.com}$>$
| #+EMAIL: nicholas.dokos@hp.com
| #+OPTIONS: toc:nil H:2
| 
| * Why
| ** Reason 1.
|    Text explaining reason #1.
| ** Reason 2.
|    ... more explanations.
| ** Reason 3.
|    Blah, blah, blah.
|  
| ** Reason 4.
|    Why not?
| 
| * What
| ** First piece.
| ** Second piece.
| ** Third piece.
| ** Fourth piece.
`----

Re: Exporting to a Beamer presentation

[Sébastien Vauban]

Hi Nick,

>>>> BTW, any solution for exporting to a Beamer presentation? I'd be very
>>>> very very interested by anything in that direction. That's the last piece
>>>> of the whole puzzle, IMHO.
>>>
>>> I did a beamer presentation in org-mode last month (1 hour, about 20
>>> slides). Here is a simplified version (I'll talk about some problems at
>>> the end).
>>>
>>> o org-export-latex-classes is augmented with a beamer element as follows:
>>>
>>> ,----
>>> | (add-to-list 'org-export-latex-classes
>>> |                '("beamer"
>>> |                  "\\documentclass[11pt]{beamer}\n\\usepackage[utf8]{inputenc}\n\\usepackage[T1]{fontenc}\n\\usepackage{hyperref}\n\\usepackage{verbatim}\n\\setbeameroption{show notes}\n\\usetheme{Goettingen}\n\\useoutertheme{infolines}"
>>> |                  ("\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}"
>>> |                   "\\begin{frame}\\frametitle{%s}\\begin{itemize}" "\\end{itemize}\\end{frame}")
>>> |                  ("\\item{%s}" . "\\item*{%s}")
>>> |                  ("\\end{itemize}\\note{" "}")))
>>> `----

BTW, you'd better use `C-c M-m' for quoting your code. It will allow an easy
copy past of it... Like this:

--8<---------------cut here---------------start------------->8---
C-c M-m runs the command message-mark-inserted-region, which is an interactive
compiled Lisp function in `message.el'.

It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.

(message-mark-inserted-region beg end &optional verbatim)

Mark some region in the current article with enclosing tags.
See `message-mark-insert-begin' and `message-mark-insert-end'.
If verbatim, use slrn style verbatim marks ("#v+" and "#v-").
--8<---------------cut here---------------end--------------->8---


>> Excellent idea... [But] having done the above `add-to-list' in Emacs (with
>> `C-x C-e'), I got a different exported file than yours. But really
>> different [...]
>>
>> There is no text, in fact...
>> Don't understand why...
>
> I don't understand why either, but it may be some setting in my setup
> or your setup that leads to the different behavior.

Spotted it down...

I am skipping even levels and only use odd levels for the outline:

--8<---------------cut here---------------start------------->8---
    (setq org-odd-levels-only t)
--8<---------------cut here---------------end--------------->8---

But your example had even levels...

So, changing:

--8<---------------cut here---------------start------------->8---
** Reason 1
--8<---------------cut here---------------end--------------->8---

to:

--8<---------------cut here---------------start------------->8---
*** Reason 1
--8<---------------cut here---------------end--------------->8---

solves the main issue, and let me test better this fantastic export...

Thanks Nick,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Eric S Fraga]

At Mon, 06 Jul 2009 17:40:48 +0200,
Sébastien Vauban wrote:
> It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.
> 
> (message-mark-inserted-region beg end &optional verbatim)

I'm curious:  I don't have this function defined (using emacs
23.0.94.1).  Where do you get this from as it would be nice to have.

thanks,
eric

Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> At Mon, 06 Jul 2009 17:40:48 +0200,
> S=C3=A9bastien Vauban wrote:
> > It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.
> >=20
> > (message-mark-inserted-region beg end &optional verbatim)
> 
> I'm curious:  I don't have this function defined (using emacs
> 23.0.94.1).  Where do you get this from as it would be nice to have.
> 

I had the same question: it's part of message.el, but it is bound to
C-c m (at least on GNU Emacs 23.1.50.1).

HTH,
Nick

Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Eric S Fraga]

At Mon, 06 Jul 2009 13:55:45 -0400,
Nick Dokos wrote:
> I had the same question: it's part of message.el, but it is bound to
> C-c m (at least on GNU Emacs 23.1.50.1).

Ah ha!  Found it (and it's bound to C-c M-m in my version).  Didn't
see it before because I was no longer loading message.el, having moved
to wanderlust which doesn't need it.

Thanks,
eric

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi all,

Carsten Dominik wrote:
> Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> Sébastien Vauban wrote:
>> [This is not working...]
>>
--8<---------------cut here---------------start------------->8---
#+LaTeX: \begin{framed}
#+ATTR_LaTeX: align=lrrr
| Code      | \euro{} |  \% | \euro{} |
|-----------+---------+-----+---------|
| GSM       |         |     |    0.00 |
| Internet  |  168.45 | 100 |  168.45 |
| Matériel  |  295.99 | 100 |  295.99 |
| Publicité |  214.25 |  33 |   70.70 |
| Autres    |         |     |    0.00 |
|-----------+---------+-----+---------|
| Total     |         |     |  535.14 |
#+TBLFM: $4=$2*$3/100;%.2f::@7$4=vsum(@-I..@-II)
#+LaTeX: \end{framed}
--8<---------------cut here---------------end--------------->8---
>>
>> Am I misunderstanding section 12.7.2 or is this a feature?
>
> This does not work. What is happening here is that during LaTeX export,
> these begin/end lines are inserted into the buffer. Then the LaTeX exporter
> marks the entire content of this environment as something that should be
> exported literally to LaTeX, this is why you can write
>
> \begin{equation}
> a=b
> \end{equation}
>
> and it will all be exported literally to LaTeX.
>
> The fact that the table is transformed into a LaTeX table at all is actually
> a bug which I will fix.

I'm not sure I understand what's the impact of your last sentence. But, maybe,
I don't have too...

Related to this:

>> Now, more important question, one of the few that's not answered from my
>> previous post: how can I shade or frame a table? For me, inserting #+LaTeX
>> tags is different from inserting #+BEGIN_LaTeX and #+END_LaTeX tags: the
>> first one should have no impact on the rest of the text.

Rephrasing my question, asking it again in other words (showing you I did not
follow correctly): for me,

--8<---------------cut here---------------start------------->8---
#+BEGIN_framed
XXX
#+END_framed
--8<---------------cut here---------------end--------------->8---

is equivalent to:

--8<---------------cut here---------------start------------->8---
#+LaTeX: \begin{framed}
XXX
#+LaTeX: \end{framed}
--8<---------------cut here---------------end--------------->8---

If not, that's not what I understand from reading section 12.7.2 about the
quoting of LaTeX code?  Though, it seems (seemed) clear...


> So there is not really a standard way to do what you want.
>
> However, you could take a look as Chris Gray's contributes package
> org-special-blocks.el
>
>    http://orgmode.org/worg/org-contrib/org-special-blocks.php
>
> which was made just for this use case.

Excellent. Tested. Work perfectly, except for:


>>>> - Even with version 6.28, the `#+TBLNAME' tag must be located in column 0
>>>> (at least, for the highlighting features to work)
>>>
>>> Fixed, thanks.

Same problem with the Org-special-blocks constructs: they need to be declared
in column 0; otherwise, they're just ignored...

A detail, though: putting my table in a `framed' block makes the highlighting
of the keywords such as TBLNAME and TBLFM disappear...

Many thanks for all the help you all provide us with!

Best regards,
  Seb

PS- Hoping desperately Org-mode will win!

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Sébastien Vauban]

Hi Nick and Eric,

Nick Dokos wrote:
> Eric S Fraga wrote:
>> Se9bastien Vauban wrote:
>>> It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.
>>>
>>> (message-mark-inserted-region beg end &optional verbatim)
>>
>> I'm curious:  I don't have this function defined (using emacs
>> 23.0.94.1).  Where do you get this from as it would be nice to have.
>
> I had the same question: it's part of message.el, but it is bound to
> C-c m (at least on GNU Emacs 23.1.50.1).

You answered before I have the opportunity to do it...

But the answer already was in my article ;-)

>>> BTW, you'd better use `C-c M-m' for quoting your code. It will allow an
>>> easy copy past of it... Like this:

--8<---------------cut here---------------start------------->8---
C-c M-m runs the command message-mark-inserted-region, which is an interactive
compiled Lisp function in `message.el'.
--8<---------------cut here---------------end--------------->8---
                           ^^^^^^^^^^

Though, on my system:

--8<---------------cut here---------------start------------->8---
GNU Emacs 23.0.94.1 (i486-pc-linux-gnu, GTK+ Version 2.16.1) of 2009-06-18 on samarium, modified by Debian
--8<---------------cut here---------------end--------------->8---

it is still `C-c M-m'...

--8<---------------cut here---------------start------------->8---
It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.

(message-mark-inserted-region beg end &optional verbatim)
--8<---------------cut here---------------end--------------->8---

Happy Emacsing to you...

BTW, would you want a quite comprehensive `.emacs' as example, you could have
a look at http://www.mygooglest.com/fni. It's not really detailed nor
configured for Org-mode, but there is a lot to drink and to eat...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Nick Dokos]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:


> But the answer already was in my article=C2=A0;-)
> 
> >>> BTW, you'd better use `C-c M-m' for quoting your code. It will allow an
> >>> easy copy past of it... Like this:
> 
> C-c M-m runs the command message-mark-inserted-region, which is an interact=
> ive
> compiled Lisp function in `message.el'.
>                            ^^^^^^^^^^
> 

Absolutely right - and my failure to read your message thoroughly caused
me to waste some time searching for an answer that was in front of my
eyes. Consider me suitably chastised - but, knowing me, I'll probably
commit this sin again in the future...

> It is bound to C-c M-m, <menu-bar> <Message> <Insert Region Marked>.
> 

> BTW, would you want a quite comprehensive `.emacs' as example, you could ha=
> ve
> a look at http://www.mygooglest.com/fni. It's not really detailed nor
> configured for Org-mode, but there is a lot to drink and to eat...

No, thanks: I like little sips, otherwise I drown !-)

Thanks,
Nick

Re: Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Eric S Fraga]

At Mon, 06 Jul 2009 17:08:09 -0400,
Nick Dokos wrote:
> 
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> > But the answer already was in my article=C2=A0;-)

it's the things in front of you that are easiest to miss...  :(
<blush>

Re: [OT] message-mark-inserted-region (was Re: Re: Exporting to a Beamer presentation)

[Sébastien Vauban]

Nick,

Nick Dokos wrote:
> Sébastien Vauban wrote:
>
>> But the answer already was in my article ;-)
>>
>> >>> BTW, you'd better use `C-c M-m' for quoting your code. It will allow an
>> >>> easy copy past of it... Like this:
>>
>> C-c M-m runs the command message-mark-inserted-region, which is an
>> interactive compiled Lisp function in `message.el'.
>>                                        ^^^^^^^^^^
>
> Absolutely right - and my failure to read your message thoroughly caused
> me to waste some time searching for an answer that was in front of my
> eyes. Consider me suitably chastised - but, knowing me, I'll probably
> commit this sin again in the future...

I'd be glad as well I could be different. But, no, I too want to take a joker
for future misunderstandings or useless questions... ;-)

BTW, would you make progresses or new discoveries regarding the "Org2Beamer"
theme, I'm always glad to know, to test and to share remarks...

Thanks for all,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Newbie Questions

[Andrew M. Nuxoll]

Ok, newb here.  I have only been using org-mode for a few days now.  But 
I've been an emacs guy since 1992, I have read the manual and I've also 
searched the archive of this mailing list.  So, forgive me if these 
questions are repeats.  Also, Dominick said you had to be nice to me 
while he was away.

1.  When I view my agenda for a day it displays TODO items twice if they 
are both SCHEDULED and DEADLINEd (a common occurrence for me).  Can this 
be avoided?  Here's a generic example snippet from my agenda:
    Thursday    9 July 2009
      nux:        Scheduled:  TODO [#B] Call Mary :PROJECT::
      nux:        In   1 d.:  TODO [#B] Call Mary :PROJECT::

2.  Once a TODO item has been marked as DONE, it still shows up on my 
agenda.  Can this be avoided? 


Meta-Comments on Questions 1&2:  I realize I have the option of using 
the "ToDo Items" agenda view instead of the day/week agenda view but 
that doesn't work for me because I use the SCHEDULED property as a way 
of selecting a small subset of tasks for the day from a long list of 
TODO items.  I also rely heavily upon repeating tasks to automate most 
of this.  So maybe the solution to #1 and #2 is to use a custom agenda 
of some sort but I don't see an obvious way to create one that does what 
I want.

3.  Once I set a deadline for a task, it'd be nice if the priority would 
increase as the deadline approached.  Ideally the  criteria for 
increasing the priority could be specified via a customizable formula.  
Does this functionality (or anything like it) exist?

Thanks,
:AMN:

Re: Newbie Questions

[Brian van den Broek]

Andrew M. Nuxoll said unto the world at 09/07/09 04:37 PM:

> 2.  Once a TODO item has been marked as DONE, it still shows up on my 
> agenda.  Can this be avoided?

I have the following lines in my .emacs:

(setq org-agenda-skip-scheduled-if-done t)
(setq org-agenda-skip-deadline-if-done t)


Best,

Brian vdB

Re: Newbie Questions

[Nick Dokos]

Andrew M. Nuxoll <nuxoll@up.edu> wrote:

> Also, Dominick said you had to be nice to me while he was away.
> 

Just an FYI (a nice one since Carsten said so :-): Carsten is the first
name, Dominik (no c) is the surname of the creator of Org-mode. And I
promise we'll be nice even after he comes back :-)

> 1.  When I view my agenda for a day it displays TODO items twice if they 
> are both SCHEDULED and DEADLINEd (a common occurrence for me).  Can this 
> be avoided?  Here's a generic example snippet from my agenda:
>     Thursday    9 July 2009
>       nux:        Scheduled:  TODO [#B] Call Mary :PROJECT::
>       nux:        In   1 d.:  TODO [#B] Call Mary :PROJECT::
> 

I think you SCHEDULE an item on a given day, in order to start working
on it on that day. There is generally no penalty for taking perhaps a
long time to finish it, or rescheduling it for a later time. All that
happens is that at some point in the future it'll pop up in the
agenda. DEADLINE on the other hand implies a penalty: if you don't
finish it by the deadline, something bad is going to happen. It then
starts appearing in the agenda a few days before the actual deadline to
remind you of the dire consequences, should you miss the deadline. How
many days before is controllable either by a global variable or by
modifying the timestamp (see section 8.3 of the manual: Deadlines and
Scheduling). Apologies if you already know the details, but I wanted
to highlight the difference between these two.

So let me turn the question around: why do you need to both SCHEDULE
and DEADLINE the same item?

> 2.  Once a TODO item has been marked as DONE, it still shows up on my 
> agenda.  Can this be avoided? 
> 

I believe this was answered already.

> 
> Meta-Comments on Questions 1&2:  I realize I have the option of using 
> the "ToDo Items" agenda view instead of the day/week agenda view but 
> that doesn't work for me because I use the SCHEDULED property as a way 
> of selecting a small subset of tasks for the day from a long list of 
> TODO items.  I also rely heavily upon repeating tasks to automate most 
> of this.  So maybe the solution to #1 and #2 is to use a custom agenda 
> of some sort but I don't see an obvious way to create one that does what 
> I want.
> 
> 3.  Once I set a deadline for a task, it'd be nice if the priority would 
> increase as the deadline approached.  Ideally the  criteria for 
> increasing the priority could be specified via a customizable formula.  
> Does this functionality (or anything like it) exist?
> 

I don't think anything like that exists, but with a Small[1] Amount of
Programming (TM), it could probably be cobbled up - maybe as a cron job?


Nick

[1] OK, maybe not so small...

Re: Newbie Questions

[Andrew M. Nuxoll]

Nick Dokos wrote:
> Just an FYI (a nice one since Carsten said so :-): Carsten is the first
> name, Dominik (no c) is the surname of the creator of Org-mode. And I
> promise we'll be nice even after he comes back :-)
>   
Err, whoops!
> So let me turn the question around: why do you need to both SCHEDULE
> and DEADLINE the same item?
>   
In my mind, there is no conflict between scheduling and deadlining.  So, 
I may be missing something.  In my case, I am scheduling myself to work 
on an item that has a deadline.  I don't think that's an unusual 
scenario.  For example, I have a grant proposal I need to have a draft 
of by Monday (DEADLINE) but I've scheduled Thursday afternoon to work on 
it.  By putting SCHEDULED on it means that it gets attention on that day 
unless Murphy steps in.  If Murphy does, then I still have the benefit 
of the DEADLINE to keep me apprised of my dire situation.

An alternative (which I don't like) is to not use DEADLINE on a 
SCHEDULED item.  Instead, I can just attach a second date to the item 
and label it "deadline" or "drop dead date."  So, the best option I have 
now is to ignore the double entry.  I was hoping there was a magic 
variable(TM) for this like there was with the other issue. 

>   
>> 2.  Once a TODO item has been marked as DONE, it still shows up on my 
>> agenda.  Can this be avoided? 
> I believe this was answered already.
>   
Yes it was.  Thanks, Brian.

Re: Newbie Questions

[Ian Barton]

Andrew M. Nuxoll wrote:
> Nick Dokos wrote:
>> Just an FYI (a nice one since Carsten said so :-): Carsten is the first
>> name, Dominik (no c) is the surname of the creator of Org-mode. And I
>> promise we'll be nice even after he comes back :-)
>>   
> Err, whoops!
>> So let me turn the question around: why do you need to both SCHEDULE
>> and DEADLINE the same item?
>>   
> In my mind, there is no conflict between scheduling and deadlining.  So, 
> I may be missing something.  In my case, I am scheduling myself to work 
> on an item that has a deadline.  I don't think that's an unusual 
> scenario.  For example, I have a grant proposal I need to have a draft 
> of by Monday (DEADLINE) but I've scheduled Thursday afternoon to work on 
> it.  By putting SCHEDULED on it means that it gets attention on that day 
> unless Murphy steps in.  If Murphy does, then I still have the benefit 
> of the DEADLINE to keep me apprised of my dire situation.
> 
> An alternative (which I don't like) is to not use DEADLINE on a 
> SCHEDULED item.  Instead, I can just attach a second date to the item 
> and label it "deadline" or "drop dead date."  So, the best option I have 
> now is to ignore the double entry.  I was hoping there was a magic 
> variable(TM) for this like there was with the other issue.
>>  

You could specify a per deadline warning period. The example for the 
manual: DEADLINE: <2004-02-29 Sun -5d>, which will start prompting you 5 
days before the deadline. I use this to remind me that I need to start 
working on something which has a fixed deadline.

Ian.

Re: Newbie Questions

[Eric S Fraga]

At Thu, 09 Jul 2009 21:08:31 -0700,
Andrew M. Nuxoll wrote:
> In my mind, there is no conflict between scheduling and deadlining.

I agree with you on this point but, in this case, it makes sense for
both aspects to be highlighted in the agenda view.  I would suggest
that you might wish to change (reduce) the warning period for the
deadline when you schedule an item or alternatively not schedule an
item but simply assign an appointment date/time (i.e. an active time
stamp) to it for when you want to work on the task.  The latter is
what I do in many cases.

eric

Re: Newbie Questions

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> At Thu, 09 Jul 2009 21:08:31 -0700,
> Andrew M. Nuxoll wrote:
> > In my mind, there is no conflict between scheduling and deadlining.
> 
> I agree with you on this point but, in this case, it makes sense for
> both aspects to be highlighted in the agenda view.  I would suggest
> that you might wish to change (reduce) the warning period for the
> deadline when you schedule an item or alternatively not schedule an
> item but simply assign an appointment date/time (i.e. an active time
> stamp) to it for when you want to work on the task.  The latter is
> what I do in many cases.
> 

Quite likely it's a failure of imagination on my part, but I still
don't see why you would both schedule and deadline an item. Could
you provide a scenario where that would be useful?

Thanks,
Nick

Re: Newbie Questions

[Memnon Anon]

"Andrew M. Nuxoll" <nuxoll@up.edu> writes:

> 1.  When I view my agenda for a day it displays TODO items twice if they
> are both SCHEDULED and DEADLINEd (a common occurrence for me).  Can this
> be avoided?  Here's a generic example snippet from my agenda:
>    Thursday    9 July 2009
>      nux:        Scheduled:  TODO [#B] Call Mary :PROJECT::
>      nux:        In   1 d.:  TODO [#B] Call Mary :PROJECT::

I think this is a feature.
For example, if I get some books from a library, I use the deadline to
mark when I absolutely must return the books. The schedule tells me:
Hey, I am near the library this day, so I *want* to do this today. 
I absolutely want both informations in my agenda.

From the manual:
DEADLINE
        Meaning: the task (most likely a TODO item, though not necessarily) is
        supposed to be finished on that date. 
SCHEDULED
    Meaning: you are planning to start working on that task on the given
    date.

You can set a different deadline for each item, but "avoiding this" totally
means avoiding crucial information in your agenda.

Re: Newbie Questions

[Nicolas Goaziou]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Quite likely it's a failure of imagination on my part, but I still
> don't see why you would both schedule and deadline an item. Could
> you provide a scenario where that would be useful?

I think the OP has a time frame to execute some task. He doesn't want to
be bugged about it before SCHEDULED, and it will be too late after
DEADLINE.

Imagine you have to make a gift to someone on Sunday, but got so much
work to do that you won't be able to go to the mall before Thursday...
oh well, you can always buy online then, but that would defeat the point
of my example.

Then again, as someone said, a DEADLINE with an appropriate warning
delay would be fine in that case too.

-- 
Nicolas Goaziou

Re: Newbie Questions

[Eric S Fraga]

At Fri, 10 Jul 2009 12:32:59 -0400,
Nick Dokos wrote:
> Quite likely it's a failure of imagination on my part, but I still
> don't see why you would both schedule and deadline an item. Could
> you provide a scenario where that would be useful?

Well, to use an example that I think the OP (Andrew) would identify
with, when a funding agency puts out a call for proposals, they will
give a strict deadline (e.g. 12 noon, 5 August 2009).  That date is
critical to the activity of writing the proposal if one intends to
apply for funding so the date gets put in my org file immediately.

Subsequently, when I figure out when I will have time to work on
writing the proposal, I will schedule the appropriate event.  I must
admit, however, that I do frequently simply put an active time stamp
on the note for when I want to work on this task.  I guess it depends
on the "granularity" of the scheduling of the task: if I intend to
work on it at some specific hour of the day, I'll use a time stamp; if
I intend to tackle the task "sometime" on Thursday, I'll schedule it.

The latter may be the wrong way to do it but the reality is that my
"planned" schedule often goes completely out the window due to
external factors and any time stamped activities disappear off the
agenda view the following day whereas scheduled items do not.  This
makes scheduling appealing as it allows me to say, the next day,
"ooops, I forgot to actually work on that proposal yesterday...".

YMMV, of course!

cheers,
eric

Re: Newbie Questions

[Eric S Fraga]

At Fri, 10 Jul 2009 19:48:20 +0200,
Nicolas Goaziou wrote:
> [...]
> Then again, as someone said, a DEADLINE with an appropriate warning
> delay would be fine in that case too.

I have tasks that have deadlines months in the future and which need
tackling from now until the deadline, although obviously not
continuously.  Putting a warning on the deadline to cover the full
time range would fill my agenda view with deadlines, making it rather
ineffective!

Re: Newbie Questions

[Carsten Dominik]

On Jul 10, 2009, at 5:16 AM, Nick Dokos wrote:

> Andrew M. Nuxoll <nuxoll@up.edu> wrote:
>>
>> 3.  Once I set a deadline for a task, it'd be nice if the priority  
>> would
>> increase as the deadline approached.  Ideally the  criteria for
>> increasing the priority could be specified via a customizable  
>> formula.
>> Does this functionality (or anything like it) exist?
>>
>
> I don't think anything like that exists, but with a Small[1] Amount of
> Programming (TM), it could probably be cobbled up - maybe as a cron  
> job?

In fact, the priority does increase.

Org-mode has two notions of priority.

1. The specified priority like [#A]
2. A computed numerical priority

The specified priority is set solely by the user, and it is also the
only thing that influences how prioritized lines are displayed
according to `org-agenda-fontify-priorities'.

The computed priority is a number that all items in the agenda have,
you can look at the actual number pressing `P' in the agenda.
The number is composed of the specified priority times 1000, so #C
items have 0, #B items have 1000 and #A items have 2000.
TO this values, certain amounts are added depending on how close
you are to the deadline, or how long ago an item was first scheduled.

This computed, numerical priority is used when sorting items.

The numbers added for closeness to a deadline are usually not large
enough to make an overdue item with specified priority #B to score
higher than one with #A, but within each group of specified priorities,
closeness to a deadline does make a difference.

If you want items to change from #B to #A automatically, you need
to do some programming, as Nick says.

The formula is not configurable currently, nor is it documented
anywhere, nor do I remember exactly what the formula is :-D .
I am not a big fan of priorities, because I don't think one should
trust the system so much that it will actually decide for you what
to work on.  However, I could dig up the formula, even make it
configurable if there was a need for it.

HTH

- Carsten

Re: Newbie Questions

[Samuel Wales]

Hi Andrew,

On 2009-07-09, Andrew M. Nuxoll <nuxoll@up.edu> wrote:
> 3.  Once I set a deadline for a task, it'd be nice if the priority would
> increase as the deadline approached.  Ideally the  criteria for
> increasing the priority could be specified via a customizable formula.
> Does this functionality (or anything like it) exist?

I do not use priority-as-calculated.  That is, I don't sort by
closeness to deadline, etc.  That way, everything is in a consistent
order, which I find pleasing.  I sort by my fixed urgency and
priority-as-set-by-user.  This almost certainly violates GTD, but
priorities and urgencies work for me.  Org flexibly supports any
method you want.

I do, however, rely on the agenda's built-in faces, and the second
colum that says "Deadline" etc., for status.  These are very useful.

I have a thorough testcase for this and found several potential bugs
that I will report on in a separate post.

DiTAA error under Ubuntu

[Sébastien Vauban]

Hello,

I'm trying to use the DiTAA tool for making easy graphics in a couple of
minutes.

Though, I've this error when exporting to LaTeX:

--8<---------------cut here---------------start------------->8---
[sva@mundaneum] ...texmf/tex/latex>java -jar /home/sva/Downloads/emacs/site-lisp/org-mode/contrib/scripts/ditaa.jar  /tmp/org-ditaa13182XLS archi.png

DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris

Using options: 
Reading file: /tmp/org-ditaa13182XLS
Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1666)
	at java.lang.Runtime.load0(Runtime.java:787)
	at java.lang.System.load(System.java:1022)
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1767)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1684)
	at java.lang.Runtime.loadLibrary0(Runtime.java:840)
	at java.lang.System.loadLibrary(System.java:1047)
	at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:67)
	at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:47)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.awt.Toolkit.loadLibraries(Toolkit.java:1614)
	at java.awt.Toolkit.<clinit>(Toolkit.java:1636)
	at java.awt.Color.<clinit>(Color.java:279)
	at org.stathissideris.ascii2image.graphics.DiagramShape.<init>(DiagramShape.java:52)
	at org.stathissideris.ascii2image.graphics.DiagramComponent.createClosedFromBoundaryCells(DiagramComponent.java:82)
	at org.stathissideris.ascii2image.graphics.Diagram.<init>(Diagram.java:320)
	at org.stathissideris.ascii2image.core.CommandLineConverter.main(CommandLineConverter.java:195)
--8<---------------cut here---------------end--------------->8---

I know this is purely related to Java components, but -- being completely
newbie in Java, and being overwhelmed by the impressive long list of possible
packages --, can someone tell me which Ubuntu package I should have to install
to get this working?

I can provide any needed information...

Best regards,
  Seb

PS- In the past, when playing with Java packages, I've already corrupted one
    Java installation, so I wanna do this with care...

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: DiTAA error under Ubuntu

[Nick Dokos]

=?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> wrote:

> I'm trying to use the DiTAA tool for making easy graphics in a couple of
> minutes.
> 
> Though, I've this error when exporting to LaTeX:
> 
> --8<---------------cut here---------------start------------->8---
> [sva@mundaneum] ...texmf/tex/latex>java -jar /home/sva/Downloads/emacs/site=
> -lisp/org-mode/contrib/scripts/ditaa.jar  /tmp/org-ditaa13182XLS archi.png
> 
> DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris
> 
> Using options:=20
> Reading file: /tmp/org-ditaa13182XLS
> Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load libra=
> ry: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
> ...

From a quick look at synaptic, it seemed `openjdk-6-jre-lib' would be the most
likely candidate package to contain libmawt.so, but it wasn't there.
However, the headless package has it:

,----
| $ dpkg --contents openjdk-6-jre-headless_6b11-2ubuntu2.1_i386.deb  | grep awt
| -rw-r--r-- root/root     18232 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so
| -rw-r--r-- root/root    554920 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/libawt.so
| -rw-r--r-- root/root      3008 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/libjawt.so
`----

HTH,
Nick

Re: DiTAA error under Ubuntu

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> > I'm trying to use the DiTAA tool for making easy graphics in a couple of
> > minutes.
> > 
> > Though, I've this error when exporting to LaTeX:
> > 
> > --8<---------------cut here---------------start------------->8---
> > [sva@mundaneum] ...texmf/tex/latex>java -jar /home/sva/Downloads/emacs/site=
> > -lisp/org-mode/contrib/scripts/ditaa.jar  /tmp/org-ditaa13182XLS archi.png
> > 
> > DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris
> > 
> > Using options:=20
> > Reading file: /tmp/org-ditaa13182XLS
> > Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load libra=
> > ry: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
> > ...
> 
> From a quick look at synaptic, it seemed `openjdk-6-jre-lib' would be the most
> likely candidate package to contain libmawt.so, but it wasn't there.
> However, the headless package has it:
> 
> ,----
> | $ dpkg --contents openjdk-6-jre-headless_6b11-2ubuntu2.1_i386.deb  | grep awt
> | -rw-r--r-- root/root     18232 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so
> | -rw-r--r-- root/root    554920 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/libawt.so
> | -rw-r--r-- root/root      3008 2009-01-30 18:43 ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/libjawt.so
> `----
> 

... and I should have continued: you probably have headless already, since the library
depends on it; in which case, a cunningly placed symlink should do the trick.

Nick

Re: DiTAA error under Ubuntu

[Eric S Fraga, Eric S Fraga]

At Tue, 11 Aug 2009 17:18:41 +0200,
Sébastien Vauban wrote:

[...]

> I know this is purely related to Java components, but -- being completely
> newbie in Java, and being overwhelmed by the impressive long list of possible
> packages --, can someone tell me which Ubuntu package I should have to install
> to get this working?

I don't use ubuntu but Debian on which ubuntu is based so maybe I can
help.  I have the following jdk/java packages installed on my system:

,----
| ii  java-common          0.32          Base of all Java packages
| ii  libjline-java        0.9.94-1      Java library for handling console input
| ii  sun-java6-bin        6-14-1        Sun Java(TM) Runtime Environment (JRE) 6 (ar
| ii  sun-java6-jdk        6-14-1        Sun Java(TM) Development Kit (JDK) 6
| ii  sun-java6-jre        6-14-1        Sun Java(TM) Runtime Environment (JRE) 6 (ar
`----

(You can probably ignored libjline.)  I haven't used the openjdk
version and I'm surprised it's not working as it's meant to be the
same as the Sun version.  Maybe openjdk is missing the AWT libraries?
Have you checked ubuntu's bug reports on this?

In any case, can you install the direct-from-sun packages on your
system (as I have, via aptitude or apt-get, assuming they are present
in the ubuntu repositories) and see whether that works better?

HTH,
eric

Re: DiTAA error under Ubuntu

[Sébastien Vauban]

Nick, Eric,

Sorry for answering late -- while you were prompt at replying. Have been out
for one day.

Nick Dokos wrote:
> Nick Dokos <nicholas.dokos-VXdhtT5mjnY@public.gmane.org> wrote:
>> Sebastien_Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>>
>>> I'm trying to use the DiTAA tool for making easy graphics in a couple of
>>> minutes.
>>>
>>> Though, I've this error when exporting to LaTeX:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> [sva@mundaneum] ...texmf/tex/latex>java -jar /home/sva/Downloads/emacs/site
>>> -lisp/org-mode/contrib/scripts/ditaa.jar  /tmp/org-ditaa13182XLS archi.png
>>>
>>> DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris
>>>
>>> Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load
>>> library: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
>>
>> From a quick look at synaptic, it seemed `openjdk-6-jre-lib' would be the
>> most likely candidate package to contain libmawt.so, but it wasn't there.

Here is the situation of Java-related packages on my system so far:

i A bootchart-java                  - Boot process performance analyser (visuali
i A ca-certificates-java            - Common CA certificates (JKS keystore)
i A default-jre-headless            - Standard Java or Java compatible Runtime (headless)
i A java-common                     - Base of all Java packages
i A java-gcj-compat                 - Java runtime environment using GIJ
i A java-gcj-compat-headless        - Java runtime environment using GIJ (headle
i A java-gcj-compat-headless        - Java runtime environment using GIJ (headless version)
i A libaccess-bridge-java           - Java Access Bridge for GNOME
i A libbcel-java                    - Analyze, create, and manipulate (binary) J
i A libcommons-cli-java             - API for working with the command line argu
i A libcommons-compress-java        - Java API for working with tar, zip and bzi
i A libcommons-lang-java            - Extension of the java.lang package
i A liblog4j1.2-java                - Logging library for java
i A liblog4j1.2-java-gcj            - Logging library for java (native code)
i A libmx4j-java                    - An open source implementation of the JMX(T
i A libregexp-java                  - regular expression library for Java
i A openjdk-6-jre-headless          - OpenJDK Java runtime, using Hotspot JIT (headless)
i A openjdk-6-jre-lib               - OpenJDK Java runtime (architecture independent libraries)
i A tzdata-java                     - time zone and daylight-saving time data fo
p   default-jdk                     - Standard Java or Java compatible Development Kit
p   default-jdk-builddep            - Standard Java or Java compatible build dependencies
p   openjdk-6-dbg                   - Java runtime based on OpenJDK (debugging symbols)
p   openjdk-6-demo                  - Java runtime based on OpenJDK (demos and examples)
p   openjdk-6-doc                   - OpenJDK Development Kit (JDK) documentation
p   openjdk-6-jdk                   - OpenJDK Development Kit (JDK)
p   openjdk-6-jre                   - OpenJDK Java runtime, using Hotspot JIT
p   openjdk-6-jre-zero              - Alternatve JVM for OpenJDK, using Zero/Shark
p   openjdk-6-source                - OpenJDK Development Kit (JDK) source files
p   openjdk-6-source-files          - OpenJDK 6 source files (used as a build dependency)
p   sun-java5-bin                   - Sun Java(TM) Runtime Environment (JRE) 5.0 (architecture dependent f
p   sun-java5-demo                  - Sun Java(TM) Development Kit (JDK) 5.0 demos and examples
p   sun-java5-doc                   - Sun JDK(TM) Documention -- integration installer
p   sun-java5-fonts                 - Lucida TrueType fonts (from the Sun JRE)
p   sun-java5-jdk                   - Sun Java(TM) Development Kit (JDK) 5.0
p   sun-java5-jre                   - Sun Java(TM) Runtime Environment (JRE) 5.0 (architecture independent
p   sun-java5-plugin                - The Java(TM) Plug-in, Java SE 5.0
p   sun-java5-source                - Sun Java(TM) Development Kit (JDK) 5.0 source files
p   sun-java6-bin                   - Sun Java(TM) Runtime Environment (JRE) 6 (architecture dependent fil
p   sun-java6-demo                  - Sun Java(TM) Development Kit (JDK) 6 demos and examples
p   sun-java6-doc                   - Sun JDK(TM) Documention -- integration installer
p   sun-java6-fonts                 - Lucida TrueType fonts (from the Sun JRE)
p   sun-java6-javadb                - Java(TM) DB, Sun Microsystems' distribution of Apache Derby
p   sun-java6-jdk                   - Sun Java(TM) Development Kit (JDK) 6
p   sun-java6-jre                   - Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent f
p   sun-java6-plugin                - The Java(TM) Plug-in, Java SE 6
p   sun-java6-source                - Sun Java(TM) Development Kit (JDK) 6 source files
p   sun-javadb-client               - Java DB client
p   sun-javadb-common               - Java DB common files
p   sun-javadb-core                 - Java DB core
p   sun-javadb-demo                 - Java DB demo
p   sun-javadb-doc                  - Java DB documentation
p   sun-javadb-javadoc              - Java DB javadoc
v   java-runtime-headless           -
v   java1-runtime-headless          -
v   java2-runtime-headless          -
v   java5-runtime-headless          -
v   java6-runtime-headless          -

(from a few `aptitude search XXX' commands where XXX = headless, java, jdk, sun-)

For the records:

--8<---------------cut here---------------start------------->8---
> which java
/usr/bin/java

> ls -lia /usr/bin/java
94778 lrwxrwxrwx 1 root root 22 Aug  6 15:28 /usr/bin/java -> /etc/alternatives/java*
--8<---------------cut here---------------end--------------->8---


> ... and I should have continued: you probably have headless already, since
> the library depends on it; in which case, a cunningly placed symlink should
> do the trick.

I indeed already have libmawt.so there:

./usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so

You propose me to link

link /usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so \
     /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so

That's it?

It can't hurt... Trying it...

--8<---------------cut here---------------start------------->8---
cd /usr/lib/jvm/java-6-openjdk/jre/lib/i386/
sudo mkdir xawt
sudo link /usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so \
          /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
--8<---------------cut here---------------end--------------->8---

Exporting the DiTAA figure:

--8<---------------cut here---------------start------------->8---
> java -jar /home/sva/Downloads/emacs/site-lisp/org-mode/contrib/scripts/ditaa.jar  /tmp/org-ditaa3944YGv archi.png

DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris

Using options: 
Reading file: /tmp/org-ditaa3944YGv
Exception in thread "main" java.lang.UnsatisfiedLinkError: sun.awt.X11GraphicsEnvironment.initDisplay(Z)V
	at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
	at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:62)
	at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:166)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:142)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:186)
	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82)
	at java.awt.image.BufferedImage.createGraphics(BufferedImage.java:1152)
	at org.stathissideris.ascii2image.graphics.FontMeasurer.<init>(FontMeasurer.java:44)
	at org.stathissideris.ascii2image.graphics.FontMeasurer.<clinit>(FontMeasurer.java:39)
	at org.stathissideris.ascii2image.graphics.Diagram.<init>(Diagram.java:448)
	at org.stathissideris.ascii2image.core.CommandLineConverter.main(CommandLineConverter.java:195)
--8<---------------cut here---------------end--------------->8---

One step further?  Reading those messages is really like Chinese for me...

What do you advise me to do?  Installing another well-chosen package?

Thanks a lot!

Seb


-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: DiTAA error under Ubuntu

[Nick Dokos]

[-- Attachment #1: Type: text/plain, Size: 3261 bytes --]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:


> > ... and I should have continued: you probably have headless already, since
> > the library depends on it; in which case, a cunningly placed symlink shou=
> ld
> > do the trick.
> 
> I indeed already have libmawt.so there:
> 
> ./usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so
> 
> You propose me to link
> 
> link /usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so \
>      /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
> 
> That's it?
> 
> It can't hurt... Trying it...
> 
> cd /usr/lib/jvm/java-6-openjdk/jre/lib/i386/
> sudo mkdir xawt
> sudo link /usr/lib/jvm/java-6-openjdk/jre/lib/i386/headless/libmawt.so \
>           /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
> 
> Exporting the DiTAA figure:
> 
> > java -jar /home/sva/Downloads/emacs/site-lisp/org-mode/contrib/scripts/di=
> taa.jar  /tmp/org-ditaa3944YGv archi.png
> 
> DiTAA version 0.6b, Copyright (C) 2004 Efstathios Sideris
> 
> Using options:=20
> Reading file: /tmp/org-ditaa3944YGv
> Exception in thread "main" java.lang.UnsatisfiedLinkError: sun.awt.X11Graph=
> icsEnvironment.initDisplay(Z)V
> 	at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> 	at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:6=
> 2)
> 	at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:166)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:142)
> 	at java.lang.Class.forName0(Native Method)
> 	at java.lang.Class.forName(Class.java:186)
> 	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnviro=
> nment.java:82)
> 	at java.awt.image.BufferedImage.createGraphics(BufferedImage.java:1152)
> 	at org.stathissideris.ascii2image.graphics.FontMeasurer.<init>(FontMeasure=
> r.java:44)
> 	at org.stathissideris.ascii2image.graphics.FontMeasurer.<clinit>(FontMeasu=
> rer.java:39)
> 	at org.stathissideris.ascii2image.graphics.Diagram.<init>(Diagram.java:448)
> 	at org.stathissideris.ascii2image.core.CommandLineConverter.main(CommandLi=
> neConverter.java:195)
> 
> One step further?  Reading those messages is really like Chinese for me...
> 
> What do you advise me to do?  Installing another well-chosen package?
> 

Maybe two steps back :-) But reading the messages is not that hard (I
know as much Java as you do - perhaps less). As the program runs, it
loads classes as needed: the classes are specified in a path-like
way. They are found in jar files in standard places.

Looking at the above: the ditaa FontMeasurer class calls its <init>
which loads the java.awt.image.BufferedImage class and calls its
createGraphics() method, etc.

I'd suggest that you run jave with the -verbose:class option and look
around for the error - this is the kind of problem where what you have
on your machine is the determinining factor, so it's very hard for outsiders
to figure out what's wrong.

I did a ditaa run on a simple diagram and I'm attaching the output of the
command for comparison purposes (btw, I don't use openjdk - I've installed
the jdk from Sun).

HTH,
Nick


[-- Attachment #2: ditaa verbose:class output --]
[-- Type: text/plain, Size: 60878 bytes --]

$ java -verbose:class -jar ~/src/emacs/org/org-mode/contrib/scripts/ditaa.jar foo.txt
[Loaded java.lang.Object from shared objects file]
[Loaded java.io.Serializable from shared objects file]
[Loaded java.lang.Comparable from shared objects file]
[Loaded java.lang.CharSequence from shared objects file]
[Loaded java.lang.String from shared objects file]
[Loaded java.lang.reflect.GenericDeclaration from shared objects file]
[Loaded java.lang.reflect.Type from shared objects file]
[Loaded java.lang.reflect.AnnotatedElement from shared objects file]
[Loaded java.lang.Class from shared objects file]
[Loaded java.lang.Cloneable from shared objects file]
[Loaded java.lang.ClassLoader from shared objects file]
[Loaded java.lang.System from shared objects file]
[Loaded java.lang.Throwable from shared objects file]
[Loaded java.lang.Error from shared objects file]
[Loaded java.lang.ThreadDeath from shared objects file]
[Loaded java.lang.Exception from shared objects file]
[Loaded java.lang.RuntimeException from shared objects file]
[Loaded java.security.ProtectionDomain from shared objects file]
[Loaded java.security.AccessControlContext from shared objects file]
[Loaded java.lang.ClassNotFoundException from shared objects file]
[Loaded java.lang.LinkageError from shared objects file]
[Loaded java.lang.NoClassDefFoundError from shared objects file]
[Loaded java.lang.ClassCastException from shared objects file]
[Loaded java.lang.ArrayStoreException from shared objects file]
[Loaded java.lang.VirtualMachineError from shared objects file]
[Loaded java.lang.OutOfMemoryError from shared objects file]
[Loaded java.lang.StackOverflowError from shared objects file]
[Loaded java.lang.IllegalMonitorStateException from shared objects file]
[Loaded java.lang.ref.Reference from shared objects file]
[Loaded java.lang.ref.SoftReference from shared objects file]
[Loaded java.lang.ref.WeakReference from shared objects file]
[Loaded java.lang.ref.FinalReference from shared objects file]
[Loaded java.lang.ref.PhantomReference from shared objects file]
[Loaded java.lang.ref.Finalizer from shared objects file]
[Loaded java.lang.Runnable from shared objects file]
[Loaded java.lang.Thread from shared objects file]
[Loaded java.lang.Thread$UncaughtExceptionHandler from shared objects file]
[Loaded java.lang.ThreadGroup from shared objects file]
[Loaded java.util.Dictionary from shared objects file]
[Loaded java.util.Map from shared objects file]
[Loaded java.util.Hashtable from shared objects file]
[Loaded java.util.Properties from shared objects file]
[Loaded java.lang.reflect.AccessibleObject from shared objects file]
[Loaded java.lang.reflect.Member from shared objects file]
[Loaded java.lang.reflect.Field from shared objects file]
[Loaded java.lang.reflect.Method from shared objects file]
[Loaded java.lang.reflect.Constructor from shared objects file]
[Loaded sun.reflect.MagicAccessorImpl from shared objects file]
[Loaded sun.reflect.MethodAccessor from shared objects file]
[Loaded sun.reflect.MethodAccessorImpl from shared objects file]
[Loaded sun.reflect.ConstructorAccessor from shared objects file]
[Loaded sun.reflect.ConstructorAccessorImpl from shared objects file]
[Loaded sun.reflect.DelegatingClassLoader from shared objects file]
[Loaded sun.reflect.ConstantPool from shared objects file]
[Loaded sun.reflect.FieldAccessor from shared objects file]
[Loaded sun.reflect.FieldAccessorImpl from shared objects file]
[Loaded sun.reflect.UnsafeFieldAccessorImpl from shared objects file]
[Loaded sun.reflect.UnsafeStaticFieldAccessorImpl from shared objects file]
[Loaded java.lang.Iterable from shared objects file]
[Loaded java.util.Collection from shared objects file]
[Loaded java.util.AbstractCollection from shared objects file]
[Loaded java.util.List from shared objects file]
[Loaded java.util.AbstractList from shared objects file]
[Loaded java.util.RandomAccess from shared objects file]
[Loaded java.util.Vector from shared objects file]
[Loaded java.lang.Appendable from shared objects file]
[Loaded java.lang.AbstractStringBuilder from shared objects file]
[Loaded java.lang.StringBuffer from shared objects file]
[Loaded java.lang.StackTraceElement from shared objects file]
[Loaded java.nio.Buffer from shared objects file]
[Loaded sun.misc.AtomicLong from shared objects file]
[Loaded sun.misc.AtomicLongCSImpl from shared objects file]
[Loaded java.lang.Boolean from shared objects file]
[Loaded java.lang.Character from shared objects file]
[Loaded java.lang.Number from shared objects file]
[Loaded java.lang.Float from shared objects file]
[Loaded java.lang.Double from shared objects file]
[Loaded java.lang.Byte from shared objects file]
[Loaded java.lang.Short from shared objects file]
[Loaded java.lang.Integer from shared objects file]
[Loaded java.lang.Long from shared objects file]
[Loaded java.io.ObjectStreamField from shared objects file]
[Loaded java.util.Comparator from shared objects file]
[Loaded java.lang.String$CaseInsensitiveComparator from shared objects file]
[Loaded java.security.Guard from shared objects file]
[Loaded java.security.Permission from shared objects file]
[Loaded java.security.BasicPermission from shared objects file]
[Loaded java.lang.RuntimePermission from shared objects file]
[Loaded java.util.AbstractMap from shared objects file]
[Loaded sun.misc.SoftCache from shared objects file]
[Loaded java.lang.ref.ReferenceQueue from shared objects file]
[Loaded java.lang.ref.ReferenceQueue$Null from shared objects file]
[Loaded java.lang.ref.ReferenceQueue$Lock from shared objects file]
[Loaded java.util.HashMap from shared objects file]
[Loaded java.util.Map$Entry from shared objects file]
[Loaded java.util.HashMap$Entry from shared objects file]
[Loaded java.security.AccessController from shared objects file]
[Loaded java.lang.reflect.ReflectPermission from shared objects file]
[Loaded java.security.PrivilegedAction from shared objects file]
[Loaded sun.reflect.ReflectionFactory$GetReflectionFactoryAction from shared objects file]
[Loaded java.util.Stack from shared objects file]
[Loaded sun.reflect.ReflectionFactory from shared objects file]
[Loaded java.lang.ref.Reference$Lock from shared objects file]
[Loaded java.lang.ref.Reference$ReferenceHandler from shared objects file]
[Loaded java.lang.ref.Finalizer$FinalizerThread from shared objects file]
[Loaded java.util.Enumeration from shared objects file]
[Loaded java.util.Hashtable$EmptyEnumerator from shared objects file]
[Loaded java.util.Iterator from shared objects file]
[Loaded java.util.Hashtable$EmptyIterator from shared objects file]
[Loaded java.util.Hashtable$Entry from shared objects file]
[Loaded java.nio.charset.Charset from shared objects file]
[Loaded java.nio.charset.spi.CharsetProvider from shared objects file]
[Loaded sun.nio.cs.FastCharsetProvider from shared objects file]
[Loaded sun.nio.cs.StandardCharsets from shared objects file]
[Loaded sun.util.PreHashedMap from shared objects file]
[Loaded sun.nio.cs.StandardCharsets$Aliases from shared objects file]
[Loaded sun.nio.cs.StandardCharsets$Classes from shared objects file]
[Loaded sun.nio.cs.StandardCharsets$Cache from shared objects file]
[Loaded java.lang.ThreadLocal from shared objects file]
[Loaded java.util.concurrent.atomic.AtomicInteger from shared objects file]
[Loaded sun.misc.Unsafe from shared objects file]
[Loaded java.lang.IncompatibleClassChangeError from shared objects file]
[Loaded java.lang.NoSuchMethodError from shared objects file]
[Loaded sun.reflect.Reflection from shared objects file]
[Loaded java.util.Collections from shared objects file]
[Loaded java.util.Set from shared objects file]
[Loaded java.util.AbstractSet from shared objects file]
[Loaded java.util.Collections$EmptySet from shared objects file]
[Loaded java.util.Collections$EmptyList from shared objects file]
[Loaded java.util.Collections$EmptyMap from shared objects file]
[Loaded java.util.Collections$ReverseComparator from shared objects file]
[Loaded java.util.Collections$SynchronizedMap from shared objects file]
[Loaded java.lang.Class$3 from shared objects file]
[Loaded java.lang.reflect.Modifier from shared objects file]
[Loaded sun.reflect.LangReflectAccess from shared objects file]
[Loaded java.lang.reflect.ReflectAccess from shared objects file]
[Opened /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.lang.StringValue from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.util.Arrays from shared objects file]
[Loaded java.lang.Math from shared objects file]
[Loaded java.lang.StringBuilder from shared objects file]
[Loaded sun.nio.cs.HistoricallyNamedCharset from shared objects file]
[Loaded sun.nio.cs.Unicode from shared objects file]
[Loaded sun.nio.cs.UTF_8 from shared objects file]
[Loaded java.lang.Class$1 from shared objects file]
[Loaded sun.reflect.ReflectionFactory$1 from shared objects file]
[Loaded sun.reflect.NativeConstructorAccessorImpl from shared objects file]
[Loaded sun.reflect.DelegatingConstructorAccessorImpl from shared objects file]
[Loaded sun.misc.VM from shared objects file]
[Loaded java.lang.StringCoding from shared objects file]
[Loaded java.lang.ThreadLocal$ThreadLocalMap from shared objects file]
[Loaded java.lang.ThreadLocal$ThreadLocalMap$Entry from shared objects file]
[Loaded java.lang.StringCoding$StringDecoder from shared objects file]
[Loaded java.nio.charset.CharsetDecoder from shared objects file]
[Loaded sun.nio.cs.UTF_8$Decoder from shared objects file]
[Loaded java.nio.charset.CodingErrorAction from shared objects file]
[Loaded java.nio.ByteBuffer from shared objects file]
[Loaded java.nio.HeapByteBuffer from shared objects file]
[Loaded java.nio.Bits from shared objects file]
[Loaded java.nio.ByteOrder from shared objects file]
[Loaded java.lang.Readable from shared objects file]
[Loaded java.nio.CharBuffer from shared objects file]
[Loaded java.nio.HeapCharBuffer from shared objects file]
[Loaded java.nio.charset.CoderResult from shared objects file]
[Loaded java.nio.charset.CoderResult$Cache from shared objects file]
[Loaded java.nio.charset.CoderResult$1 from shared objects file]
[Loaded java.nio.charset.CoderResult$2 from shared objects file]
[Loaded sun.misc.Version from shared objects file]
[Loaded sun.misc.JavaLangAccess from shared objects file]
[Loaded java.lang.System$2 from shared objects file]
[Loaded sun.misc.SharedSecrets from shared objects file]
[Loaded java.lang.Runtime from shared objects file]
[Loaded java.io.File from shared objects file]
[Loaded java.io.FileSystem from shared objects file]
[Loaded java.io.UnixFileSystem from shared objects file]
[Loaded java.io.ExpiringCache from shared objects file]
[Loaded java.util.LinkedHashMap from shared objects file]
[Loaded java.io.ExpiringCache$1 from shared objects file]
[Loaded java.util.LinkedHashMap$Entry from shared objects file]
[Loaded sun.security.action.GetPropertyAction from shared objects file]
[Loaded sun.jkernel.DownloadManager from shared objects file]
[Loaded sun.jkernel.DownloadManager$1 from shared objects file]
[Loaded sun.jkernel.DownloadManager$2 from shared objects file]
[Loaded java.lang.StringCoding$StringEncoder from shared objects file]
[Loaded java.nio.charset.CharsetEncoder from shared objects file]
[Loaded sun.nio.cs.UTF_8$Encoder from shared objects file]
[Loaded java.lang.ClassLoader$3 from shared objects file]
[Loaded java.io.ExpiringCache$Entry from shared objects file]
[Loaded java.lang.ClassLoader$NativeLibrary from shared objects file]
[Loaded java.io.Closeable from shared objects file]
[Loaded java.io.InputStream from shared objects file]
[Loaded java.io.FileInputStream from shared objects file]
[Loaded java.io.FileDescriptor from shared objects file]
[Loaded java.io.Flushable from shared objects file]
[Loaded java.io.OutputStream from shared objects file]
[Loaded java.io.FileOutputStream from shared objects file]
[Loaded java.io.FilterInputStream from shared objects file]
[Loaded java.io.BufferedInputStream from shared objects file]
[Loaded java.util.concurrent.atomic.AtomicReferenceFieldUpdater from shared objects file]
[Loaded java.util.concurrent.atomic.AtomicReferenceFieldUpdater$AtomicReferenceFieldUpdaterImpl from shared objects file]
[Loaded sun.reflect.misc.ReflectUtil from shared objects file]
[Loaded java.io.FilterOutputStream from shared objects file]
[Loaded java.io.PrintStream from shared objects file]
[Loaded java.io.BufferedOutputStream from shared objects file]
[Loaded java.io.Writer from shared objects file]
[Loaded java.io.OutputStreamWriter from shared objects file]
[Loaded sun.nio.cs.StreamEncoder from shared objects file]
[Loaded java.io.BufferedWriter from shared objects file]
[Loaded java.lang.Terminator from shared objects file]
[Loaded sun.misc.SignalHandler from shared objects file]
[Loaded java.lang.Terminator$1 from shared objects file]
[Loaded sun.misc.Signal from shared objects file]
[Loaded sun.misc.NativeSignalHandler from shared objects file]
[Loaded sun.misc.OSEnvironment from shared objects file]
[Loaded java.lang.NullPointerException from shared objects file]
[Loaded java.lang.ArithmeticException from shared objects file]
[Loaded java.lang.Compiler from shared objects file]
[Loaded java.lang.Compiler$1 from shared objects file]
[Loaded sun.misc.Launcher from shared objects file]
[Loaded java.net.URLStreamHandlerFactory from shared objects file]
[Loaded sun.misc.Launcher$Factory from shared objects file]
[Loaded java.security.SecureClassLoader from shared objects file]
[Loaded java.net.URLClassLoader from shared objects file]
[Loaded sun.misc.Launcher$ExtClassLoader from shared objects file]
[Loaded sun.security.util.Debug from shared objects file]
[Loaded sun.misc.JavaNetAccess from shared objects file]
[Loaded java.net.URLClassLoader$7 from shared objects file]
[Loaded java.util.StringTokenizer from shared objects file]
[Loaded java.security.PrivilegedExceptionAction from shared objects file]
[Loaded sun.misc.Launcher$ExtClassLoader$1 from shared objects file]
[Loaded sun.misc.MetaIndex from shared objects file]
[Loaded java.io.Reader from shared objects file]
[Loaded java.io.BufferedReader from shared objects file]
[Loaded java.io.InputStreamReader from shared objects file]
[Loaded java.io.FileReader from shared objects file]
[Loaded sun.nio.cs.StreamDecoder from shared objects file]
[Loaded java.util.ArrayList from shared objects file]
[Loaded java.lang.reflect.Array from shared objects file]
[Loaded sun.net.www.ParseUtil from shared objects file]
[Loaded java.util.BitSet from shared objects file]
[Loaded java.io.ObjectStreamClass from shared objects file]
[Loaded java.net.URL from shared objects file]
[Loaded java.util.Locale from shared objects file]
[Loaded java.util.concurrent.ConcurrentMap from shared objects file]
[Loaded java.util.concurrent.ConcurrentHashMap from shared objects file]
[Loaded java.util.concurrent.locks.Lock from shared objects file]
[Loaded java.util.concurrent.locks.ReentrantLock from shared objects file]
[Loaded java.util.concurrent.ConcurrentHashMap$Segment from shared objects file]
[Loaded java.util.concurrent.locks.AbstractOwnableSynchronizer from shared objects file]
[Loaded java.util.concurrent.locks.AbstractQueuedSynchronizer from shared objects file]
[Loaded java.util.concurrent.locks.ReentrantLock$Sync from shared objects file]
[Loaded java.util.concurrent.locks.ReentrantLock$NonfairSync from shared objects file]
[Loaded java.util.concurrent.locks.AbstractQueuedSynchronizer$Node from shared objects file]
[Loaded java.util.concurrent.ConcurrentHashMap$HashEntry from shared objects file]
[Loaded java.lang.CharacterDataLatin1 from shared objects file]
[Loaded java.net.Parts from shared objects file]
[Loaded java.net.URLStreamHandler from shared objects file]
[Loaded sun.net.www.protocol.file.Handler from shared objects file]
[Loaded java.util.HashSet from shared objects file]
[Loaded sun.misc.URLClassPath from shared objects file]
[Loaded sun.net.www.protocol.jar.Handler from shared objects file]
[Loaded sun.misc.Launcher$AppClassLoader from shared objects file]
[Loaded sun.misc.Launcher$AppClassLoader$1 from shared objects file]
[Loaded java.lang.SystemClassLoaderAction from shared objects file]
[Loaded java.util.zip.ZipConstants from shared objects file]
[Loaded java.util.zip.ZipFile from shared objects file]
[Loaded java.util.jar.JarFile from shared objects file]
[Loaded sun.misc.JavaUtilJarAccess from shared objects file]
[Loaded java.util.jar.JavaUtilJarAccessImpl from shared objects file]
[Loaded java.util.zip.ZipEntry from shared objects file]
[Loaded java.util.jar.JarEntry from shared objects file]
[Loaded java.util.jar.JarFile$JarFileEntry from shared objects file]
[Loaded java.io.DataInput from shared objects file]
[Loaded java.io.DataInputStream from shared objects file]
[Loaded java.util.zip.ZipFile$ZipFileInputStream from shared objects file]
[Loaded java.util.zip.InflaterInputStream from shared objects file]
[Loaded java.util.zip.ZipFile$1 from shared objects file]
[Loaded java.util.zip.Inflater from shared objects file]
[Loaded java.util.jar.Manifest from shared objects file]
[Loaded java.io.ByteArrayInputStream from shared objects file]
[Loaded java.util.jar.Attributes from shared objects file]
[Loaded java.util.jar.Manifest$FastInputStream from shared objects file]
[Loaded java.util.jar.Attributes$Name from shared objects file]
[Loaded sun.misc.ASCIICaseInsensitiveComparator from shared objects file]
[Loaded java.util.jar.JarVerifier from shared objects file]
[Loaded java.io.ByteArrayOutputStream from shared objects file]
[Loaded java.net.URLClassLoader$1 from shared objects file]
[Loaded sun.misc.URLClassPath$3 from shared objects file]
[Loaded sun.misc.URLClassPath$Loader from shared objects file]
[Loaded sun.misc.URLClassPath$JarLoader from shared objects file]
[Loaded java.security.PrivilegedActionException from shared objects file]
[Loaded sun.misc.URLClassPath$JarLoader$1 from shared objects file]
[Loaded sun.misc.FileURLMapper from shared objects file]
[Loaded sun.misc.JarIndex from shared objects file]
[Loaded sun.misc.ExtensionDependency from shared objects file]
[Loaded sun.misc.Resource from shared objects file]
[Loaded sun.misc.URLClassPath$JarLoader$2 from shared objects file]
[Loaded java.lang.Package from shared objects file]
[Loaded sun.security.util.ManifestEntryVerifier from shared objects file]
[Loaded sun.misc.CharacterDecoder from shared objects file]
[Loaded sun.misc.BASE64Decoder from shared objects file]
[Loaded sun.security.util.SignatureFileVerifier from shared objects file]
[Loaded sun.nio.ByteBuffered from shared objects file]
[Loaded java.security.CodeSource from shared objects file]
[Loaded java.security.PermissionCollection from shared objects file]
[Loaded java.security.Permissions from shared objects file]
[Loaded java.net.URLConnection from shared objects file]
[Loaded sun.net.www.URLConnection from shared objects file]
[Loaded sun.net.www.protocol.file.FileURLConnection from shared objects file]
[Loaded java.net.ContentHandler from shared objects file]
[Loaded java.net.UnknownContentHandler from shared objects file]
[Loaded sun.net.www.MessageHeader from shared objects file]
[Loaded java.io.FilePermission from shared objects file]
[Loaded java.io.FilePermission$1 from shared objects file]
[Loaded java.security.Policy from shared objects file]
[Loaded sun.security.provider.PolicyFile from shared objects file]
[Loaded java.security.Policy$UnsupportedEmptyCollection from shared objects file]
[Loaded java.io.FilePermissionCollection from shared objects file]
[Loaded java.security.AllPermission from shared objects file]
[Loaded java.security.UnresolvedPermission from shared objects file]
[Loaded java.security.BasicPermissionCollection from shared objects file]
[Loaded java.security.Principal from shared objects file]
[Loaded java.security.cert.Certificate from shared objects file]
[Loaded org.stathissideris.ascii2image.core.CommandLineConverter from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.io.IOException from shared objects file]
[Loaded java.io.FileNotFoundException from shared objects file]
[Loaded java.io.UnsupportedEncodingException from shared objects file]
[Loaded org.apache.commons.cli.ParseException from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.CommandLineParser from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.Parser from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.PosixParser from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.text.TextGrid from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]

DiTAA version 0.8, Copyright (C) 2004--2009  Efstathios Sideris

[Loaded org.apache.commons.cli.Options from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.OptionBuilder from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.lang.IllegalArgumentException from shared objects file]
[Loaded org.apache.commons.cli.Option from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.lang.CloneNotSupportedException from shared objects file]
[Loaded java.lang.UnsupportedOperationException from shared objects file]
[Loaded org.apache.commons.cli.OptionValidator from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.UnrecognizedOptionException from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.MissingArgumentException from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.apache.commons.cli.MissingOptionException from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.HashMap$Values from shared objects file]
[Loaded java.util.HashMap$HashIterator from shared objects file]
[Loaded java.util.HashMap$ValueIterator from shared objects file]
[Loaded java.util.AbstractList$Itr from shared objects file]
[Loaded org.apache.commons.cli.CommandLine from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.AbstractSequentialList from shared objects file]
[Loaded java.util.Queue from shared objects file]
[Loaded java.util.Deque from shared objects file]
[Loaded java.util.LinkedList from shared objects file]
[Loaded java.util.LinkedList$Entry from shared objects file]
[Loaded java.util.Arrays$ArrayList from shared objects file]
[Loaded java.util.ListIterator from shared objects file]
[Loaded java.util.AbstractList$ListItr from shared objects file]
[Loaded org.apache.commons.cli.Util from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.core.ConversionOptions from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.xml.sax.SAXException from shared objects file]
[Loaded javax.xml.parsers.ParserConfigurationException from shared objects file]
[Loaded org.stathissideris.ascii2image.core.ProcessingOptions from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.core.RenderingOptions from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.core.ConfigurationParser from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.xml.sax.EntityResolver from shared objects file]
[Loaded org.xml.sax.DTDHandler from shared objects file]
[Loaded org.xml.sax.ContentHandler from shared objects file]
[Loaded org.xml.sax.ErrorHandler from shared objects file]
[Loaded org.xml.sax.helpers.DefaultHandler from shared objects file]
[Loaded org.stathissideris.ascii2image.core.ConfigurationParser$XMLHandler from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
Running with options:
[Loaded java.util.HashMap$KeySet from shared objects file]
[Loaded java.util.HashMap$KeyIterator from shared objects file]
Reading file: foo.txt
[Loaded org.stathissideris.ascii2image.core.FileUtils from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.regex.Pattern from shared objects file]
[Loaded java.util.regex.Pattern$Node from shared objects file]
[Loaded java.util.regex.Pattern$5 from shared objects file]
[Loaded java.util.regex.Pattern$LastNode from shared objects file]
[Loaded java.util.regex.Pattern$GroupHead from shared objects file]
[Loaded java.util.regex.Pattern$GroupTail from shared objects file]
[Loaded java.util.regex.Pattern$CharProperty from shared objects file]
[Loaded java.util.regex.Pattern$BmpCharProperty from shared objects file]
[Loaded java.util.regex.Pattern$Single from shared objects file]
[Loaded java.util.regex.Pattern$Ques from shared objects file]
[Loaded java.util.regex.Pattern$BranchConn from shared objects file]
[Loaded java.util.regex.Pattern$Branch from shared objects file]
[Loaded java.util.regex.Pattern$SliceNode from shared objects file]
[Loaded java.util.regex.Pattern$Slice from shared objects file]
[Loaded java.util.regex.Pattern$Begin from shared objects file]
[Loaded java.util.regex.Pattern$First from shared objects file]
[Loaded java.util.regex.Pattern$Start from shared objects file]
[Loaded java.util.regex.Pattern$TreeInfo from shared objects file]
[Loaded java.util.regex.MatchResult from shared objects file]
[Loaded java.util.regex.Matcher from shared objects file]
[Loaded java.util.SubList from shared objects file]
[Loaded java.util.RandomAccessSubList from shared objects file]
[Loaded java.util.SubList$1 from shared objects file]
[Loaded org.stathissideris.ascii2image.text.StringUtils from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.regex.Pattern$Ctype from shared objects file]
[Loaded java.util.regex.Pattern$Curly from shared objects file]
[Loaded java.util.regex.Pattern$Dollar from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.util.regex.ASCII from shared objects file]
[Loaded org.stathissideris.ascii2image.text.TextGrid$Cell from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.regex.Pattern$BnM from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.util.regex.Pattern$SliceS from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded org.stathissideris.ascii2image.graphics.Diagram from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.text.AbstractionGrid from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded sun.misc.Cleaner from shared objects file]
[Loaded java.lang.Enum from shared objects file]
[Loaded org.stathissideris.ascii2image.text.CellSet from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.text.GridPatternGroup from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.text.GridPattern from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.regex.Pattern$Dot from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.util.regex.Pattern$BitClass from shared objects file]
[Loaded java.util.regex.Pattern$CharProperty$1 from shared objects file]
[Loaded java.util.regex.Pattern$8 from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded org.stathissideris.ascii2image.text.AbstractCell from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.graphics.DiagramComponent from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.graphics.DiagramShape from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.geom.Point2D from shared objects file]
[Loaded java.awt.geom.Point2D$Float from shared objects file]
[Loaded org.stathissideris.ascii2image.graphics.ShapePoint from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.Shape from shared objects file]
[Loaded java.awt.Transparency from shared objects file]
[Loaded java.awt.Paint from shared objects file]
[Loaded java.awt.Color from shared objects file]
[Loaded java.awt.Toolkit from shared objects file]
[Loaded java.awt.Toolkit$3 from shared objects file]
[Loaded java.util.ResourceBundle$Control from shared objects file]
[Loaded sun.util.CoreResourceBundleControl from shared objects file]
[Loaded java.util.Collections$UnmodifiableCollection from shared objects file]
[Loaded java.util.Collections$UnmodifiableList from shared objects file]
[Loaded java.util.Collections$UnmodifiableRandomAccessList from shared objects file]
[Loaded java.util.ResourceBundle from shared objects file]
[Loaded java.util.ResourceBundle$1 from shared objects file]
[Loaded java.util.ResourceBundle$RBClassLoader from shared objects file]
[Loaded java.util.ResourceBundle$RBClassLoader$1 from shared objects file]
[Loaded java.util.ResourceBundle$CacheKey from shared objects file]
[Loaded java.util.ResourceBundle$CacheKeyReference from shared objects file]
[Loaded java.util.ResourceBundle$LoaderReference from shared objects file]
[Loaded java.util.ResourceBundle$SingleFormatControl from shared objects file]
[Loaded java.util.ListResourceBundle from shared objects file]
[Loaded sun.awt.resources.awt from shared objects file]
[Loaded sun.security.action.LoadLibraryAction from shared objects file]
[Loaded java.awt.GraphicsEnvironment from shared objects file]
[Loaded java.awt.GraphicsEnvironment$1 from shared objects file]
[Loaded java.lang.ProcessEnvironment from shared objects file]
[Loaded java.lang.ProcessEnvironment$ExternalData from shared objects file]
[Loaded java.lang.ProcessEnvironment$Variable from shared objects file]
[Loaded java.lang.ProcessEnvironment$Value from shared objects file]
[Loaded java.lang.ProcessEnvironment$StringEnvironment from shared objects file]
[Loaded java.util.Collections$UnmodifiableMap from shared objects file]
[Loaded java.awt.Toolkit$1 from shared objects file]
[Loaded sun.awt.DebugHelper from shared objects file]
[Loaded sun.awt.NativeLibLoader from shared objects file]
[Loaded sun.awt.DebugHelperStub from shared objects file]
[Loaded org.stathissideris.ascii2image.graphics.ShapeEdge from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.core.Pair from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.geom.Path2D from shared objects file]
[Loaded java.awt.geom.Path2D$Float from shared objects file]
[Loaded java.awt.geom.GeneralPath from shared objects file]
[Loaded sun.awt.geom.Curve from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded org.stathissideris.ascii2image.graphics.CompositeDiagramShape from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.util.regex.Pattern$2 from shared objects file]
[Loaded java.util.regex.Pattern$6 from shared objects file]
[Loaded org.stathissideris.ascii2image.text.TextGrid$CellTagPair from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded org.stathissideris.ascii2image.graphics.FontMeasurer from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.Image from shared objects file]
[Loaded java.awt.image.RenderedImage from shared objects file]
[Loaded java.awt.image.WritableRenderedImage from shared objects file]
[Loaded java.awt.image.BufferedImage from shared objects file]
[Loaded java.awt.ImageCapabilities from shared objects file]
[Loaded sun.awt.image.SurfaceManager$ImageAccessor from shared objects file]
[Loaded java.awt.Image$1 from shared objects file]
[Loaded sun.awt.image.SurfaceManager from shared objects file]
[Loaded java.awt.image.ColorModel from shared objects file]
[Loaded java.awt.image.PackedColorModel from shared objects file]
[Loaded java.awt.image.DirectColorModel from shared objects file]
[Loaded java.awt.color.ColorSpace from shared objects file]
[Loaded java.awt.color.ICC_Profile from shared objects file]
[Loaded sun.awt.color.ProfileDeferralInfo from shared objects file]
[Loaded sun.awt.color.ProfileDeferralMgr from shared objects file]
[Loaded java.awt.color.ICC_ProfileRGB from shared objects file]
[Loaded sun.awt.color.ProfileActivator from shared objects file]
[Loaded java.awt.color.ICC_Profile$1 from shared objects file]
[Loaded java.awt.color.ICC_ColorSpace from shared objects file]
[Loaded java.awt.image.Raster from shared objects file]
[Loaded java.awt.image.DataBuffer from shared objects file]
[Loaded java.awt.image.DataBufferInt from shared objects file]
[Loaded java.awt.Point from shared objects file]
[Loaded java.awt.image.SampleModel from shared objects file]
[Loaded java.awt.image.SinglePixelPackedSampleModel from shared objects file]
[Loaded java.awt.image.WritableRaster from shared objects file]
[Loaded sun.awt.image.SunWritableRaster from shared objects file]
[Loaded sun.awt.image.IntegerComponentRaster from shared objects file]
[Loaded sun.awt.image.IntegerInterleavedRaster from shared objects file]
[Loaded sun.awt.image.NativeLibLoader from shared objects file]
[Loaded java.awt.geom.RectangularShape from shared objects file]
[Loaded java.awt.geom.Rectangle2D from shared objects file]
[Loaded java.awt.Rectangle from shared objects file]
[Loaded sun.java2d.FontSupport from shared objects file]
[Loaded java.util.EventListener from shared objects file]
[Loaded sun.awt.DisplayChangedListener from shared objects file]
[Loaded sun.java2d.SunGraphicsEnvironment from shared objects file]
[Loaded sun.awt.X11GraphicsEnvironment from shared objects file]
[Loaded sun.java2d.SunGraphicsEnvironment$1 from shared objects file]
[Loaded java.io.FilenameFilter from shared objects file]
[Loaded sun.java2d.SunGraphicsEnvironment$TTFilter from shared objects file]
[Loaded sun.java2d.SunGraphicsEnvironment$T1Filter from shared objects file]
[Loaded sun.awt.X11GraphicsEnvironment$1 from shared objects file]
[Loaded sun.awt.WindowClosingSupport from shared objects file]
[Loaded sun.awt.WindowClosingListener from shared objects file]
[Loaded sun.awt.ComponentFactory from shared objects file]
[Loaded sun.awt.InputMethodSupport from shared objects file]
[Loaded sun.awt.SunToolkit from shared objects file]
[Loaded java.util.logging.Logger from shared objects file]
[Loaded java.util.logging.Handler from shared objects file]
[Loaded java.util.logging.Level from shared objects file]
[Loaded java.util.logging.LogManager from shared objects file]
[Loaded java.util.logging.LogManager$1 from shared objects file]
[Loaded java.beans.PropertyChangeSupport from shared objects file]
[Loaded java.util.logging.LogManager$LogNode from shared objects file]
[Loaded java.util.logging.LoggingPermission from shared objects file]
[Loaded java.util.logging.LogManager$Cleaner from shared objects file]
[Loaded java.lang.ApplicationShutdownHooks from shared objects file]
[Loaded java.lang.ApplicationShutdownHooks$1 from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.lang.Shutdown from shared objects file]
[Loaded java.lang.Shutdown$Lock from shared objects file]
[Loaded java.util.IdentityHashMap from shared objects file]
[Loaded java.util.logging.LogManager$RootLogger from shared objects file]
[Loaded java.util.logging.LogManager$2 from shared objects file]
[Loaded java.util.Properties$LineReader from shared objects file]
[Loaded java.util.Hashtable$Enumerator from shared objects file]
[Loaded java.util.EventObject from shared objects file]
[Loaded java.beans.PropertyChangeEvent from shared objects file]
[Loaded java.util.concurrent.locks.Condition from shared objects file]
[Loaded java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject from shared objects file]
[Loaded sun.awt.AWTAutoShutdown from shared objects file]
[Loaded sun.awt.AWTAutoShutdown$PeerMap from shared objects file]
[Loaded java.util.WeakHashMap from shared objects file]
[Loaded java.util.WeakHashMap$Entry from shared objects file]
[Loaded sun.awt.SunDisplayChanger from shared objects file]
[Loaded sun.java2d.SunGraphicsEnvironment$2 from shared objects file]
[Loaded java.io.StreamTokenizer from shared objects file]
[Loaded sun.font.FontManager from shared objects file]
[Loaded sun.font.Font2D from shared objects file]
[Loaded sun.font.PhysicalFont from shared objects file]
[Loaded sun.font.FileFont from shared objects file]
[Loaded sun.font.CompositeFont from shared objects file]
[Loaded sun.font.FontManager$1 from shared objects file]
[Loaded java.awt.Font from shared objects file]
[Loaded java.awt.geom.AffineTransform from shared objects file]
[Loaded sun.font.AttributeValues from shared objects file]
[Loaded sun.font.EAttribute from shared objects file]
[Loaded java.text.AttributedCharacterIterator$Attribute from shared objects file]
[Loaded java.lang.Class$4 from shared objects file]
[Loaded sun.reflect.NativeMethodAccessorImpl from shared objects file]
[Loaded sun.reflect.DelegatingMethodAccessorImpl from shared objects file]
[Loaded java.awt.font.TextAttribute from shared objects file]
[Loaded java.lang.Integer$IntegerCache from shared objects file]
[Loaded sun.font.TrueTypeFont from shared objects file]
[Loaded java.awt.font.FontRenderContext from shared objects file]
[Loaded java.awt.RenderingHints from shared objects file]
[Loaded sun.awt.SunHints from shared objects file]
[Loaded java.awt.RenderingHints$Key from shared objects file]
[Loaded sun.awt.SunHints$Key from shared objects file]
[Loaded sun.awt.SunHints$Value from shared objects file]
[Loaded sun.awt.SunHints$LCDContrastKey from shared objects file]
[Loaded sun.font.Type1Font from shared objects file]
[Loaded sun.font.StrikeMetrics from shared objects file]
[Loaded java.awt.geom.Rectangle2D$Float from shared objects file]
[Loaded sun.font.CharToGlyphMapper from shared objects file]
[Loaded sun.font.FontStrike from shared objects file]
[Loaded sun.font.PhysicalStrike from shared objects file]
[Loaded sun.font.GlyphList from shared objects file]
[Loaded sun.font.StrikeCache from shared objects file]
[Loaded sun.java2d.Disposer from shared objects file]
[Loaded sun.java2d.Disposer$1 from shared objects file]
[Loaded sun.font.StrikeCache$1 from shared objects file]
[Loaded sun.font.FontManager$FontRegistrationInfo from shared objects file]
[Loaded sun.awt.FontConfiguration from shared objects file]
[Loaded sun.awt.motif.MFontConfiguration from shared objects file]
[Loaded sun.awt.FontDescriptor from shared objects file]
[Loaded sun.awt.FontConfiguration$PropertiesHandler from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.awt.FontConfiguration$PropertiesHandler$FontProperties from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.lang.Short$ShortCache from shared objects file]
[Loaded java.util.HashMap$EntrySet from shared objects file]
[Loaded java.util.HashMap$EntryIterator from shared objects file]
[Loaded java.util.LinkedHashMap$LinkedHashIterator from shared objects file]
[Loaded java.util.LinkedHashMap$KeyIterator from shared objects file]
[Loaded sun.font.NativeFont from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.font.CompositeFontDescriptor from shared objects file]
[Loaded sun.font.Font2DHandle from shared objects file]
[Loaded sun.font.FontFamily from shared objects file]
[Loaded sun.java2d.DisposerTarget from shared objects file]
[Loaded sun.java2d.Surface from shared objects file]
[Loaded sun.java2d.SurfaceData from shared objects file]
[Loaded java.lang.IllegalStateException from shared objects file]
[Loaded sun.java2d.InvalidPipeException from shared objects file]
[Loaded sun.java2d.NullSurfaceData from shared objects file]
[Loaded sun.java2d.loops.SurfaceType from shared objects file]
[Loaded sun.awt.image.PixelConverter from shared objects file]
[Loaded sun.awt.image.PixelConverter$Xrgb from shared objects file]
[Loaded sun.awt.image.PixelConverter$Argb from shared objects file]
[Loaded sun.awt.image.PixelConverter$ArgbPre from shared objects file]
[Loaded sun.awt.image.PixelConverter$Xbgr from shared objects file]
[Loaded sun.awt.image.PixelConverter$Rgba from shared objects file]
[Loaded sun.awt.image.PixelConverter$RgbaPre from shared objects file]
[Loaded sun.awt.image.PixelConverter$Ushort565Rgb from shared objects file]
[Loaded sun.awt.image.PixelConverter$Ushort555Rgb from shared objects file]
[Loaded sun.awt.image.PixelConverter$Ushort555Rgbx from shared objects file]
[Loaded sun.awt.image.PixelConverter$Ushort4444Argb from shared objects file]
[Loaded sun.awt.image.PixelConverter$ByteGray from shared objects file]
[Loaded sun.awt.image.PixelConverter$UshortGray from shared objects file]
[Loaded sun.awt.image.PixelConverter$Rgbx from shared objects file]
[Loaded sun.awt.image.PixelConverter$Bgrx from shared objects file]
[Loaded sun.awt.image.PixelConverter$ArgbBm from shared objects file]
[Loaded sun.java2d.pipe.PixelDrawPipe from shared objects file]
[Loaded sun.java2d.pipe.PixelFillPipe from shared objects file]
[Loaded sun.java2d.pipe.ShapeDrawPipe from shared objects file]
[Loaded sun.java2d.pipe.TextPipe from shared objects file]
[Loaded sun.java2d.pipe.DrawImagePipe from shared objects file]
[Loaded sun.java2d.pipe.NullPipe from shared objects file]
[Loaded java.awt.image.IndexColorModel from shared objects file]
[Loaded sun.java2d.pipe.ParallelogramPipe from shared objects file]
[Loaded sun.java2d.pipe.LoopPipe from shared objects file]
[Loaded sun.java2d.pipe.OutlineTextRenderer from shared objects file]
[Loaded sun.java2d.pipe.GlyphListPipe from shared objects file]
[Loaded sun.java2d.pipe.GlyphListLoopPipe from shared objects file]
[Loaded sun.java2d.pipe.SolidTextRenderer from shared objects file]
[Loaded sun.java2d.pipe.AATextRenderer from shared objects file]
[Loaded sun.java2d.pipe.LCDTextRenderer from shared objects file]
[Loaded sun.java2d.pipe.CompositePipe from shared objects file]
[Loaded sun.java2d.pipe.AlphaColorPipe from shared objects file]
[Loaded sun.java2d.pipe.PixelToShapeConverter from shared objects file]
[Loaded sun.java2d.pipe.PixelToParallelogramConverter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.pipe.TextRenderer from shared objects file]
[Loaded sun.java2d.pipe.SpanClipRenderer from shared objects file]
[Loaded sun.java2d.pipe.Region from shared objects file]
[Loaded sun.java2d.pipe.RegionIterator from shared objects file]
[Loaded sun.java2d.pipe.Region$ImmutableRegion from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.pipe.AlphaPaintPipe from shared objects file]
[Loaded sun.java2d.pipe.SpanShapeRenderer from shared objects file]
[Loaded sun.java2d.pipe.SpanShapeRenderer$Composite from shared objects file]
[Loaded sun.java2d.pipe.GeneralCompositePipe from shared objects file]
[Loaded sun.java2d.pipe.DrawImage from shared objects file]
[Loaded sun.java2d.loops.RenderCache from shared objects file]
[Loaded sun.java2d.loops.RenderCache$Entry from shared objects file]
[Loaded sun.java2d.SurfaceManagerFactory from shared objects file]
[Loaded sun.awt.image.RasterListener from shared objects file]
[Loaded sun.awt.image.CachingSurfaceManager from shared objects file]
[Loaded sun.java2d.x11.X11CachingSurfaceManager from shared objects file]
[Loaded sun.awt.image.BufImgSurfaceData from shared objects file]
[Loaded sun.java2d.loops.RenderLoops from shared objects file]
[Loaded sun.java2d.DisposerRecord from shared objects file]
[Loaded sun.java2d.DefaultDisposerRecord from shared objects file]
[Loaded sun.java2d.loops.CompositeType from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitive from shared objects file]
[Loaded sun.java2d.loops.DrawLine from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitiveMgr from shared objects file]
[Loaded java.awt.Graphics from shared objects file]
[Loaded java.awt.Graphics2D from shared objects file]
[Loaded sun.awt.ConstrainableGraphics from shared objects file]
[Loaded sun.java2d.DestSurfaceProvider from shared objects file]
[Loaded sun.java2d.SunGraphics2D from shared objects file]
[Loaded java.awt.Composite from shared objects file]
[Loaded sun.java2d.loops.XORComposite from shared objects file]
[Loaded java.awt.AlphaComposite from shared objects file]
[Loaded sun.java2d.loops.Blit from shared objects file]
[Loaded sun.java2d.loops.BlitBg from shared objects file]
[Loaded sun.java2d.loops.ScaledBlit from shared objects file]
[Loaded sun.java2d.loops.FillRect from shared objects file]
[Loaded sun.java2d.loops.FillSpans from shared objects file]
[Loaded sun.java2d.loops.FillParallelogram from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.loops.DrawParallelogram from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.loops.DrawRect from shared objects file]
[Loaded sun.java2d.loops.DrawPolygons from shared objects file]
[Loaded sun.java2d.loops.DrawPath from shared objects file]
[Loaded sun.java2d.loops.FillPath from shared objects file]
[Loaded sun.java2d.loops.MaskBlit from shared objects file]
[Loaded sun.java2d.loops.MaskFill from shared objects file]
[Loaded sun.java2d.loops.DrawGlyphList from shared objects file]
[Loaded sun.java2d.loops.DrawGlyphListAA from shared objects file]
[Loaded sun.java2d.loops.DrawGlyphListLCD from shared objects file]
[Loaded sun.java2d.loops.TransformHelper from shared objects file]
[Loaded java.awt.Stroke from shared objects file]
[Loaded java.awt.BasicStroke from shared objects file]
[Loaded sun.misc.PerformanceLogger from shared objects file]
[Loaded sun.misc.PerformanceLogger$TimeData from shared objects file]
[Loaded sun.java2d.pipe.ValidatePipe from shared objects file]
[Loaded sun.java2d.loops.CustomComponent from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitiveProxy from shared objects file]
[Loaded sun.java2d.loops.GeneralRenderer from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitiveMgr$1 from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitiveMgr$2 from shared objects file]
[Loaded sun.java2d.loops.GraphicsPrimitiveMgr$PrimitiveSpec from shared objects file]
Locale: en_US
Dialog.bold
[Loaded java.awt.FontMetrics from shared objects file]
[Loaded sun.font.FontDesignMetrics from shared objects file]
[Loaded java.awt.GraphicsDevice from shared objects file]
[Loaded sun.awt.X11GraphicsDevice from shared objects file]
[Loaded java.awt.GraphicsConfiguration from shared objects file]
[Loaded sun.awt.X11GraphicsConfig from shared objects file]
[Loaded sun.java2d.x11.X11SurfaceData from shared objects file]
[Loaded sun.font.X11TextRenderer from shared objects file]
[Loaded sun.java2d.x11.X11PMBlitLoops from shared objects file]
[Loaded sun.java2d.x11.X11PMBlitLoops$DelegateBlitLoop from shared objects file]
[Loaded sun.java2d.x11.X11PMBlitBgLoops from shared objects file]
[Loaded sun.java2d.x11.X11SurfaceData$LazyPipe from shared objects file]
[Loaded sun.awt.X11GraphicsConfig$X11GCDisposerRecord from shared objects file]
[Loaded sun.font.FontDesignMetrics$MetricsKey from shared objects file]
[Loaded sun.font.FontStrikeDesc from shared objects file]
[Loaded sun.font.CompositeStrike from shared objects file]
[Loaded sun.font.FontStrikeDisposer from shared objects file]
[Loaded sun.font.StrikeCache$DisposableStrike from shared objects file]
[Loaded sun.font.StrikeCache$SoftDisposerRef from shared objects file]
[Loaded sun.font.TrueTypeFont$TTDisposerRecord from shared objects file]
[Loaded sun.font.TrueTypeFont$1 from shared objects file]
[Loaded java.io.DataOutput from shared objects file]
[Loaded java.io.RandomAccessFile from shared objects file]
[Loaded java.nio.channels.Channel from shared objects file]
[Loaded java.nio.channels.InterruptibleChannel from shared objects file]
[Loaded java.nio.channels.spi.AbstractInterruptibleChannel from shared objects file]
[Loaded java.nio.channels.ReadableByteChannel from shared objects file]
[Loaded java.nio.channels.WritableByteChannel from shared objects file]
[Loaded java.nio.channels.ByteChannel from shared objects file]
[Loaded java.nio.channels.GatheringByteChannel from shared objects file]
[Loaded java.nio.channels.ScatteringByteChannel from shared objects file]
[Loaded java.nio.channels.FileChannel from shared objects file]
[Loaded sun.nio.ch.FileChannelImpl from shared objects file]
[Loaded sun.nio.ch.Util from shared objects file]
[Loaded sun.nio.ch.IOUtil from shared objects file]
[Loaded sun.nio.ch.NativeDispatcher from shared objects file]
[Loaded sun.nio.ch.FileDispatcher from shared objects file]
[Loaded sun.nio.ch.NativeThreadSet from shared objects file]
[Loaded sun.nio.ch.Interruptible from shared objects file]
[Loaded java.nio.channels.spi.AbstractInterruptibleChannel$1 from shared objects file]
[Loaded sun.nio.ch.NativeThread from shared objects file]
[Loaded sun.nio.ch.IOStatus from shared objects file]
[Loaded sun.nio.ch.DirectBuffer from shared objects file]
[Loaded java.nio.MappedByteBuffer from shared objects file]
[Loaded java.nio.DirectByteBuffer from shared objects file]
[Loaded java.nio.DirectByteBuffer$Deallocator from shared objects file]
[Loaded java.nio.IntBuffer from shared objects file]
[Loaded java.nio.ByteBufferAsIntBufferB from shared objects file]
[Loaded sun.font.TrueTypeFont$DirectoryEntry from shared objects file]
[Loaded java.nio.ShortBuffer from shared objects file]
[Loaded java.nio.ByteBufferAsShortBufferB from shared objects file]
[Loaded sun.nio.cs.UTF_16 from shared objects file]
[Loaded sun.nio.cs.UnicodeDecoder from shared objects file]
[Loaded sun.nio.cs.UTF_16$Decoder from shared objects file]
[Loaded sun.nio.cs.Surrogate from shared objects file]
[Loaded sun.font.FileFontStrike from shared objects file]
[Loaded sun.font.FileFont$FileFontDisposer from shared objects file]
[Loaded sun.font.TrueTypeGlyphMapper from shared objects file]
[Loaded sun.font.CMap from shared objects file]
[Loaded sun.font.CMap$NullCMapClass from shared objects file]
[Loaded sun.font.CMap$CMapFormat4 from shared objects file]
[Loaded java.nio.ByteBufferAsCharBufferB from shared objects file]
[Loaded sun.font.FontDesignMetrics$KeyReference from shared objects file]
[Loaded org.stathissideris.ascii2image.text.TextGrid$CellStringPair from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.font.GlyphVector from shared objects file]
[Loaded sun.font.StandardGlyphVector from shared objects file]
[Loaded sun.font.CompositeGlyphMapper from shared objects file]
[Loaded sun.font.StandardGlyphVector$GlyphStrike from shared objects file]
[Loaded sun.font.CoreMetrics from shared objects file]
[Loaded java.awt.font.LineMetrics from shared objects file]
[Loaded sun.font.FontLineMetrics from shared objects file]
[Loaded org.stathissideris.ascii2image.graphics.DiagramText from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.geom.PathIterator from shared objects file]
[Loaded java.awt.geom.Path2D$Iterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.geom.Path2D$Float$CopyIterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.lang.StrictMath from shared objects file]
Rendering to file: foo_3.png
[Loaded org.stathissideris.ascii2image.graphics.BitmapRenderer from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded sun.java2d.SurfaceData$AA from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.pipe.DuctusShapeRenderer from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.geom.Path2D$Float$TxIterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.java2d.pipe.DuctusRenderer from shared objects file]
[Loaded sun.dc.pr.Rasterizer from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.dc.path.PathConsumer from shared objects file]
[Loaded sun.dc.pr.PathFiller from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.dc.pr.PathStroker from shared objects file]
[Loaded sun.dc.pr.PathDasher from shared objects file]
[Loaded sun.dc.pr.Rasterizer$ConsumerDisposer from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.Kernel from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.BufferedImageOp from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.RasterOp from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.ConvolveOp from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.awt.image.ImagingLib from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.awt.image.ImagingLib$1 from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.LookupOp from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.AffineTransformOp from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded org.stathissideris.ascii2image.core.Shape3DOrderingComparator from file:/home/nick/src/emacs/org/org-mode/contrib/scripts/ditaa.jar]
[Loaded java.awt.geom.Line2D from shared objects file]
[Loaded sun.java2d.loops.FontInfo from shared objects file]
[Loaded javax.imageio.ImageIO from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ServiceRegistry from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.IIORegistry from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.RegisterableService from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.IIOServiceProvider from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageReaderWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageTranscoderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageInputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.ImageOutputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.awt.AppContext from shared objects file]
[Loaded sun.awt.AppContext$1 from shared objects file]
[Loaded sun.awt.AppContext$2 from shared objects file]
[Loaded sun.awt.MostRecentKeyValue from shared objects file]
[Loaded javax.imageio.spi.SubRegistry from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.PartiallyOrderedSet from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.gif.GIFImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.stream.ImageInputStream from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.DigraphNode from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.gif.GIFImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.stream.ImageOutputStream from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.bmp.BMPImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.bmp.BMPImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.wbmp.WBMPImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.wbmp.WBMPImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.PNGImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.PNGImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.jpeg.JPEGImageReaderSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.jpeg.JPEG from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.jpeg.JPEGImageWriterSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.FileImageInputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.FileImageOutputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.InputStreamImageInputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.OutputStreamImageOutputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.RAFImageInputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.spi.RAFImageOutputStreamSpi from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.IIORegistry$1 from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.misc.Service from shared objects file]
[Loaded sun.misc.Service$LazyIterator from shared objects file]
[Loaded java.util.SortedSet from shared objects file]
[Loaded java.util.NavigableSet from shared objects file]
[Loaded java.util.TreeSet from shared objects file]
[Loaded java.util.SortedMap from shared objects file]
[Loaded java.util.NavigableMap from shared objects file]
[Loaded java.util.TreeMap from shared objects file]
[Loaded sun.misc.Launcher$1 from shared objects file]
[Loaded sun.misc.Launcher$2 from shared objects file]
[Loaded sun.misc.URLClassPath$2 from shared objects file]
[Loaded java.lang.ClassLoader$2 from shared objects file]
[Loaded sun.misc.URLClassPath$1 from shared objects file]
[Loaded java.net.URLClassLoader$3 from shared objects file]
[Loaded sun.misc.CompoundEnumeration from shared objects file]
[Loaded java.net.URLClassLoader$3$1 from shared objects file]
[Loaded javax.imageio.ImageReader from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.metadata.IIOMetadataFormat from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageTranscoder from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageWriter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageTypeSpecifier from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.PartialOrderIterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageIO$CacheInfo from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.stream.ImageInputStreamImpl from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.stream.ImageOutputStreamImpl from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.stream.FileImageOutputStream from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.stream.CloseableDisposerRecord from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageTypeSpecifier$Packed from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded sun.awt.color.CMM$CSAccessor from shared objects file]
[Loaded javax.imageio.spi.ServiceRegistry$Filter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageIO$CanEncodeImageAndFormatFilter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.spi.FilterIterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.ImageIO$ImageWriterIterator from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.PNGImageWriter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.RowFilter from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.IIOImage from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded javax.imageio.metadata.IIOMetadata from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.PNGMetadata from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.ChunkStream from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.CRC from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded com.sun.imageio.plugins.png.IDATOutputStream from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.util.zip.Deflater from /usr/lib/jvm/java-6-sun-1.6.0.14/jre/lib/rt.jar]
[Loaded java.awt.image.ComponentSampleModel from shared objects file]
[Loaded java.awt.image.PixelInterleavedSampleModel from shared objects file]
Done in 0sec
[Loaded java.util.IdentityHashMap$KeySet from shared objects file]
[Loaded java.util.IdentityHashMap$IdentityHashMapIterator from shared objects file]
[Loaded java.util.IdentityHashMap$KeyIterator from shared objects file]

[-- Attachment #3: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: DiTAA error under Ubuntu

[Eric S Fraga]

At Thu, 13 Aug 2009 11:04:04 +0200,
Sébastien Vauban wrote:
> 
> Nick, Eric,
> 
> Sorry for answering late -- while you were prompt at replying. Have been out
> for one day.

[...]

> Here is the situation of Java-related packages on my system so far:
> 

[...]

> p   openjdk-6-dbg                   - Java runtime based on OpenJDK (debugging symbols)
> p   openjdk-6-demo                  - Java runtime based on OpenJDK (demos and examples)
> p   openjdk-6-doc                   - OpenJDK Development Kit (JDK) documentation
> p   openjdk-6-jdk                   - OpenJDK Development Kit (JDK)
> p   openjdk-6-jre                   - OpenJDK Java runtime, using Hotspot JIT
> p   openjdk-6-jre-zero              - Alternatve JVM for OpenJDK, using Zero/Shark
> p   openjdk-6-source                - OpenJDK Development Kit (JDK) source files
> p   openjdk-6-source-files          - OpenJDK 6 source files (used as a build dependency)

[...]

> p   sun-java6-demo                  - Sun Java(TM) Development Kit (JDK) 6 demos and examples
> p   sun-java6-doc                   - Sun JDK(TM) Documention -- integration installer
> p   sun-java6-fonts                 - Lucida TrueType fonts (from the Sun JRE)
> p   sun-java6-javadb                - Java(TM) DB, Sun Microsystems' distribution of Apache Derby
> p   sun-java6-jdk                   - Sun Java(TM) Development Kit (JDK) 6
> p   sun-java6-jre                   - Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent f
> p   sun-java6-plugin                - The Java(TM) Plug-in, Java SE 6
> p   sun-java6-source                - Sun Java(TM) Development Kit (JDK) 6 source files

Is there any reason you do not wish to install either of openjdk or
sun-java?  The gnu java implementation is (I believe -- I could be
horridly out of date on this) still not complete, especially with
respect to AWT.  My recommendation would be to install either
openjdk-6 (which Nick I believe is using and works) or sun-java6
(which I am using and works).

> For the records:
> 
> --8<---------------cut here---------------start------------->8---
> > which java
> /usr/bin/java
> 
> > ls -lia /usr/bin/java
> 94778 lrwxrwxrwx 1 root root 22 Aug  6 15:28 /usr/bin/java -> /etc/alternatives/java*
> --8<---------------cut here---------------end--------------->8---

Best is to do:

update-alternatives --display java

which will list the alternatives installed for that command as well as
tell you the default.  For me:

--8<---------------cut here---------------start------------->8---
$ update-alternatives --display java
java - manual mode
 link currently points to /usr/lib/jvm/java-6-sun/jre/bin/java
/usr/bin/gij-4.3 - priority 43
/usr/bin/gij-wrapper-4.0 - priority 40
 slave java.1.gz: /usr/share/man/man1/gij-wrapper-4.0.1.gz
/usr/bin/gij-wrapper-4.1 - priority 41
/usr/lib/jvm/java-6-sun/jre/bin/java - priority 63
 slave java.1.gz: /usr/lib/jvm/java-6-sun/jre/man/man1/java.1.gz
/usr/lib/jvm/java-gcj/jre/bin/java - priority 1043
 slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.
$
--8<---------------cut here---------------end--------------->8---

so my default Java is the one from Sun, version 6.

> What do you advise me to do?  Installing another well-chosen
> package?

Yes, my recommendation would indeed be to install one of openjdk or
sun-java.

Re: Re: DiTAA error under Ubuntu

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> 
> Is there any reason you do not wish to install either of openjdk or
> sun-java?  The gnu java implementation is (I believe -- I could be
> horridly out of date on this) still not complete, especially with
> respect to AWT.  My recommendation would be to install either
> openjdk-6 (which Nick I believe is using and works) or sun-java6
> (which I am using and works).
> 

Seb is using openjdk. I, otoh, use Sun's version, as you do: perhaps
there is a problem with openjdk, perhaps it's just Seb's setup.

> 
> Best is to do:
> 
> update-alternatives --display java
> 
> which will list the alternatives installed for that command as well as
> tell you the default.  For me:
> 
> --8<---------------cut here---------------start------------->8---
> $ update-alternatives --display java
> java - manual mode
>  link currently points to /usr/lib/jvm/java-6-sun/jre/bin/java
> /usr/bin/gij-4.3 - priority 43
> /usr/bin/gij-wrapper-4.0 - priority 40
>  slave java.1.gz: /usr/share/man/man1/gij-wrapper-4.0.1.gz
> /usr/bin/gij-wrapper-4.1 - priority 41
> /usr/lib/jvm/java-6-sun/jre/bin/java - priority 63
>  slave java.1.gz: /usr/lib/jvm/java-6-sun/jre/man/man1/java.1.gz
> /usr/lib/jvm/java-gcj/jre/bin/java - priority 1043
>  slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
> Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.
> $
> --8<---------------cut here---------------end--------------->8---
> 
> so my default Java is the one from Sun, version 6.
> 

In my case, this gives

$ update-alternatives --display java
java - status is auto.
 link currently points to /usr/lib/jvm/java-6-sun/jre/bin/java
/usr/lib/jvm/java-6-sun/jre/bin/java - priority 63
 slave java.1.gz: /usr/lib/jvm/java-6-sun/jre/man/man1/java.1.gz
Current `best' version is /usr/lib/jvm/java-6-sun/jre/bin/java.

> > What do you advise me to do?  Installing another well-chosen
> > package?
> 
> Yes, my recommendation would indeed be to install one of openjdk or
> sun-java.
> 

I guess the question is: is there anybody with an openjdk install
for whom ditaa is working?

Thanks,
Nick

Re: Re: DiTAA error under Ubuntu

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > 
> > Is there any reason you do not wish to install either of openjdk or
> > sun-java?  The gnu java implementation is (I believe -- I could be
> > horridly out of date on this) still not complete, especially with
> > respect to AWT.  My recommendation would be to install either
> > openjdk-6 (which Nick I believe is using and works) or sun-java6
> > (which I am using and works).
> > 
> 
> Seb is using openjdk. I, otoh, use Sun's version, as you do: perhaps
> there is a problem with openjdk, perhaps it's just Seb's setup.
> 

My mistake: I must have misread Seb's original mail (see, Seb, I told you it
wouldn't be the last time!-) Apparently, openjdk works fine.

Thanks,
Nick

Re: DiTAA error under Ubuntu

[Sébastien Vauban]

Hi Nick, Hi Eric,

Eric S Fraga wrote:
> Sébastien Vauban wrote:
>> Here is the situation of Java-related packages on my system so far:
>
> [...]
>
>> p   openjdk-6-dbg                   - Java runtime based on OpenJDK (debugging symbols)
>> p   openjdk-6-demo                  - Java runtime based on OpenJDK (demos and examples)
>> p   openjdk-6-doc                   - OpenJDK Development Kit (JDK) documentation
>> p   openjdk-6-jdk                   - OpenJDK Development Kit (JDK)
>> p   openjdk-6-jre                   - OpenJDK Java runtime, using Hotspot JIT
>> p   openjdk-6-jre-zero              - Alternatve JVM for OpenJDK, using Zero/Shark
>> p   openjdk-6-source                - OpenJDK Development Kit (JDK) source files
>> p   openjdk-6-source-files          - OpenJDK 6 source files (used as a build dependency)
>
> [...]
>
>> p   sun-java6-demo                  - Sun Java(TM) Development Kit (JDK) 6 demos and examples
>> p   sun-java6-doc                   - Sun JDK(TM) Documention -- integration installer
>> p   sun-java6-fonts                 - Lucida TrueType fonts (from the Sun JRE)
>> p   sun-java6-javadb                - Java(TM) DB, Sun Microsystems' distribution of Apache Derby
>> p   sun-java6-jdk                   - Sun Java(TM) Development Kit (JDK) 6
>> p   sun-java6-jre                   - Sun Java(TM) Runtime Environment (JRE) 6 (architecture independent f
>> p   sun-java6-plugin                - The Java(TM) Plug-in, Java SE 6
>> p   sun-java6-source                - Sun Java(TM) Development Kit (JDK) 6 source files
>
> Is there any reason you do not wish to install either of openjdk or
> sun-java?

No, it's just that part of the Java things were installed with `bootchart'.
So, I did not make any choice, and I fear problems of mixing versions...


> The gnu java implementation is (I believe -- I could be horridly
> out of date on this) still not complete, especially with respect to AWT. My
> recommendation would be to install either openjdk-6 (which Nick I believe is
> using and works) or sun-java6 (which I am using and works).

This clarifies what I have to do...

Just did:

--8<---------------cut here---------------start------------->8---
sudo aptitude install openjdk-6-jre
--8<---------------cut here---------------end--------------->8---

And, now, it works!  Thanks a lot!


> Best is to do:
>
> update-alternatives --display java
>
> which will list the alternatives installed for that command as well as
> tell you the default.  For me:
>
> $ update-alternatives --display java
> java - manual mode
>  link currently points to /usr/lib/jvm/java-6-sun/jre/bin/java
> /usr/bin/gij-4.3 - priority 43
> /usr/bin/gij-wrapper-4.0 - priority 40
>  slave java.1.gz: /usr/share/man/man1/gij-wrapper-4.0.1.gz
> /usr/bin/gij-wrapper-4.1 - priority 41
> /usr/lib/jvm/java-6-sun/jre/bin/java - priority 63
>  slave java.1.gz: /usr/lib/jvm/java-6-sun/jre/man/man1/java.1.gz
> /usr/lib/jvm/java-gcj/jre/bin/java - priority 1043
>  slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
> Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.
> $

For the records, I now have:

--8<---------------cut here---------------start------------->8---
> update-alternatives --display java
java - status is auto.
 link currently points to /usr/lib/jvm/java-6-openjdk/jre/bin/java
/usr/bin/gij-4.3 - priority 43
 slave java.1.gz: /usr/share/man/man1/gij-4.3.1.gz
/usr/lib/jvm/java-gcj/jre/bin/java - priority 1042
 slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
/usr/lib/jvm/java-6-openjdk/jre/bin/java - priority 1061
 slave java.1.gz: /usr/lib/jvm/java-6-openjdk/jre/man/man1/java.1.gz
Current `best' version is /usr/lib/jvm/java-6-openjdk/jre/bin/java.
--8<---------------cut here---------------end--------------->8---

Thanks again,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: DiTAA error under Ubuntu

[Eric S Fraga]

At Sat, 15 Aug 2009 10:23:59 +0200,
Sébastien Vauban wrote:

[...]

> > The gnu java implementation is (I believe -- I could be horridly
> > out of date on this) still not complete, especially with respect to AWT. My
> > recommendation would be to install either openjdk-6 (which Nick I believe is
> > using and works) or sun-java6 (which I am using and works).
> 
> This clarifies what I have to do...
> 
> Just did:
> 
> --8<---------------cut here---------------start------------->8---
> sudo aptitude install openjdk-6-jre
> --8<---------------cut here---------------end--------------->8---
> 
> And, now, it works!  Thanks a lot!

Excellent.  Glad we could help.

eric

configure latex fragments preview

[Nicolas Goaziou]

Hello,

This is some minor annoyance, but I would like to find a solution for it
anyway.

The preview image of a latex fragment produced by C-c C-x C-l is so
small that I sometimes find it hard to read.

In order to solve that situation, I modified org-format-latex-header so
that the template for the preview starts with
\documentclass[17pt]{extarticle}.

Though, I find it not quite satisfying as there is little control on
that size (I would like it to be a bit less than 17pt). Thus my question
(eventually) : is it possible to play with dvipng options like scale or
dpi directly, without modifying org.el ?

And if it doesn't exist, could a variable be introduced to fine-tune it ?

As a last note, I think there is a Latex only way to solve all of this,
but I wouldn't like to depends on too much latex packages or tricks.

Regards,

-- 
Nicolas Goaziou

Re: configure latex fragments preview

[Nick Dokos]

Nicolas Goaziou <n.goaziou@gmail.com> wrote:


> This is some minor annoyance, but I would like to find a solution for it
> anyway.
> 
> The preview image of a latex fragment produced by C-c C-x C-l is so
> small that I sometimes find it hard to read.
> 
> In order to solve that situation, I modified org-format-latex-header so
> that the template for the preview starts with
> \documentclass[17pt]{extarticle}.
> 
> Though, I find it not quite satisfying as there is little control on
> that size (I would like it to be a bit less than 17pt). Thus my question
> (eventually) : is it possible to play with dvipng options like scale or
> dpi directly, without modifying org.el ?
> 
> And if it doesn't exist, could a variable be introduced to fine-tune it ?
> 
> As a last note, I think there is a Latex only way to solve all of this,
> but I wouldn't like to depends on too much latex packages or tricks.
> 

The call to dvipng in org.el looks like this:

,----
|         ...
| 	  (call-process "dvipng" nil nil nil
| 			"-fg" fg "-bg" bg
| 			"-D" dpi
| 			;;"-x" scale "-y" scale
| 			"-T" "tight"
| 			"-o" pngfile
| 			dvifile)
|         ...
`----

Try modifying it to this:

,----
|           ...
| 	  (call-process "dvipng" nil nil nil
| 			"-fg" fg "-bg" bg
| 			"-D" dpi
| 			;;"-x" scale "-y" scale
|                         "-x" "2074"
| 			"-T" "tight"
| 			"-o" pngfile
| 			dvifile)
`----

The dvipng man page suggests values for the -x option:

,----
|        -x num
|            Set the x magnification ratio to num/1000. Overrides the magnification specified in the
|            DVI file.  Must be between 10 and 100000.  It is recommended that you use standard mag‐
|            step values (1095, 1200, 1440, 1728, 2074, 2488, 2986, and so on) to help reduce the
|            total number of PK files generated.  num may be a real number, not an integer, for
|            increased precision.
`----

Note the commented out -x/-y options in org.el: afaict, there is no -y
option, but perhaps Carsten can reintroduce the -x option, and then use
scale to set it properly (although the value of scale will need to be,
ahem, scaled).  If so, then you 'd be able to get what you want by
customizing org-format-latex-options:

,----
| org-format-latex-options is a variable defined in `org.el'.
| Its value is 
| (:foreground default :background default :scale 1.0 :html-foreground "Black" :html-background "Transparent" :html-scale 1.0 :matchers
|              ("begin" "$1" "$" "$$" "\\(" "\\["))
| 
| 
| Documentation:
| Options for creating images from LaTeX fragments.
| This is a property list with the following properties:
| :foreground  the foreground color for images embedded in Emacs, e.g. "Black".
|              `default' means use the foreground of the default face.
| :background  the background color, or "Transparent".
|              `default' means use the background of the default face.
| :scale       a scaling factor for the size of the images.
| :html-foreground, :html-background, :html-scale
|              the same numbers for HTML export.
| :matchers    a list indicating which matchers should be used to
|              find LaTeX fragments.  Valid members of this list are:
|              "begin"  find environments
|              "$1"     find single characters surrounded by $.$
|              "$"      find math expressions surrounded by $...$
|              "$$"     find math expressions surrounded by $$....$$
|              "\("     find math expressions surrounded by \(...\)
|              "\ ["    find math expressions surrounded by \ [...\]
| 
| You can customize this variable.
`----

HTH,
Nick

Re: configure latex fragments preview

[Nicolas Goaziou]

Nick Dokos <nicholas.dokos@hp.com> writes:

This variable is what I looked for. I still wonder how I overlooked it.

> ,----
> | org-format-latex-options is a variable defined in `org.el'.
> | Its value is 
> | (:foreground default :background default :scale 1.0 :html-foreground "Black" :html-background "Transparent" :html-scale 1.0 :matchers
> |              ("begin" "$1" "$" "$$" "\\(" "\\["))
> | 
> | 
> | Documentation:
> | Options for creating images from LaTeX fragments.
> | This is a property list with the following properties:
> | :foreground  the foreground color for images embedded in Emacs, e.g. "Black".
> |              `default' means use the foreground of the default face.
> | :background  the background color, or "Transparent".
> |              `default' means use the background of the default face.
> | :scale       a scaling factor for the size of the images.
> | :html-foreground, :html-background, :html-scale
> |              the same numbers for HTML export.
> | :matchers    a list indicating which matchers should be used to
> |              find LaTeX fragments.  Valid members of this list are:
> |              "begin"  find environments
> |              "$1"     find single characters surrounded by $.$
> |              "$"      find math expressions surrounded by $...$
> |              "$$"     find math expressions surrounded by $$....$$
> |              "\("     find math expressions surrounded by \(...\)
> |              "\ ["    find math expressions surrounded by \ [...\]
> | 
> | You can customize this variable.
> `----
>
> HTH,

It does, thank you.

-- 
Nicolas Goaziou

Re: configure latex fragments preview

[Carsten Dominik]

Hi Nick,

:scale is use to change the -D dpi setting, which also changes the  
image size.

- Carsten

On Sep 14, 2009, at 8:39 PM, Nick Dokos wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>
>> This is some minor annoyance, but I would like to find a solution  
>> for it
>> anyway.
>>
>> The preview image of a latex fragment produced by C-c C-x C-l is so
>> small that I sometimes find it hard to read.
>>
>> In order to solve that situation, I modified org-format-latex- 
>> header so
>> that the template for the preview starts with
>> \documentclass[17pt]{extarticle}.
>>
>> Though, I find it not quite satisfying as there is little control on
>> that size (I would like it to be a bit less than 17pt). Thus my  
>> question
>> (eventually) : is it possible to play with dvipng options like  
>> scale or
>> dpi directly, without modifying org.el ?
>>
>> And if it doesn't exist, could a variable be introduced to fine- 
>> tune it ?
>>
>> As a last note, I think there is a Latex only way to solve all of  
>> this,
>> but I wouldn't like to depends on too much latex packages or tricks.
>>
>
> The call to dvipng in org.el looks like this:
>
> ,----
> |         ...
> | 	  (call-process "dvipng" nil nil nil
> | 			"-fg" fg "-bg" bg
> | 			"-D" dpi
> | 			;;"-x" scale "-y" scale
> | 			"-T" "tight"
> | 			"-o" pngfile
> | 			dvifile)
> |         ...
> `----
>
> Try modifying it to this:
>
> ,----
> |           ...
> | 	  (call-process "dvipng" nil nil nil
> | 			"-fg" fg "-bg" bg
> | 			"-D" dpi
> | 			;;"-x" scale "-y" scale
> |                         "-x" "2074"
> | 			"-T" "tight"
> | 			"-o" pngfile
> | 			dvifile)
> `----
>
> The dvipng man page suggests values for the -x option:
>
> ,----
> |        -x num
> |            Set the x magnification ratio to num/1000. Overrides  
> the magnification specified in the
> |            DVI file.  Must be between 10 and 100000.  It is  
> recommended that you use standard mag‐
> |            step values (1095, 1200, 1440, 1728, 2074, 2488, 2986,  
> and so on) to help reduce the
> |            total number of PK files generated.  num may be a real  
> number, not an integer, for
> |            increased precision.
> `----
>
> Note the commented out -x/-y options in org.el: afaict, there is no -y
> option, but perhaps Carsten can reintroduce the -x option, and then  
> use
> scale to set it properly (although the value of scale will need to be,
> ahem, scaled).  If so, then you 'd be able to get what you want by
> customizing org-format-latex-options:
>
> ,----
> | org-format-latex-options is a variable defined in `org.el'.
> | Its value is
> | (:foreground default :background default :scale 1.0 :html- 
> foreground "Black" :html-background "Transparent" :html-scale  
> 1.0 :matchers
> |              ("begin" "$1" "$" "$$" "\\(" "\\["))
> |
> |
> | Documentation:
> | Options for creating images from LaTeX fragments.
> | This is a property list with the following properties:
> | :foreground  the foreground color for images embedded in Emacs,  
> e.g. "Black".
> |              `default' means use the foreground of the default face.
> | :background  the background color, or "Transparent".
> |              `default' means use the background of the default face.
> | :scale       a scaling factor for the size of the images.
> | :html-foreground, :html-background, :html-scale
> |              the same numbers for HTML export.
> | :matchers    a list indicating which matchers should be used to
> |              find LaTeX fragments.  Valid members of this list are:
> |              "begin"  find environments
> |              "$1"     find single characters surrounded by $.$
> |              "$"      find math expressions surrounded by $...$
> |              "$$"     find math expressions surrounded by $$....$$
> |              "\("     find math expressions surrounded by \(...\)
> |              "\ ["    find math expressions surrounded by \ [...\]
> |
> | You can customize this variable.
> `----
>
> HTH,
> Nick
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: configure latex fragments preview

[Carsten Dominik]

Hi Nick,

:scale is use to change the -D dpi setting, which also changes the  
image size.

- Carsten

On Sep 14, 2009, at 8:39 PM, Nick Dokos wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>
>> This is some minor annoyance, but I would like to find a solution  
>> for it
>> anyway.
>>
>> The preview image of a latex fragment produced by C-c C-x C-l is so
>> small that I sometimes find it hard to read.
>>
>> In order to solve that situation, I modified org-format-latex- 
>> header so
>> that the template for the preview starts with
>> \documentclass[17pt]{extarticle}.
>>
>> Though, I find it not quite satisfying as there is little control on
>> that size (I would like it to be a bit less than 17pt). Thus my  
>> question
>> (eventually) : is it possible to play with dvipng options like  
>> scale or
>> dpi directly, without modifying org.el ?
>>
>> And if it doesn't exist, could a variable be introduced to fine- 
>> tune it ?
>>
>> As a last note, I think there is a Latex only way to solve all of  
>> this,
>> but I wouldn't like to depends on too much latex packages or tricks.
>>
>
> The call to dvipng in org.el looks like this:
>
> ,----
> |         ...
> | 	  (call-process "dvipng" nil nil nil
> | 			"-fg" fg "-bg" bg
> | 			"-D" dpi
> | 			;;"-x" scale "-y" scale
> | 			"-T" "tight"
> | 			"-o" pngfile
> | 			dvifile)
> |         ...
> `----
>
> Try modifying it to this:
>
> ,----
> |           ...
> | 	  (call-process "dvipng" nil nil nil
> | 			"-fg" fg "-bg" bg
> | 			"-D" dpi
> | 			;;"-x" scale "-y" scale
> |                         "-x" "2074"
> | 			"-T" "tight"
> | 			"-o" pngfile
> | 			dvifile)
> `----
>
> The dvipng man page suggests values for the -x option:
>
> ,----
> |        -x num
> |            Set the x magnification ratio to num/1000. Overrides  
> the magnification specified in the
> |            DVI file.  Must be between 10 and 100000.  It is  
> recommended that you use standard mag‐
> |            step values (1095, 1200, 1440, 1728, 2074, 2488, 2986,  
> and so on) to help reduce the
> |            total number of PK files generated.  num may be a real  
> number, not an integer, for
> |            increased precision.
> `----
>
> Note the commented out -x/-y options in org.el: afaict, there is no -y
> option, but perhaps Carsten can reintroduce the -x option, and then  
> use
> scale to set it properly (although the value of scale will need to be,
> ahem, scaled).  If so, then you 'd be able to get what you want by
> customizing org-format-latex-options:
>
> ,----
> | org-format-latex-options is a variable defined in `org.el'.
> | Its value is
> | (:foreground default :background default :scale 1.0 :html- 
> foreground "Black" :html-background "Transparent" :html-scale  
> 1.0 :matchers
> |              ("begin" "$1" "$" "$$" "\\(" "\\["))
> |
> |
> | Documentation:
> | Options for creating images from LaTeX fragments.
> | This is a property list with the following properties:
> | :foreground  the foreground color for images embedded in Emacs,  
> e.g. "Black".
> |              `default' means use the foreground of the default face.
> | :background  the background color, or "Transparent".
> |              `default' means use the background of the default face.
> | :scale       a scaling factor for the size of the images.
> | :html-foreground, :html-background, :html-scale
> |              the same numbers for HTML export.
> | :matchers    a list indicating which matchers should be used to
> |              find LaTeX fragments.  Valid members of this list are:
> |              "begin"  find environments
> |              "$1"     find single characters surrounded by $.$
> |              "$"      find math expressions surrounded by $...$
> |              "$$"     find math expressions surrounded by $$....$$
> |              "\("     find math expressions surrounded by \(...\)
> |              "\ ["    find math expressions surrounded by \ [...\]
> |
> | You can customize this variable.
> `----
>
> HTH,
> Nick
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Francesco Pizzolante]

Hi,

Carsten Dominik wrote:
> On Jul 1, 2009, at 10:21 PM, Sébastien Vauban wrote:
>> Other things I've noticed:
>>
>> - Even with version 6.28, the `#+TBLNAME' tag must be located in column 0
>> (at
>>  least, for the highlighting features to work)
>
> Fixed, thanks.

I'm using orgmode 6.30c and I still have this problem: if the #+TBLNAME: tag
is not located in column 0, the remote reference does not work.

Here's my little test:

#+TBLNAME: A
    |   |     T |
    |---+-------|
    |   |  2.00 |
    |   |  5.00 |
    |---+-------|
    | # |  9.00 |
    | ^ | total |
    #+TBLFM: $2=vsum(@-I..@-II);%.2f

    #+TBLNAME: price
       |    T |    PU | Total |
       |------+-------+-------|
       | 9.00 | 10.25 | 92.25 |
       |------+-------+-------|
    #+TBLFM: @2$1=remote(A,$total);%.2f::@2$3=$1*$2;%.2f


Just add a few spaces at the first line and when you recompute the second
table you get a "Can't find remote table A" message.

Moreover, in a LaTeX environment, using the orgtbl minor mode, the
highlighting (font locking) does not work on the #+TBLNAME: line, even if
located in column 0.

Thanks.
F.


_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Carsten Dominik]

Hi Francesco,

indeed, it looks like I did make a mistake when recently trying to fix  
this.

I believe I have got it right this time (current git version), please  
verify.

- Carsten

On Sep 15, 2009, at 1:11 PM, Francesco Pizzolante wrote:

> Hi,
>
> Carsten Dominik wrote:
>> On Jul 1, 2009, at 10:21 PM, Sébastien Vauban wrote:
>>> Other things I've noticed:
>>>
>>> - Even with version 6.28, the `#+TBLNAME' tag must be located in  
>>> column 0
>>> (at
>>> least, for the highlighting features to work)
>>
>> Fixed, thanks.
>
> I'm using orgmode 6.30c and I still have this problem: if the # 
> +TBLNAME: tag
> is not located in column 0, the remote reference does not work.
>
> Here's my little test:
>
> #+TBLNAME: A
>    |   |     T |
>    |---+-------|
>    |   |  2.00 |
>    |   |  5.00 |
>    |---+-------|
>    | # |  9.00 |
>    | ^ | total |
>    #+TBLFM: $2=vsum(@-I..@-II);%.2f
>
>    #+TBLNAME: price
>       |    T |    PU | Total |
>       |------+-------+-------|
>       | 9.00 | 10.25 | 92.25 |
>       |------+-------+-------|
>    #+TBLFM: @2$1=remote(A,$total);%.2f::@2$3=$1*$2;%.2f
>
>
> Just add a few spaces at the first line and when you recompute the  
> second
> table you get a "Can't find remote table A" message.
>
> Moreover, in a LaTeX environment, using the orgtbl minor mode, the
> highlighting (font locking) does not work on the #+TBLNAME: line,  
> even if
> located in column 0.
>
> Thanks.
> F.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: LaTeX export bugs?

[Francesco Pizzolante]

Hi Carsten,

> indeed, it looks like I did make a mistake when recently trying to fix  
> this.
> 
> I believe I have got it right this time (current git version), please  
> verify.

It works perfectly now.

Thanks!

Francesco

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi Carsten,

Francesco Pizzolante wrote:
>
>> indeed, it looks like I did make a mistake when recently trying to fix
>> this.
>>
>> I believe I have got it right this time (current git version), please
>> verify.
>
> It works perfectly now.

Not exactly the same problem, but very similar IMHO, there is (now or still?)
a problem of highlighting with `#+BEGIN' meta info not starting in column 0.

Just test with the following:

--8<---------------cut here---------------start------------->8---
* 2009-09

#+BEGIN: clocktable :maxlevel 2 :scope file :block yesterday
Clock summary at [2009-09-16 Wed 17:27], for Tuesday, September 15, 2009.

| L | Headline     | Time   |      |
|---+--------------+--------+------|
|   | *Total time* | *7:25* |      |
|---+--------------+--------+------|
| 1 | 2009-09      | 7:25   |      |
| 2 | Some project |        | 7:25 |
#+END:
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: LaTeX export bugs?

[Carsten Dominik]

On Sep 17, 2009, at 3:52 PM, Sébastien Vauban wrote:

> Hi Carsten,
>
> Francesco Pizzolante wrote:
>>
>>> indeed, it looks like I did make a mistake when recently trying to  
>>> fix
>>> this.
>>>
>>> I believe I have got it right this time (current git version),  
>>> please
>>> verify.
>>
>> It works perfectly now.
>
> Not exactly the same problem, but very similar IMHO, there is (now  
> or still?)
> a problem of highlighting with `#+BEGIN' meta info not starting in  
> column 0.
>
> Just test with the following:
>
> --8<---------------cut here---------------start------------->8---
> * 2009-09
>
> #+BEGIN: clocktable :maxlevel 2 :scope file :block yesterday
> Clock summary at [2009-09-16 Wed 17:27], for Tuesday, September 15,  
> 2009.
>
> | L | Headline     | Time   |      |
> |---+--------------+--------+------|
> |   | *Total time* | *7:25* |      |
> |---+--------------+--------+------|
> | 1 | 2009-09      | 7:25   |      |
> | 2 | Some project |        | 7:25 |
> #+END:
> --8<---------------cut here---------------end--------------->8---

Hi Sebasien,

I am aware of this problem, but it is not so easy to solve.
The reason for this is that dynamic blocks are written by some
user function, which is not aware of any indentation to be applied.
So if I would allow indentation for the BEGIN line, I would end up
with

          #+BEGIN: clocktable
| L | Headline     | Time   |      |
|---+--------------+--------+------|
|   | *Total time* | *7:25* |      |
|---+--------------+--------+------|
| 1 | 2009-09      | 7:25   |      |
| 2 | Some project |        | 7:25 |
          #+END:

Is that the desired outcome?
I guess I could enforce indentation of the block written by
the user function, but I am not sure if this might cause
problems in some cases.

I need to think more about this.

- Carsten

Re: Re: LaTeX export bugs?

[Carsten Dominik]

On Sep 18, 2009, at 7:37 AM, Carsten Dominik wrote:

>
> On Sep 17, 2009, at 3:52 PM, Sébastien Vauban wrote:
>
>> Hi Carsten,
>>
>> Francesco Pizzolante wrote:
>>>
>>>> indeed, it looks like I did make a mistake when recently trying  
>>>> to fix
>>>> this.
>>>>
>>>> I believe I have got it right this time (current git version),  
>>>> please
>>>> verify.
>>>
>>> It works perfectly now.
>>
>> Not exactly the same problem, but very similar IMHO, there is (now  
>> or still?)
>> a problem of highlighting with `#+BEGIN' meta info not starting in  
>> column 0.
>>
>> Just test with the following:
>>
>> --8<---------------cut here---------------start------------->8---
>> * 2009-09
>>
>> #+BEGIN: clocktable :maxlevel 2 :scope file :block yesterday
>> Clock summary at [2009-09-16 Wed 17:27], for Tuesday, September 15,  
>> 2009.
>>
>> | L | Headline     | Time   |      |
>> |---+--------------+--------+------|
>> |   | *Total time* | *7:25* |      |
>> |---+--------------+--------+------|
>> | 1 | 2009-09      | 7:25   |      |
>> | 2 | Some project |        | 7:25 |
>> #+END:
>> --8<---------------cut here---------------end--------------->8---
>
> Hi Sebasien,
>
> I am aware of this problem, but it is not so easy to solve.
> The reason for this is that dynamic blocks are written by some
> user function, which is not aware of any indentation to be applied.
> So if I would allow indentation for the BEGIN line, I would end up
> with
>
>         #+BEGIN: clocktable
> | L | Headline     | Time   |      |
> |---+--------------+--------+------|
> |   | *Total time* | *7:25* |      |
> |---+--------------+--------+------|
> | 1 | 2009-09      | 7:25   |      |
> | 2 | Some project |        | 7:25 |
>         #+END:
>
> Is that the desired outcome?
> I guess I could enforce indentation of the block written by
> the user function, but I am not sure if this might cause
> problems in some cases.
>
> I need to think more about this.


I just *did* think more about it.  Indented dynamic blocks are now  
possible.

- Carsten

Re: LaTeX export bugs?

[Sébastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On Sep 18, 2009, at 7:37 AM, Carsten Dominik wrote:
>>
>> I am aware of this problem, but it is not so easy to solve. The reason for
>> this is that dynamic blocks are written by some user function, which is not
>> aware of any indentation to be applied. So if I would allow indentation for
>> the BEGIN line, I would end up with
>>
>>         #+BEGIN: clocktable
>> | L | Headline     | Time   |      |
>> |---+--------------+--------+------|
>> |   | *Total time* | *7:25* |      |
>> |---+--------------+--------+------|
>> | 1 | 2009-09      | 7:25   |      |
>> | 2 | Some project |        | 7:25 |
>>         #+END:
>>
>> Is that the desired outcome?

Certainly not.


>> I guess I could enforce indentation of the block written by the user
>> function, but I am not sure if this might cause problems in some cases.
>>
>> I need to think more about this.
>
> I just *did* think more about it. Indented dynamic blocks are now possible.

Great!  Otherwise, leave it as it is...

Best regards,
  Seb

-- 
Sébastien Vauban



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Changing paragraph setting in Latex export

[Paul Mead]

Hi

I'm trying to export an org-mode file to Latex but I've got a couple of
niggles with the output.

Firstly, there are no spaces between paragraph breaks, so my text looks
horribly bunched up (I'm converting to RTF using latex2rtf, btw)

Secondly, the paragraphs all come out fully justified - this looks
pretty terrible on a fairly wide page (A4 with 1" margins in my case),
and I can't seem to find a way of changing this layout from the org
file.

Can anyone help with this please?

Thanks
Paul

Re: Changing paragraph setting in Latex export

[Nick Dokos]

Paul Mead <paul.d.mead@gmail.com> wrote:


> I'm trying to export an org-mode file to Latex but I've got a couple of
> niggles with the output.
> 
> Firstly, there are no spaces between paragraph breaks, so my text looks
> horribly bunched up (I'm converting to RTF using latex2rtf, btw)
> 
> Secondly, the paragraphs all come out fully justified - this looks
> pretty terrible on a fairly wide page (A4 with 1" margins in my case),
> and I can't seem to find a way of changing this layout from the org
> file.
> 

Try adding

#+LaTeX: \setlength\parskip{5mm}
#+LaTeX: \raggedright

(season to taste).

HTH,
Nick

Re: Changing paragraph setting in Latex export

[Eric S Fraga]

At Thu, 04 Feb 2010 17:09:27 +0000,
Paul Mead wrote:
> 
> Hi
> 
> I'm trying to export an org-mode file to Latex but I've got a couple of
> niggles with the output.
> 
> Firstly, there are no spaces between paragraph breaks, so my text looks
> horribly bunched up (I'm converting to RTF using latex2rtf, btw)
> 
> Secondly, the paragraphs all come out fully justified - this looks
> pretty terrible on a fairly wide page (A4 with 1" margins in my case),
> and I can't seem to find a way of changing this layout from the org
> file.
> 
> Can anyone help with this please?

These are more latex questions than org-mode.  On that note, I also
recommend the visual FAQ for latex users:

http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf

Links are clickable leading to web pages that describe the particular
elements that accomplish whatever task you wish.

page 10 has an example of "raggedright" or "flushleft" text.

for paragraph spacing, you want to modify latex variables \parindent
and \parskip; whether these get transferred through latex2rtf, I have
no idea.  Sorry.

HTH,
eric

Re: Changing paragraph setting in Latex export

[Paul Mead]

Eric S Fraga <ucecesf@ucl.ac.uk> writes:

>
> These are more latex questions than org-mode.  On that note, I also
> recommend the visual FAQ for latex users:
>
> http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf

Thanks, although I'm going to have to find a pdf viewer that can deal
with the popups - evince doesn't seem to want to know.

> page 10 has an example of "raggedright" or "flushleft" text.
>
> for paragraph spacing, you want to modify latex variables \parindent
> and \parskip; whether these get transferred through latex2rtf, I have
> no idea.  Sorry.

Doesn't look like they do, unfortunately. Looks fine in PDF but my tutor
insists on marking using Word...

I'll see if there's anything in the latex2rtf documentation which might
help.

Thanks guys.

Re: Changing paragraph setting in Latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> 
> These are more latex questions than org-mode.  On that note, I also
> recommend the visual FAQ for latex users:
> 
> http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf
> 
> Links are clickable leading to web pages that describe the particular
> elements that accomplish whatever task you wish.
> 
> page 10 has an example of "raggedright" or "flushleft" text.
> 
> 

All I can say is: Wow! It's a keeper.

Thanks for posting this.

Nick

Re: Changing paragraph setting in Latex export

[Eric S Fraga]

At Thu, 04 Feb 2010 18:03:03 +0000,
Paul Mead wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> 
> >
> > These are more latex questions than org-mode.  On that note, I also
> > recommend the visual FAQ for latex users:
> >
> > http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf
> 
> Thanks, although I'm going to have to find a pdf viewer that can deal
> with the popups - evince doesn't seem to want to know.

xpdf works well with links, at least on my system.  i've never tried
evince however.

Re: Changing paragraph setting in Latex export

[Eric S Fraga]

At Thu, 04 Feb 2010 13:24:55 -0500,
Nick Dokos wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > 
> > These are more latex questions than org-mode.  On that note, I also
> > recommend the visual FAQ for latex users:
> > 
> > http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf
> > 
> > Links are clickable leading to web pages that describe the particular
> > elements that accomplish whatever task you wish.
> > 
> > page 10 has an example of "raggedright" or "flushleft" text.
> > 
> > 
> 
> All I can say is: Wow! It's a keeper.
> 
> Thanks for posting this.
> 
> Nick

You're very welcome.  It's a fantastic document!  It's saved me hours
of googling or reading my latex books.

[babel] confusion about org-confirm-babel-evaluate

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

Hello all,

Back from a short holiday and trying to catch up on work... and so I
may have missed something in the org mailing list (although I've
searched...).

I have a large file which includes many babel code blocks (mostly
maxima) that I wish to have evaluated on export.  This works except
that I have to confirm each evaluation (which takes some time).  I
know that org-confirm-babel-evaluate exists so I have put the
following at the top of my org file:

# -*- org-confirm-babel-evaluate: nil; -*-

checking the value of this variable (C-h v org-babel-confirm-evaluate)
gives me:

,----
| org-confirm-babel-evaluate is a variable defined in `ob.el'.
| Its value is nil
| Local in buffer deferred-questions.org; global value is t
| 
|   This variable is a file local variable.
|   This variable is safe as a file local variable if its value
|   satisfies the predicate which is byte-compiled expression.
| 
| Documentation:
| Confirm before evaluation.
| Require confirmation before interactively evaluating code
| blocks in Org-mode buffers.  The default value of this variable
| is t, meaning confirmation is required for any code block
| evaluation.  This variable can be set to nil to inhibit any
| future confirmation requests.  This variable can also be set to a
| [...]
`----

so the value is indeed nil.  However, exporting to PDF, say, still
requires me to confirm each evaluation.  Typing C-c C-c doesn't
require confirmation, however, so the variable does seem to have some
effect.

What am I missing here to avoid having to confirm on export?  The only
variable I have found that combines both export and babel is
org-export-babel-evaluate which is not what I want.

Thanks,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] confusion about org-confirm-babel-evaluate

[Erik Iverson]

Can you try setting it via setq (i.e., globally) and see what happens?

On 08/12/2010 07:53 AM, Eric S Fraga wrote:
> Hello all,
>
> Back from a short holiday and trying to catch up on work... and so I
> may have missed something in the org mailing list (although I've
> searched...).
>
> I have a large file which includes many babel code blocks (mostly
> maxima) that I wish to have evaluated on export.  This works except
> that I have to confirm each evaluation (which takes some time).  I
> know that org-confirm-babel-evaluate exists so I have put the
> following at the top of my org file:
>
> # -*- org-confirm-babel-evaluate: nil; -*-
>
> checking the value of this variable (C-h v org-babel-confirm-evaluate)
> gives me:
>
> ,----
> | org-confirm-babel-evaluate is a variable defined in `ob.el'.
> | Its value is nil
> | Local in buffer deferred-questions.org; global value is t
> |
> |   This variable is a file local variable.
> |   This variable is safe as a file local variable if its value
> |   satisfies the predicate which is byte-compiled expression.
> |
> | Documentation:
> | Confirm before evaluation.
> | Require confirmation before interactively evaluating code
> | blocks in Org-mode buffers.  The default value of this variable
> | is t, meaning confirmation is required for any code block
> | evaluation.  This variable can be set to nil to inhibit any
> | future confirmation requests.  This variable can also be set to a
> | [...]
> `----
>
> so the value is indeed nil.  However, exporting to PDF, say, still
> requires me to confirm each evaluation.  Typing C-c C-c doesn't
> require confirmation, however, so the variable does seem to have some
> effect.
>
> What am I missing here to avoid having to confirm on export?  The only
> variable I have found that combines both export and babel is
> org-export-babel-evaluate which is not what I want.
>
> Thanks,
> 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

Re: [babel] confusion about org-confirm-babel-evaluate

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

On Thu, 12 Aug 2010 08:44:42 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
> 
> Can you try setting it via setq (i.e., globally) and see what happens?
> 
> On 08/12/2010 07:53 AM, Eric S Fraga wrote:
> > Hello all,
> >
> > Back from a short holiday and trying to catch up on work... and so I
> > may have missed something in the org mailing list (although I've
> > searched...).
> >
> > I have a large file which includes many babel code blocks (mostly
> > maxima) that I wish to have evaluated on export.  This works except
> > that I have to confirm each evaluation (which takes some time).  I
> > know that org-confirm-babel-evaluate exists so I have put the
> > following at the top of my org file:
> >
> > # -*- org-confirm-babel-evaluate: nil; -*-

[...]

Erik,

setting it globally (well, through customize as with setq didn't
actually change the global value) works just fine so there must be
some problem with the local value being ignored (I don't know enough
about emacs variables to understand the distinction, at the level of
lisp programming, between global and buffer local variables)?

Of course, I'm not comfortable with the global setting for all the
reasons already discussed on this list!

Thanks for this, in any case, as it makes life a little less painful
for today while I work on this long document!

eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] confusion about org-confirm-babel-evaluate

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> Hello all,
> 
> Back from a short holiday and trying to catch up on work... and so I
> may have missed something in the org mailing list (although I've
> searched...).
> 
> I have a large file which includes many babel code blocks (mostly
> maxima) that I wish to have evaluated on export.  This works except
> that I have to confirm each evaluation (which takes some time).  I
> know that org-confirm-babel-evaluate exists so I have put the
> following at the top of my org file:
> 
> # -*- org-confirm-babel-evaluate: nil; -*-
> 
> checking the value of this variable (C-h v org-babel-confirm-evaluate)
> gives me:
> 
> ,----
> | org-confirm-babel-evaluate is a variable defined in `ob.el'.
> | Its value is nil
> | Local in buffer deferred-questions.org; global value is t
> | 
> |   This variable is a file local variable.
> |   This variable is safe as a file local variable if its value
> |   satisfies the predicate which is byte-compiled expression.
> | 
> | Documentation:
> | Confirm before evaluation.
> | Require confirmation before interactively evaluating code
> | blocks in Org-mode buffers.  The default value of this variable
> | is t, meaning confirmation is required for any code block
> | evaluation.  This variable can be set to nil to inhibit any
> | future confirmation requests.  This variable can also be set to a
> | [...]
> `----
> 
> so the value is indeed nil.  However, exporting to PDF, say, still
> requires me to confirm each evaluation.  Typing C-c C-c doesn't
> require confirmation, however, so the variable does seem to have some
> effect.
> 
> What am I missing here to avoid having to confirm on export?  The only
> variable I have found that combines both export and babel is
> org-export-babel-evaluate which is not what I want.
> 

Seems to me that the variable is not effective at all at this point in time:
it still has to be connected up and wired in. Here's what I see:

Org-mode version 7.01trans (release_7.01h.112.g13a0)
GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2010-05-17 on gamaville.dokosmarshall.org

org-babel-execute-src-block calls org-babel-confirm-evaluate in the
following context:

        (let (...
	 (evaluation-confirmed (org-babel-confirm-evaluate info))
         ...)
         ...

but evaluation-confirmed is not used anywhere. In fact, there is a comment
on the line above:

	 ;; note the `evaluation-confirmed' variable is currently not
	 ;; used, but could be used later to avoid the need for
	 ;; chaining confirmations
	 (evaluation-confirmed (org-babel-confirm-evaluate info))

but that's the *only* place where org-babel-confirm-evaluate is called,
so I don't think the function (or the variable that Eric is trying to
set) has any effect at all. I haven't chased things through to the C-c C-c
stage that Eric mentions, so I'm not sure what causes that.

Am I missing something?

Thanks,
Nick

Re: [babel] confusion about org-confirm-babel-evaluate

[Erik Iverson]

Eric S Fraga wrote:
> On Thu, 12 Aug 2010 08:44:42 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
>> Can you try setting it via setq (i.e., globally) and see what happens?
>>
>> On 08/12/2010 07:53 AM, Eric S Fraga wrote:
>>> Hello all,
>>>
>>> Back from a short holiday and trying to catch up on work... and so I
>>> may have missed something in the org mailing list (although I've
>>> searched...).
>>>
>>> I have a large file which includes many babel code blocks (mostly
>>> maxima) that I wish to have evaluated on export.  This works except
>>> that I have to confirm each evaluation (which takes some time).  I
>>> know that org-confirm-babel-evaluate exists so I have put the
>>> following at the top of my org file:
>>>
>>> # -*- org-confirm-babel-evaluate: nil; -*-
> 
> [...]
> 
> Erik,
> 
> setting it globally (well, through customize as with setq didn't
> actually change the global value) works just fine so there must be
> some problem with the local value being ignored (I don't know enough
> about emacs variables to understand the distinction, at the level of
> lisp programming, between global and buffer local variables)?
> 
> Of course, I'm not comfortable with the global setting for all the
> reasons already discussed on this list!

If you look at the definition of org-confirm-babel-evaluate, you'll see:

;; don't allow this variable to be changed through file settings
(put 'org-confirm-babel-evaluate 'safe-local-variable (lambda (x) (eq x t)))

I'll guess as to why this is.  You might not want to have a malicious 
file essentially being able to override the very feature meant to 
protect the user. I could be off base with that.  I'm guessing there is 
a solution to your problem, I just don't know it.

Re: [babel] confusion about org-confirm-babel-evaluate

[Erik Iverson]

Nick Dokos wrote:
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
>> Hello all,
>>
>> Back from a short holiday and trying to catch up on work... and so I
>> may have missed something in the org mailing list (although I've
>> searched...).
>>
>> I have a large file which includes many babel code blocks (mostly
>> maxima) that I wish to have evaluated on export.  This works except
>> that I have to confirm each evaluation (which takes some time).  I
>> know that org-confirm-babel-evaluate exists so I have put the
>> following at the top of my org file:
>>
>> # -*- org-confirm-babel-evaluate: nil; -*-
>>
>> checking the value of this variable (C-h v org-babel-confirm-evaluate)
>> gives me:
>>
>> ,----
>> | org-confirm-babel-evaluate is a variable defined in `ob.el'.
>> | Its value is nil
>> | Local in buffer deferred-questions.org; global value is t
>> | 
>> |   This variable is a file local variable.
>> |   This variable is safe as a file local variable if its value
>> |   satisfies the predicate which is byte-compiled expression.
>> | 
>> | Documentation:
>> | Confirm before evaluation.
>> | Require confirmation before interactively evaluating code
>> | blocks in Org-mode buffers.  The default value of this variable
>> | is t, meaning confirmation is required for any code block
>> | evaluation.  This variable can be set to nil to inhibit any
>> | future confirmation requests.  This variable can also be set to a
>> | [...]
>> `----
>>
>> so the value is indeed nil.  However, exporting to PDF, say, still
>> requires me to confirm each evaluation.  Typing C-c C-c doesn't
>> require confirmation, however, so the variable does seem to have some
>> effect.
>>
>> What am I missing here to avoid having to confirm on export?  The only
>> variable I have found that combines both export and babel is
>> org-export-babel-evaluate which is not what I want.
>>
> 
> Seems to me that the variable is not effective at all at this point in time:
> it still has to be connected up and wired in. Here's what I see:
> 
> Org-mode version 7.01trans (release_7.01h.112.g13a0)
> GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2010-05-17 on gamaville.dokosmarshall.org
> 
> org-babel-execute-src-block calls org-babel-confirm-evaluate in the
> following context:
> 
>         (let (...
> 	 (evaluation-confirmed (org-babel-confirm-evaluate info))
>          ...)
>          ...
> 
> but evaluation-confirmed is not used anywhere. In fact, there is a comment
> on the line above:
> 
> 	 ;; note the `evaluation-confirmed' variable is currently not
> 	 ;; used, but could be used later to avoid the need for
> 	 ;; chaining confirmations
> 	 (evaluation-confirmed (org-babel-confirm-evaluate info))
> 
> but that's the *only* place where org-babel-confirm-evaluate is called,
> so I don't think the function (or the variable that Eric is trying to
> set) has any effect at all. I haven't chased things through to the C-c C-c
> stage that Eric mentions, so I'm not sure what causes that.
> 
> Am I missing something?

org-babel-confirm-evaluate is a function.
org-confirm-babel-evaluate is a variable.


evaluation-confirmed is the result of evaluating the
org-babel-confirm-evaluate function.  So even though the
/result/ of that function isn't used yet, the function is still
called.  That function uses the value of org-confirm-babel-evaluate
to decide to prompt the user or not. So, as of now,
setting org-confirm-babel-evaluate to t or nil definitely has an
effect.

Re: [babel] confusion about org-confirm-babel-evaluate

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]

On Thu, 12 Aug 2010 09:59:02 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
> 
> 
> 
> Eric S Fraga wrote:
> > On Thu, 12 Aug 2010 08:44:42 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
> >> Can you try setting it via setq (i.e., globally) and see what happens?
> >>
> >> On 08/12/2010 07:53 AM, Eric S Fraga wrote:
> >>> Hello all,
> >>>
> >>> Back from a short holiday and trying to catch up on work... and so I
> >>> may have missed something in the org mailing list (although I've
> >>> searched...).
> >>>
> >>> I have a large file which includes many babel code blocks (mostly
> >>> maxima) that I wish to have evaluated on export.  This works except
> >>> that I have to confirm each evaluation (which takes some time).  I
> >>> know that org-confirm-babel-evaluate exists so I have put the
> >>> following at the top of my org file:
> >>>
> >>> # -*- org-confirm-babel-evaluate: nil; -*-
> >
> > [...]
> >
> > Erik,
> >
> > setting it globally (well, through customize as with setq didn't
> > actually change the global value) works just fine so there must be
> > some problem with the local value being ignored (I don't know enough
> > about emacs variables to understand the distinction, at the level of
> > lisp programming, between global and buffer local variables)?
> >
> > Of course, I'm not comfortable with the global setting for all the
> > reasons already discussed on this list!
> 
> If you look at the definition of org-confirm-babel-evaluate, you'll see:
> 
> ;; don't allow this variable to be changed through file settings
> (put 'org-confirm-babel-evaluate 'safe-local-variable (lambda (x) (eq x t)))
> 
> I'll guess as to why this is.  You might not want to have a malicious
> file essentially being able to override the very feature meant to
> protect the user. I could be off base with that.  I'm guessing there
> is a solution to your problem, I just don't know it.
> 

Ahhh...

I can see the reasoning behind this but I guess the question becomes
one of whether there is any way to turn this off for a file I am
working on without having to turn it off globally?  If not, I could
turn it off globally for a while... not a big deal, I guess.

Thanks!

eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] confusion about org-confirm-babel-evaluate

[Erik Iverson]

Eric S Fraga wrote:
> On Thu, 12 Aug 2010 09:59:02 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
>>
>>
>> Eric S Fraga wrote:
>>> On Thu, 12 Aug 2010 08:44:42 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:
>>>> Can you try setting it via setq (i.e., globally) and see what happens?
>>>>
>>>> On 08/12/2010 07:53 AM, Eric S Fraga wrote:
>>>>> Hello all,
>>>>>
>>>>> Back from a short holiday and trying to catch up on work... and so I
>>>>> may have missed something in the org mailing list (although I've
>>>>> searched...).
>>>>>
>>>>> I have a large file which includes many babel code blocks (mostly
>>>>> maxima) that I wish to have evaluated on export.  This works except
>>>>> that I have to confirm each evaluation (which takes some time).  I
>>>>> know that org-confirm-babel-evaluate exists so I have put the
>>>>> following at the top of my org file:
>>>>>
>>>>> # -*- org-confirm-babel-evaluate: nil; -*-
>>> [...]
>>>
>>> Erik,
>>>
>>> setting it globally (well, through customize as with setq didn't
>>> actually change the global value) works just fine so there must be
>>> some problem with the local value being ignored (I don't know enough
>>> about emacs variables to understand the distinction, at the level of
>>> lisp programming, between global and buffer local variables)?
>>>
>>> Of course, I'm not comfortable with the global setting for all the
>>> reasons already discussed on this list!
>> If you look at the definition of org-confirm-babel-evaluate, you'll see:
>>
>> ;; don't allow this variable to be changed through file settings
>> (put 'org-confirm-babel-evaluate 'safe-local-variable (lambda (x) (eq x t)))
>>
>> I'll guess as to why this is.  You might not want to have a malicious
>> file essentially being able to override the very feature meant to
>> protect the user. I could be off base with that.  I'm guessing there
>> is a solution to your problem, I just don't know it.
>>
> 
> Ahhh...
> 
> I can see the reasoning behind this but I guess the question becomes
> one of whether there is any way to turn this off for a file I am
> working on without having to turn it off globally?  If not, I could
> turn it off globally for a while... not a big deal, I guess.
> 
> Thanks!

Also, not that it solves your issue at all, but I have

(setq org-confirm-babel-evaluate nil)

in my .emacs, and it sets it globally just fine...

Re: [babel] confusion about org-confirm-babel-evaluate

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 407 bytes --]

On Thu, 12 Aug 2010 10:12:56 -0500, Erik Iverson <eriki@ccbr.umn.edu> wrote:

[...]

> Also, not that it solves your issue at all, but I have
> 
> (setq org-confirm-babel-evaluate nil)
> 
> in my .emacs, and it sets it globally just fine...

Okay.  Strange that setting it after loading everything doesn't work.
May have been an error on my part.

In any case, thanks for all your help on this issue!

eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] confusion about org-confirm-babel-evaluate

[Nick Dokos]

Erik Iverson <eriki@ccbr.umn.edu> wrote:

> >
> > Am I missing something?
> 
> org-babel-confirm-evaluate is a function.
> org-confirm-babel-evaluate is a variable.
> 

I got that much, but I was expecting the return value of the function to
make a difference...
> 
> evaluation-confirmed is the result of evaluating the
> org-babel-confirm-evaluate function.  So even though the
> /result/ of that function isn't used yet, the function is still
> called.  That function uses the value of org-confirm-babel-evaluate
> to decide to prompt the user or not. So, as of now,
> setting org-confirm-babel-evaluate to t or nil definitely has an
> effect.

... but of course in this case, the function never returns in the
no-confirm case.

Thanks for setting me straight!
Nick

Bibtex and latex export

[Rafael Calsaverini]

[-- Attachment #1.1: Type: text/plain, Size: 1178 bytes --]

Hi there,

I'm trying to use org-mode to compose latex documents and I'm having a
problem with bibtex. When I export to pdf with C-c C-e p, pdflatex runs and
everything works gracefully with respect to the latex code (the output is
even prettier than I used to have patience to do only with latex), but
bibtex isn't called.

I tried to fiddle with org-exp-bibtex, which is nice, but apparently it
don't call bibtex either.

I tried to edit the function that calls pdflatex to include a call to
bibtex, but to be honest I know zero about lisp, so I couldn't even edit a
simple list of commands. :P (I must be the only emacs user in the world that
can't write or read lisp... it would be swell if I could use haskell to
extend emacs instead of lisp :P).

How should I go about automatically including a call to bibtex whenever I
want to export my org document as a pdf?

Thanks for your time, and sorry to bore you with simple questions...
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo

rafael.calsaverini@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803

[-- Attachment #1.2: Type: text/html, Size: 1465 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Bibtex and latex export

[Rafael Calsaverini]

[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]

Hi there,

I'm trying to use org-mode to compose latex documents and I'm having a
problem with bibtex. When I export to pdf with C-c C-e p, pdflatex runs and
everything works gracefully with respect to the latex code (the output is
even prettier than I used to have patience to do only with latex), but
bibtex isn't called.

I've  tried to fiddle with org-exp-bibtex, which is nice, but apparently it
don't call bibtex either.

I've tried to edit the function that calls pdflatex to include a call to
bibtex, but to be honest I know zero about lisp, so I couldn't even edit a
simple list of commands. :P (I must be the only emacs user in the world that
can't write or read lisp... it would be swell if I could use haskell to
extend emacs instead of lisp :P).

How should I go about automatically including a call to bibtex whenever I
want to export my org document as a pdf?

Thanks for your time, and sorry to bore you with simple questions...
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo

rafael.calsaverini@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803

[-- Attachment #1.2: Type: text/html, Size: 1557 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bibtex and latex export

[Erik Iverson]

Rafael,

I asked the same question last week :).

http://www.mail-archive.com/emacs-orgmode@gnu.org/msg30073.html


I've just now looked into the org-latex.el file, and found:

(defcustom org-latex-to-pdf-process
   '("pdflatex -interaction nonstopmode -output-directory %o %f"
     "pdflatex -interaction nonstopmode -output-directory %o %f")
   "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.

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"))
		 (function)))


Looks like you can just customize that variable, easy!

--Erik


Rafael Calsaverini wrote:
> Hi there, 
> 
> I'm trying to use org-mode to compose latex documents and I'm having a 
> problem with bibtex. When I export to pdf with C-c C-e p, pdflatex runs 
> and everything works gracefully with respect to the latex code (the 
> output is even prettier than I used to have patience to do only with 
> latex), but bibtex isn't called. 
> 
> I've  tried to fiddle with org-exp-bibtex, which is nice, but apparently 
> it don't call bibtex either. 
> 
> I've tried to edit the function that calls pdflatex to include a call to 
> bibtex, but to be honest I know zero about lisp, so I couldn't even edit 
> a simple list of commands. :P (I must be the only emacs user in the 
> world that can't write or read lisp... it would be swell if I could use 
> haskell to extend emacs instead of lisp :P). 
> 
> How should I go about automatically including a call to bibtex whenever 
> I want to export my org document as a pdf?
> 
> Thanks for your time, and sorry to bore you with simple questions...
> ---
> Rafael Calsaverini
> Dep. de Física Geral, Sala 336
> Instituto de Física - Universidade de São Paulo
> 
> rafael.calsaverini@gmail.com <mailto:rafael.calsaverini@gmail.com>
> http://stoa.usp.br/calsaverini/weblog
> CEL: (11) 7525-6222
> USP: (11) 3091-6803
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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: Bibtex and latex export

[Sébastien Vauban]

Hi Rafael and Erik,

Erik Iverson wrote:
> Rafael Calsaverini wrote:
>> Hi there,
>>
>> I'm trying to use org-mode to compose latex documents and I'm having a
>> problem with bibtex. When I export to pdf with C-c C-e p, pdflatex runs and
>> everything works gracefully with respect to the latex code (the output is
>> even prettier than I used to have patience to do only with latex), but
>> bibtex isn't called.
>
> I've just now looked into the org-latex.el file, and found:
>
> (defcustom org-latex-to-pdf-process
>   '("pdflatex -interaction nonstopmode -output-directory %o %f"
>     "pdflatex -interaction nonstopmode -output-directory %o %f")
>   "Commands to process a LaTeX file to a PDF file.
> [...]
> Looks like you can just customize that variable, easy!

FYI, this should be fixed now.

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]

On Wed, 06 Oct 2010 13:30:30 +0200, Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Rafael and Erik,
> 
> Erik Iverson wrote:
> > Rafael Calsaverini wrote:
> >> Hi there,
> >>
> >> I'm trying to use org-mode to compose latex documents and I'm having a
> >> problem with bibtex. When I export to pdf with C-c C-e p, pdflatex runs and
> >> everything works gracefully with respect to the latex code (the output is
> >> even prettier than I used to have patience to do only with latex), but
> >> bibtex isn't called.
> >
> > I've just now looked into the org-latex.el file, and found:
> >
> > (defcustom org-latex-to-pdf-process
> >   '("pdflatex -interaction nonstopmode -output-directory %o %f"
> >     "pdflatex -interaction nonstopmode -output-directory %o %f")
> >   "Commands to process a LaTeX file to a PDF file.
> > [...]
> > Looks like you can just customize that variable, easy!
> 
> FYI, this should be fixed now.
> 
> 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

Hello,

between yesterday and today, something changed that no longer allows
me to create PDFs from my org files, causing momentary panic as I
making the final changes to a lecture I had to give this morning --
luckily, latex export worked just fine.  

Reading between the lines, I gather it is the change to
org-latex-to-pdf-process that has caused me problems.  The output I
get when the export takes place is:

,----
| /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
| egrep: Invalid range end
| /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
`----

The current value of that variable is:

,----
| org-latex-to-pdf-process is a variable defined in `org-latex.el'.
| Its value is 
| ("texi2dvi -p -b -c -V %f")
`----

I can obviously change back to the setting that was the default before
but I do like the idea of using texi2dvi.  Can anybody suggest what
may be wrong on my system or my configuration?

Thanks,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

I should have added:

,----
| org-version: release_7.01h-638-gd9e44
| Org-mode version 7.01trans (release_7.01h.638.gd9e44)
| 
| GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of
| 2010-08-14 on raven, modified by Debian
`----

Thanks again,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Carsten Dominik]

On Oct 6, 2010, at 5:02 PM, Eric S Fraga wrote:

> On Wed, 06 Oct 2010 13:30:30 +0200, Sébastien Vauban <wxhgmqzgwmuf@spammotel.com 
> > wrote:
>>
>> Hi Rafael and Erik,
>>
>> Erik Iverson wrote:
>>> Rafael Calsaverini wrote:
>>>> Hi there,
>>>>
>>>> I'm trying to use org-mode to compose latex documents and I'm  
>>>> having a
>>>> problem with bibtex. When I export to pdf with C-c C-e p,  
>>>> pdflatex runs and
>>>> everything works gracefully with respect to the latex code (the  
>>>> output is
>>>> even prettier than I used to have patience to do only with  
>>>> latex), but
>>>> bibtex isn't called.
>>>
>>> I've just now looked into the org-latex.el file, and found:
>>>
>>> (defcustom org-latex-to-pdf-process
>>>  '("pdflatex -interaction nonstopmode -output-directory %o %f"
>>>    "pdflatex -interaction nonstopmode -output-directory %o %f")
>>>  "Commands to process a LaTeX file to a PDF file.
>>> [...]
>>> Looks like you can just customize that variable, easy!
>>
>> FYI, this should be fixed now.
>>
>> 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
>
> Hello,
>
> between yesterday and today, something changed that no longer allows
> me to create PDFs from my org files, causing momentary panic as I
> making the final changes to a lecture I had to give this morning --
> luckily, latex export worked just fine.
>
> Reading between the lines, I gather it is the change to
> org-latex-to-pdf-process that has caused me problems.  The output I
> get when the export takes place is:
>
> ,----
> | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> | egrep: Invalid range end
> | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex,  
> skipping.
> `----
>

That is bad - I have no idea here.  Maybe a non-standard
version of egrep?  But I am really guessing here.

Lets see if this affects more people - for the time being you might  
just change the variable to have it make 2-3 pdflatex runs.

- Carsten

> The current value of that variable is:
>
> ,----
> | org-latex-to-pdf-process is a variable defined in `org-latex.el'.
> | Its value is
> | ("texi2dvi -p -b -c -V %f")
> `----
>
> I can obviously change back to the setting that was the default before
> but I do like the idea of using texi2dvi.  Can anybody suggest what
> may be wrong on my system or my configuration?
>
> Thanks,
> eric
> -- 
> Eric S Fraga
> GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D
> _______________________________________________
> 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: Bibtex and latex export

[Achim Gratz]

Hi Eric,

Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> | egrep: Invalid range end
> | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.

Something somewhere tries to make a local path from an absolute one by
prepending "./", which fails (predictably).  Is the input readable at
the original path?  Not sure the error message from egrep has to do with
it or not, but it must be in any case one of the processes started by
texi2dvi (does not show up on my system, I only have calls to grep when
I trace it, but one of the sub-processes might still use it).  I think
texi2dvi also invokes shell scripts, so any funny configuration in the
environment, especially where path points to, could throw it off.


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

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Wed, 6 Oct 2010 18:40:12 +0200, Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On Oct 6, 2010, at 5:02 PM, Eric S Fraga wrote:

[...]

> > Reading between the lines, I gather it is the change to
> > org-latex-to-pdf-process that has caused me problems.  The output I
> > get when the export takes place is:
> >
> > ,----
> > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> > | egrep: Invalid range end
> > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex,
> > skipping.
> > `----
> >
> 
> That is bad - I have no idea here.  Maybe a non-standard
> version of egrep?  But I am really guessing here.

Well, I'm running Debian Linux (testing+unstable mix) so it could be
something I (or Debian) have done.  I've got grep-2.6.3-3 installed
which is from Debian testing.

Is there any way to see what egrep is trying to do? 

> Lets see if this affects more people - for the time being you might
> just change the variable to have it make 2-3 pdflatex runs.

Yes, no problem at all.  This is what I did later but exporting to
latex and running pdflatex myself got me through when the crisis
happened!

Thanks,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <Stromeko@nexgo.de> wrote:
> 
> Hi Eric,
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> > | egrep: Invalid range end
> > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
> 
> Something somewhere tries to make a local path from an absolute one by
> prepending "./", which fails (predictably).  Is the input readable at
> the original path?  Not sure the error message from egrep has to do with
> it or not, but it must be in any case one of the processes started by
> texi2dvi (does not show up on my system, I only have calls to grep when
> I trace it, but one of the sub-processes might still use it).  I think
> texi2dvi also invokes shell scripts, so any funny configuration in the
> environment, especially where path points to, could throw it off.

As far as I know, there is nothing out of the ordinary with my paths
etc (please note that the /.../ above was an edit on my part to hide a
rather long path).  Any hints as to what I can do to explore this
would be most helpful.  How can I get a trace on what texi2dvi is
doing?  (sh -v /usr/bin/texi2dvi?)

Thanks,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bibtex and latex export

[Sébastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> As far as I know, there is nothing out of the ordinary with my paths etc
> (please note that the /.../ above was an edit on my part to hide a rather
> long path). Any hints as to what I can do to explore this would be most
> helpful. How can I get a trace on what texi2dvi is doing? (sh -v
> /usr/bin/texi2dvi?)

I tried:

#+begin_src emacs-lisp
(setq org-latex-to-pdf-process '("sh -v -x texi2dvi -p -b -c -V %f"))
#+end_src

and only see the following in *Messages*:

#+begin_src log
Exporting to LaTeX...done
Processing LaTeX file /home/sva/Projects/Institutions/Forem/Pfi/pfi/Specs/2010-DMFA-et-Autres/Devis-Demandes-2010.tex...
(Shell command failed with code 2 and some error output)
Processing LaTeX file /home/sva/Projects/Institutions/Forem/Pfi/pfi/Specs/2010-DMFA-et-Autres/Devis-Demandes-2010.tex...done
Exporting to PDF...done
#+end_src

The default way, for comparison:

#+begin_src emacs-lisp
(setq org-latex-to-pdf-process '("texi2dvi -p -b -c -V %f"))
#+end_src

displays:

#+begin_src log
Exporting to LaTeX...done
Processing LaTeX file /home/sva/Projects/Institutions/Forem/Pfi/pfi/Specs/2010-DMFA-et-Autres/Devis-Demandes-2010.tex...done
Exporting to PDF...done
#+end_src

So, I've got no idea on how to see the real calls made in sh, for debugging
purpose. Thanks for the =-v= switch to sh. Only knew =-x=...

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <Stromeko@nexgo.de> wrote:
> > 
> > Hi Eric,
> > 
> > Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> > > | egrep: Invalid range end
> > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
> > 
> > Something somewhere tries to make a local path from an absolute one by
> > prepending "./", which fails (predictably).  Is the input readable at
> > the original path?  Not sure the error message from egrep has to do with
> > it or not, but it must be in any case one of the processes started by
> > texi2dvi (does not show up on my system, I only have calls to grep when
> > I trace it, but one of the sub-processes might still use it).  I think
> > texi2dvi also invokes shell scripts, so any funny configuration in the
> > environment, especially where path points to, could throw it off.
> 
> As far as I know, there is nothing out of the ordinary with my paths
> etc (please note that the /.../ above was an edit on my part to hide a
> rather long path).  Any hints as to what I can do to explore this
> would be most helpful.  How can I get a trace on what texi2dvi is
> doing?  (sh -v /usr/bin/texi2dvi?)
> 

There is an explicit egrep on line 1563 or thereabouts (my version
says

# texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
# $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $

at the top of the file):


  # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
  # prepend `./' in order to avoid that the tools take it as an option.
  echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
  || command_line_filename="./$command_line_filename"


The regular expression seems a bit weird (upper case A to lower case
z?), but I can't see off the top of my head how it gets tripped up.  For
tracing, try

   sh -x texi2dvi ....

Nick

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 3613 bytes --]

On Thu, 07 Oct 2010 09:29:59 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <Stromeko@nexgo.de> wrote:
> > > 
> > > Hi Eric,
> > > 
> > > Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> > > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
> > > > | egrep: Invalid range end
> > > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
> > > 
> > > Something somewhere tries to make a local path from an absolute one by
> > > prepending "./", which fails (predictably).  Is the input readable at
> > > the original path?  Not sure the error message from egrep has to do with
> > > it or not, but it must be in any case one of the processes started by
> > > texi2dvi (does not show up on my system, I only have calls to grep when
> > > I trace it, but one of the sub-processes might still use it).  I think
> > > texi2dvi also invokes shell scripts, so any funny configuration in the
> > > environment, especially where path points to, could throw it off.
> > 
> > As far as I know, there is nothing out of the ordinary with my paths
> > etc (please note that the /.../ above was an edit on my part to hide a
> > rather long path).  Any hints as to what I can do to explore this
> > would be most helpful.  How can I get a trace on what texi2dvi is
> > doing?  (sh -v /usr/bin/texi2dvi?)
> > 
> 
> There is an explicit egrep on line 1563 or thereabouts (my version
> says
> 
> # texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
> # $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $
> 
> at the top of the file):
> 
> 
>   # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
>   # prepend `./' in order to avoid that the tools take it as an option.
>   echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
>   || command_line_filename="./$command_line_filename"
> 
> 
> The regular expression seems a bit weird (upper case A to lower case
> z?), but I can't see off the top of my head how it gets tripped up.  For
> tracing, try
> 
>    sh -x texi2dvi ....
> 
> Nick

Thanks Nick.  If I do this:

: (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))

the following is a snippet of the output:

,----
| + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
| egrep: Invalid range end
| + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
| + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
| + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex, skipping.
`----

Because the egrep fails completely, the script assumes that it does
need to prepend "./" to the file name even though the file name
already starts with "/" (and is definitely *not* a DOS type file name
;-).

I don't understand why the egrep is failing although it definitely has
something to do with A-z range; if I try the egrep at the shell and
use "A-Za-z" instead of "A-z", the command works fine.  Does it work
for anybody else on Linux?

I wonder if the problem with the range is locale dependent?  My locale
is en_GB.UTF-8.  The manual page for egrep does indicate that ranges
may not mean the same thing in different locales and suggests using
locale C.  I don't want to change my locale but maybe it could be set
for the invocation of texi2dvi...  (yech).

This is obviously not an org problem as such but I am surprised it's
working for anybody at all...

I guess I'll stick to multiple invocations of pdflatex directly for
the time being.

cheers,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
> 
> the following is a snippet of the output:
> 
> ,----
> | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
> | egrep: Invalid range end
> | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex, skipping.
> `----
> 

What's that '+' sign at the end of the path? 

> Because the egrep fails completely, the script assumes that it does
> need to prepend "./" to the file name even though the file name
> already starts with "/" (and is definitely *not* a DOS type file name
> ;-).
> 
> I don't understand why the egrep is failing although it definitely has
> something to do with A-z range; if I try the egrep at the shell and
> use "A-Za-z" instead of "A-z", the command works fine.  Does it work
> for anybody else on Linux?
> 
I'm using en_US.UTF-8  on Ubuntu 8.10 and it seems to work for me.

The regexp does look funny: there are non-letters included in the
range and it may be that different versions of egrep are more or less
strict in checking it. I would change the texi2dvi script to use [A-Za-z]
and submit a bug report to texinfo.

> I wonder if the problem with the range is locale dependent?  My locale
> is en_GB.UTF-8.  The manual page for egrep does indicate that ranges
> may not mean the same thing in different locales and suggests using
> locale C.  I don't want to change my locale but maybe it could be set
> for the invocation of texi2dvi...  (yech).
> 

You can always change the LOCALE just for the texi2dvi invocation.
I believe that the following works (untested):

LANG=C texi2dvi ....

or maybe

LC_ALL=C texi2dvi ...

Nick

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]

On Thu, 07 Oct 2010 10:22:25 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
> > 
> > the following is a snippet of the output:
> > 
> > ,----
> > | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
> > | egrep: Invalid range end
> > | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> > | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> > | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex, skipping.
> > `----
> > 
> 
> What's that '+' sign at the end of the path? 

I think that's "sh -x" indicating a | between commands; it's not
actually in the file name.  Mind you, even if it were part of the file
name, things should work (well, maybe not latex itself...).

> > I don't understand why the egrep is failing although it definitely has
> > something to do with A-z range; if I try the egrep at the shell and
> > use "A-Za-z" instead of "A-z", the command works fine.  Does it work
> > for anybody else on Linux?
> > 
> I'm using en_US.UTF-8  on Ubuntu 8.10 and it seems to work for me.

Interesting.

> The regexp does look funny: there are non-letters included in the
> range and it may be that different versions of egrep are more or less
> strict in checking it. I would change the texi2dvi script to use [A-Za-z]
> and submit a bug report to texinfo.

I think I will do so.  The thing is that the check is very much for
DOS file names so I don't actually care what that part of the regex is
doing!

> You can always change the LOCALE just for the texi2dvi invocation.
> I believe that the following works (untested):
> 
> LANG=C texi2dvi ....
> 
> or maybe
> 
> LC_ALL=C texi2dvi ...

but this may have unexpected side effects?  I'm not sure if any of the
latex suite use the locale...

Thanks again,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> > ... I would change the texi2dvi script to use [A-Za-z]
> > and submit a bug report to texinfo.
> 
> I think I will do so.  The thing is that the check is very much for
> DOS file names so I don't actually care what that part of the regex is
> doing!
> 

M$ will get you one way or another :-)

BTW, if you do

     echo /foo | egrep '^(/|[A-z]:/)'

do you get the bad range end error message? If so, then your egrep
is indeed stricter than mine.

> > LC_ALL=C texi2dvi ...
> 
> but this may have unexpected side effects?  I'm not sure if any of the
> latex suite use the locale...
> 

Yeah, perhaps...

Nick

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]

On Thu, 07 Oct 2010 10:43:21 +0200, Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Eric,
> 
> Eric S Fraga wrote:
> > As far as I know, there is nothing out of the ordinary with my paths etc
> > (please note that the /.../ above was an edit on my part to hide a rather
> > long path). Any hints as to what I can do to explore this would be most
> > helpful. How can I get a trace on what texi2dvi is doing? (sh -v
> > /usr/bin/texi2dvi?)
> 
> I tried:
> 
> #+begin_src emacs-lisp
> (setq org-latex-to-pdf-process '("sh -v -x texi2dvi -p -b -c -V %f"))
> #+end_src
> 
> and only see the following in *Messages*:

You can see the full output in the special buffer org creates: 
: *Org PDF LaTeX Output*
All the output from the actual commands, such as the following, is
placed in this buffer.  Very useful for when there are problems with
the latex.

,----
| This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
|  restricted \write18 enabled.
| entering extended mode
| (/home/ucecesf/s/teaching/cape/lectures/matlab.tex
| LaTeX2e <2009/09/24>
| Babel <v3.8l> and hyphenation patterns for english, usenglishmax, dumylang, noh
| yphenation, loaded.
| (/usr/share/texmf/tex/latex/beamer/base/beamer.cls
| (/usr/share/texmf/tex/latex/beamer/base/beamerbasercs.sty)
`----

This is different from the messages generated by the elisp code which
appear in *Messages*.

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bibtex and latex export

[Achim Gratz]

Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> I think I will do so.  The thing is that the check is very much for
> DOS file names so I don't actually care what that part of the regex is
> doing!

Since texi2dvi is not fixing a locale this is clearly a bug that you
should report.  It should use character classes instead.  Why your
version of egrep complains about the range expression is not clear to me
(it may be locale dependent behaviour, but not syntactically an invalid
range expression), but you could check LC_COLLATE if "z" gets sorted
before "A".  I have an older version of egrep that will simply ignore
the range in this case and never match, but it certainly doesn't throw
an error.  Maybe this was changed to weed out bad regex's... :-)

> but this may have unexpected side effects?  I'm not sure if any of the
> latex suite use the locale...

I'd be wary of that, too.  If anything you might precede just the call to
egrep by "LC_ALL=C".


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

On Thu, 07 Oct 2010 10:37:52 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > > ... I would change the texi2dvi script to use [A-Za-z]
> > > and submit a bug report to texinfo.
> > 
> > I think I will do so.  The thing is that the check is very much for
> > DOS file names so I don't actually care what that part of the regex is
> > doing!
> > 
> 
> M$ will get you one way or another :-)
> 
> BTW, if you do
> 
>      echo /foo | egrep '^(/|[A-z]:/)'
> 
> do you get the bad range end error message? If so, then your egrep
> is indeed stricter than mine.

I do indeed:

: egrep: Invalid range end.

Very strange.

> > > LC_ALL=C texi2dvi ...
> > 
> > but this may have unexpected side effects?  I'm not sure if any of the
> > latex suite use the locale...
> 
> Yeah, perhaps...

Interestingly, it *is* a locale issue:

: $ echo /foo | LC_ALL=C egrep '^(/|[A-z]:/)'
: /foo


[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> >      echo /foo | egrep '^(/|[A-z]:/)'
> > 
> > do you get the bad range end error message? If so, then your egrep
> > is indeed stricter than mine.
> 
> I do indeed:
> 
> : egrep: Invalid range end.
> 
> Very strange.
> 
> > > > LC_ALL=C texi2dvi ...
> > > 
> > > but this may have unexpected side effects?  I'm not sure if any of the
> > > latex suite use the locale...
> > 
> > Yeah, perhaps...
> 
> Interestingly, it *is* a locale issue:
> 
> : $ echo /foo | LC_ALL=C egrep '^(/|[A-z]:/)'
> : /foo
> 

Yup: the egrep man page says

,----
| Within a bracket expression, a range expression consists of two
| characters separated by a hyphen.  It matches any single character that
| sorts between the two characters, inclusive, using the locale’s
| collating sequence and character set.  For example, in the default C
| locale, [a-d] is equivalent to [abcd].  Many locales sort characters in
| dictionary order, and in these locales [a-d] is typically not equivalent
| to [abcd]; it might be equivalent to [aBbCcDd], for example.  To obtain
| the traditional interpretation of bracket expressions, you can use the C
| locale by setting the LC_ALL environment variable to the value C.
`----

So as Achim pointed out, unless texi2dvi explicitly specifies the locale
for egrep, that regexp is busted. Even [A-Za-z] is busted in the absence
of a locale: it would have to be something like [:alpha:], although I'm
not sure what DOS allows/requires as a drive prefix. And even in the C
locale, [A-z] allows non-letters which, I'm pretty sure, cannot be used
as drive prefixes.

Nick

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]

On Thu, 07 Oct 2010 16:11:32 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> 
> > >      echo /foo | egrep '^(/|[A-z]:/)'
> > > 
> > > do you get the bad range end error message? If so, then your egrep
> > > is indeed stricter than mine.
> > 
> > I do indeed:
> > 
> > : egrep: Invalid range end.
> > 
> > Very strange.
> > 
> > > > > LC_ALL=C texi2dvi ...
> > > > 
> > > > but this may have unexpected side effects?  I'm not sure if any of the
> > > > latex suite use the locale...
> > > 
> > > Yeah, perhaps...
> > 
> > Interestingly, it *is* a locale issue:
> > 
> > : $ echo /foo | LC_ALL=C egrep '^(/|[A-z]:/)'
> > : /foo
> > 
> 
> Yup: the egrep man page says
> 
> ,----
> | Within a bracket expression, a range expression consists of two
> | characters separated by a hyphen.  It matches any single character that
> | sorts between the two characters, inclusive, using the locale’s
> | collating sequence and character set.  For example, in the default C
> | locale, [a-d] is equivalent to [abcd].  Many locales sort characters in
> | dictionary order, and in these locales [a-d] is typically not equivalent
> | to [abcd]; it might be equivalent to [aBbCcDd], for example.  To obtain
> | the traditional interpretation of bracket expressions, you can use the C
> | locale by setting the LC_ALL environment variable to the value C.
> `----
> 
> So as Achim pointed out, unless texi2dvi explicitly specifies the locale
> for egrep, that regexp is busted. Even [A-Za-z] is busted in the absence
> of a locale: it would have to be something like [:alpha:], although I'm
> not sure what DOS allows/requires as a drive prefix. And even in the C
> locale, [A-z] allows non-letters which, I'm pretty sure, cannot be used
> as drive prefixes.
> 
> Nick
> 

Okay, I think this has convinced me to file a bug report.  I'll start
with Debian's system (reporting a bug against the texinfo package) and
hope it filters upstream appropriately.  texi2dvi definitely does not
specify the locale for egrep.  [:alpha:] is probably the right choice
from the little I know about DOS...

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[suvayu ali]

On 7 October 2010 06:58, Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> On Thu, 07 Oct 2010 09:29:59 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
>>
>> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
>>
>> > On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <Stromeko@nexgo.de> wrote:
>> > >
>> > > Hi Eric,
>> > >
>> > > Eric S Fraga <ucecesf@ucl.ac.uk> writes:
>> > > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
>> > > > | egrep: Invalid range end
>> > > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
>> > >
>> > > Something somewhere tries to make a local path from an absolute one by
>> > > prepending "./", which fails (predictably).  Is the input readable at
>> > > the original path?  Not sure the error message from egrep has to do with
>> > > it or not, but it must be in any case one of the processes started by
>> > > texi2dvi (does not show up on my system, I only have calls to grep when
>> > > I trace it, but one of the sub-processes might still use it).  I think
>> > > texi2dvi also invokes shell scripts, so any funny configuration in the
>> > > environment, especially where path points to, could throw it off.
>> >
>> > As far as I know, there is nothing out of the ordinary with my paths
>> > etc (please note that the /.../ above was an edit on my part to hide a
>> > rather long path).  Any hints as to what I can do to explore this
>> > would be most helpful.  How can I get a trace on what texi2dvi is
>> > doing?  (sh -v /usr/bin/texi2dvi?)
>> >
>>
>> There is an explicit egrep on line 1563 or thereabouts (my version
>> says
>>
>> # texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
>> # $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $
>>
>> at the top of the file):
>>
>>
>>   # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
>>   # prepend `./' in order to avoid that the tools take it as an option.
>>   echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
>>   || command_line_filename="./$command_line_filename"
>>
>>
>> The regular expression seems a bit weird (upper case A to lower case
>> z?), but I can't see off the top of my head how it gets tripped up.  For
>> tracing, try
>>
>>    sh -x texi2dvi ....
>>
>> Nick
>
> Thanks Nick.  If I do this:
>
> : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
>
> the following is a snippet of the output:
>
> ,----
> | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
> | egrep: Invalid range end
> | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex, skipping.
> `----
>
> Because the egrep fails completely, the script assumes that it does
> need to prepend "./" to the file name even though the file name
> already starts with "/" (and is definitely *not* a DOS type file name
> ;-).
>
> I don't understand why the egrep is failing although it definitely has
> something to do with A-z range; if I try the egrep at the shell and
> use "A-Za-z" instead of "A-z", the command works fine.  Does it work
> for anybody else on Linux?
>
> I wonder if the problem with the range is locale dependent?  My locale
> is en_GB.UTF-8.  The manual page for egrep does indicate that ranges
> may not mean the same thing in different locales and suggests using
> locale C.  I don't want to change my locale but maybe it could be set
> for the invocation of texi2dvi...  (yech).
>
> This is obviously not an org problem as such but I am surprised it's
> working for anybody at all...
>
> I guess I'll stick to multiple invocations of pdflatex directly for
> the time being.
>

I have the exact same problem ever since I updated org today. (from
commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
Eric Schulte)

My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
understand the discussion where the bug actually is. To resolve this
do I need to file a bug with the Fedora bugzilla? I am confused how
can that be possible because I can successfully export to pdf if I
downgrade org to commit 344785b.

Any suggestions welcome.

> cheers,
> eric
>

-- 
Suvayu

Open source is the future. It sets us free.

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

On Fri, 8 Oct 2010 01:43:25 -0700, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

[...]

> 
> I have the exact same problem ever since I updated org today. (from
> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
> Eric Schulte)
> 
> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
> understand the discussion where the bug actually is. To resolve this
> do I need to file a bug with the Fedora bugzilla? I am confused how
> can that be possible because I can successfully export to pdf if I
> downgrade org to commit 344785b.
> 
> Any suggestions welcome.
> 
> > cheers,
> > eric
> >
> 
> -- 
> Suvayu
> 
> Open source is the future. It sets us free.

Suvayu,

the bug is due to the expression in the texi2dvi script used in an
egrep command.  The reason it is hitting you now and not before is
that the default sequence of commands for exporting org files to PDF
has changed from a sequence of "pdflatex" and "bibtex" commands to one
of using only "texi2dvi".  You can fix the problem by changing the
variable org-latex-to-pdf-process.  I have set it to

: ("pdflatex %f" "bibtex %f" "pdflatex %f" "pdflatex %f")

and this works just fine for me.  If you don't need bibtex at all, you
can remove that entry.  You only need multiple runs of pdflatex if you
have cross-references (including tables of contents etc).

This is a solution in one sense but the real bug is the egrep
expression in texi2dvi which is why it is suggested that a bug report
be filed.

HTH,
eric

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Bibtex and latex export

[Bernt Hansen]

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> On 7 October 2010 06:58, Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
>> On Thu, 07 Oct 2010 09:29:59 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
>>>
>>> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
>>>
>>> > On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz <Stromeko@nexgo.de> wrote:
>>> > >
>>> > > Hi Eric,
>>> > >
>>> > > Eric S Fraga <ucecesf@ucl.ac.uk> writes:
>>> > > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
>>> > > > | egrep: Invalid range end
>>> > > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex, skipping.
>>> > >
>>> > > Something somewhere tries to make a local path from an absolute one by
>>> > > prepending "./", which fails (predictably).  Is the input readable at
>>> > > the original path?  Not sure the error message from egrep has to do with
>>> > > it or not, but it must be in any case one of the processes started by
>>> > > texi2dvi (does not show up on my system, I only have calls to grep when
>>> > > I trace it, but one of the sub-processes might still use it).  I think
>>> > > texi2dvi also invokes shell scripts, so any funny configuration in the
>>> > > environment, especially where path points to, could throw it off.
>>> >
>>> > As far as I know, there is nothing out of the ordinary with my paths
>>> > etc (please note that the /.../ above was an edit on my part to hide a
>>> > rather long path).  Any hints as to what I can do to explore this
>>> > would be most helpful.  How can I get a trace on what texi2dvi is
>>> > doing?  (sh -v /usr/bin/texi2dvi?)
>>> >
>>>
>>> There is an explicit egrep on line 1563 or thereabouts (my version
>>> says
>>>
>>> # texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
>>> # $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $
>>>
>>> at the top of the file):
>>>
>>>
>>>   # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
>>>   # prepend `./' in order to avoid that the tools take it as an option.
>>>   echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
>>>   || command_line_filename="./$command_line_filename"
>>>
>>>
>>> The regular expression seems a bit weird (upper case A to lower case
>>> z?), but I can't see off the top of my head how it gets tripped up.  For
>>> tracing, try
>>>
>>>    sh -x texi2dvi ....
>>>
>>> Nick
>>
>> Thanks Nick.  If I do this:
>>
>> : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
>>
>> the following is a snippet of the output:
>>
>> ,----
>> | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
>> | egrep: Invalid range end
>> | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
>> | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
>> | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex, skipping.
>> `----
>>
>> Because the egrep fails completely, the script assumes that it does
>> need to prepend "./" to the file name even though the file name
>> already starts with "/" (and is definitely *not* a DOS type file name
>> ;-).
>>
>> I don't understand why the egrep is failing although it definitely has
>> something to do with A-z range; if I try the egrep at the shell and
>> use "A-Za-z" instead of "A-z", the command works fine.  Does it work
>> for anybody else on Linux?
>>
>> I wonder if the problem with the range is locale dependent?  My locale
>> is en_GB.UTF-8.  The manual page for egrep does indicate that ranges
>> may not mean the same thing in different locales and suggests using
>> locale C.  I don't want to change my locale but maybe it could be set
>> for the invocation of texi2dvi...  (yech).
>>
>> This is obviously not an org problem as such but I am surprised it's
>> working for anybody at all...
>>
>> I guess I'll stick to multiple invocations of pdflatex directly for
>> the time being.
>>
>
> I have the exact same problem ever since I updated org today. (from
> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
> Eric Schulte)
>
> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
> understand the discussion where the bug actually is. To resolve this
> do I need to file a bug with the Fedora bugzilla? I am confused how
> can that be possible because I can successfully export to pdf if I
> downgrade org to commit 344785b.

Hi suvayu ali,

The change probably is in commit
59ba412 (Use texi2dvi for processing LaTeX to pdf, 2010-10-05)
where we switch from using pdflatex to texi2dvi if it is available.

Regards,
Bernt

Re: Re: Bibtex and latex export

[suvayu ali]

On 8 October 2010 04:35, Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
> On Fri, 8 Oct 2010 01:43:25 -0700, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
> [...]
> Suvayu,
>
> the bug is due to the expression in the texi2dvi script used in an
> egrep command.  The reason it is hitting you now and not before is
> that the default sequence of commands for exporting org files to PDF
> has changed from a sequence of "pdflatex" and "bibtex" commands to one
> of using only "texi2dvi".  You can fix the problem by changing the
> variable org-latex-to-pdf-process.  I have set it to
>
> : ("pdflatex %f" "bibtex %f" "pdflatex %f" "pdflatex %f")
>
> and this works just fine for me.  If you don't need bibtex at all, you
> can remove that entry.  You only need multiple runs of pdflatex if you
> have cross-references (including tables of contents etc).
>
> This is a solution in one sense but the real bug is the egrep
> expression in texi2dvi which is why it is suggested that a bug report
> be filed.
>

Hi Eric,

Thanks a lot for the explanation and the fix for now. I'll definitely
file a bug report with Fedora.

> HTH,
> eric
>
> --
> Eric S Fraga
> GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D
>
>



-- 
Suvayu

Open source is the future. It sets us free.

Re: Bibtex and latex export

[suvayu ali]

Hi Bernt,

On 8 October 2010 05:01, Bernt Hansen <bernt@norang.ca> wrote:
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>
>> ....
>>
>> I have the exact same problem ever since I updated org today. (from
>> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
>> Eric Schulte)
>>
>> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
>> understand the discussion where the bug actually is. To resolve this
>> do I need to file a bug with the Fedora bugzilla? I am confused how
>> can that be possible because I can successfully export to pdf if I
>> downgrade org to commit 344785b.
>
> Hi suvayu ali,
>
> The change probably is in commit
> 59ba412 (Use texi2dvi for processing LaTeX to pdf, 2010-10-05)
> where we switch from using pdflatex to texi2dvi if it is available.
>

Thank you! I found the lines that changed the behaviour for me. :)

> Regards,
> Bernt
>

-- 
Suvayu

Open source is the future. It sets us free.

Re: Re: Bibtex and latex export

[Nick Dokos]

Eric S Fraga <ucecesf@ucl.ac.uk> wrote:

> This is a solution in one sense but the real bug is the egrep
> expression in texi2dvi which is why it is suggested that a bug report
> be filed.
> 

texi2dvi includes the following address for bug reports:

         bug-texinfo@gnu.org

so maybe *one* of the people filing a bug report with debian/fedora/etc
should cc: this address. Eric, do you want to do that?

FWIW, I just tried

      echo /foo | egrep '^(/|[A-z]:/)'

on Ubuntu 10.04 and egrep does not complain. Can you guys try

   egrep -V

and see what version of egrep you are running?

On Ubuntu 8.10:  egrep -V says GNU grep 2.5.3
On Ubuntu 10.04: egrep -V says GNU grep 2.5.4

and neither of these is picky about the regexp.

Thanks,
Nick

Re: Re: Bibtex and latex export

[suvayu ali]

Hi Nick,

On 8 October 2010 08:51, Nick Dokos <nicholas.dokos@hp.com> wrote:
> Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
>
>> This is a solution in one sense but the real bug is the egrep
>> expression in texi2dvi which is why it is suggested that a bug report
>> be filed.
>>
>
> texi2dvi includes the following address for bug reports:
>
>         bug-texinfo@gnu.org
>
> so maybe *one* of the people filing a bug report with debian/fedora/etc
> should cc: this address. Eric, do you want to do that?
>
> FWIW, I just tried
>
>      echo /foo | egrep '^(/|[A-z]:/)'
>
> on Ubuntu 10.04 and egrep does not complain.

I get "egrep: Invalid range end" on Fedora 13 and works as expected on
Ubuntu 10.04 (pdf export works as expected here).

> Can you guys try
>
>   egrep -V
>
> and see what version of egrep you are running?
>
> On Ubuntu 8.10:  egrep -V says GNU grep 2.5.3
> On Ubuntu 10.04: egrep -V says GNU grep 2.5.4
>
> and neither of these is picky about the regexp.
>

For me,

GNU grep 2.6.3 on Fedora 13  (fails)
GNU grep 2.5.4 on Ubuntu 10.04  (works)

> Thanks,
> Nick
>
>

-- 
Suvayu

Open source is the future. It sets us free.

Re: Re: Bibtex and latex export

[Nick Dokos]

There is a thread in the bugs-texinfo mailing list on the egrep
problem in texi2dvi:

  http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html

Nick

Re: Bibtex and latex export

[Achim Gratz]

I'm pretty sure that this behaviour of egrep has been introduced with
GNU grep version 2.6 (which says it fixed some long-standing bugs with
regards to locale handling and character classes if you care to read the
release notes).  Unfortunately, as we see here, fixing bugs in one place
often uncovers bugs someplace else, as the texi2dvi maintainers
certainly didn't suspect a new version of grep to cause breakage.  There
are some bugs introduced with 2.6 that supposedly have been fixed in
2.7.

Since the intent of the regex is obviously to allow an absolute path to
start either with a "/" or a DOS drive letter, contrary to what I wrote
before it is _not_ possible to use character classes as that would also
allow extra characters not allowed in drive letters in most locales.
Probably the most compatible version is to force the "C" locale for the
egrep call in question and slightly modify the range expression:

  echo "$command_line_filename" | LC_ALL=C $EGREP '^(/|[A-Za-z]:/)' >&6 \
  || command_line_filename="./$command_line_filename"

Otherwise you can't really use range expressions or character classes at
all since they either permit illegal drive letters or might not work
with due to the bugs in older versions of grep... it would however be
possible to spell out each drive letter bot in upper and lower case,
although that handicaps the permissible length of the filename (if the
"-i" switch wasn't broken in some locales one could use it and save one
version of the cases):

  echo "$command_line_filename" | LC_ALL=C $EGREP \
  '^(/|[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz]:/)' >&6 \
  || command_line_filename="./$command_line_filename"

*Shudder* :-)


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

Re: Bibtex and latex export

[Achim Gratz]

Nick Dokos <nicholas.dokos@hp.com> writes:
> There is a thread in the bugs-texinfo mailing list on the egrep
> problem in texi2dvi:
>
>   http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html

They came to the same conclusion... :-)


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: Re: Bibtex and latex export

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

On Fri, 08 Oct 2010 13:27:15 -0400, Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> There is a thread in the bugs-texinfo mailing list on the egrep
> problem in texi2dvi:
> 
>   http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html
> 
> Nick
> 

Yeah, it sure looks like we're not the only runs bitten by this bug.
I guess there's no point in filing a bug with them but I may still do
it with Debian.

Thanks for digging this up.  The scary thing is that nobody seems to
be seriously suggesting fixing this on that list?  Also, nobody has
suggested [:alpha:] as a replacement, although this may not be
strictly correct for DOS disk designators if alpha includes all
accented letters etc...

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Bibtex and latex export

[Nick Dokos]

Achim Gratz <Stromeko@nexgo.de> wrote:

> Otherwise you can't really use range expressions or character classes at
> all since they either permit illegal drive letters or might not work
> with due to the bugs in older versions of grep... it would however be
> possible to spell out each drive letter bot in upper and lower case,
> although that handicaps the permissible length of the filename (if the
> "-i" switch wasn't broken in some locales one could use it and save one
> version of the cases):
> 
>   echo "$command_line_filename" | LC_ALL=C $EGREP \
>   '^(/|[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz]:/)' >&6 \
>   || command_line_filename="./$command_line_filename"
> 
> *Shudder* :-)
> 

Indeed :-)

There is a locale-independent range spec for regexps:

      [:alpha:]

would match the indicated class in any locale. See the egrep man page
for more of these. I sent some mail to bug-texinfo@gnu.org suggesting
this, so we'll see.

I also found out to my surprise from the previously posted bug-texinfo
thread, that the ASCII characters between 'Z' and 'a' are (or were) legal
drive letters, but the assumption is that nobody would be so foolish as
to use them any more, so not checking for them is OK.

Nick

Re: Bibtex and latex export

[Achim Gratz]

Nick Dokos <nicholas.dokos@hp.com> writes:
> I also found out to my surprise from the previously posted bug-texinfo
> thread, that the ASCII characters between 'Z' and 'a' are (or were) legal
> drive letters, but the assumption is that nobody would be so foolish as
> to use them any more, so not checking for them is OK.

Ah yes, the LASTDRIVE=32 hack (Novell, I think?).  That's pretty
theoretical since most applications couldn't use them anyway, but that
didn't stop MS from later copying it.  It sure doesn't work if you try
and shove these through a POSIX command line...

BTW, Wikipedia has a good writeup on that, much to my surprise:
http://en.wikipedia.org/wiki/Drive_letter_assignment

Ob-org (enough off-topic for today): once we get the lettered lists, we
should have a LASTDRIVE configuration option to allow [\]^_` as
additional list members when lists get longer than 26 elements... ;-P


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

Selective export of table columns

[Suvayu Ali]

Hi,

I recently was in a situation where I had tables like these,


|    | smear param | \chi^2/DoF  | \chi^2/DoF |
| Sl |  caloE perp | perp before | perp after |
|----+-------------+-------------+------------|
|  3 |       3.008 | 8/13        | 8.3/13     |
|  2 |       3.508 | 8/13        | 8.2/13     |
|  0 |       4.008 | 8/13        | 8.3/13     |
|  4 |       4.508 | 8.1/13      | 8.4/13     |


Now the 1st and 2nd column are something for my reference and I don't
want to export them to my presentation slides. So is there an option for
selective export of table columns? If not can someone give any hints how
I might try to achieve that? I am just learning some lisp, so maybe this
could be a good practice. :)

Thanks for any insights.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Selective export of table columns

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi,
> 
> I recently was in a situation where I had tables like these,
> 
> 
> |    | smear param | \chi^2/DoF  | \chi^2/DoF |
> | Sl |  caloE perp | perp before | perp after |
> |----+-------------+-------------+------------|
> |  3 |       3.008 | 8/13        | 8.3/13     |
> |  2 |       3.508 | 8/13        | 8.2/13     |
> |  0 |       4.008 | 8/13        | 8.3/13     |
> |  4 |       4.508 | 8.1/13      | 8.4/13     |
> 
> 
> Now the 1st and 2nd column are something for my reference and I don't
> want to export them to my presentation slides. So is there an option for
> selective export of table columns? If not can someone give any hints how
> I might try to achieve that? I am just learning some lisp, so maybe this
> could be a good practice. :)
> 
> Thanks for any insights.
> 

Perhaps radio tables with :skipcols can help? See section A.5.1 of the
Org manual.

Nick

Re: Selective export of table columns

[Darlan Cavalcante Moreira]

You could also use org-babel to get a new table with only the desired
columns.

--
Darlan

At Tue, 23 Nov 2010 08:18:40 -0500,
Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> 
> > Hi,
> > 
> > I recently was in a situation where I had tables like these,
> > 
> > 
> > |    | smear param | \chi^2/DoF  | \chi^2/DoF |
> > | Sl |  caloE perp | perp before | perp after |
> > |----+-------------+-------------+------------|
> > |  3 |       3.008 | 8/13        | 8.3/13     |
> > |  2 |       3.508 | 8/13        | 8.2/13     |
> > |  0 |       4.008 | 8/13        | 8.3/13     |
> > |  4 |       4.508 | 8.1/13      | 8.4/13     |
> > 
> > 
> > Now the 1st and 2nd column are something for my reference and I don't
> > want to export them to my presentation slides. So is there an option for
> > selective export of table columns? If not can someone give any hints how
> > I might try to achieve that? I am just learning some lisp, so maybe this
> > could be a good practice. :)
> > 
> > Thanks for any insights.
> > 
> 
> Perhaps radio tables with :skipcols can help? See section A.5.1 of the
> Org manual.
> 
> 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: Selective export of table columns

[Suvayu Ali]

On Tuesday 23 November 2010 05:18 AM, Nick Dokos wrote:
> Perhaps radio tables with :skipcols can help? See section A.5.1 of the
> Org manual.
>

I need to hit tab once to get the alignment right, but other than that 
this works very well. Thank you. :)

But I have a related but probably slightly off-topic question. I tried 
setting the label of a radio table in a tex source file. This breaks the 
conversion. Is this supported?

> Nick


-- 
Suvayu

Open source is the future. It sets us free.

Re: Selective export of table columns

[Carsten Dominik]

On Nov 24, 2010, at 8:02 AM, Suvayu Ali wrote:

> On Tuesday 23 November 2010 05:18 AM, Nick Dokos wrote:
>> Perhaps radio tables with :skipcols can help? See section A.5.1 of  
>> the
>> Org manual.
>>
>
> I need to hit tab once to get the alignment right, but other than  
> that this works very well. Thank you. :)
>
> But I have a related but probably slightly off-topic question. I  
> tried setting the label of a radio table in a tex source file. This  
> breaks the conversion. Is this supported?


You mean the receiver location is in a TeX file?

In this case you should also put the sender table into the TeX file,  
between \begin{comment}...\end{comment}, and turn on the minor orgtbl- 
mode in that TEX file to edit the table.

- Carsten

>
>> Nick
>
>
> -- 
> Suvayu
>
> Open source is the future. It sets us free.
>
> _______________________________________________
> 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: Selective export of table columns

[Suvayu Ali]

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Hi Carsten,

On Tuesday 23 November 2010 11:47 PM, Carsten Dominik wrote:
>> But I have a related but probably slightly off-topic question. I tried
>> setting the label of a radio table in a tex source file. This breaks
>> the conversion. Is this supported?
>
>
> You mean the receiver location is in a TeX file?
>
> In this case you should also put the sender table into the TeX file,
> between \begin{comment}...\end{comment}, and turn on the minor
> orgtbl-mode in that TEX file to edit the table.
>

Yes I did exactly that. And the regular table conversion works just 
fine. I was asking whether it is possible to specify the label for the 
table using this method, as the "#+LABEL: tbl:somename" directive does 
for regular latex export of org files.

My issue is if I set the label by putting a "\label{tbl:somename}" by 
hand after the conversion, it goes away the next time I refresh the orgtbl.

I have attached an example showing the two occasions.

> - Carsten

-- 
Suvayu

Open source is the future. It sets us free.

[-- Attachment #2: radio_tables.tex --]
[-- Type: application/x-tex, Size: 1747 bytes --]

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Title page in latex export

[Suvayu Ali]

Hi Orgers,

I am trying to write my thesis as per my university style. It requires
I use the \title{Thesis title} command before the

\begin{document}
...
\end{document}

Is there any way to do that? Thanks for any thoughts.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Title page in latex export

[Camille persson]

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

Hi,

I think that what it already does

But if you mean you should use \maketitlte before \begin{document} you could
do it like this:

#+BIND: org-export-latex-title-command ""
#+LATEX_HEADER: \maketitle


Regards,
CP


2011/3/4 Suvayu Ali <fatkasuvayu+linux@gmail.com>

> Hi Orgers,
>
> I am trying to write my thesis as per my university style. It requires
> I use the \title{Thesis title} command before the
>
> \begin{document}
> ...
> \end{document}
>
> Is there any way to do that? Thanks for any thoughts.
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>

[-- Attachment #2: Type: text/html, Size: 980 bytes --]

Re: Title page in latex export

[Suvayu Ali]

Hi Camille,

Thanks a lot for your response.

On Fri, 4 Mar 2011 11:48:39 +0100
Camille persson <camille.persson@gmail.com> wrote:

> Hi,
> 
> I think that what it already does
> 

I don't think it does that. e.g.

#+TITLE:     Thesis title
#+AUTHOR:    Suvayu Ali

#+LaTeX_CLASS: book

* Introduction
** Chapter 1
** Chapter 2
* My analysis
** Chapter 3
** Chapter 4

gets exported to latex as,

% Created 2011-03-04 Fri 03:19
\documentclass[11pt]{book}
\usepackage[utf8]{inputenc}
...
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\begin{document}

\title{Thesis title}
\author{Suvayu Ali}
\date{04 March 2011}
\maketitle

\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}

\part{Introduction}
\label{sec-1}
\chapter{Chapter 1}
\label{sec-1_1}
\chapter{Chapter 2}
\label{sec-1_2}
\part{My analysis}
\label{sec-2}
\chapter{Chapter 3}
\label{sec-2_1}
\chapter{Chapter 4}
\label{sec-2_2}

\end{document}


I would like the:

\title{Thesis title}
\author{Suvayu Ali}
\date{04 March 2011}

to be outside the

\begin{document}
...
\end{document}

I hope this clears any confusion.


> But if you mean you should use \maketitlte before \begin{document}
> you could do it like this:
> 
> #+BIND: org-export-latex-title-command ""
> #+LATEX_HEADER: \maketitle
> 
> 
> Regards,
> CP


-- 
Suvayu

Open source is the future. It sets us free.

Re: Title page in latex export

[Lawrence Mitchell]

Suvayu Ali wrote:

> Hi Camille,

> Thanks a lot for your response.

> On Fri, 4 Mar 2011 11:48:39 +0100
> Camille persson <camille.persson@gmail.com> wrote:

>> Hi,

>> I think that what it already does


> I don't think it does that. e.g.

Try this patch to org-latex.el:

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 19baa40..4db38d6 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1352,9 +1352,6 @@ OPT-PLIST is the options plist for current buffer."
      (org-export-apply-macros-in-string org-export-latex-append-header)
      ;; define alert if not yet defined
      "\n\\providecommand{\\alert}[1]{\\textbf{#1}}"
-     ;; beginning of the document
-     "\n\\begin{document}\n\n"
-     ;; insert the title
      (format
       "\n\n\\title{%s}\n"
       ;; convert the title
@@ -1374,6 +1371,9 @@ OPT-PLIST is the options plist for current buffer."
 	     (format-time-string
 	      (or (plist-get opt-plist :date)
 		  org-export-latex-date-format)))
+     ;; beginning of the document
+     "\n\\begin{document}\n\n"
+     ;; insert the title
      ;; insert the title command
      (when (string-match "\\S-" title)
        (if (string-match "%s" org-export-latex-title-command)

-- 
Lawrence Mitchell <wence@gmx.li>

Re: Title page in latex export

[Suvayu Ali]

Hi Lawrence,

On Fri, 04 Mar 2011 11:38:08 +0000
Lawrence Mitchell <wence@gmx.li> wrote:

> Try this patch to org-latex.el:
> 
> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> index 19baa40..4db38d6 100644
> --- a/lisp/org-latex.el
> +++ b/lisp/org-latex.el

That does the trick. :) Thanks a lot.

I am not very familiar with LaTeX, is the org default the proper syntax
and my university style is buggy? 

-- 
Suvayu

Open source is the future. It sets us free.

Re: Title page in latex export

[Camille persson]

[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]

Hi Suvayu,

Do you use the lastest update of org-mode ?
cause it works perfectly for me without any patch actually...

The following org :

#+begin_org
#+TITLE: My title
#+AUTHOR: Camille Persson
#+DATE: 2011
#+LATEX_CLASS: book
#+end_org

... produce the following latex code:

#+begin_latex
\documentclass[11pt,letter]{book}
%% package list
%% ....
\title{My title}
\author{Camille Persson}
\date{2011}

\begin{document}

\maketitle
%.... etc
#+end_latex

to use your university's custom style, you need to put it in your texmf
directory and use the following header lines:
#+LATEX_CLASS: MyUnivThesis
#+LATEX_CLASS_OPTIONS: [options...]

and then customize your .emacs file (or a file in your .emacs.d/) as
following

(add-to-list 'org-export-latex-classes
          '("MyUnivThesis"
             "\\documentclass{univstyle}"
               ("\\part{%s}" . "\\part*{%s}")
               ("\\chapter{%s}" . "\\chapter*{%s}")
               ("\\section{%s}" . "\\section*{%s}")
               ("\\subsection{%s}" . "\\subsection*{%s}")
               ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))


See http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-6

Yours,
CP

2011/3/4 Suvayu Ali <fatkasuvayu+linux@gmail.com>

> Hi Lawrence,
>
> On Fri, 04 Mar 2011 11:38:08 +0000
> Lawrence Mitchell <wence@gmx.li> wrote:
>
> > Try this patch to org-latex.el:
> >
> > diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> > index 19baa40..4db38d6 100644
> > --- a/lisp/org-latex.el
> > +++ b/lisp/org-latex.el
>
> That does the trick. :) Thanks a lot.
>
> I am not very familiar with LaTeX, is the org default the proper syntax
> and my university style is buggy?
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>

[-- Attachment #2: Type: text/html, Size: 2995 bytes --]

Re: Title page in latex export

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> 
> I am trying to write my thesis as per my university style. It requires
> I use the \title{Thesis title} command before the
> 
> \begin{document}
> ...
> \end{document}
> 
> Is there any way to do that? Thanks for any thoughts.
> 

This is really a bug in your university's style. Lamport (p.21 of the
second edition) says:

  The \maketitle command comes after the \begin{document}, usually
  before any other text. The \title, \author, and \date commands can
  come *anywhere* before the \maketitle.

[Emphasis added] \title etc. does not have to be in the
preamble. However, there are many styles out there that restrict the
placement of these macros to the preamble, just as your university's
style does (they probably cribbed from each other :-) ), so applying
Lawrence's patch is probably the best long term solution for org.

Nick

Re: Title page in latex export

[Bastien]

Hi Nick,

Nick Dokos <nicholas.dokos@hp.com> writes:

> [Emphasis added] \title etc. does not have to be in the
> preamble. However, there are many styles out there that restrict the
> placement of these macros to the preamble, just as your university's
> style does (they probably cribbed from each other :-) ), so applying
> Lawrence's patch is probably the best long term solution for org.

Thanks for the explanations -- I've now applied Lawrence's patch (thanks
Lawrence!) 

-- 
 Bastien

[Accepted] [O] Title page in latex export

[Bastien Guerry]

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

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3Cm34o7j5d5r.fsf%40e4300lm.epcc.ed.ac.uk%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: [O] Title page in latex export
> Date: Fri, 04 Mar 2011 16:38:08 -0000
> From: Lawrence Mitchell <wence@gmx.li>
> X-Patchwork-Id: 649
> Message-Id: <m34o7j5d5r.fsf@e4300lm.epcc.ed.ac.uk>
> To: emacs-orgmode@gnu.org
> 
> Suvayu Ali wrote:
> 
> > Hi Camille,
> 
> > Thanks a lot for your response.
> 
> > On Fri, 4 Mar 2011 11:48:39 +0100
> > Camille persson <camille.persson@gmail.com> wrote:
> 
> >> Hi,
> 
> >> I think that what it already does
> 
> 
> > I don't think it does that. e.g.
> 
> Try this patch to org-latex.el:
> 
> 
> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> index 19baa40..4db38d6 100644
> --- a/lisp/org-latex.el
> +++ b/lisp/org-latex.el
> @@ -1352,9 +1352,6 @@ OPT-PLIST is the options plist for current buffer."
>       (org-export-apply-macros-in-string org-export-latex-append-header)
>       ;; define alert if not yet defined
>       "\n\\providecommand{\\alert}[1]{\\textbf{#1}}"
> -     ;; beginning of the document
> -     "\n\\begin{document}\n\n"
> -     ;; insert the title
>       (format
>        "\n\n\\title{%s}\n"
>        ;; convert the title
> @@ -1374,6 +1371,9 @@ OPT-PLIST is the options plist for current buffer."
>  	     (format-time-string
>  	      (or (plist-get opt-plist :date)
>  		  org-export-latex-date-format)))
> +     ;; beginning of the document
> +     "\n\\begin{document}\n\n"
> +     ;; insert the title
>       ;; insert the title command
>       (when (string-match "\\S-" title)
>         (if (string-match "%s" org-export-latex-title-command)
> 

Re: Title page in latex export

[Suvayu Ali]

Hi Nick,

On Fri, 04 Mar 2011 10:45:08 -0500
Nick Dokos <nicholas.dokos@hp.com> wrote:

> This is really a bug in your university's style. Lamport (p.21 of the
> second edition) says:
> 
>   The \maketitle command comes after the \begin{document}, usually
>   before any other text. The \title, \author, and \date commands can
>   come *anywhere* before the \maketitle.
> 
> [Emphasis added] \title etc. does not have to be in the
> preamble. However, there are many styles out there that restrict the
> placement of these macros to the preamble, just as your university's
> style does (they probably cribbed from each other :-) ), so applying
> Lawrence's patch is probably the best long term solution for org.
> 

Thanks a lot for clarifying that. :)

> Nick


-- 
Suvayu

Open source is the future. It sets us free.

Re: Title page in latex export

[Suvayu Ali]

Hi Camille,

On Fri, 4 Mar 2011 15:17:58 +0100
Camille persson <camille.persson@gmail.com> wrote:

> Hi Suvayu,
> 
> Do you use the lastest update of org-mode ?
> cause it works perfectly for me without any patch actually...
> 

Yes, my org-mode is less than a day old. But I didn't have any LaTeX
customisations in my setup. I am not sure why our exports are
different. However with Lawerence's patch things work very smoothly.

> 
> to use your university's custom style, you need to put it in your
> texmf directory and use the following header lines:
> #+LATEX_CLASS: MyUnivThesis
> #+LATEX_CLASS_OPTIONS: [options...]
> 
> and then customize your .emacs file (or a file in your .emacs.d/) as
> following
> 
> (add-to-list 'org-export-latex-classes
>           '("MyUnivThesis"
>              "\\documentclass{univstyle}"
>                ("\\part{%s}" . "\\part*{%s}")
>                ("\\chapter{%s}" . "\\chapter*{%s}")
>                ("\\section{%s}" . "\\section*{%s}")
>                ("\\subsection{%s}" . "\\subsection*{%s}")
>                ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
> 
> 

Thanks for pointing it out. This will be very helpful. :)

> See http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-6
> 
> Yours,
> CP

-- 
Suvayu

Open source is the future. It sets us free.

Future Worg publishing failure :)

[Nick Dokos]

org-glossary.org contains the following text at one point:

... The number of days is
14.

Current org code takes the 14. as an item in a numbered list.  When
exporting to HTML, this causes an error in org-html-export-list-line -
hence the subject line. It's not a problem right now but it will be when
orgmode.org gets the updated version. I reformatted the line to avoid
the awkward newline, so the future publishing failure will not
happen. I'll let Nicolas worry about what should be done about the
error.

Nick

Org-mode version 7.5 (release_7.5.77.g74268.dirty)

Here's the backtrace of the error:

Debugger entered--Lisp error: (args-out-of-range #("14." 0 3 (fontified t list-item 11895 list-struct ((11895 0 "14." nil nil nil 11899)) list-prevs ((11895)) list-context nil)) 9 10)
  match-string(3 #("14." 0 3 (fontified t list-item 11895 list-struct ((11895 0 "14." nil nil nil 11899)) list-prevs ((11895)) list-context nil)))
  (let* ((checkbox (match-string 3 line)) (desc-tag (or (match-string 4 line) "???")) (body (or (match-string 5 line) "")) (list-beg (org-list-get-list-begin pos struct prevs)) (firstp (= list-beg pos)) (type (funcall get-type list-beg struct prevs)) (counter (let ((count-tmp (org-list-get-counter pos struct))) (cond ((not count-tmp) nil) ((string-match "[A-Za-z]" count-tmp) (- (string-to-char ...) 64)) ((string-match "[0-9]+" count-tmp) count-tmp))))) (when firstp (org-close-par-maybe) (insert (format "<%sl>\n" type))) (insert (cond ((equal type "d") (format "<dt>%s</dt><dd>" desc-tag)) ((and (equal type "o") counter) (format "<li value=\"%s\">" counter)) (t "<li>"))) (when checkbox (setq body (concat (cond ((string-match "X" checkbox) "<code>[X]</code> ") ((string-match " " checkbox) "<c
 ode>[&nbsp;]</code> ") (t "<code>[-]</code> ")) body))) body)
  (cond ((assq pos struct) (string-match (concat "[ 	]*\\(\\S-+[ 	]+\\)" "\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\]\\)?" "\\(?:\\(\\[[ X-]\\]\\)[ 	]+\\)?" "\\(?:\\(.*\\)[ 	]+::[ 	]+\\)?" "\\(.*\\)") line) (let* ((checkbox (match-string 3 line)) (desc-tag (or (match-string 4 line) "???")) (body (or (match-string 5 line) "")) (list-beg (org-list-get-list-begin pos struct prevs)) (firstp (= list-beg pos)) (type (funcall get-type list-beg struct prevs)) (counter (let ((count-tmp ...)) (cond (... nil) (... ...) (... count-tmp))))) (when firstp (org-close-par-maybe) (insert (format "<%sl>\n" type))) (insert (cond ((equal type "d") (format "<dt>%s</dt><dd>" desc-tag)) ((and (equal type "o") counter) (format "<li value=\"%s\">" counter)) (t "<li>"))) (when checkbox (setq body (concat (con
 d (... "<code>[X]</code> ") (... "<code>[&nbsp;]</code> ") (t "<code>[-]</code> ")) body))) body)) ((equal "ORG-LIST-END-MARKER" line) (throw (quote nextline) nil)) (t line))
  (let* ((get-type (function (lambda (pos struct prevs) (let ((type ...)) (cond (... "o") (... "d") (t "u")))))) (get-closings (function (lambda (pos) (let (out) (catch (quote exit) (mapc ... struct)) out))))) (mapc (lambda (e) (let* ((lastp (= (org-list-get-last-item e struct prevs) e)) (first-item (org-list-get-list-begin e struct prevs)) (type (funcall get-type first-item struct prevs))) (org-close-par-maybe) (org-close-li type) (when lastp (insert (format "</%sl>\n" type)) (org-open-par)))) (funcall get-closings pos)) (cond ((assq pos struct) (string-match (concat "[ 	]*\\(\\S-+[ 	]+\\)" "\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\]\\)?" "\\(?:\\(\\[[ X-]\\]\\)[ 	]+\\)?" "\\(?:\\(.*\\)[ 	]+::[ 	]+\\)?" "\\(.*\\)") line) (let* ((checkbox (match-string 3 line)) (desc-tag (or (match
 -string 4 line) "???")) (body (or (match-string 5 line) "")) (list-beg (org-list-get-list-begin pos struct prevs)) (firstp (= list-beg pos)) (type (funcall get-type list-beg struct prevs)) (
 counter (let (...) (cond ... ... ...)))) (when firstp (org-close-par-maybe) (insert (format "<%sl>\n" type))) (insert (cond ((equal type "d") (format "<dt>%s</dt><dd>" desc-tag)) ((and ... counter) (format "<li value=\"%s\">" counter)) (t "<li>"))) (when checkbox (setq body (concat (cond ... ... ...) body))) body)) ((equal "ORG-LIST-END-MARKER" line) (throw (quote nextline) nil)) (t line)))
  org-html-export-list-line(#("14." 0 3 (fontified t list-item 11895 list-struct ((11895 0 "14." nil nil nil 11899)) list-prevs ((11895)) list-context nil)) 11895 ((11895 0 "14." nil nil nil 11899)) ((11895)))
  (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line)))
  (progn (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line))))
  (if (get-text-property 0 (quote list-item) line) (progn (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line)))))
  (when (get-text-property 0 (quote list-item) line) (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line))))
  (cond ((string-match "^\\(\\*+\\)[ 	]+\\(.*\\)" line) (setq level (org-tr-level (- (match-end 1) (match-beginning 1) level-offset)) txt (match-string 2 line)) (if (string-match quote-re0 txt) (setq txt (replace-match "" t t txt))) (if (<= level (max umax umax-toc)) (setq head-count (+ head-count 1))) (setq first-heading-pos (or first-heading-pos (point))) (org-html-level-start level txt umax (and org-export-with-toc (<= level umax)) head-count) (when (string-match quote-re line) (org-close-par-maybe) (insert "<pre>") (setq inquote t))) ((and org-export-with-tables (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" line)) (when (not table-open) (setq table-open t table-buffer nil table-orig-buffer nil)) (setq table-buffer (cons line table-buffer) table-orig-buffer (cons origline table-orig-bu
 ffer)) (when (or (not lines) (not (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" (car lines)))) (setq table-open nil table-buffer (nreverse table-buffer) table-orig-buffer (nreverse table-or
 ig-buffer)) (org-close-par-maybe) (insert (org-format-table-html table-buffer table-orig-buffer)))) (t (when (get-text-property 0 (quote list-item) line) (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line)))) (when (string-match "^[ 	]*-\\{5,\\}[ 	]*$" line) (if org-par-open (insert "\n</p>\n<hr/>\n<p>\n") (insert "\n<hr/>\n")) (throw (quote nextline) nil)) (if (string-match "^ [-+*]-\\|^[ 	]*$" line) (org-open-par)) (when org-export-with-footnotes (when (and (boundp (quote footnote-section-tag-regexp)) (string-match (concat "^" footnote-section-tag-regexp) line)) (throw (quote nextline) nil)) (when (string-match "^[ 	]*\\[\\([0-9]+\\)\\]" line) (org-close-par-m
 aybe) (let ((n (match-string 1 line))) (setq org-par-open t line (replace-match (format ... n n n) t t line))))) (cond ((string-match "\\\\\\\\[ 	]*$" line) (setq line (replace-match "<br/>"
  t t line))) (org-export-preserve-breaks (setq line (concat line "<br/>")))) (let ((start 0)) (while (and org-par-open (string-match "\\\\par\\>" line start)) (if (not (get-text-property (match-beginning 0) (quote org-protected) line)) (setq line (replace-match "</p ><p >" t t line))) (setq start (match-end 0)))) (insert line "\n")))
  (catch (quote nextline) (when (and inquote (string-match "^\\*+ " line)) (insert "</pre>\n") (org-open-par) (setq inquote nil)) (when inquote (insert (org-html-protect line) "\n") (throw (quote nextline) nil)) (when (and org-export-with-fixed-width (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" line)) (when (not infixed) (setq infixed t) (org-close-par-maybe) (insert "<pre class=\"example\">\n")) (insert (org-html-protect (match-string 3 line)) "\n") (when (or (not lines) (not (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" (car lines)))) (setq infixed nil) (insert "</pre>\n") (org-open-par)) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quote org-protected) line) (not (< (or (next-single-property-change 0 (quote org-protected) line) 10000) (length line)))) (let
  (par (ind (get-text-property 0 (quote original-indentation) line))) (when (re-search-backward "\\(<p>\\)\\([ 	
\n]*\\)\\=" (- (point) 100) t) (setq par (match-string 1)) (replace-match "\\2
 \n")) (insert line "\n") (while (and lines (or (= (length ...) 0) (not ind) (equal ind (get-text-property 0 ... ...))) (or (= (length ...) 0) (get-text-property 0 (quote org-protected) (car lines)))) (insert (pop lines) "\n")) (and par (insert "<p>\n"))) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-START" line) (org-close-par-maybe) (insert "<blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-END" line) (org-close-par-maybe) (insert "\n</blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-START" line) (org-close-par-maybe) (insert "\n<p class=\"verse\">\n") (setq org-par-open t) (setq inverse t) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-END" line) (insert "</p>\n") (setq org-par-open nil) (or
 g-open-par) (setq inverse nil) (throw (quote nextline) nil)) (when (equal "ORG-CENTER-START" line) (org-close-par-maybe) (insert "\n<div style=\"text-align: center\">") (org-open-par) (throw
  (quote nextline) nil)) (when (equal "ORG-CENTER-END" line) (org-close-par-maybe) (insert "\n</div>") (org-open-par) (throw (quote nextline) nil)) (run-hooks (quote org-export-html-after-blockquotes-hook)) (when inverse (let ((i (org-get-string-indentation line))) (if (> i 0) (setq line (concat (mapconcat (quote identity) (make-list ... "\\nbsp") "") " " (org-trim line)))) (unless (string-match "\\\\\\\\[ 	]*$" line) (setq line (concat line "\\\\"))))) (setq start 0) (while (string-match "<<<?\\([^<>]*\\)>>>?\\((INVISIBLE)\\)?[ 	]*\n?" line start) (cond ((get-text-property (match-beginning 1) (quote org-protected) line) (setq start (match-end 1))) ((match-end 2) (setq line (replace-match (format "@<a name=\"%s\" id=\"%s\">@</a>" (org-solidify-link-text ...) (org-solidify-link-text ...)) t
  t line))) ((and org-export-with-toc (equal (string-to-char line) 42)) (setq line (replace-match (concat "@<span class=\"target\">" (match-string 1 line) "@</span> ") t t line))) (t (setq li
 ne (replace-match (concat "@<a name=\"" (org-solidify-link-text ...) "\" class=\"target\">" (match-string 1 line) "@</a> ") t t line))))) (setq line (org-html-handle-time-stamps line)) (or (string-match org-table-hline-regexp line) (setq line (org-html-expand line))) (setq line (org-html-handle-links line opt-plist)) (if (and (string-match org-todo-line-regexp line) (match-beginning 2)) (setq line (concat (substring line 0 (match-beginning 2)) "<span class=\"" (if (member (match-string 2 line) org-done-keywords) "done" "todo") " " (match-string 2 line) "\"> " (org-export-html-get-todo-kwd-class-name (match-string 2 line)) "</span>" (substring line (match-end 2))))) (when org-export-with-footnotes (setq start 0) (while (string-match "\\([^* 	].*?\\)\\[\\([0-9]+\\)\\]" line start) (if (get-
 text-property (match-beginning 2) (quote org-protected) line) (setq start (match-end 2)) (let ((n (match-string 2 line)) extra a) (if (setq a (assoc n footref-seen)) (progn (setcdr a ...) (s
 etq extra ...)) (setq extra "") (push (cons n 1) footref-seen)) (setq line (replace-match (format ... ... n extra n n) t t line)))))) (cond ((string-match "^\\(\\*+\\)[ 	]+\\(.*\\)" line) (setq level (org-tr-level (- (match-end 1) (match-beginning 1) level-offset)) txt (match-string 2 line)) (if (string-match quote-re0 txt) (setq txt (replace-match "" t t txt))) (if (<= level (max umax umax-toc)) (setq head-count (+ head-count 1))) (setq first-heading-pos (or first-heading-pos (point))) (org-html-level-start level txt umax (and org-export-with-toc (<= level umax)) head-count) (when (string-match quote-re line) (org-close-par-maybe) (insert "<pre>") (setq inquote t))) ((and org-export-with-tables (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" line)) (when (not table-open) (setq table-open 
 t table-buffer nil table-orig-buffer nil)) (setq table-buffer (cons line table-buffer) table-orig-buffer (cons origline table-orig-buffer)) (when (or (not lines) (not (string-match "^\\([ 	]
 *\\)\\(|\\|\\+-+\\+\\)" (car lines)))) (setq table-open nil table-buffer (nreverse table-buffer) table-orig-buffer (nreverse table-orig-buffer)) (org-close-par-maybe) (insert (org-format-table-html table-buffer table-orig-buffer)))) (t (when (get-text-property 0 (quote list-item) line) (setq line (org-html-export-list-line line (get-text-property 0 (quote list-item) line) (get-text-property 0 (quote list-struct) line) (get-text-property 0 (quote list-prevs) line)))) (when (string-match "^[ 	]*-\\{5,\\}[ 	]*$" line) (if org-par-open (insert "\n</p>\n<hr/>\n<p>\n") (insert "\n<hr/>\n")) (throw (quote nextline) nil)) (if (string-match "^ [-+*]-\\|^[ 	]*$" line) (org-open-par)) (when org-export-with-footnotes (when (and (boundp (quote footnote-section-tag-regexp)) (string-match (concat "^" fo
 otnote-section-tag-regexp) line)) (throw (quote nextline) nil)) (when (string-match "^[ 	]*\\[\\([0-9]+\\)\\]" line) (org-close-par-maybe) (let ((n ...)) (setq org-par-open t line (replace-m
 atch ... t t line))))) (cond ((string-match "\\\\\\\\[ 	]*$" line) (setq line (replace-match "<br/>" t t line))) (org-export-preserve-breaks (setq line (concat line "<br/>")))) (let ((start 0)) (while (and org-par-open (string-match "\\\\par\\>" line start)) (if (not (get-text-property ... ... line)) (setq line (replace-match "</p ><p >" t t line))) (setq start (match-end 0)))) (insert line "\n"))))
  (while (setq line (pop lines) origline line) (catch (quote nextline) (when (and inquote (string-match "^\\*+ " line)) (insert "</pre>\n") (org-open-par) (setq inquote nil)) (when inquote (insert (org-html-protect line) "\n") (throw (quote nextline) nil)) (when (and org-export-with-fixed-width (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" line)) (when (not infixed) (setq infixed t) (org-close-par-maybe) (insert "<pre class=\"example\">\n")) (insert (org-html-protect (match-string 3 line)) "\n") (when (or (not lines) (not (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" (car lines)))) (setq infixed nil) (insert "</pre>\n") (org-open-par)) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quote org-protected) line) (not (< (or (next-single-property-change 0 ... line) 1
 0000) (length line)))) (let (par (ind (get-text-property 0 (quote original-indentation) line))) (when (re-search-backward "\\(<p>\\)\\([ 	
\n]*\\)\\=" (- (point) 100) t) (setq par (match-str
 ing 1)) (replace-match "\\2\n")) (insert line "\n") (while (and lines (or (= ... 0) (not ind) (equal ind ...)) (or (= ... 0) (get-text-property 0 ... ...))) (insert (pop lines) "\n")) (and par (insert "<p>\n"))) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-START" line) (org-close-par-maybe) (insert "<blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-END" line) (org-close-par-maybe) (insert "\n</blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-START" line) (org-close-par-maybe) (insert "\n<p class=\"verse\">\n") (setq org-par-open t) (setq inverse t) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-END" line) (insert "</p>\n") (setq org-par-open nil) (org-open-par) (setq inverse nil) (throw (quot
 e nextline) nil)) (when (equal "ORG-CENTER-START" line) (org-close-par-maybe) (insert "\n<div style=\"text-align: center\">") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-C
 ENTER-END" line) (org-close-par-maybe) (insert "\n</div>") (org-open-par) (throw (quote nextline) nil)) (run-hooks (quote org-export-html-after-blockquotes-hook)) (when inverse (let ((i (org-get-string-indentation line))) (if (> i 0) (setq line (concat (mapconcat ... ... "") " " (org-trim line)))) (unless (string-match "\\\\\\\\[ 	]*$" line) (setq line (concat line "\\\\"))))) (setq start 0) (while (string-match "<<<?\\([^<>]*\\)>>>?\\((INVISIBLE)\\)?[ 	]*\n?" line start) (cond ((get-text-property (match-beginning 1) (quote org-protected) line) (setq start (match-end 1))) ((match-end 2) (setq line (replace-match (format "@<a name=\"%s\" id=\"%s\">@</a>" ... ...) t t line))) ((and org-export-with-toc (equal (string-to-char line) 42)) (setq line (replace-match (concat "@<span class=\"target
 \">" ... "@</span> ") t t line))) (t (setq line (replace-match (concat "@<a name=\"" ... "\" class=\"target\">" ... "@</a> ") t t line))))) (setq line (org-html-handle-time-stamps line)) (or
  (string-match org-table-hline-regexp line) (setq line (org-html-expand line))) (setq line (org-html-handle-links line opt-plist)) (if (and (string-match org-todo-line-regexp line) (match-beginning 2)) (setq line (concat (substring line 0 (match-beginning 2)) "<span class=\"" (if (member (match-string 2 line) org-done-keywords) "done" "todo") " " (match-string 2 line) "\"> " (org-export-html-get-todo-kwd-class-name (match-string 2 line)) "</span>" (substring line (match-end 2))))) (when org-export-with-footnotes (setq start 0) (while (string-match "\\([^* 	].*?\\)\\[\\([0-9]+\\)\\]" line start) (if (get-text-property (match-beginning 2) (quote org-protected) line) (setq start (match-end 2)) (let ((n ...) extra a) (if (setq a ...) (progn ... ...) (setq extra "") (push ... footref-seen)) (s
 etq line (replace-match ... t t line)))))) (cond ((string-match "^\\(\\*+\\)[ 	]+\\(.*\\)" line) (setq level (org-tr-level (- (match-end 1) (match-beginning 1) level-offset)) txt (match-stri
 ng 2 line)) (if (string-match quote-re0 txt) (setq txt (replace-match "" t t txt))) (if (<= level (max umax umax-toc)) (setq head-count (+ head-count 1))) (setq first-heading-pos (or first-heading-pos (point))) (org-html-level-start level txt umax (and org-export-with-toc (<= level umax)) head-count) (when (string-match quote-re line) (org-close-par-maybe) (insert "<pre>") (setq inquote t))) ((and org-export-with-tables (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" line)) (when (not table-open) (setq table-open t table-buffer nil table-orig-buffer nil)) (setq table-buffer (cons line table-buffer) table-orig-buffer (cons origline table-orig-buffer)) (when (or (not lines) (not (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" ...))) (setq table-open nil table-buffer (nreverse table-buffer) ta
 ble-orig-buffer (nreverse table-orig-buffer)) (org-close-par-maybe) (insert (org-format-table-html table-buffer table-orig-buffer)))) (t (when (get-text-property 0 (quote list-item) line) (s
 etq line (org-html-export-list-line line (get-text-property 0 ... line) (get-text-property 0 ... line) (get-text-property 0 ... line)))) (when (string-match "^[ 	]*-\\{5,\\}[ 	]*$" line) (if org-par-open (insert "\n</p>\n<hr/>\n<p>\n") (insert "\n<hr/>\n")) (throw (quote nextline) nil)) (if (string-match "^ [-+*]-\\|^[ 	]*$" line) (org-open-par)) (when org-export-with-footnotes (when (and (boundp ...) (string-match ... line)) (throw (quote nextline) nil)) (when (string-match "^[ 	]*\\[\\([0-9]+\\)\\]" line) (org-close-par-maybe) (let (...) (setq org-par-open t line ...)))) (cond ((string-match "\\\\\\\\[ 	]*$" line) (setq line (replace-match "<br/>" t t line))) (org-export-preserve-breaks (setq line (concat line "<br/>")))) (let ((start 0)) (while (and org-par-open (string-match "\\\\par\
 \>" line start)) (if (not ...) (setq line ...)) (setq start (match-end 0)))) (insert line "\n")))))
  (let ((case-fold-search nil) (org-odd-levels-only odd)) (mapc (lambda (x) (set (make-local-variable (nth 2 x)) (plist-get opt-plist (car x)))) org-export-plist-vars) (setq umax (if arg (prefix-numeric-value arg) org-export-headline-levels)) (setq umax-toc (if (integerp org-export-with-toc) (min org-export-with-toc umax) umax)) (unless body-only (insert (format "%s\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"\n               \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\"\nlang=\"%s\" xml:lang=\"%s\">\n<head>\n<title>%s</title>\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=%s\"/>\n<meta name=\"generator\" content=\"Org-mode\"/>\n<meta name=\"generated\" content=\"%s\"/>\n<meta name=\"author\" content=\"%s
 \"/>\n<meta name=\"description\" content=\"%s\"/>\n<meta name=\"keywords\" content=\"%s\"/>\n%s\n%s\n</head>\n<body>\n<div id=\"content\">\n%s\n" (format (or (and (stringp org-export-html-xm
 l-declaration) org-export-html-xml-declaration) (cdr (assoc html-extension org-export-html-xml-declaration)) (cdr (assoc "html" org-export-html-xml-declaration)) "") (or charset "iso-8859-1")) language language title (or charset "iso-8859-1") date author description keywords style mathjax (if (or link-up link-home) (concat (format org-export-html-home/up-format (or link-up link-home) (or link-home link-up)) "\n") ""))) (when (plist-get opt-plist :html-preamble) (let ((html-pre (plist-get opt-plist :html-preamble))) (cond ((stringp html-pre) (insert (format-spec html-pre ...))) ((functionp html-pre) (funcall html-pre opt-plist)) (t (insert (format-spec ... ...))))))) (if (and org-export-with-toc (not body-only)) (progn (push (format "<h%d>%s</h%d>\n" org-export-html-toplevel-hlevel (nth 3 
 lang-words) org-export-html-toplevel-hlevel) thetoc) (push "<div id=\"text-table-of-contents\">\n" thetoc) (push "<ul>\n<li>" thetoc) (setq lines (mapcar (quote (lambda (line) (if ... ...) l
 ine)) lines)) (while (> org-last-level (1- org-min-level)) (setq org-last-level (1- org-last-level)) (push "</li>\n</ul>\n" thetoc)) (push "</div>\n" thetoc) (setq thetoc (if have-headings (nreverse thetoc) nil)))) (setq head-count 0) (org-init-section-numbers) (org-open-par) (while (setq line (pop lines) origline line) (catch (quote nextline) (when (and inquote (string-match "^\\*+ " line)) (insert "</pre>\n") (org-open-par) (setq inquote nil)) (when inquote (insert (org-html-protect line) "\n") (throw (quote nextline) nil)) (when (and org-export-with-fixed-width (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" line)) (when (not infixed) (setq infixed t) (org-close-par-maybe) (insert "<pre class=\"example\">\n")) (insert (org-html-protect (match-string 3 line)) "\n") (when (or (not li
 nes) (not (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" ...))) (setq infixed nil) (insert "</pre>\n") (org-open-par)) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quo
 te org-protected) line) (not (< (or ... 10000) (length line)))) (let (par (ind (get-text-property 0 ... line))) (when (re-search-backward "\\(<p>\\)\\([ 	
\n]*\\)\\=" (- ... 100) t) (setq par (match-string 1)) (replace-match "\\2\n")) (insert line "\n") (while (and lines (or ... ... ...) (or ... ...)) (insert (pop lines) "\n")) (and par (insert "<p>\n"))) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-START" line) (org-close-par-maybe) (insert "<blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-END" line) (org-close-par-maybe) (insert "\n</blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-START" line) (org-close-par-maybe) (insert "\n<p class=\"verse\">\n") (setq org-par-open t) (setq inverse t) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-END" line) (insert "</p>\n") (setq org-par-open nil) (org-open-par) (setq inverse nil) (throw (quote nextline
 ) nil)) (when (equal "ORG-CENTER-S
 TART" line) (org-close-par-maybe) (insert "\n<div style=\"text-align: center\">") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-CENTER-END" line) (org-close-par-maybe) (insert "\n</div>") (org-open-par) (throw (quote nextline) nil)) (run-hooks (quote org-export-html-after-blockquotes-hook)) (when inverse (let ((i (org-get-string-indentation line))) (if (> i 0) (setq line (concat ... " " ...))) (unless (string-match "\\\\\\\\[ 	]*$" line) (setq line (concat line "\\\\"))))) (setq start 0) (while (string-match "<<<?\\([^<>]*\\)>>>?\\((INVISIBLE)\\)?[ 	]*\n?" line start) (cond ((get-text-property (match-beginning 1) (quote org-protected) line) (setq start (match-end 1))) ((match-end 2) (setq line (replace-match ... t t line))) ((and org-export-with-toc (equal ... 42)) (setq 
 line (replace-match ... t t line))) (t (setq line (replace-match ... t t line))))) (setq line (org-html-handle-time-stamps line)) (or (string-match org-table-hline-regexp line) (setq line (o
 rg-html-expand line))) (setq line (org-html-handle-links line opt-plist)) (if (and (string-match org-todo-line-regexp line) (match-beginning 2)) (setq line (concat (substring line 0 (match-beginning 2)) "<span class=\"" (if (member ... org-done-keywords) "done" "todo") " " (match-string 2 line) "\"> " (org-export-html-get-todo-kwd-class-name (match-string 2 line)) "</span>" (substring line (match-end 2))))) (when org-export-with-footnotes (setq start 0) (while (string-match "\\([^* 	].*?\\)\\[\\([0-9]+\\)\\]" line start) (if (get-text-property (match-beginning 2) (quote org-protected) line) (setq start (match-end 2)) (let (... extra a) (if ... ... ... ...) (setq line ...))))) (cond ((string-match "^\\(\\*+\\)[ 	]+\\(.*\\)" line) (setq level (org-tr-level (- ... ... level-offset)) txt (mat
 ch-string 2 line)) (if (string-match quote-re0 txt) (setq txt (replace-match "" t t txt))) (if (<= level (max umax umax-toc)) (setq head-count (+ head-count 1))) (setq first-heading-pos (or 
 first-heading-pos (point))) (org-html-level-start level txt umax (and org-export-with-toc (<= level umax)) head-count) (when (string-match quote-re line) (org-close-par-maybe) (insert "<pre>") (setq inquote t))) ((and org-export-with-tables (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" line)) (when (not table-open) (setq table-open t table-buffer nil table-orig-buffer nil)) (setq table-buffer (cons line table-buffer) table-orig-buffer (cons origline table-orig-buffer)) (when (or (not lines) (not ...)) (setq table-open nil table-buffer (nreverse table-buffer) table-orig-buffer (nreverse table-orig-buffer)) (org-close-par-maybe) (insert (org-format-table-html table-buffer table-orig-buffer)))) (t (when (get-text-property 0 (quote list-item) line) (setq line (org-html-export-list-line line 
 ... ... ...))) (when (string-match "^[ 	]*-\\{5,\\}[ 	]*$" line) (if org-par-open (insert "\n</p>\n<hr/>\n<p>\n") (insert "\n<hr/>\n")) (throw (quote nextline) nil)) (if (string-match "^ [-+
 *]-\\|^[ 	]*$" line) (org-open-par)) (when org-export-with-footnotes (when (and ... ...) (throw ... nil)) (when (string-match "^[ 	]*\\[\\([0-9]+\\)\\]" line) (org-close-par-maybe) (let ... ...))) (cond ((string-match "\\\\\\\\[ 	]*$" line) (setq line ...)) (org-export-preserve-breaks (setq line ...))) (let ((start 0)) (while (and org-par-open ...) (if ... ...) (setq start ...))) (insert line "\n"))))) (when inquote (insert "</pre>\n") (org-open-par)) (org-html-level-start 1 nil umax (and org-export-with-toc (<= level umax)) head-count) (when (and (> umax 0) first-heading-pos) (insert "</div>\n")) (save-excursion (goto-char (point-min)) (while (re-search-forward "<p class=\"footnote\">[^"<p class=\"email\">" email "</p>\n")) (when (plist-get opt-plist :creator-info) (insert "<p class=\"cr
 eator\">" ...)) (insert html-validation-link "\n</div>")) (t (insert "<div id=\"postamble\">\n") (insert (format-spec ... ...)) (insert "</div>")))))) (if org-export-html-with-timestamp (ins
 ert org-export-html-html-helper-timestamp)) (unless body-only (insert "\n</div>\n</body>\n</html>\n")) (unless (plist-get opt-plist :buffer-will-be-killed) (normal-mode) (if (eq major-mode (default-value (quote major-mode))) (html-mode))) (goto-char (point-min)) (when thetoc (if (or (re-search-forward "<p>\\s-*\\[TABLE-OF-CONTENTS\\]\\s-*</p>" nil t) (re-search-forward "\\[TABLE-OF-CONTENTS\\]" nil t)) (progn (goto-char (match-beginning 0)) (replace-match "")) (goto-char first-heading-pos) (when (looking-at "\\s-*</p>") (goto-char (match-end 0)) (insert "\n"))) (insert "<div id=\"table-of-contents\">\n") (let ((beg (point))) (mapc (quote insert) thetoc) (insert "</div>\n") (while (re-search-backward "<li>[ 
\n	]*</li>\n?" beg t) (replace-match "")))) (goto-char (point-min)) (while (re-search-forward "<p>[ 
\n	]*</p>" nil t) (replace-match "")) (goto-char (point-min)) (goto-char (point-min)) (let (beg end n) (while (setq beg (next-single-property-change (point) (quote org-whi
 tespace))) (setq n (get-text-property beg (quote org-whitespace)) end (next-single-property-change beg (quote org-whitespace))) (goto-char beg) (delete-region beg end) (insert (format "<span style=\"visibility:hidden;\">%s</span>" (make-string n 120))))) (goto-char (point-min)) (when (looking-at "\\s-+\n") (replace-match "")) (remove-text-properties (point-min) (point-max) (quote (display t))) (run-hooks (quote org-export-html-final-hook)) (or to-buffer (save-buffer)) (goto-char (point-min)) (or (org-export-push-to-kill-ring "HTML") (message "Exporting... done")) (if (eq to-buffer (quote string)) (prog1 (buffer-substring (point-min) (point-max)) (kill-buffer (current-buffer))) (current-buffer)))
  (let* ((opt-plist (org-export-process-option-filters (org-combine-plists (org-default-export-plist) ext-plist (org-infile-export-plist)))) (body-only (or body-only (plist-get opt-plist :body-only))) (style (concat (if (plist-get opt-plist :style-include-default) org-export-html-style-default) (plist-get opt-plist :style) (plist-get opt-plist :style-extra) "\n" (if (plist-get opt-plist :style-include-scripts) org-export-html-scripts))) (html-extension (plist-get opt-plist :html-extension)) valid thetoc have-headings first-heading-pos (odd org-odd-levels-only) (region-p (org-region-active-p)) (rbeg (and region-p (region-beginning))) (rend (and region-p (region-end))) (subtree-p (if (plist-get opt-plist :ignore-subtree-p) nil (when region-p (save-excursion (goto-char rbeg) (and (org-at-head
 ing-p) (>= ... rend)))))) (level-offset (if subtree-p (save-excursion (goto-char rbeg) (+ (funcall outline-level) (if org-odd-levels-only 1 0))) 0)) (opt-plist (setq org-export-opt-plist (if
  subtree-p (org-export-add-subtree-options opt-plist rbeg) opt-plist))) (org-current-export-dir (or pub-dir (org-export-directory :html opt-plist))) (org-current-export-file buffer-file-name) (level 0) (line "") (origline "") txt todo (umax nil) (umax-toc nil) (filename (if to-buffer nil (expand-file-name (concat (file-name-sans-extension (or ... ...)) "." html-extension) (file-name-as-directory (or pub-dir (org-export-directory :html opt-plist)))))) (current-dir (if buffer-file-name (file-name-directory buffer-file-name) default-directory)) (buffer (if to-buffer (cond ((eq to-buffer (quote string)) (get-buffer-create "*Org HTML Export*")) (t (get-buffer-create to-buffer))) (find-file-noselect filename))) (org-levels-open (make-vector org-level-max nil)) (date (plist-get opt-plist :date))
  (author (plist-get opt-plist :author)) (html-validation-link (or org-export-html-validation-link "")) (title (org-html-expand (or (and subtree-p (org-export-get-title-from-subtree)) (plist-
 get opt-plist :title) (and (not body-only) (not (plist-get opt-plist :skip-before-1st-heading)) (org-export-grab-title-from-buffer)) (and buffer-file-name (file-name-sans-extension (file-name-nondirectory buffer-file-name))) "UNTITLED"))) (link-up (and (plist-get opt-plist :link-up) (string-match "\\S-" (plist-get opt-plist :link-up)) (plist-get opt-plist :link-up))) (link-home (and (plist-get opt-plist :link-home) (string-match "\\S-" (plist-get opt-plist :link-home)) (plist-get opt-plist :link-home))) (dummy (setq opt-plist (plist-put opt-plist :title title))) (html-table-tag (plist-get opt-plist :html-table-tag)) (quote-re0 (concat "^[ 	]*" org-quote-string "\\>")) (quote-re (concat "^\\(\\*+\\)\\([ 	]+" org-quote-string "\\>\\)")) (inquote nil) (infixed nil) (inverse nil) (email (plis
 t-get opt-plist :email)) (language (plist-get opt-plist :language)) (keywords (plist-get opt-plist :keywords)) (description (plist-get opt-plist :description)) (lang-words nil) (head-count 0
 ) cnt (start 0) (coding-system (and (boundp (quote buffer-file-coding-system)) buffer-file-coding-system)) ...) (let ((inhibit-read-only t)) (org-unmodified (remove-text-properties (point-min) (point-max) (quote (:org-license-to-kill t))))) (message "Exporting...") (setq org-min-level (org-get-min-level lines level-offset)) (setq org-last-level org-min-level) (org-init-section-numbers) (cond ((and date (string-match "%" date)) (setq date (format-time-string date))) (date) (t (setq date (format-time-string "%Y-%m-%d %T %Z")))) (setq lang-words (or (assoc language org-export-language-setup) (assoc "en" org-export-language-setup))) (set-buffer buffer) (let ((inhibit-read-only t)) (erase-buffer)) (fundamental-mode) (org-install-letbind) (and (fboundp (quote set-buffer-file-coding-system)) (se
 t-buffer-file-coding-system coding-system-for-write)) (let ((case-fold-search nil) (org-odd-levels-only odd)) (mapc (lambda (x) (set (make-local-variable (nth 2 x)) (plist-get opt-plist (car
  x)))) org-export-plist-vars) (setq umax (if arg (prefix-numeric-value arg) org-export-headline-levels)) (setq umax-toc (if (integerp org-export-with-toc) (min org-export-with-toc umax) umax)) (unless body-only (insert (format "%s\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"\n               \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\n<html xmlns=\"http://www.w3.org/1999/xhtml\"\nlang=\"%s\" xml:lang=\"%s\">\n<head>\n<title>%s</title>\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=%s\"/>\n<meta name=\"generator\" content=\"Org-mode\"/>\n<meta name=\"generated\" content=\"%s\"/>\n<meta name=\"author\" content=\"%s\"/>\n<meta name=\"description\" content=\"%s\"/>\n<meta name=\"keywords\" content=\"%s\"/>\n%s\n%s\n</head>\n<body>\n<div id=\"content\"
 >\n%s\n" (format (or (and ... org-export-html-xml-declaration) (cdr ...) (cdr ...) "") (or charset "iso-8859-1")) language language title (or charset "iso-8859-1") date author description ke
 ywords style mathjax (if (or link-up link-home) (concat (format org-export-html-home/up-format ... ...) "\n") ""))) (when (plist-get opt-plist :html-preamble) (let ((html-pre (plist-get opt-plist :html-preamble))) (cond ((stringp html-pre) (insert ...)) ((functionp html-pre) (funcall html-pre opt-plist)) (t (insert ...)))))) (if (and org-export-with-toc (not body-only)) (progn (push (format "<h%d>%s</h%d>\n" org-export-html-toplevel-hlevel (nth 3 lang-words) org-export-html-toplevel-hlevel) thetoc) (push "<div id=\"text-table-of-contents\">\n" thetoc) (push "<ul>\n<li>" thetoc) (setq lines (mapcar (quote (lambda ... ... line)) lines)) (while (> org-last-level (1- org-min-level)) (setq org-last-level (1- org-last-level)) (push "</li>\n</ul>\n" thetoc)) (push "</div>\n" thetoc) (setq thetoc
  (if have-headings (nreverse thetoc) nil)))) (setq head-count 0) (org-init-section-numbers) (org-open-par) (while (setq line (pop lines) origline line) (catch (quote nextline) (when (and inq
 uote (string-match "^\\*+ " line)) (insert "</pre>\n") (org-open-par) (setq inquote nil)) (when inquote (insert (org-html-protect line) "\n") (throw (quote nextline) nil)) (when (and org-export-with-fixed-width (string-match "^[ 	]*:\\(\\([ 	]\\|$\\)\\(.*\\)\\)" line)) (when (not infixed) (setq infixed t) (org-close-par-maybe) (insert "<pre class=\"example\">\n")) (insert (org-html-protect (match-string 3 line)) "\n") (when (or (not lines) (not ...)) (setq infixed nil) (insert "</pre>\n") (org-open-par)) (throw (quote nextline) nil)) (when (and (get-text-property 0 (quote org-protected) line) (not (< ... ...))) (let (par (ind ...)) (when (re-search-backward "\\(<p>\\)\\([ 	
\n]*\\)\\=" ... t) (setq par ...) (replace-match "\\2\n")) (insert line "\n") (while (and lines ... ...) (insert ... "\n")) (and par (insert "<p>\n"))) (throw (quote nextline) nil)) (when (equal "ORG-BLOCKQUOTE-START" line) (org-close-par-maybe) (insert "<blockquote>\n") (org-open-par) (throw (quote nextl
 ine) nil)) (when (equal "ORG-BLOCKQUOTE-END" line) (org-close-par-maybe) (insert "\n</blockquote>\n") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-START" line) (org-close-par-maybe) (insert "\n<p class=\"verse\">\n") (setq org-par-open t) (setq inverse t) (throw (quote nextline) nil)) (when (equal "ORG-VERSE-END" line) (insert "</p>\n") (setq org-par-open nil) (org-open-par) (setq inverse nil) (throw (quote nextline) nil)) (when (equal "ORG-CENTER-START" line) (org-close-par-maybe) (insert "\n<div style=\"text-align: center\">") (org-open-par) (throw (quote nextline) nil)) (when (equal "ORG-CENTER-END" line) (org-close-par-maybe) (insert "\n</div>") (org-open-par) (throw (quote nextline) nil)) (run-hooks (quote org-export-html-after-blockquotes-hook)) (when inverse
  (let ((i ...)) (if (> i 0) (setq line ...)) (unless (string-match "\\\\\\\\[ 	]*$" line) (setq line ...)))) (setq start 0) (while (string-match "<<<?\\([^<>]*\\)>>>?\\((INVISIBLE)\\)?[ 	]*\
 n?" line start) (cond ((get-text-property ... ... line) (setq start ...)) ((match-end 2) (setq line ...)) ((and org-export-with-toc ...) (setq line ...)) (t (setq line ...)))) (setq line (org-html-handle-time-stamps line)) (or (string-match org-table-hline-regexp line) (setq line (org-html-expand line))) (setq line (org-html-handle-links line opt-plist)) (if (and (string-match org-todo-line-regexp line) (match-beginning 2)) (setq line (concat (substring line 0 ...) "<span class=\"" (if ... "done" "todo") " " (match-string 2 line) "\"> " (org-export-html-get-todo-kwd-class-name ...) "</span>" (substring line ...)))) (when org-export-with-footnotes (setq start 0) (while (string-match "\\([^* 	].*?\\)\\[\\([0-9]+\\)\\]" line start) (if (get-text-property ... ... line) (setq start ...) (let .
 .. ... ...)))) (cond ((string-match "^\\(\\*+\\)[ 	]+\\(.*\\)" line) (setq level (org-tr-level ...) txt (match-string 2 line)) (if (string-match quote-re0 txt) (setq txt ...)) (if (<= level 
 ...) (setq head-count ...)) (setq first-heading-pos (or first-heading-pos ...)) (org-html-level-start level txt umax (and org-export-with-toc ...) head-count) (when (string-match quote-re line) (org-close-par-maybe) (insert "<pre>") (setq inquote t))) ((and org-export-with-tables (string-match "^\\([ 	]*\\)\\(|\\|\\+-+\\+\\)" line)) (when (not table-open) (setq table-open t table-buffer nil table-orig-buffer nil)) (setq table-buffer (cons line table-buffer) table-orig-buffer (cons origline table-orig-buffer)) (when (or ... ...) (setq table-open nil table-buffer ... table-orig-buffer ...) (org-close-par-maybe) (insert ...))) (t (when (get-text-property 0 ... line) (setq line ...)) (when (string-match "^[ 	]*-\\{5,\\}[ 	]*$" line) (if org-par-open ... ...) (throw ... nil)) (if (string-match
  "^ [-+*]-\\|^[ 	]*$" line) (org-open-par)) (when org-export-with-footnotes (when ... ...) (when ... ... ...)) (cond (... ...) (org-export-preserve-breaks ...)) (let (...) (while ... ... ...
 )) (insert line "\n"))))) (when inquote (insert "</pre>\n") (org-open-par)) (org-html-level-start 1 nil umax (and org-export-with-toc (<= level umax)) head-count) (when (and (> umax 0) first-heading-pos) (insert "</div>\n")) (save-excursion (goto-char (point-min)) (while (re-search-forward "<p class=\"footnote\">[^footnotes (insert (format org-export-html-footnotes-section (nth 4 lang-words) (mapconcat (quote identity) (nreverse footnotes) "\n")) "\n")) (let ((bib (org-export-html-get-bibliography))) (when bib (insert "\n" bib "\n"))) (unless body-only (let ((html-post (plist-get opt-plist :html-postamble)) (email (mapconcat (lambda ... ...) (split-string email ",+ *") ", ")) (creator-info (concat "Org version " org-version " with Emacs version " (number-to-string emacs-major-version)))) 
 (when (plist-get opt-plist :html-postamble) (cond ((stringp html-post) (insert "<div id=\"postamble\">\n") (insert ...) (insert "</div>")) ((functionp html-post) (funcall html-post opt-plist
 )) ((eq html-post ...) (insert "<div id=\"postamble\">\n") (when ... ...) (when ... ...) (when ... ...) (when ... ...) (insert html-validation-link "\n</div>")) (t (insert "<div id=\"postamble\">\n") (insert ...) (insert "</div>")))))) (if org-export-html-with-timestamp (insert org-export-html-html-helper-timestamp)) (unless body-only (insert "\n</div>\n</body>\n</html>\n")) (unless (plist-get opt-plist :buffer-will-be-killed) (normal-mode) (if (eq major-mode (default-value (quote major-mode))) (html-mode))) (goto-char (point-min)) (when thetoc (if (or (re-search-forward "<p>\\s-*\\[TABLE-OF-CONTENTS\\]\\s-*</p>" nil t) (re-search-forward "\\[TABLE-OF-CONTENTS\\]" nil t)) (progn (goto-char (match-beginning 0)) (replace-match "")) (goto-char first-heading-pos) (when (looking-at "\\s-*</p>"
 ) (goto-char (match-end 0)) (insert "\n"))) (insert "<div id=\"table-of-contents\">\n") (let ((beg (point))) (mapc (quote insert) thetoc) (insert "</div>\n") (while (re-search-backward "<li>
 [ 
\n	]*</li>\n?" beg t) (replace-match "")))) (goto-char (point-min)) (while (re-search-forward "<p>[ 
\n	]*</p>" nil t) (replace-match "")) (goto-char (point-min)) (goto-char (point-min)) (let (beg end n) (while (setq beg (next-single-property-change (point) (quote org-whitespace))) (setq n (get-text-property beg (quote org-whitespace)) end (next-single-property-change beg (quote org-whitespace))) (goto-char beg) (delete-region beg end) (insert (format "<span style=\"visibility:hidden;\">%s</span>" (make-string n 120))))) (goto-char (point-min)) (when (looking-at "\\s-+\n") (replace-match "")) (remove-text-properties (point-min) (point-max) (quote (display t))) (run-hooks (quote org-export-html-final-hook)) (or to-buffer (save-buffer)) (goto-char (point-min)) (or (org-export-push-to-kill-ring "HTML") (message "Exporting... done")) (if (eq to-buffer (quote string)) (prog1 (buffer-substring 
 (point-min) (point-max)) (kill-buffer (current-buffer))) (current-buffer))))
  org-export-as-html(nil)
  call-interactively(org-export-as-html)
  org-export(nil)
  call-interactively(org-export nil nil)

Re: Future Worg publishing failure :)

[Bastien]

Hi Nick,

Nick Dokos <nicholas.dokos@hp.com> writes:

> Current org code takes the 14. as an item in a numbered list.  When
> exporting to HTML, this causes an error in org-html-export-list-line -
> hence the subject line. It's not a problem right now but it will be when
> orgmode.org gets the updated version. I reformatted the line to avoid
> the awkward newline, so the future publishing failure will not
> happen. 

Thanks for that!

> I'll let Nicolas worry about what should be done about the error.

Let's not leave Nicolas alone here :)  I'll take a look myself into it
over the week-end.

Best,

-- 
 Bastien

Re: Future Worg publishing failure :)

[Nicolas]

Hello,

Bastien <bzg@altern.org> writes:

>> Current org code takes the 14. as an item in a numbered list.  When
>> exporting to HTML, this causes an error in org-html-export-list-line -
>> hence the subject line. It's not a problem right now but it will be when
>> orgmode.org gets the updated version. I reformatted the line to avoid
>> the awkward newline, so the future publishing failure will not
>> happen. 
>
> Thanks for that!
>
>> I'll let Nicolas worry about what should be done about the error.
>
> Let's not leave Nicolas alone here :)  I'll take a look myself into it
> over the week-end.

Phew, what a relief ;)

The only solution I could think of is somewhere in the patchwork server
("Auto-fill shouldn't insert new items").

Regards,

-- 
Nicolas

Re: Re: Future Worg publishing failure :)

[Nick Dokos]

Nicolas <n.goaziou@gmail.com> wrote:

> Hello,
> 
> Bastien <bzg@altern.org> writes:
> 
> >> Current org code takes the 14. as an item in a numbered list.  When
> >> exporting to HTML, this causes an error in org-html-export-list-line -
> >> hence the subject line. It's not a problem right now but it will be when
> >> orgmode.org gets the updated version. I reformatted the line to avoid
> >> the awkward newline, so the future publishing failure will not
> >> happen. 
> >
> > Thanks for that!
> >
> >> I'll let Nicolas worry about what should be done about the error.
> >
> > Let's not leave Nicolas alone here :)  I'll take a look myself into it
> > over the week-end.
> 

By the time I find my way through the code, Nicolas will have solved it 10
times over.

> Phew, what a relief ;)
> 
> The only solution I could think of is somewhere in the patchwork server
> ("Auto-fill shouldn't insert new items").
> 

Are you saying that the patchwork server introduced this? Or that the
patchwork server should solve it? In the case I stumbled upon (a Worg
file), the patchwork server is nowhere in sight, I think: the change was
(I'm guessing here) directly committed, so maybe the original writer had
auto-fill turned on, but maybe not and just typed it that way. So
neither the patchwork server nor making auto-fill smarter would provide
a guaranteed solution. But maybe there is no such thing.

Perhaps a heuristic in html export to just take care of the error: if
it looks like a numbered list item but there is no item body, bail and
assume it's part of the text. Or a combination of that together with
the item number > 1. Would that work?

Nick

> Regards,
> 
> -- 
> Nicolas
> 

Re: Future Worg publishing failure :)

[Nicolas]

Hello,

Nick Dokos <nicholas.dokos@hp.com> writes:

>> The only solution I could think of is somewhere in the patchwork server
>> ("Auto-fill shouldn't insert new items").
>> 
>
> Are you saying that the patchwork server introduced this? Or that the
> patchwork server should solve it? In the case I stumbled upon (a Worg
> file), the patchwork server is nowhere in sight, I think: the change was
> (I'm guessing here) directly committed, so maybe the original writer had
> auto-fill turned on, but maybe not and just typed it that way. So
> neither the patchwork server nor making auto-fill smarter would provide
> a guaranteed solution. But maybe there is no such thing.

I'm not sure to understand. I mean that there is a patch waiting to be
processed in the patchwork server, that should get us as close to the
solution as I can think of (so, probably not very close).

It is true that the patch only solves the problem if it would happen
with auto-fill (or fill-paragraph). On the other hand, if the original
writer typed it that way, it's an user problem, and I don't think we
should add cruft to solve it.

> Perhaps a heuristic in html export to just take care of the error: if
> it looks like a numbered list item but there is no item body, bail and
> assume it's part of the text.

I introduced support for empty items on purpose. That would be
a regression.

> Or a combination of that together with the item number > 1. Would that
> work?

It would partly work. But:
- You would get false positives (rarely, but still),
- It wouldn't handle case when line, beside the bullet, isn't empty,
- It isn't only about HTML export, not even about export, as the same
  situation happens in Org buffers. 

Again, preventing the problem to happen automatically, i.e. without the
user knowing for sure about it, is taken care of by the patch (provided
it doesn't break anything else, thus its journey on the patchwork
server). In every other case, we can assume that the user knows (should
know) both Org syntax and what he is doing.

Now, for already introduced problems, it is indeed possible to build
a function using heuristics to scan files, and when matching, offer to
join lines and fill-paragraph. I don't think there are enough cases to
justify this, though.

Regards,

-- 
Nicolas

Re: Future Worg publishing failure :)

[Nick Dokos]

Nicolas <n.goaziou@gmail.com> wrote:

> Hello,
> 
> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> >> The only solution I could think of is somewhere in the patchwork server
> >> ("Auto-fill shouldn't insert new items").
> >> 
> >
> > Are you saying that the patchwork server introduced this? Or that the
> > patchwork server should solve it? In the case I stumbled upon (a Worg
> > file), the patchwork server is nowhere in sight, I think: the change was
> > (I'm guessing here) directly committed, so maybe the original writer had
> > auto-fill turned on, but maybe not and just typed it that way. So
> > neither the patchwork server nor making auto-fill smarter would provide
> > a guaranteed solution. But maybe there is no such thing.
> 
> I'm not sure to understand. I mean that there is a patch waiting to be
> processed in the patchwork server, that should get us as close to the
> solution as I can think of (so, probably not very close).
> 
Ah, OK - I was just dense: I misread it completely.

> It is true that the patch only solves the problem if it would happen
> with auto-fill (or fill-paragraph). On the other hand, if the original
> writer typed it that way, it's an user problem, and I don't think we
> should add cruft to solve it.
> 
> > Perhaps a heuristic in html export to just take care of the error: if
> > it looks like a numbered list item but there is no item body, bail and
> > assume it's part of the text.
> 
> I introduced support for empty items on purpose. That would be
> a regression.
> 
> > Or a combination of that together with the item number > 1. Would that
> > work?
> 
> It would partly work. But:
> - You would get false positives (rarely, but still),
> - It wouldn't handle case when line, beside the bullet, isn't empty,
> - It isn't only about HTML export, not even about export, as the same
>   situation happens in Org buffers. 
> 
> Again, preventing the problem to happen automatically, i.e. without the
> user knowing for sure about it, is taken care of by the patch (provided
> it doesn't break anything else, thus its journey on the patchwork
> server). In every other case, we can assume that the user knows (should
> know) both Org syntax and what he is doing.
> 
> Now, for already introduced problems, it is indeed possible to build
> a function using heuristics to scan files, and when matching, offer to
> join lines and fill-paragraph. I don't think there are enough cases to
> justify this, though.
> 

OK: agreed - we just fix existing org files on a case-by-case basis.

So manually inserting "14." at the beginning of the line is user error,
auto-fill is taken care of by your patch. However, there is still the
problem that an empty item in a numbered list will trigger the error
that I posted, so org-html-export-list-line will need to be taught how
to deal with an empty list item - correct?

Nick

Re: Future Worg publishing failure :)

[Nick Dokos]

I have the same problem with replying/all that I had before when
trying to reply to Julien.

Apologies again: I'll try to figure it out before sending mail
again.

Nick

Re: Future Worg publishing failure :)

[Nicolas]

Nick Dokos <nicholas.dokos@hp.com> writes:

> However, there is still the problem that an empty item in a numbered
> list will trigger the error that I posted, so
> org-html-export-list-line will need to be taught how to deal with an
> empty list item - correct?

Correct. I overlooked that part of the problem, being focused on the
number interpretation as a list item.

This is now fixed in master, for HTML and DocBook.

Thanks !

Regards,

-- 
Nicolas

Re: Re: Future Worg publishing failure :)

[Nick Dokos]

Nicolas <n.goaziou@gmail.com> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > However, there is still the problem that an empty item in a numbered
> > list will trigger the error that I posted, so
> > org-html-export-list-line will need to be taught how to deal with an
> > empty list item - correct?
> 
> Correct. I overlooked that part of the problem, being focused on the
> number interpretation as a list item.
> 
> This is now fixed in master, for HTML and DocBook.
> 

Confirm the fix for HTML. I've never set up the DocBook tool chain, so
I can't check that.

Thanks,
Nick

Re: Future Worg publishing failure :)

[Matt Lundin]

Nicolas <n.goaziou@gmail.com> writes:

> It is true that the patch only solves the problem if it would happen
> with auto-fill (or fill-paragraph). On the other hand, if the original
> writer typed it that way, it's an user problem, and I don't think we
> should add cruft to solve it.

FWIW, I wrote the original text and can confirm that it resulted from
calling fill-paragraph.

Best,
Matt

orgmode BEAMER scaling image

[Gilberto]

[-- Attachment #1: Type: text/plain, Size: 469 bytes --]

In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW, thanks) gives an example of using an image, and writes

> I have added an attribute to the image to tell LaTeX to scale the image to the full width of the column.


Can I add a similar attribute to my images without having to tweak the .tex file? In other words, can I directly do that in org beamer mode?

Gilberto Conde
ah.gilberto.c@gmail.com
___________________________________




[-- Attachment #2: Type: text/html, Size: 2189 bytes --]

Re: orgmode BEAMER scaling image

[John Hendy]

On Thu, Mar 24, 2011 at 11:35 AM, Gilberto <ah.gilberto.c@gmail.com> wrote:
> In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW,
> thanks) gives an example of using an image, and writes
>
> I have added an attribute to the image to tell LaTeX to scale the image to
> the full width of the column.
>
> Can I add a similar attribute to my images without having to tweak the .tex
> file? In other words, can I directly do that in org beamer mode?

You want the #+attr_latex feature to send export options to LaTeX[1].
Here's an example:

---------
* Section
** Slide name
*** Column 1 					      :BMCOL:B_ignoreheading:
    :PROPERTIES:
    :BEAMER_col: 0.45
    :BEAMER_env: ignoreheading
    :END:
Here's the text for column 1.

*** Column 2 					      :BMCOL:B_ignoreheading:
    :PROPERTIES:
    :BEAMER_col: 0.45
    :BEAMER_env: ignoreheading
    :END:

#+ATTR_LaTeX: width=0.95\textwidth
[[/here/is/the/path/to/your/image.jpg]]
----------

The width= option scales the image. \textwidth when used in the column
environment applies to the width of the *column* textwidth, not that
of the actual total page size.

I've found that using 0.45 for the :BEAMER_col width made things look
a little better, but that might have been due to my custom template.
Use 0.5 if you want to make it bigger and it works for you.

[1] http://orgmode.org/manual/Images-in-LaTeX-export.html


Hope that helps,
John

> Gilberto Conde
> ah.gilberto.c@gmail.com
> ___________________________________
>
>
>

Re: orgmode BEAMER scaling image

[Eric S Fraga]

Gilberto <ah.gilberto.c@gmail.com> writes:

> In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW,
> thanks) gives an example of using an image, and writes

You're very welcome!

>
>> I have added an attribute to the image to tell LaTeX to scale the
>> image to the full width of the column.
>
>
> Can I add a similar attribute to my images without having to tweak the
> .tex file? In other words, can I directly do that in org beamer mode?

John Hendy has already answered but I guess you are implying that the
tutorial on Worg is not clear about how that is done.  The example code
snippet has the #+ATTR_LATEX line in it.  I guess I should be more
explicit in the text?  Thanks for highlighting this!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)

Re: orgmode BEAMER scaling image

[Gilberto]

It worked great. Thanks a lot!!!
Gilberto

On 3/24/2011 9:26 AM, John Hendy wrote:
> On Thu, Mar 24, 2011 at 11:35 AM, Gilberto<ah.gilberto.c@gmail.com>  wrote:
>> In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW,
>> thanks) gives an example of using an image, and writes
>>
>> I have added an attribute to the image to tell LaTeX to scale the image to
>> the full width of the column.
>>
>> Can I add a similar attribute to my images without having to tweak the .tex
>> file? In other words, can I directly do that in org beamer mode?
> You want the #+attr_latex feature to send export options to LaTeX[1].
> Here's an example:
>
> ---------
> * Section
> ** Slide name
> *** Column 1 					      :BMCOL:B_ignoreheading:
>      :PROPERTIES:
>      :BEAMER_col: 0.45
>      :BEAMER_env: ignoreheading
>      :END:
> Here's the text for column 1.
>
> *** Column 2 					      :BMCOL:B_ignoreheading:
>      :PROPERTIES:
>      :BEAMER_col: 0.45
>      :BEAMER_env: ignoreheading
>      :END:
>
> #+ATTR_LaTeX: width=0.95\textwidth
> [[/here/is/the/path/to/your/image.jpg]]
> ----------
>
> The width= option scales the image. \textwidth when used in the column
> environment applies to the width of the *column* textwidth, not that
> of the actual total page size.
>
> I've found that using 0.45 for the :BEAMER_col width made things look
> a little better, but that might have been due to my custom template.
> Use 0.5 if you want to make it bigger and it works for you.
>
> [1] http://orgmode.org/manual/Images-in-LaTeX-export.html
>
>
> Hope that helps,
> John
>
>> Gilberto Conde
>> ah.gilberto.c@gmail.com
>> ___________________________________
>>
>>
>>

Outlook replacement

[Henri-Paul Indiogine]

Greetings!

A few days ago I noticed a headline somewhere, possibly
http://linuxtoday.com or http://lxer.com, that read "an Outlook
replacement for Linux".

Then I thought, I have an Emacs gnus frame next to a frame with my
agenda.org.   I guess that is my "Outlook replacement".  Also, regularly I
export my agenda to Google Calendar.   So, I am not missing anything
from Outlook.  Yes, I know, I can not schedule appointments in a
corporate setting, but I work more or less alone.

Best,
Henri-Paul



-- 
Henri-Paul Indiogine
Email: hindiogine@gmail.com
Running: Ubuntu Linux 10.10, Emacs 24.0.50.1, org-mode 7.4

[bug] Problem with Worg (html?) publishing (was Re: orgmode BEAMER scaling image)

[Eric S Fraga]

Gilberto <ah.gilberto.c@gmail.com> writes:

> That should help, but the thing is that the
>> |#+ATTR_LATEX| line
> is missing from the example:
>> *** A screenshot                                            :BMCOL:B_example:
>>      :PROPERTIES:
>>      :BEAMER_col: 0.6
>>      :BEAMER_env: example
>>      :END:
>>      [[file://../../images/org-beamer/a-simple-slide.png]]
> It'd be great if you could add it.
> I promise I'll check how to contribute to Worg so I can give a hand in
> situtations like this.
>
> Gilberto

Ah, this is a problem with the publishing of Worg as the original org
file on Worg has the line.  Thanks for noticing this.  I have cc-ed the
org list.  

For the list:

In the org-beamer tutorial (Worg/org-tutorials/org-beamer/tutorial.org),
I have the following:

,----
| 
| #+BEGIN_Example
| ,** Two columns
| 
| ,*** A block                                           :B_ignoreheading:BMCOL:
|     :PROPERTIES:
|     :BEAMER_env: ignoreheading
|     :BEAMER_col: 0.4
|     :END:
|     - this slide consists of two columns
|     - the first (left) column has no heading and consists of text
|     - the second (right) column has an image and is enclosed in an
|       @example@ block
| 
| ,*** A screenshot                                            :BMCOL:B_example:
|     :PROPERTIES:
|     :BEAMER_col: 0.6
|     :BEAMER_env: example
|     :END:
| ,    #+ATTR_LATEX: width=\textwidth
|     [[file://../../images/org-beamer/a-simple-slide.png]]
| #+END_Example
`----

Note the second last line of the example which sets the latex attribute
for the following image.  On export to HTML for publishing on the Worg
website, this line has magically *disappeared*!  The ',' is supposed to
protect this line but instead it disappears.

I have gone through the whole tutorial and this is the only line that
has disappeared.  My intuition is that the HTML export is ignoring all
LATEX attribute lines (as it should) but that maybe the regex for is
rather greedy?  However, I have looked at the code but have not seen
anywhere obvious where this happens -- all the regexs I found seem to be
pinned at the start of the line with only whitespace allowed before
the #+.

I'll leave this for the exports methinks...

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

Re: [bug] Problem with Worg (html?) publishing (was Re: orgmode BEAMER scaling image)

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:


> In the org-beamer tutorial (Worg/org-tutorials/org-beamer/tutorial.org),
> I have the following:
> 
> ,----
> | 
> | #+BEGIN_Example
> | ,** Two columns
> | 
> | ,*** A block                                           :B_ignoreheading:BMCOL:
> |     :PROPERTIES:
> |     :BEAMER_env: ignoreheading
> |     :BEAMER_col: 0.4
> |     :END:
> |     - this slide consists of two columns
> |     - the first (left) column has no heading and consists of text
> |     - the second (right) column has an image and is enclosed in an
> |       @example@ block
> | 
> | ,*** A screenshot                                            :BMCOL:B_example:
> |     :PROPERTIES:
> |     :BEAMER_col: 0.6
> |     :BEAMER_env: example
> |     :END:
> | ,    #+ATTR_LATEX: width=\textwidth
> |     [[file://../../images/org-beamer/a-simple-slide.png]]
> | #+END_Example
> `----
> 
> Note the second last line of the example which sets the latex attribute
> for the following image.  On export to HTML for publishing on the Worg
> website, this line has magically *disappeared*!  The ',' is supposed to
> protect this line but instead it disappears.
> 
> I have gone through the whole tutorial and this is the only line that
> has disappeared.  My intuition is that the HTML export is ignoring all
> LATEX attribute lines (as it should) but that maybe the regex for is
> rather greedy?  However, I have looked at the code but have not seen
> anywhere obvious where this happens -- all the regexs I found seem to be
> pinned at the start of the line with only whitespace allowed before
> the #+.
> 

Your intuition is (almost) correct: in org-export-preprocess-string, the comma
is stripped by org-export-replace-src-segments-and-examples and the
ATTR_LATEX is stripped by org-export-select-backend-specific-text which 
very explicitly says:

,----
|       ...
|       ;; Delete #+attr_Backend: stuff of another backend. Those
|       ;; matching the current backend will be taken care of by
|       ;; `org-export-attach-captions-and-attributes'
|       ...
`----


Nick

Re: Outlook replacement

[Chris Malone]

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

Hi Henri-Paul,

While you've brought the topic up I /have/ been recently curious about
others' email setup and how they incorporate that into Emacs/org-mode?  I
notice several users send emails from within Emacs using org-mode syntax -
any tips on setting such a thing up?  Also, how do you handle outside email
accounts, for example, from gmail?

Chris

On Fri, Mar 25, 2011 at 2:56 PM, Henri-Paul Indiogine
<hindiogine@gmail.com>wrote:

> Greetings!
>
> A few days ago I noticed a headline somewhere, possibly
> http://linuxtoday.com or http://lxer.com, that read "an Outlook
> replacement for Linux".
>
> Then I thought, I have an Emacs gnus frame next to a frame with my
> agenda.org.   I guess that is my "Outlook replacement".  Also, regularly I
> export my agenda to Google Calendar.   So, I am not missing anything
> from Outlook.  Yes, I know, I can not schedule appointments in a
> corporate setting, but I work more or less alone.
>
> Best,
> Henri-Paul
>
>
>
> --
> Henri-Paul Indiogine
> Email: hindiogine@gmail.com
> Running: Ubuntu Linux 10.10, Emacs 24.0.50.1, org-mode 7.4
>
>

[-- Attachment #2: Type: text/html, Size: 1685 bytes --]

Comma-protection of Org blocks (was: [bug] Problem with Worg (html?) publishing)

[Sébastien Vauban]

Hi Eric (and Eric, and Dan, and ...),

Eric S Fraga wrote:
> In the org-beamer tutorial (Worg/org-tutorials/org-beamer/tutorial.org),
> I have the following:
>
> ,----
> | 
> | #+BEGIN_Example
> | ,** Two columns
> | 
> | ,*** A block                                           :B_ignoreheading:BMCOL:
> |     :PROPERTIES:
> |     :BEAMER_env: ignoreheading
> |     :BEAMER_col: 0.4
> |     :END:
> |     - this slide consists of two columns
> |     - the first (left) column has no heading and consists of text
> |     - the second (right) column has an image and is enclosed in an
> |       @example@ block
> | 
> | ,*** A screenshot                                            :BMCOL:B_example:
> |     :PROPERTIES:
> |     :BEAMER_col: 0.6
> |     :BEAMER_env: example
> |     :END:
> | ,    #+ATTR_LATEX: width=\textwidth
> |     [[file://../../images/org-beamer/a-simple-slide.png]]
> | #+END_Example
> `----
>
> Note the second last line of the example which sets the latex attribute
> for the following image.  On export to HTML for publishing on the Worg
> website, this line has magically *disappeared*!  The ',' is supposed to
> protect this line but instead it disappears.

This makes me think of a request I briefly discussed with Carsten and Bastien,
the day of Fosdem.

The "comma-protection" causes troubles when M-q comes into play.

For the sake of clarity -- I hope --, an example (for my Isodoc letters in Org):

    * Body
    #+srcname: body
    #+begin_src org :results latex
    ,Ik ben het totaalbedrag van de omzet 2010 vergeten op te nemen. De ontbrekende
    ,gegeven voor mijn kleine onderneming is 0,00 EUR (nul euro).
    #+end_src

    * Composed letter                                                  :noexport:
    #+begin_src latex :noweb yes :tangle yes
    \documentclass[11pt]{isodoc}

    \begin{document}
    \letter[language=dutch,to={\firstname~\lastname\\\addressi\\\postcode~\town\\\country},openingcomma={,}]{%
    <<body()>>
    }
    \end{document}
    #+end_src

The above "body" block is converted to LaTeX and its result is tangled into
the Isodoc LaTeX letter (here, voluntary kept to an ultra-minimal).

The prefix "," is not kept in the process, that's what is expected. But the
trouble is if I press M-q, because I add words to the sentences directly in
the whole Org buffer: pressing M-q will move all the leading "," everywhere in
the text, and then they will be transported up to the TeX file. Not what I
want.

The above user mistake (pressing M-q, what puts the leading commas everywhere,
letting them loose their initial meaning) -- is it really an error? -- would
have had no impact (or much much less), would the prefix be a space, for
example...

Hence, questions:

- would it be possible to replace the comma by something more neutral (maybe a
  space, or a non-breaking space for example) for HTML/LaTeX exports?

- would it be possible to put the "protecting prefix" only when needed
  (automatic detection when TAB'ing), or let it be specified by the user?

- is there maybe an alternative for the above Org/TeX problem (conversion +
  tangling)?

Best regards,
  Seb

-- 
Sébastien Vauban

Re: Outlook replacement

[John Hendy]

On Fri, Mar 25, 2011 at 1:56 PM, Henri-Paul Indiogine
<hindiogine@gmail.com> wrote:
> Greetings!
>
> A few days ago I noticed a headline somewhere, possibly
> http://linuxtoday.com or http://lxer.com, that read "an Outlook
> replacement for Linux".
>
> Then I thought, I have an Emacs gnus frame next to a frame with my
> agenda.org.   I guess that is my "Outlook replacement".  Also, regularly I
> export my agenda to Google Calendar.   So, I am not missing anything
> from Outlook.  Yes, I know, I can not schedule appointments in a
> corporate setting, but I work more or less alone.
>

I would love to do this. Unfortunately, it is limiting in a corporate
setting -- my IMAP/POP ports are blocked (using emacs for personal
email is out), the admins have not enabled IMAP/POP on the company
Lotus Notes Domino server (using emacs for work emails is out), and
yes, no scheduling would work from emacs through Domino innards,
probably.

There is some hope: http://bit.ly/fEkWrN

They've created a command line interface to Lotus Notes that works...
but only 32bit (I have to chroot into a 32bit environment) and one
would have to parse everything that came through to make it usable and
also write elisp functions that sent Lotus Notes commands via the
command line client.

Anyway, I *love* the idea of doing this... but it's quite difficult
when the "corporate world" is against you!


John


> Best,
> Henri-Paul
>
>
>
> --
> Henri-Paul Indiogine
> Email: hindiogine@gmail.com
> Running: Ubuntu Linux 10.10, Emacs 24.0.50.1, org-mode 7.4
>
>

Re: [bug] Problem with Worg (html?) publishing (was Re: orgmode BEAMER scaling image)

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> 
> 
> > In the org-beamer tutorial (Worg/org-tutorials/org-beamer/tutorial.org),
> > I have the following:
> > 
> > ,----
> > | 
> > | #+BEGIN_Example
> > | ,** Two columns
> > | 
> > | ,*** A block                                           :B_ignoreheading:BMCOL:
> > |     :PROPERTIES:
> > |     :BEAMER_env: ignoreheading
> > |     :BEAMER_col: 0.4
> > |     :END:
> > |     - this slide consists of two columns
> > |     - the first (left) column has no heading and consists of text
> > |     - the second (right) column has an image and is enclosed in an
> > |       @example@ block
> > | 
> > | ,*** A screenshot                                            :BMCOL:B_example:
> > |     :PROPERTIES:
> > |     :BEAMER_col: 0.6
> > |     :BEAMER_env: example
> > |     :END:
> > | ,    #+ATTR_LATEX: width=\textwidth
> > |     [[file://../../images/org-beamer/a-simple-slide.png]]
> > | #+END_Example
> > `----
> > 
> > Note the second last line of the example which sets the latex attribute
> > for the following image.  On export to HTML for publishing on the Worg
> > website, this line has magically *disappeared*!  The ',' is supposed to
> > protect this line but instead it disappears.
> > 
> > I have gone through the whole tutorial and this is the only line that
> > has disappeared.  My intuition is that the HTML export is ignoring all
> > LATEX attribute lines (as it should) but that maybe the regex for is
> > rather greedy?  However, I have looked at the code but have not seen
> > anywhere obvious where this happens -- all the regexs I found seem to be
> > pinned at the start of the line with only whitespace allowed before
> > the #+.
> > 
> 
> Your intuition is (almost) correct: in org-export-preprocess-string, the comma
> is stripped by org-export-replace-src-segments-and-examples and the
> ATTR_LATEX is stripped by org-export-select-backend-specific-text which 
> very explicitly says:
> 
> ,----
> |       ...
> |       ;; Delete #+attr_Backend: stuff of another backend. Those
> |       ;; matching the current backend will be taken care of by
> |       ;; `org-export-attach-captions-and-attributes'
> |       ...
> `----
> 
> 

Commenting out the two forms that follow this comment preserve the ATTR_LATEX,
but that's obviously not *the* fix:

,----
|       ...
|       ;; Delete #+attr_Backend: stuff of another backend. Those
|       ;; matching the current backend will be taken care of by
|       ;; `org-export-attach-captions-and-attributes'
|       ;; <ND>
|       ;; (goto-char (point-min))
|       ;; (while (re-search-forward (concat "^\\([ \t]*\\)#\\+attr_" (cadr fmt)
|       ;; 					":[ \t]*\\(.*\\)") nil t)
|       ;; 	(setq ind (org-get-indentation))
|       ;; 	(when (not (eq (car fmt) org-export-current-backend))
|       ;; 	  (delete-region (point-at-bol) (min (1+ (point-at-eol)) (point-max)))))
|       ;; </ND>
|       ;; Handle #+begin_backend and #+end_backend stuff
|       ...
`----

It's not clear to me how to fix it properly: at the point where
org-export-select-backend-specific-text is called, there's been a
partial transformation of the input, so the function is looking at the
following:

,----
| 
| #+BEGIN_HTML
| <pre class="example">
| *** A block                                           :B_ignoreheading:BMCOL:
|     :PROPERTIES:
|     :BEAMER_env: ignoreheading
|     :BEAMER_col: 0.4
|     :END:
|     - this slide consists of two columns
|     - the first (left) column has no heading and consists of text
|     - the second (right) column has an image and is enclosed in an
|       @example@ block
| 
| *** A screenshot                                            :BMCOL:B_example:
|     :PROPERTIES:
|     :BEAMER_col: 0.6
|     :BEAMER_env: example
|     :END:
|     #+ATTR_LATEX: width=\textwidth
|     [[file://../../images/org-beamer/a-simple-slide.png]]
| </pre>
| 
| #+END_HTML
| 
`----

It could use the fact that it is in a <pre> section - but the function
is generic wrt backends, so it doesn't worry about details like this.
Maybe a backend-specific function can be called at this point to deal
with it - and that can be smarter about how to transform it properly.

Nick

Re: Outlook replacement

[Eric S Fraga]

Chris Malone <chris.m.malone@gmail.com> writes:

> Hi Henri-Paul,
>
> While you've brought the topic up I /have/ been recently curious about
> others' email setup and how they incorporate that into Emacs/org-mode?  I
> notice several users send emails from within Emacs using org-mode syntax -
> any tips on setting such a thing up?  Also, how do you handle outside email
> accounts, for example, from gmail?
>
> Chris

The short answer is to use *Emacs* for your email, e.g. with gnus or
wanderlust or mh-e or vm or rmail or ...  after all, why would you want
to leave emacs and interrupt your flow!

I use gnus to read email from imap and pop servers as well as gmail
(imap).  I send via them as well.

Sending with org-mode syntax is basically down to "It's all text" (R)
;-)  Just type it in!  (of course, you can define yasnippets or whatever
to help)

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

Re: Outlook replacement

[Sébastien Vauban]

Chris Malone,

Chris Malone wrote:
> Hi Henri-Paul,
>
> While you've brought the topic up I /have/ been recently curious about
> others' email setup and how they incorporate that into Emacs/org-mode?  I
> notice several users send emails from within Emacs using org-mode syntax -
> any tips on setting such a thing up?

For the list and table stuff, here's an example from my .gnus file:

#+begin_src emacs-lisp
      ;; operates on messages you send
      (defun my/message-mode-hook ()

        ;; tab completion for alias in `.mailrc'
        (local-set-key (kbd "M-TAB") 'mail-abbrev-complete-alias)

        ;; enable automatic word-wrap when composing messages
        (setq fill-column 78)
        (turn-on-auto-fill)

        (when (try-require 'org-footnote)
          ;; default style used for footnoting is local to the Message being
          ;; written
          (set (make-local-variable 'org-footnote-auto-label) 'plain))

        (when (locate-library "org.el")

          ;; turn on the `org-mode' table editor
          (turn-on-orgtbl)

          ;; turn on orgstruct-mode
          (turn-on-orgstruct)

          ;; turn on the enhanced version of orgstruct-mode
          (turn-on-orgstruct++)))

      (add-hook 'message-mode-hook 'my/message-mode-hook)
#+end_src

For "Org-mode syntax" (putting codes as the above):

- simply copy/paste,
- select region with C-x C-x,
- demarcate block with C-c C-v C-d and insert the correct language (here:
  emacs-lisp).

> Also, how do you handle outside email accounts, for example, from gmail?

What do you mean?  Accessing them?  That can be done from Emacs, although I
did not set this up (yet).

Does the above meet your question?

Best regards,
  Seb

-- 
Sébastien Vauban

Re: Re: Outlook replacement

[Chris Malone]

[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]

Hi Seb and Eric,

Thanks for the advice - the info and sample .gnus file were great!

Chris

2011/3/25 Sébastien Vauban <wxhgmqzgwmuf@spammotel.com>

> Chris Malone,
>
> Chris Malone wrote:
> > Hi Henri-Paul,
> >
> > While you've brought the topic up I /have/ been recently curious about
> > others' email setup and how they incorporate that into Emacs/org-mode?  I
> > notice several users send emails from within Emacs using org-mode syntax
> -
> > any tips on setting such a thing up?
>
> For the list and table stuff, here's an example from my .gnus file:
>
> #+begin_src emacs-lisp
>      ;; operates on messages you send
>      (defun my/message-mode-hook ()
>
>        ;; tab completion for alias in `.mailrc'
>        (local-set-key (kbd "M-TAB") 'mail-abbrev-complete-alias)
>
>        ;; enable automatic word-wrap when composing messages
>        (setq fill-column 78)
>        (turn-on-auto-fill)
>
>        (when (try-require 'org-footnote)
>          ;; default style used for footnoting is local to the Message being
>          ;; written
>          (set (make-local-variable 'org-footnote-auto-label) 'plain))
>
>        (when (locate-library "org.el")
>
>          ;; turn on the `org-mode' table editor
>          (turn-on-orgtbl)
>
>          ;; turn on orgstruct-mode
>          (turn-on-orgstruct)
>
>          ;; turn on the enhanced version of orgstruct-mode
>          (turn-on-orgstruct++)))
>
>      (add-hook 'message-mode-hook 'my/message-mode-hook)
> #+end_src
>
> For "Org-mode syntax" (putting codes as the above):
>
> - simply copy/paste,
> - select region with C-x C-x,
> - demarcate block with C-c C-v C-d and insert the correct language (here:
>  emacs-lisp).
>
> > Also, how do you handle outside email accounts, for example, from gmail?
>
> What do you mean?  Accessing them?  That can be done from Emacs, although I
> did not set this up (yet).
>
> Does the above meet your question?
>
> Best regards,
>  Seb
>
> --
> Sébastien Vauban
>
>
>

[-- Attachment #2: Type: text/html, Size: 2651 bytes --]

[Link] Missing referenced page in Org-beamer

[Sébastien Vauban]

Hi Eric,

Check this out in section 4.3 of
http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
(last line).

Best regards,
  Seb

-- 
Sébastien Vauban

Re: [bug] Problem with Worg (html?) publishing

[Sébastien Vauban]

Hi Nick,

Nick Dokos wrote:
> It's not clear to me how to fix it properly: at the point where
> org-export-select-backend-specific-text is called, there's been a
> partial transformation of the input, so the function is looking at the
> following:
>
> ,----
> | 
> | #+BEGIN_HTML
> | <pre class="example">
> | *** A block                                           :B_ignoreheading:BMCOL:
> |     :PROPERTIES:
> |     :BEAMER_env: ignoreheading
> |     :BEAMER_col: 0.4
> |     :END:
> |     - this slide consists of two columns
> |     - the first (left) column has no heading and consists of text
> |     - the second (right) column has an image and is enclosed in an
> |       @example@ block
> | 
> | *** A screenshot                                            :BMCOL:B_example:
> |     :PROPERTIES:
> |     :BEAMER_col: 0.6
> |     :BEAMER_env: example
> |     :END:
> |     #+ATTR_LATEX: width=\textwidth
> |     [[file://../../images/org-beamer/a-simple-slide.png]]
> | </pre>
> | 
> | #+END_HTML
> | 
> `----
>
> It could use the fact that it is in a <pre> section - but the function
> is generic wrt backends, so it doesn't worry about details like this.
> Maybe a backend-specific function can be called at this point to deal
> with it - and that can be smarter about how to transform it properly.

A comment from a 30,000 feet view: why looking at <pre>?  Maybe looking at the
fact it is (still, at that point in time) a LaTeX order in a HTML block?

The opposite could be as generic: not interpreting HTML orders when in LaTeX
blocks?

Best regards,
  Seb

-- 
Sébastien Vauban

Re: Outlook replacement

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Chris Malone <chris.m.malone@gmail.com> writes:
> 
> > Hi Henri-Paul,
> >
> > While you've brought the topic up I /have/ been recently curious about
> > others' email setup and how they incorporate that into Emacs/org-mode?  I
> > notice several users send emails from within Emacs using org-mode syntax -
> > any tips on setting such a thing up?  Also, how do you handle outside email
> > accounts, for example, from gmail?
> >
> > Chris
> 
> The short answer is to use *Emacs* for your email, e.g. with gnus or
> wanderlust or mh-e or vm or rmail or ...  after all, why would you want
> to leave emacs and interrupt your flow!
> 
> I use gnus to read email from imap and pop servers as well as gmail
> (imap).  I send via them as well.
> 
> Sending with org-mode syntax is basically down to "It's all text" (R)
> ;-)  Just type it in!  (of course, you can define yasnippets or whatever
> to help)
> 

... and orgstruct-mode and orgtbl-mode help as well.

Nick

Re: Outlook replacement

[Nick Dokos]

John Hendy <jw.hendy@gmail.com> wrote:

> I would love to do this. Unfortunately, it is limiting in a corporate
> setting -- my IMAP/POP ports are blocked (using emacs for personal
> email is out), the admins have not enabled IMAP/POP on the company
> Lotus Notes Domino server (using emacs for work emails is out), and
> yes, no scheduling would work from emacs through Domino innards,
> probably.
> 

I don't understand: how do you send and receive mail?

Nick

Re: Outlook replacement

[John Hendy]

On Fri, Mar 25, 2011 at 4:38 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> John Hendy <jw.hendy@gmail.com> wrote:
>
>> I would love to do this. Unfortunately, it is limiting in a corporate
>> setting -- my IMAP/POP ports are blocked (using emacs for personal
>> email is out), the admins have not enabled IMAP/POP on the company
>> Lotus Notes Domino server (using emacs for work emails is out), and
>> yes, no scheduling would work from emacs through Domino innards,
>> probably.
>>
>
> I don't understand: how do you send and receive mail?
>

Work email: Lotus Notes
Personal email: Gmail web client

> Nick
>

Re: Re: Outlook replacement

[Nick Dokos]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:

> > Also, how do you handle outside email accounts, for example, from gmail?
> 
> What do you mean?  Accessing them?  That can be done from Emacs, although I
> did not set this up (yet).
> 

I use fetchmail for incoming mail and a local postfix server (sending
either through a company relay at work, or the smtp server of my ISP at
home) for outgoing mail: as far as emacs is concerned, all mail is
local.

Nick

Re: Re: [bug] Problem with Worg (html?) publishing

[Nick Dokos]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:

> >
> > It could use the fact that it is in a <pre> section - but the function
> > is generic wrt backends, so it doesn't worry about details like this.
> > Maybe a backend-specific function can be called at this point to deal
> > with it - and that can be smarter about how to transform it properly.
> 
> A comment from a 30,000 feet view: why looking at <pre>?  Maybe looking at the
> fact it is (still, at that point in time) a LaTeX order in a HTML block?
> 

Well, my view is maybe from 29000 feet, so I'm not sure I can see any
better than you can: the <pre> suggestion was because clearly anything
in a <pre> should not be transformed any further by the HTML exporter;
I'm not sure whether you can make similar (but perhaps somewhat weaker)
statements outside of a <pre>.

> The opposite could be as generic: not interpreting HTML orders when in LaTeX
> blocks?
> 

Yes, the way that is done today is draconian: delete the thing. If it's
not there, it cannot be interpreted. So off with its head! Dead men tell
no tales :-)

You are right: it is a generic problem - writing HTML examples to be
published with LaTeX would lead to the same difficulties.

Nick

Re: Outlook replacement

[Nick Dokos]

John Hendy <jw.hendy@gmail.com> wrote:

> On Fri, Mar 25, 2011 at 4:38 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> > John Hendy <jw.hendy@gmail.com> wrote:
> >
> >> I would love to do this. Unfortunately, it is limiting in a corporate
> >> setting -- my IMAP/POP ports are blocked (using emacs for personal
> >> email is out), the admins have not enabled IMAP/POP on the company
> >> Lotus Notes Domino server (using emacs for work emails is out), and
> >> yes, no scheduling would work from emacs through Domino innards,
> >> probably.
> >>
> >
> > I don't understand: how do you send and receive mail?
> >
> 
> Work email: Lotus Notes
> Personal email: Gmail web client
> 

OK, I see: thanks.

Re: [Link] Missing referenced page in Org-beamer

[Eric S Fraga]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> Hi Eric,
>
> Check this out in section 4.3 of
> http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
> (last line).

Thanks Seb.

Yes, that document ceased to exist a while back.  I forgot I was linking
to it.  It's the original document by Carsten, I believe, which was
superseded by the section in the info document.  I guess the link should
really be to there, section 12.6.6 to be exact.  Can somebody recommend
the best way to link there?

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)

Re: Outlook replacement

[Suvayu Ali]

On Fri, 25 Mar 2011 21:11:02 +0000
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> The short answer is to use *Emacs* for your email,

How do you (as in all users using Emacs as their email client) deal with
unreliable networks? When I used to use tramp over a particularly
slow/unreliable network day before, I found every time tramp got stuck
emacs would hang too until tramp could recover. I thought it was
because emacs is still not multi-threaded (am I correct?), so a stuck
process would bring make the entire session unresponsive. This was more
annoying when I was running `emacs --daemon'. So as a conpromise, I
resorted to using plugins (wherever I could) to use emacs as my
alternate editor. So far this has worked very well in Firefox (It's all
text), Thunderbird (Alternate Editor) and claws-mail (native support).

Is there any resolution to these issues? If so, I would really love to
try an Emacs based email client. Of course as always if my understanding
is incorrect please feel free to correct me. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Outlook replacement

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> On Fri, 25 Mar 2011 21:11:02 +0000
> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> 
> > The short answer is to use *Emacs* for your email,
> 
> How do you (as in all users using Emacs as their email client) deal with
> unreliable networks? When I used to use tramp over a particularly
> slow/unreliable network day before, I found every time tramp got stuck
> emacs would hang too until tramp could recover. I thought it was
> because emacs is still not multi-threaded (am I correct?), so a stuck
> process would bring make the entire session unresponsive. This was more
> annoying when I was running `emacs --daemon'. So as a conpromise, I
> resorted to using plugins (wherever I could) to use emacs as my
> alternate editor. So far this has worked very well in Firefox (It's all
> text), Thunderbird (Alternate Editor) and claws-mail (native support).
> 
> Is there any resolution to these issues? If so, I would really love to
> try an Emacs based email client. Of course as always if my understanding
> is incorrect please feel free to correct me. :)
> 

[I sound like a broken record]

I use fetchmail and postfix. They run in the background dealing with
incoming and outgoing mail resp. - as far as emacs is concerned, all
mail is local. If the network is gone, fetchmail tries and fails, so I
don't see any new mail. I can send mail but it stays local until postfix
can connect to my relay and send it out. emacs does not know anything
about nor does it care about the network outage (well,
org-google-weather causes the agenda to be slow, so I know something is
up :-) )

Nick

Re: Outlook replacement

[Suvayu Ali]

On Fri, 25 Mar 2011 22:19:08 -0400
Nick Dokos <nicholas.dokos@hp.com> wrote:

> [I sound like a broken record]
> 

I saw your response but forgot to comment about it.

> I use fetchmail and postfix. They run in the background dealing with
> incoming and outgoing mail resp. - as far as emacs is concerned, all
> mail is local.

I have tried that too but unsuccessfully, my understanding of mail
servers and email protocols are rather limited. I use several emails
accounts on markedly different email systems (GMail, Zimbra, some kind
of M$ mail server). Trying to talk to all these simultaneously seemed
extremely difficult.

Also I often access email from multiple locations, home workstation,
university workstation and my laptop. Not sure how to deal with that. I
once tried OfflineImap but something came up before I could set it up
properly and I never had the time to get back to it. Maybe when I have
the time again.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Outlook replacement

[Memnon Anon]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> How do you (as in all users using Emacs as their email client) deal with
> unreliable networks?

Setup here:

Emacs +
      leafnode (local newsserver for gmane, gwene)
      fetchmail
      msmtp

So all data is dealt with locally, as far as Emacs is concerned.

hth
Memnon

Re: Outlook replacement

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

>> I use fetchmail and postfix. They run in the background dealing with
>> incoming and outgoing mail resp. - as far as emacs is concerned, all
>> mail is local.
>
> I have tried that too but unsuccessfully, my understanding of mail
> servers and email protocols are rather limited. I use several emails
> accounts on markedly different email systems (GMail, Zimbra, some kind
> of M$ mail server). Trying to talk to all these simultaneously seemed
> extremely difficult.
> 
Well, fetchmail can read POP or IMAP from various servers. Don't know anything
about Zimbra, don't *want* to know anything about M$.

> Also I often access email from multiple locations, home workstation,
> university workstation and my laptop. Not sure how to deal with that. I
> once tried OfflineImap but something came up before I could set it up
> properly and I never had the time to get back to it. Maybe when I have
> the time again.
> 

That's tough: you'll need to leave the mail server-side so that you can
access it from all the different machines, but that leaves you vulnerable
to network outages. offlineIMAP might be a good solution for you.

I get my email (three different servers) on a laptop that travels
between home and work. The setup I have is enough for that.

Nick

Re: [Link] Missing referenced page in Org-beamer

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> ...  I guess the link should really be to there, section 12.6.6 to be
> exact.  Can somebody recommend the best way to link there?

Something like this perhaps?

--8<---------------cut here---------------start------------->8---
[1] [[http://orgmode.org/manual/Beamer-class-export.html#Beamer-class-export][A previously created example presentation]], now part of the
Org manual, is available.
--8<---------------cut here---------------end--------------->8---

Nick

Re: Outlook replacement

[Suvayu Ali]

Hi Nick and Memnon,

On Fri, 25 Mar 2011 23:31:21 -0400
Nick Dokos <nicholas.dokos@hp.com> wrote:

> That's tough: you'll need to leave the mail server-side so that you
> can access it from all the different machines, but that leaves you
> vulnerable to network outages. offlineIMAP might be a good solution
> for you.

Looks like this is the only feasible solution for now. I will try my
hand at it again when I have the time.

Thanks a lot. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Outlook replacement

[Eric Abrahamsen]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com>
writes:

> Chris Malone,
>
> Chris Malone wrote:
>> Hi Henri-Paul,
>>
>> While you've brought the topic up I /have/ been recently curious about
>> others' email setup and how they incorporate that into Emacs/org-mode?  I
>> notice several users send emails from within Emacs using org-mode syntax -
>> any tips on setting such a thing up?

[...]

> For "Org-mode syntax" (putting codes as the above):
>
> - simply copy/paste,
> - select region with C-x C-x,
> - demarcate block with C-c C-v C-d and insert the correct language (here:
>   emacs-lisp).

Where does that last keybinding come from? I run (turn-on-orgstruct++),
but org-babel-demarcate-block isn't bound to anything, and C-c C-v runs
message-delete-not-region…

Eric

Re: Outlook replacement

[Sébastien Vauban]

Hi Eric,

Eric Abrahamsen wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Chris Malone wrote:
>>> Hi Henri-Paul,
>>>
>>> While you've brought the topic up I /have/ been recently curious about
>>> others' email setup and how they incorporate that into Emacs/org-mode? I
>>> notice several users send emails from within Emacs using org-mode syntax -
>>> any tips on setting such a thing up?
>>
>> For "Org-mode syntax" (putting codes as the above):
>>
>> - simply copy/paste,
>> - select region with C-x C-x,
>> - demarcate block with C-c C-v C-d and insert the correct language (here:
>>   emacs-lisp).
>
> Where does that last keybinding come from? I run (turn-on-orgstruct++), but
> org-babel-demarcate-block isn't bound to anything,

True. I've made a global binding of it:

#+begin_src emacs-lisp*
  (global-set-key (kbd "C-c C-v C-d") 'org-babel-demarcate-block)
#+end_src

> and C-c C-v runs message-delete-not-region…

True. I've removed that binding from Message -- never used it anyway.

#+begin_src emacs-lisp*
  ;; remove the binding of `C-c C-v', used by Org-Babel commands
  (add-hook 'message-mode-hook
            (lambda ()
              (define-key message-mode-map (kbd "C-c C-v") nil)))
#+end_src

Best regards,
  Seb

-- 
Sébastien Vauban

Re: Outlook replacement

[Achim Gratz]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> Also I often access email from multiple locations, home workstation,
> university workstation and my laptop. Not sure how to deal with that.

The two solutions to deal with that problem at the extreme ends: you
either leave all mail on the server(s) all the time, which means you
need network access (you can cache IMAP but not POP) or you always pull
all mail down to the same machine which means you'll always need access
to that machine.  There's a spectrum of solutions between these two
extremes, but if you need full access to all mail on all machines you
will have to store it on the net somehow (well, you could put it onto a
USB stick I guess *shudder*).


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: Comma-protection of Org blocks

[Achim Gratz]

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com>
writes:
> Hence, questions:
[...]

The question really is if org hasn't evolved to the point where it needs
a more general quoting/escaping mechanism.  This might be one of the
things to ponder during the upcoming exporter cleanup, but goes a bit
beyond just exporting.


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

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: Re: Outlook replacement

[Suvayu Ali]

Hi Achim,

On Sat, 26 Mar 2011 09:41:06 +0100
Achim Gratz <Stromeko@nexgo.de> wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> > Also I often access email from multiple locations, home workstation,
> > university workstation and my laptop. Not sure how to deal with
> > that.
> 
> The two solutions to deal with that problem at the extreme ends: you
> either leave all mail on the server(s) all the time, which means you
> need network access (you can cache IMAP but not POP) or you always
> pull all mail down to the same machine which means you'll always need
> access to that machine.  There's a spectrum of solutions between
> these two extremes, but if you need full access to all mail on all
> machines you will have to store it on the net somehow (well, you
> could put it onto a USB stick I guess *shudder*).
> 

After the comments form Nick, I think my last attempt to try
OfflineImap was the optimum solution for this problem. I'll have to
delve back into that when I find the time (hoping that will be in a
couple of months :) ).

> 
> Achim.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [Link] Missing referenced page in Org-beamer

[Sébastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Check this out in section 4.3 of
>> http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
>> (last line).
>
> Thanks Seb.
>
> Yes, that document ceased to exist a while back. I forgot I was linking to
> it.

This shows that we should have some type of "link checker"[1]. I began working on
one which even produces a DOT graph (let's dream of a clickable sitemap?), but
I'm still stuck with it.

I could finish it right away, using only LP, but I'd like to be able to
execute parts of the document inside it ("in situ execution") for testing
purpose, and assemble all of its parts at the end (à la LP).

For this, Dan had proposed a =:stdin= option to the Babel blocks (which I
think would resolve my problem), but I'm not sure I've communicated the
problem correctly, hence a current status quo and/or a lack of time.

See http://www.mail-archive.com/emacs-orgmode-mXXj517/zsQ@public.gmane.org/msg36924.html for the
skeleton.

Best regards,
  Seb

Footnotes:

[1] In fact, it's more than checking links, it is as well checking that no
files are just sitting there on an island, unreferenced.
-- 
Sébastien Vauban

Re: Comma-protection of Org blocks

[Rustom Mody]

Achim Gratz wrote
> The question really is if org hasn't evolved to the point where it needs
> a more general quoting/escaping mechanism.

+1

However there's caveat:
Just run

zgrep '\\\\\\\\\\\\\\\\' *.el.gz

on your emacs' el.gz files and you will find that its not empty -- So
general and convenient are somewhat at odds here :-)

Which is why python has triple-quoted strings, raw strings and what not...

Re: Re: Comma-protection of Org blocks

[Nick Dokos]

Achim Gratz <Stromeko@nexgo.de> wrote:

> The question really is if org hasn't evolved to the point where it needs
> a more general quoting/escaping mechanism.  This might be one of the
> things to ponder during the upcoming exporter cleanup, but goes a bit
> beyond just exporting.
> 

Absolutely right - org has grown organically (if you'll pardon the pun):
it has developed different quoting mechanisms for different aspects of it, and
they don't always work correctly, even in their restricted domain (braces
in the LaTeX exporter cause trouble often e.g.).

It would be great if a more general quoting mechanism could be
incorporated into the formal description of org. That could then be used
to reimplement these mechanisms. But I suspect it would be a big job and
backward compatibility would also be a big problem.

Nick

Re: Re: Comma-protection of Org blocks

[Samuel Wales]

I agree that this is important.

For new features, Extensible Syntax (capitalized because it is a
specific proposal for a concrete universal syntax) allows you to use
the same quoting, escaping, nesting, exporting, etc. solutions that
were arrived at as a one-time fundamental mechanism.

This reduces the risk of adding quoting, escaping, nesting, exporting,
etc. issues when you add new features to (asymptotically at least --
it needs writing) zero.

I only mention it again to point out that Extensible Syntax was
motivated by reducing parsing risk, including the issues discussed in
this thread.

Samuel

-- 
The Kafka Pandemic:
  http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support the Whittemore-Peterson Institute (WPI)
===
I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.

Re: Outlook replacement

[Steinar Bang]

>>>>> Suvayu Ali <fatkasuvayu+linux@gmail.com>:

> How do you (as in all users using Emacs as their email client) deal
> with unreliable networks? When I used to use tramp over a particularly
> slow/unreliable network day before, I found every time tramp got stuck
> emacs would hang too until tramp could recover.

What does tramp have to do with using emacs as an email client?

Re: Re: Outlook replacement

[Eric S Fraga]

Steinar Bang <sb@dod.no> writes:

>>>>>> Suvayu Ali <fatkasuvayu+linux@gmail.com>:
>
>> How do you (as in all users using Emacs as their email client) deal
>> with unreliable networks? When I used to use tramp over a particularly
>> slow/unreliable network day before, I found every time tramp got stuck
>> emacs would hang too until tramp could recover.
>
> What does tramp have to do with using emacs as an email client?

I think the point was that tramp on an unreliable network illustrates
the problems with emacs's single-threaded implementation and not that it
is otherwise related to email in emacs.

Even on a reliable, yet slow, network, I do get frustrated sometimes
when I have "sent" a very large email and cannot do anything in one of
org documents until the message has actually been sent.  Of course, that
is due to my using a non-queueing smtp MTA, something I *could* fix if
it bothered me enough...

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.128.ga9e6)

Re: Re: Outlook replacement

[Suvayu Ali]

On Sat, 02 Apr 2011 17:18:33 +0100
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Steinar Bang <sb@dod.no> writes:
> 
> >>>>>> Suvayu Ali <fatkasuvayu+linux@gmail.com>:  
> >  
> >> How do you (as in all users using Emacs as their email client) deal
> >> with unreliable networks? When I used to use tramp over a
> >> particularly slow/unreliable network day before, I found every
> >> time tramp got stuck emacs would hang too until tramp could
> >> recover.  
> >
> > What does tramp have to do with using emacs as an email client?  
> 
> I think the point was that tramp on an unreliable network illustrates
> the problems with emacs's single-threaded implementation and not that
> it is otherwise related to email in emacs.

Yes, that was my point of mentioning tramp. I think the conclusion we
arrived at was to use OfflineImap would be the most optimum solution
for my use case.

-- 
Suvayu

Open source is the future. It sets us free.

How to display a diary entry in agenda week view only "today"

[Rainer Stengele]

Hi!

In one of my org agenda files I have

#+CATEGORY: Sunrise
&%%(diary-sunrise-sunset)

Now, when I am in weekly agenda view the sunrise-sunset shows under every day.
This is kind of too much line noise and distracting for me - I would like to only see the entry for "today".

Is there a way to restrict the display of such a diary entry in the weekly agenda view to only today?

Regards,
Rainer

Re: How to display a diary entry in agenda week view only "today"

[Suvayu Ali]

On Mon, 11 Apr 2011 08:52:52 +0200
Rainer Stengele <rainer.stengele@diplan.de> wrote:

> Hi!
> 
> In one of my org agenda files I have
> 
> #+CATEGORY: Sunrise
> &%%(diary-sunrise-sunset)
> 
> Now, when I am in weekly agenda view the sunrise-sunset shows under
> every day. This is kind of too much line noise and distracting for me
> - I would like to only see the entry for "today".
> 
> Is there a way to restrict the display of such a diary entry in the
> weekly agenda view to only today?
> 

How about this,

%%(if (calendar-date-equal date (calendar-current-date)) (diary-sunrise-sunset))

> Regards,
> Rainer
> 

-- 
Suvayu

Open source is the future. It sets us free.

Re: How to display a diary entry in agenda week view only "today"

[Rainer Stengele]

Am 11.04.2011 10:36, schrieb Suvayu Ali:
> On Mon, 11 Apr 2011 08:52:52 +0200
> Rainer Stengele <rainer.stengele@diplan.de> wrote:
> 
>> Hi!
>>
>> In one of my org agenda files I have
>>
>> #+CATEGORY: Sunrise
>> &%%(diary-sunrise-sunset)
>>
>> Now, when I am in weekly agenda view the sunrise-sunset shows under
>> every day. This is kind of too much line noise and distracting for me
>> - I would like to only see the entry for "today".
>>
>> Is there a way to restrict the display of such a diary entry in the
>> weekly agenda view to only today?
>>
> 
> How about this,
> 
> %%(if (calendar-date-equal date (calendar-current-date)) (diary-sunrise-sunset))
> 
>> Regards,
>> Rainer
>>
> 
Perfect, thanks.

I can find the other functions in calendar.el,
but where is "date" from?

Best,
Rainer

Re: Re: How to display a diary entry in agenda week view only "today"

[Niels Giesen]

date is a dynamically bound variable at the time of evaluation.

On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
<rainer.stengele@diplan.de> wrote:
> Am 11.04.2011 10:36, schrieb Suvayu Ali:
>> On Mon, 11 Apr 2011 08:52:52 +0200
>> Rainer Stengele <rainer.stengele@diplan.de> wrote:
>>
>>> Hi!
>>>
>>> In one of my org agenda files I have
>>>
>>> #+CATEGORY: Sunrise
>>> &%%(diary-sunrise-sunset)
>>>
>>> Now, when I am in weekly agenda view the sunrise-sunset shows under
>>> every day. This is kind of too much line noise and distracting for me
>>> - I would like to only see the entry for "today".
>>>
>>> Is there a way to restrict the display of such a diary entry in the
>>> weekly agenda view to only today?
>>>
>>
>> How about this,
>>
>> %%(if (calendar-date-equal date (calendar-current-date)) (diary-sunrise-sunset))
>>
>>> Regards,
>>> Rainer
>>>
>>
> Perfect, thanks.
>
> I can find the other functions in calendar.el,
> but where is "date" from?
>
> Best,
> Rainer
>
>



-- 
http://pft.github.com

Re: Re: How to display a diary entry in agenda week view only "today"

[Suvayu Ali]

On Mon, 11 Apr 2011 14:55:24 +0200
Niels Giesen <niels.giesen@gmail.com> wrote:

> On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
> <rainer.stengele@diplan.de> wrote:
> > Am 11.04.2011 10:36, schrieb Suvayu Ali:
> >> On Mon, 11 Apr 2011 08:52:52 +0200
> >>
> >> %%(if (calendar-date-equal date (calendar-current-date))
> >> (diary-sunrise-sunset))
> >>
> > Perfect, thanks.
> >
> > I can find the other functions in calendar.el,
> > but where is "date" from?
> >
>
> date is a dynamically bound variable at the time of evaluation.
> 

I have a question I have been meaning to ask for a long time. How does
one test sexps with variables like these? I have tried the scratch
buffer but it gives errors like "(void-variable date)". I found the only
way I could test is to put it on one of the agenda files.

Any suggestions?

-- 
Suvayu

Open source is the future. It sets us free.

Re: Re: How to display a diary entry in agenda week view only "today"

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> On Mon, 11 Apr 2011 14:55:24 +0200
> Niels Giesen <niels.giesen@gmail.com> wrote:
> 
> > On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
> > <rainer.stengele@diplan.de> wrote:
> > > Am 11.04.2011 10:36, schrieb Suvayu Ali:
> > >> On Mon, 11 Apr 2011 08:52:52 +0200
> > >>
> > >> %%(if (calendar-date-equal date (calendar-current-date))
> > >> (diary-sunrise-sunset))
> > >>
> > > Perfect, thanks.
> > >
> > > I can find the other functions in calendar.el,
> > > but where is "date" from?
> > >
> >
> > date is a dynamically bound variable at the time of evaluation.
> > 
> 
> I have a question I have been meaning to ask for a long time. How does
> one test sexps with variables like these? I have tried the scratch
> buffer but it gives errors like "(void-variable date)". I found the only
> way I could test is to put it on one of the agenda files.
> 
> Any suggestions?
> 

Bind date explicitly in the scratch buffer and then evaluate:

(setq date '(4 11 2011))

...

I think the format is (month day year) but be sure to check.

Nick

Re: Re: How to display a diary entry in agenda week view only "today"

[Niels Giesen]

Or something like the following (not bullet-proof I guess):

(defmacro test-diary-sexp (date &rest body)
  `(let ((date ,date))
     ,@body))

(test-diary-sexp
 (calendar-current-date)
 (org-google-weather "De Bilt" "nl"))

... and in calendar-current-date lies your answer to the format question.

I do not know however whether or not `date' is the only variable that
is bound dynamically for sexps though; this is something that make me
go crazy too, so (better) documentation might be in order for one.


On Mon, Apr 11, 2011 at 4:55 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> On Mon, 11 Apr 2011 14:55:24 +0200
>> Niels Giesen <niels.giesen@gmail.com> wrote:
>>
>> > On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
>> > <rainer.stengele@diplan.de> wrote:
>> > > Am 11.04.2011 10:36, schrieb Suvayu Ali:
>> > >> On Mon, 11 Apr 2011 08:52:52 +0200
>> > >>
>> > >> %%(if (calendar-date-equal date (calendar-current-date))
>> > >> (diary-sunrise-sunset))
>> > >>
>> > > Perfect, thanks.
>> > >
>> > > I can find the other functions in calendar.el,
>> > > but where is "date" from?
>> > >
>> >
>> > date is a dynamically bound variable at the time of evaluation.
>> >
>>
>> I have a question I have been meaning to ask for a long time. How does
>> one test sexps with variables like these? I have tried the scratch
>> buffer but it gives errors like "(void-variable date)". I found the only
>> way I could test is to put it on one of the agenda files.
>>
>> Any suggestions?
>>
>
> Bind date explicitly in the scratch buffer and then evaluate:
>
> (setq date '(4 11 2011))
>
> ...
>
> I think the format is (month day year) but be sure to check.
>
> Nick
>



-- 
http://pft.github.com

Re: How to display a diary entry in agenda week view only "today"

[Bernt Hansen]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> On Mon, 11 Apr 2011 14:55:24 +0200
>> Niels Giesen <niels.giesen@gmail.com> wrote:
>> 
>> > On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
>> > <rainer.stengele@diplan.de> wrote:
>> > > Am 11.04.2011 10:36, schrieb Suvayu Ali:
>> > >> On Mon, 11 Apr 2011 08:52:52 +0200
>> > >>
>> > >> %%(if (calendar-date-equal date (calendar-current-date))
>> > >> (diary-sunrise-sunset))
>> > >>
>> > > Perfect, thanks.
>> > >
>> > > I can find the other functions in calendar.el,
>> > > but where is "date" from?
>> > >
>> >
>> > date is a dynamically bound variable at the time of evaluation.
>> > 
>> 
>> I have a question I have been meaning to ask for a long time. How does
>> one test sexps with variables like these? I have tried the scratch
>> buffer but it gives errors like "(void-variable date)". I found the only
>> way I could test is to put it on one of the agenda files.
>> 
>> Any suggestions?
>> 
>
> Bind date explicitly in the scratch buffer and then evaluate:
>
> (setq date '(4 11 2011))

Wouldn't a 
(let ((date '(4 11 2011)))
  <your text sexp goes here>)

be better so date isn't permanently bound?

-Bernt

Re: Re: How to display a diary entry in agenda week view only "today"

[Suvayu Ali]

On Mon, 11 Apr 2011 10:55:28 -0400
Nick Dokos <nicholas.dokos@hp.com> wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> 
> > On Mon, 11 Apr 2011 14:55:24 +0200
> > Niels Giesen <niels.giesen@gmail.com> wrote:
> > 
> > > date is a dynamically bound variable at the time of evaluation.
> > > 
> > 
> > I have a question I have been meaning to ask for a long time. How
> > does one test sexps with variables like these? I have tried the
> > scratch buffer but it gives errors like "(void-variable date)". I
> > found the only way I could test is to put it on one of the agenda
> > files.
> > 
> > Any suggestions?
> > 
> 
> Bind date explicitly in the scratch buffer and then evaluate:
> 
> (setq date '(4 11 2011))
> 
> ...
> 
> I think the format is (month day year) but be sure to check.
> 

Works like a charm. Thanks a lot Nick. :)

> Nick

-- 
Suvayu

Open source is the future. It sets us free.

Re: How to display a diary entry in agenda week view only "today"

[Nick Dokos]

Bernt Hansen <bernt@norang.ca> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> >
> >> On Mon, 11 Apr 2011 14:55:24 +0200
> >> Niels Giesen <niels.giesen@gmail.com> wrote:
> >> 
> >> > On Mon, Apr 11, 2011 at 1:57 PM, Rainer Stengele
> >> > <rainer.stengele@diplan.de> wrote:
> >> > > Am 11.04.2011 10:36, schrieb Suvayu Ali:
> >> > >> On Mon, 11 Apr 2011 08:52:52 +0200
> >> > >>
> >> > >> %%(if (calendar-date-equal date (calendar-current-date))
> >> > >> (diary-sunrise-sunset))
> >> > >>
> >> > > Perfect, thanks.
> >> > >
> >> > > I can find the other functions in calendar.el,
> >> > > but where is "date" from?
> >> > >
> >> >
> >> > date is a dynamically bound variable at the time of evaluation.
> >> > 
> >> 
> >> I have a question I have been meaning to ask for a long time. How does
> >> one test sexps with variables like these? I have tried the scratch
> >> buffer but it gives errors like "(void-variable date)". I found the only
> >> way I could test is to put it on one of the agenda files.
> >> 
> >> Any suggestions?
> >> 
> >
> > Bind date explicitly in the scratch buffer and then evaluate:
> >
> > (setq date '(4 11 2011))
> 
> Wouldn't a 
> (let ((date '(4 11 2011)))
>   <your text sexp goes here>)
> 
> be better so date isn't permanently bound?
> 

Sure - I tend to do these things in an isolated emacs, so I don't
particularly care - I kill it and restart it, since it goes off the rails
quite often - but if you use your main emacs, that is definitely
a good idea. OTOH, using your main emacs for experiments is probably *not*
a good idea anyway :-)

Nick

Re: Title page in latex export

[Sebastian Hofer]

At Fri, 04 Mar 2011 10:45:08 -0500,
Nick Dokos wrote:
> 
> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> 
> > 
> > I am trying to write my thesis as per my university style. It requires
> > I use the \title{Thesis title} command before the
> > 
> > \begin{document}
> > ...
> > \end{document}
> > 
> > Is there any way to do that? Thanks for any thoughts.
> > 
> 
> This is really a bug in your university's style. Lamport (p.21 of the
> second edition) says:
> 
>   The \maketitle command comes after the \begin{document}, usually
>   before any other text. The \title, \author, and \date commands can
>   come *anywhere* before the \maketitle.
> 
> [Emphasis added] \title etc. does not have to be in the
> preamble. However, there are many styles out there that restrict the
> placement of these macros to the preamble, just as your university's
> style does (they probably cribbed from each other :-) ), so applying
> Lawrence's patch is probably the best long term solution for org.
> 
> Nick

Hi all,

I hate to bring this up again, but this problem is still not sufficiently
fixed. As Nick pointed out, different packages give error
messages depending on where the \title, \author,... tags are located
in the document. Luck has it, that the revtex4-1 package (which is
used as the default style for the American Physical Society's
journals) chokes when these tags are _outside_ the document body (i.e.
in the preamble). This is actually why the OP experienced problems in
the first place, as I submitted a patch to move them there a couple of
months ago (http://thread.gmane.org/gmane.emacs.orgmode/34208). I just
noticed yesterday that the patch has been undone.

As this will not be the last time this issue comes up (especially due
to the increasing popularity of org-mode), I think it would be
worthwhile to do it right and introduce the possibility to customize
the placement of the title tags. Two possibilities came to my mind:

- customization on a per class basis

This would be the most logical step, but I think that the way
configuration of latex classes is handled in org speaks against that
(as org-export-latex-classes only concerns the preamble, but not the document body)

- customization on a per file basis by setting options

I think this would be a feasible alternative from the usability point
of view. At the same time I have to admit that I have no clue if it is a
complicated matter to introduce new options in org, a quick look
through the code didn't give me any inside.

What do you all think?

Cheers,
Sebastian

C-c - broken

[Marvin Doyley]

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]

Hi there,

I use to use C-c - to convert headlines to plain list, but for some reason
when I do this it tries to make a table of content, see below

TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
[?]Help
------------------------------------------------------------------------------


Does anybody now how to fix this (i.e., get it to behave the old way)

Thanks
M

[-- Attachment #2: Type: text/html, Size: 523 bytes --]

Re: C-c - broken

[Nicolas Goaziou]

Hello,

Marvin Doyley <marvinpas@gmail.com> writes:

> I use to use C-c - to convert headlines to plain list, but for some reason
> when I do this it tries to make a table of content, see below
>
> TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
> SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
> [?]Help

I cannot reproduce this. Could you be more explicit ? What is your test
file, where do you have cursor when you use C-c -, etc.

Regards,

-- 
Nicolas Goaziou

Re: C-c - broken

[Scott Randby]

On 06/06/2011 09:44 AM, Marvin Doyley wrote:
> Hi there,
> 
> I use to use C-c - to convert headlines to plain list, but for some reason
> when I do this it tries to make a table of content, see below
> 
> TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
> SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
> [?]Help
> ------------------------------------------------------------------------------
> 
> 
> Does anybody now how to fix this (i.e., get it to behave the old way)

I had a similar issue, but its occurrence was not consistent. In my
case, the headline would remain a headline. It seemed to happen only
when the last line of the file was a headline and only that headline
wouldn't change to a list item. When I would reload the file (M-x
revert-buffer), C-c - would function normally usually but not always. It
is weird and I haven't had the time to figure out exactly when this bad
behavior occurs.

Scott Randby

Re: C-c - broken

[Nick Dokos]

Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Hello,
> 
> Marvin Doyley <marvinpas@gmail.com> writes:
> 
> > I use to use C-c - to convert headlines to plain list, but for some reason
> > when I do this it tries to make a table of content, see below
> >
> > TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
> > SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
> > [?]Help
> 
> I cannot reproduce this. Could you be more explicit ? What is your test
> file, where do you have cursor when you use C-c -, etc.
> 

It looks as if C-c - has been remapped by some package. What does C-h k
say for it? What minor modes are in effect in the planner.org buffer?
Maybe if you ask for Help with ? in the context above, it'll give
you an idea of who it is that's doing this.

Nick

Re: C-c - broken

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> 
> > Hello,
> > 
> > Marvin Doyley <marvinpas@gmail.com> writes:
> > 
> > > I use to use C-c - to convert headlines to plain list, but for some reason
> > > when I do this it tries to make a table of content, see below
> > >
> > > TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
> > > SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
> > > [?]Help
> > 
> > I cannot reproduce this. Could you be more explicit ? What is your test
> > file, where do you have cursor when you use C-c -, etc.
> > 
> 
> It looks as if C-c - has been remapped by some package. What does C-h k
> say for it? What minor modes are in effect in the planner.org buffer?
> Maybe if you ask for Help with ? in the context above, it'll give
> you an idea of who it is that's doing this.
> 

Looks like reftex is the culprit - you can blame the guy who created
reftex, what's his name? Ah, yes: Carsten Dominik :-)

But why do you have reftex turned on in an org buffer?

Nick

Re: C-c - broken

[Carsten Dominik]

Hi,

On 6.6.2011, at 15:44, Marvin Doyley wrote:

> Hi there,
> 
> I use to use C-c - to convert headlines to plain list, but for some reason when I do this it tries to make a table of content, see below
> 
> TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
> SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r [?]Help
> ------------------------------------------------------------------------------
> 
> 
> Does anybody now how to fix this (i.e., get it to behave the old way)

This happens because you have turned on reftex-mode and that takes over
the `C-c -' and a couple of others.

Reftex-mode is not made for Org-mode, and should probably not be turned on in
Org-mode.  Or is anyone using this combination in a successful way?

- Carsten

Re: C-c - broken

[Marvin Doyley]

Hi guys,

Switching off  Reftex works

Cheers
M



On Jun 6, 2011, at 3:14 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>> Hello,
>>
>> Marvin Doyley <marvinpas@gmail.com> writes:
>>
>>> I use to use C-c - to convert headlines to plain list, but for some reason
>>> when I do this it tries to make a table of content, see below
>>>
>>> TABLE-OF-CONTENTS on ~/Documents/General/O/org/planner.org
>>> SPC=view TAB=goto RET=goto+hide [q]uit [r]escan [l]abels [f]ollow [x]r
>>> [?]Help
>>
>> I cannot reproduce this. Could you be more explicit ? What is your test
>> file, where do you have cursor when you use C-c -, etc.
>>
>
> It looks as if C-c - has been remapped by some package. What does C-h k
> say for it? What minor modes are in effect in the planner.org buffer?
> Maybe if you ask for Help with ? in the context above, it'll give
> you an idea of who it is that's doing this.
>
> Nick

latex checkboxes

[Skip Collins]

There is a couple of problems with the way checkboxes are typeset in LaTeX.

- [ ] a
- [X] b
- [-] c

is translated to the LaTeX

\begin{itemize}
\item $\Box$ a
\item $\boxtimes$ b
\item $\boxminus$ c
\end{itemize}

The first problem is that \Box is not the same size as \boxtimes or \boxminus .
The correct symbol to use from the amssymb package is \square which
matches the other two symbols.

Another problem is that these symbols were intended to be mathematical
binary operators, and are therefore rather small for the purposes of a
checkbox. I suggest that LaTeX output could be modified to something
like:

\setbox0=\hbox{\LARGE$\square$}
\begin{itemize}
\item {\parbox[][][c]{\wd0}{\LARGE$\square$}} a
\item {\parbox[][][c]{\wd0}{\LARGE$\boxtimes$}} b
\item {\parbox[][][c]{\wd0}{\LARGE$\boxminus$}} c
\end{itemize}

The parbox ensures that the checkbox is nicely centered with the first
line of text.

Another nice-to-have feature would be to use the checkbox as a label
for list items in non-enumerated lists. Currently, the list bullet
appears as visual clutter next to the checkbox.

Re: latex checkboxes

[Nick Dokos]

Skip Collins <skip.collins@gmail.com> wrote:

> There is a couple of problems with the way checkboxes are typeset in LaTeX.
> 
> - [ ] a
> - [X] b
> - [-] c
> 
> is translated to the LaTeX
> 
> \begin{itemize}
> \item $\Box$ a
> \item $\boxtimes$ b
> \item $\boxminus$ c
> \end{itemize}
> 
> The first problem is that \Box is not the same size as \boxtimes or \boxminus .
> The correct symbol to use from the amssymb package is \square which
> matches the other two symbols.
> 
> Another problem is that these symbols were intended to be mathematical
> binary operators, and are therefore rather small for the purposes of a
> checkbox. I suggest that LaTeX output could be modified to something
> like:
> 
> \setbox0=\hbox{\LARGE$\square$}
> \begin{itemize}
> \item {\parbox[][][c]{\wd0}{\LARGE$\square$}} a
> \item {\parbox[][][c]{\wd0}{\LARGE$\boxtimes$}} b
> \item {\parbox[][][c]{\wd0}{\LARGE$\boxminus$}} c
> \end{itemize}
> 
> The parbox ensures that the checkbox is nicely centered with the first
> line of text.
> 
> Another nice-to-have feature would be to use the checkbox as a label
> for list items in non-enumerated lists. Currently, the list bullet
> appears as visual clutter next to the checkbox.
> 

I like it! Well, almost all of it: I'd vote for \large, rather than \LARGE,
but otherwise it looks good to me.

Also, the nice-to-have feature is very easy to implement. All it needs is
a pair of square brackets around the box:

,----
| \item [{\parbox[][][c]{\wd0}{\LARGE$\square$}}] a
`----

The \setbox can go into the preamble btw.

Nick

Re: latex checkboxes

[Thomas S. Dye]

Skip Collins <skip.collins@gmail.com> writes:

> There is a couple of problems with the way checkboxes are typeset in LaTeX.
>
> - [ ] a
> - [X] b
> - [-] c
>
> is translated to the LaTeX
>
> \begin{itemize}
> \item $\Box$ a
> \item $\boxtimes$ b
> \item $\boxminus$ c
> \end{itemize}
>
> The first problem is that \Box is not the same size as \boxtimes or \boxminus .
> The correct symbol to use from the amssymb package is \square which
> matches the other two symbols.
>
> Another problem is that these symbols were intended to be mathematical
> binary operators, and are therefore rather small for the purposes of a
> checkbox. I suggest that LaTeX output could be modified to something
> like:
>
> \setbox0=\hbox{\LARGE$\square$}
> \begin{itemize}
> \item {\parbox[][][c]{\wd0}{\LARGE$\square$}} a
> \item {\parbox[][][c]{\wd0}{\LARGE$\boxtimes$}} b
> \item {\parbox[][][c]{\wd0}{\LARGE$\boxminus$}} c
> \end{itemize}
>
> The parbox ensures that the checkbox is nicely centered with the first
> line of text.
>
> Another nice-to-have feature would be to use the checkbox as a label
> for list items in non-enumerated lists. Currently, the list bullet
> appears as visual clutter next to the checkbox.
>
>
Aloha Skip,

I think you might be able to get the behavior you want by modifying the
variable org-export-latex-list-parameters, perhaps something like
'(:ustart "\\setbox0=\\hbox{\\LARGE$\\square$}\n\\begin{itemize}\n" :cboff
"\\parbox[][][c]{\\wd0}{\\LARGE$\\square$}" :cbon
"\\parbox[][][c]{\\wd0}{\\LARGE$\\boxtimes$}")

The variable is set by default to  '(:cbon "$\\boxtimes$" :cboff
"$\\Box$") in org-latex.el and is used to override the default settings
of org-list-to-latex in org-list.el.
 
Not tested.

hth,
Tom
 
-- 
Thomas S. Dye
http://www.tsdye.com

Re: latex checkboxes

[Nick Dokos]

Thomas S. Dye <tsd@tsdye.com> wrote:

> Skip Collins <skip.collins@gmail.com> writes:
> 
> > There is a couple of problems with the way checkboxes are typeset in LaTeX.
> >
> > - [ ] a
> > - [X] b
> > - [-] c
> >
> > is translated to the LaTeX
> >
> > \begin{itemize}
> > \item $\Box$ a
> > \item $\boxtimes$ b
> > \item $\boxminus$ c
> > \end{itemize}
> >
> > The first problem is that \Box is not the same size as \boxtimes or \boxminus .
> > The correct symbol to use from the amssymb package is \square which
> > matches the other two symbols.
> >
> > Another problem is that these symbols were intended to be mathematical
> > binary operators, and are therefore rather small for the purposes of a
> > checkbox. I suggest that LaTeX output could be modified to something
> > like:
> >
> > \setbox0=\hbox{\LARGE$\square$}
> > \begin{itemize}
> > \item {\parbox[][][c]{\wd0}{\LARGE$\square$}} a
> > \item {\parbox[][][c]{\wd0}{\LARGE$\boxtimes$}} b
> > \item {\parbox[][][c]{\wd0}{\LARGE$\boxminus$}} c
> > \end{itemize}
> >
> > The parbox ensures that the checkbox is nicely centered with the first
> > line of text.
> >
> > Another nice-to-have feature would be to use the checkbox as a label
> > for list items in non-enumerated lists. Currently, the list bullet
> > appears as visual clutter next to the checkbox.
> >
> >
> Aloha Skip,
> 
> I think you might be able to get the behavior you want by modifying the
> variable org-export-latex-list-parameters, perhaps something like
> '(:ustart "\\setbox0=\\hbox{\\LARGE$\\square$}\n\\begin{itemize}\n" :cboff
> "\\parbox[][][c]{\\wd0}{\\LARGE$\\square$}" :cbon
> "\\parbox[][][c]{\\wd0}{\\LARGE$\\boxtimes$}")
> 
> The variable is set by default to  '(:cbon "$\\boxtimes$" :cboff
> "$\\Box$") in org-latex.el and is used to override the default settings
> of org-list-to-latex in org-list.el.
>  
> Not tested.
> 

Yes, you can indeed - except for the [-] which is hardcoded. Try the
following:

--8<---------------cut here---------------start------------->8---
#LATEX_HEADER: \setbox0=\hbox{\large$\square$}

#+BIND: org-export-latex-list-parameters (:cbon "[{\\parbox[][][c]{\\wd0}{\\large$\\boxtimes$}}]" :cboff "[{\\parbox[][][c]{\\wd0}{\\large$\\square$}}]")

* DONE Organize party [3/4]
       - [ ] call people
       - [X] order food
       - [-] think about what music to play
       - [X] talk to the neighbors
--8<---------------cut here---------------end--------------->8---

So the question is: why is the [-] hardcoded?

Nick

Re: latex checkboxes

[Skip Collins]

On Thu, Jun 16, 2011 at 6:52 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> I like it! Well, almost all of it: I'd vote for \large, rather than \LARGE,
> but otherwise it looks good to me.

Can we compromise on \Large ? :-)

> ,----
> | \item [{\parbox[][][c]{\wd0}{\LARGE$\square$}}] a
> `----

I tried the optional preamble for \item in a very naive fashion. LaTeX
threw an error. Maybe I did it wrong. Or maybe the preamble is
fragile. Regardless, there is probably a simple solution. Even for
enumerated lists, it makes sense to place the checkbox with the list
number rather than with the item text.

Regarding the extra square brackets after \parbox, I was just using
the documentation I found at
http://www.tug.org/tutorials/latex2e/$5cparbox.html :

\parbox[position][height][inner-pos]{width}{text}

A parbox is a box whose contents are created in paragraph mode. The
\parbox has two mandatory arguments:

width - specifies the width of the parbox, and
text - the text that goes inside the parbox.
LaTeX will position a parbox so its centre lines up with the centre of
the text line. The optional position argument allows you to line up
either the top or bottom line in the parbox (default is top).

If the height argument is not given, the box will have the natural
height of the text.

The inner-pos argument controls the placement of the text inside the
box. If it is not specified, position is used.

t --- text is placed at the top of the box.
c --- text is centred in the box.
b --- text is placed at the bottom of the box.
s --- stretch vertically. The text must contain vertically stretchable
space for this to work.
A \parbox command is used for a parbox containing a small piece of
text, with nothing fancy inside. In particular, you shouldn't use any
of the paragraph-making environments inside a \parbox argument. For
larger pieces of text, including ones containing a paragraph-making
environment, you should use a minipage environment See minipage.

Re: latex checkboxes

[Nick Dokos]

Skip Collins <skip.collins@gmail.com> wrote:

> On Thu, Jun 16, 2011 at 6:52 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> > I like it! Well, almost all of it: I'd vote for \large, rather than \LARGE,
> > but otherwise it looks good to me.
> 
> Can we compromise on \Large ? :-)
> 
As Tom Dye pointed out, you can customize :cbon and :cboff, so
no compromise necessary: you say tomAHto and I say tomEIto...

The only fly in the ointment is the hardcoding of [-] but that will be
fixed a few seconds after Nicolas Goaziou gets wind of this thread :-)

> > ,----
> > | \item [{\parbox[][][c]{\wd0}{\LARGE$\square$}}] a
> > `----
> 
> I tried the optional preamble for \item in a very naive fashion. LaTeX
> threw an error. Maybe I did it wrong. Or maybe the preamble is
> fragile. Regardless, there is probably a simple solution. Even for
> enumerated lists, it makes sense to place the checkbox with the list
> number rather than with the item text.
> 

I don't know what you mean by "preamble" here. I get no errors from
the above in any case: just even, nice-looking squares and no bullets.
I have not tried enumerated lists.

> Regarding the extra square brackets after \parbox, I was just using
> the documentation I found at
> http://www.tug.org/tutorials/latex2e/$5cparbox.html :
> 

Thanks for the reference. I was going by Lamport's book which does not
mention them. I guess things have changed since 1994 - who'd have thunk
it?

Nick

Re: latex checkboxes

[Nicolas Goaziou]

Hello,

Nick Dokos <nicholas.dokos@hp.com> writes:

> Yes, you can indeed - except for the [-] which is hardcoded. Try the
> following:
>
> #LATEX_HEADER: \setbox0=\hbox{\large$\square$}
>
> #+BIND: org-export-latex-list-parameters (:cbon "[{\\parbox[][][c]{\\wd0}{\\large$\\boxtimes$}}]" :cboff "[{\\parbox[][][c]{\\wd0}{\\large$\\square$}}]")
>
> * DONE Organize party [3/4]
>        - [ ] call people
>        - [X] order food
>        - [-] think about what music to play
>        - [X] talk to the neighbors
>
> So the question is: why is the [-] hardcoded?

Historical reasons, I guess.

I've now pushed a patch introducing the new property `:cbtrans' for
those check-boxes. Sadly, it will only work with exporters making use of
list parsing, that is only the LaTeX exporter so far.

Btw, is there any consensus on better default values for :cbon, :cboff
and :cbtrans? Configurability isn't an excuse for ugly standards.

Regards,

-- 
Nicolas Goaziou

Re: latex checkboxes

[Nick Dokos]

Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Hello,
> 
> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > Yes, you can indeed - except for the [-] which is hardcoded. Try the
> > following:
> >
> > #LATEX_HEADER: \setbox0=\hbox{\large$\square$}
> >
> > #+BIND: org-export-latex-list-parameters (:cbon "[{\\parbox[][][c]{\\wd0}{\\large$\\boxtimes$}}]" :cboff "[{\\parbox[][][c]{\\wd0}{\\large$\\square$}}]")
> >
> > * DONE Organize party [3/4]
> >        - [ ] call people
> >        - [X] order food
> >        - [-] think about what music to play
> >        - [X] talk to the neighbors
> >
> > So the question is: why is the [-] hardcoded?
> 
> Historical reasons, I guess.
> 
> I've now pushed a patch introducing the new property `:cbtrans' for
> those check-boxes.

As expected :-) Thanks.

> Sadly, it will only work with exporters making use of
> list parsing, that is only the LaTeX exporter so far.
> 
> Btw, is there any consensus on better default values for :cbon, :cboff
> and :cbtrans? Configurability isn't an excuse for ugly standards.
> 

I don't think so - not yet in any case. I didn't even know about the
box stuff until Skip brought it up. I would have thought that the
default ones should be the simplest thing possible: [ ], [X] and [-]
in a monospaced font, something that does not need any help from
additional LaTeX packages, the kind of thing that org-list-to-latex
does.

Nick

Re: latex checkboxes

[Nicolas Goaziou]

Nick Dokos <nicholas.dokos@hp.com> writes:

>> Btw, is there any consensus on better default values for :cbon, :cboff
>> and :cbtrans? Configurability isn't an excuse for ugly standards.
>> 
>
> I don't think so - not yet in any case. I didn't even know about the
> box stuff until Skip brought it up. I would have thought that the
> default ones should be the simplest thing possible: [ ], [X] and [-]
> in a monospaced font, something that does not need any help from
> additional LaTeX packages, the kind of thing that org-list-to-latex
> does.

Then, what about setting :cbtrans to "\\texttt{[-]}" and
`org-export-latex-list-parameters' to nil, instead of "$\\boxminus$" and
'(:cbon "$\\boxtimes$" :cboff "$\\Box$"), respectively?

Regards,

-- 
Nicolas Goaziou

Re: latex checkboxes

[Nick Dokos]

Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> >> Btw, is there any consensus on better default values for :cbon, :cboff
> >> and :cbtrans? Configurability isn't an excuse for ugly standards.
> >> 
> >
> > I don't think so - not yet in any case. I didn't even know about the
> > box stuff until Skip brought it up. I would have thought that the
> > default ones should be the simplest thing possible: [ ], [X] and [-]
> > in a monospaced font, something that does not need any help from
> > additional LaTeX packages, the kind of thing that org-list-to-latex
> > does.
> 
> Then, what about setting :cbtrans to "\\texttt{[-]}" and
> `org-export-latex-list-parameters' to nil, instead of "$\\boxminus$" and
> '(:cbon "$\\boxtimes$" :cboff "$\\Box$"), respectively?
> 

I'm fine with that - Skip? Tom? Others? If this does end up being the case,
then Skip's \parbox method can be integrated into Tom's LaTeX tutorial
or as a separate hack on Worg.

Nick

Re: latex checkboxes

[Skip Collins]

>> Then, what about setting :cbtrans to "\\texttt{[-]}" and
>> `org-export-latex-list-parameters' to nil, instead of "$\\boxminus$" and
>> '(:cbon "$\\boxtimes$" :cboff "$\\Box$"), respectively?
>>
>
> I'm fine with that - Skip? Tom? Others? If this does end up being the case,
> then Skip's \parbox method can be integrated into Tom's LaTeX tutorial
> or as a separate hack on Worg.

Adding configurability for cbon, cboff, and cbtrans is the most important thing.

Philosophically, the whole point of exporting to LaTeX or HTML is to
take a plain text representation of lists, checkboxes, etc., and turn
it into a nice presentation format. So I don't quite agree that the
LaTeX output should mirror the appearance of the org file with a
monospaced font. If so, then logically list bullets should be exported
as hyphens. My preference would be that the default LaTeX (and html)
outputs should use the features of those formats to make the output
look nice. Within reason, of course.

Re: latex checkboxes

[Nick Dokos]

Skip Collins <skip.collins@gmail.com> wrote:

> >> Then, what about setting :cbtrans to "\\texttt{[-]}" and
> >> `org-export-latex-list-parameters' to nil, instead of "$\\boxminus$" and
> >> '(:cbon "$\\boxtimes$" :cboff "$\\Box$"), respectively?
> >>
> >
> > I'm fine with that - Skip? Tom? Others? If this does end up being the case,
> > then Skip's \parbox method can be integrated into Tom's LaTeX tutorial
> > or as a separate hack on Worg.
> 
> Adding configurability for cbon, cboff, and cbtrans is the most important thing.
> 
> Philosophically, the whole point of exporting to LaTeX or HTML is to
> take a plain text representation of lists, checkboxes, etc., and turn
> it into a nice presentation format. So I don't quite agree that the
> LaTeX output should mirror the appearance of the org file with a
> monospaced font. If so, then logically list bullets should be exported
> as hyphens. My preference would be that the default LaTeX (and html)
> outputs should use the features of those formats to make the output
> look nice. Within reason, of course.
> 

I agree of course, particularly with the last sentence. The question is:
is there some other reasonable default that will satisfy most people's
needs without requiring them to customize? I'm not too worried about the
perfection hounds: they will customize mercilessly and they will
complain if they cannot customize - and I think they (you!) will be
happy with the current solutions.  If people vote for \parbox as the
default, I'm perfectly happy with that.  The current default however is
indeed ugly and needs to be changed: I think we all agree with you on
that.

I'll try to run the same org file through the two different defaults
and put up some PDFs so people can look at them, but I won't get to it
till late tomorrow.

Nick

Re: latex checkboxes

[Thomas S. Dye]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>> Nick Dokos <nicholas.dokos@hp.com> writes:
>> 
>> >> Btw, is there any consensus on better default values for :cbon, :cboff
>> >> and :cbtrans? Configurability isn't an excuse for ugly standards.
>> >> 
>> >
>> > I don't think so - not yet in any case. I didn't even know about the
>> > box stuff until Skip brought it up. I would have thought that the
>> > default ones should be the simplest thing possible: [ ], [X] and [-]
>> > in a monospaced font, something that does not need any help from
>> > additional LaTeX packages, the kind of thing that org-list-to-latex
>> > does.
>> 
>> Then, what about setting :cbtrans to "\\texttt{[-]}" and
>> `org-export-latex-list-parameters' to nil, instead of "$\\boxminus$" and
>> '(:cbon "$\\boxtimes$" :cboff "$\\Box$"), respectively?
>> 
>
> I'm fine with that - Skip? Tom? Others? If this does end up being the case,
> then Skip's \parbox method can be integrated into Tom's LaTeX tutorial
> or as a separate hack on Worg.
>
> Nick
>
>
>

Yes, that seems like a good solution to me.  When the dust has settled
I'll work this into the LaTeX tutorial, either directly or linked to a
separate hack on Worg (written by someone else).

Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Problem with BEGIN_SRC export-as-latex and FORTRAN code

[Nick Papior Andersen]

[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]

Hi all

I have attached a sample which produces a wrong output in my org-mode
installation. Both the output TeX file and the org file are attached.

The wrong doing happens when i do "org-export-as-latex". The output tex file
has removed a certain string length (i counted 23) and inserted some from
the code below as a description in the item field (which it shouldn't do as
we are in an enumerate environment).

I have version 7.01g, i have had troubles to install the newest 7.5 org-mode
version so i cant say if it does the same there. But i have searched the
changes list for export on latex source. It didn't seem to have had any
changes as far as this bug.

I know that i probably shouldn't denote FORTRAN code as C code, but is that
internally differentiated?

Kind regards Nick

[-- Attachment #1.2: Type: text/html, Size: 975 bytes --]

[-- Attachment #2: latex-org-export-bug.zip --]
[-- Type: application/zip, Size: 1113 bytes --]

[bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric S Fraga]

Nick Papior Andersen <nickpapior@gmail.com> writes:

> Hi all
>
> I have attached a sample which produces a wrong output in my org-mode
> installation. Both the output TeX file and the org file are attached.
>
> The wrong doing happens when i do "org-export-as-latex". The output tex file
> has removed a certain string length (i counted 23) and inserted some from
> the code below as a description in the item field (which it shouldn't do as
> we are in an enumerate environment).

The problem you describe does not exist in the current git head so I
recommend you try upgrading again.  Maybe explain what problems you had
with 7.5?

In any case, using the same example file you posted, I see a different
problem when I export to latex.  Here is a snippet of the resulting
latex:

,----
| \section{Test}
| \label{sec-1}
| 
| 
| \begin{enumerate}
| \item Try and use \verb=org-export-as-latex=, it will produce error segment.
| \end{enumerate}
| \lstset{language=C}
| \begin{lstlisting}
|    MODULE m_global_precision
|      IMPLICIT NONE
|      INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
|    END MODULE m_global_precision
| \end{lstlisting}
|  
| ORG-LIST-END-MARKER
| \section{Test2}
`----

*Note* the =ORG-LIST-END-MARKER=.

Finally, why not specify language=Fortran?

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.414.g56de5)

Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code

[Eric Schulte]

Hi Nick,

I think the solution to your problem may be simply to update to the
latest version of Org-mode, I get the following output when exporting
your example to LaTeX.

--8<---------------cut here---------------start------------->8---
\section{Test}
\label{sec-1}


\begin{enumerate}
\item Try and use \texttt{org-export-as-latex}, it will produce error segment.
\begin{verbatim}
MODULE m_global_precision
  IMPLICIT NONE
  INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
END MODULE m_global_precision
\end{verbatim}
\end{enumerate}
\section{Test2}
\label{sec-2}


\begin{enumerate}
\item This will not fail as it is not in an enumerate environment.
\end{enumerate}
\begin{verbatim}
MODULE m_global_precision
  IMPLICIT NONE
  INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
END MODULE m_global_precision
\end{verbatim}
--8<---------------cut here---------------end--------------->8---

I'm using

  Org-mode version 7.5 (release_7.5.414.g56de5)

Best -- Eric

Nick Papior Andersen <nickpapior@gmail.com> writes:

> Hi all
>
> I have attached a sample which produces a wrong output in my org-mode
> installation. Both the output TeX file and the org file are attached.
>
> The wrong doing happens when i do "org-export-as-latex". The output tex file
> has removed a certain string length (i counted 23) and inserted some from
> the code below as a description in the item field (which it shouldn't do as
> we are in an enumerate environment).
>
> I have version 7.01g, i have had troubles to install the newest 7.5 org-mode
> version so i cant say if it does the same there. But i have searched the
> changes list for export on latex source. It didn't seem to have had any
> changes as far as this bug.
>
> I know that i probably shouldn't denote FORTRAN code as C code, but is that
> internally differentiated?
>
> Kind regards Nick
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nick Papior Andersen]

[-- Attachment #1: Type: text/plain, Size: 2533 bytes --]

Hi Eric

Thanks.

I can see why the new thing would work as it utilizes the listing
environment. If the bug is fully removed then great.

It shows when the verbatim environment is used in my version. If a newer
version of org-mode will ever be used with only the verbatim environment,
then what happens?

No actual reason for not writing fortran besides it is shorter... However it
will produce the same error nonetheless.

Another error in your above shown result, is that the listing should have
been exported inside the enumerate environment. I have speculated whether
the error is due to fortran is not in language list.
http://orgmode.org/worg/org-contrib/babel/languages.html

As to my installation of org-mode, i downloaded and make, make install..
Have installed correctly, i just couldn't figure out to setup the new
installation of org (i.e. it still uses the old which is shipped by
standard!).
I think i can overcome this issue if i spend some more time on it. :)

Kind regards Nick


2011/6/21 Eric S Fraga <e.fraga@ucl.ac.uk>

> Nick Papior Andersen <nickpapior@gmail.com> writes:
>
> > Hi all
> >
> > I have attached a sample which produces a wrong output in my org-mode
> > installation. Both the output TeX file and the org file are attached.
> >
> > The wrong doing happens when i do "org-export-as-latex". The output tex
> file
> > has removed a certain string length (i counted 23) and inserted some from
> > the code below as a description in the item field (which it shouldn't do
> as
> > we are in an enumerate environment).
>
> The problem you describe does not exist in the current git head so I
> recommend you try upgrading again.  Maybe explain what problems you had
> with 7.5?
>
> In any case, using the same example file you posted, I see a different
> problem when I export to latex.  Here is a snippet of the resulting
> latex:
>
> ,----
> | \section{Test}
> | \label{sec-1}
> |
> |
> | \begin{enumerate}
> | \item Try and use \verb=org-export-as-latex=, it will produce error
> segment.
> | \end{enumerate}
> | \lstset{language=C}
> | \begin{lstlisting}
> |    MODULE m_global_precision
> |      IMPLICIT NONE
> |      INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
> |    END MODULE m_global_precision
> | \end{lstlisting}
> |
> | ORG-LIST-END-MARKER
> | \section{Test2}
> `----
>
> *Note* the =ORG-LIST-END-MARKER=.
>
> Finally, why not specify language=Fortran?
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.414.g56de5)
>

[-- Attachment #2: Type: text/html, Size: 3326 bytes --]

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric S Fraga]

Nick Papior Andersen <nickpapior@gmail.com> writes:

> Hi Eric
>
> Thanks.
>
> I can see why the new thing would work as it utilizes the listing
> environment. If the bug is fully removed then great.
>
> It shows when the verbatim environment is used in my version. If a newer
> version of org-mode will ever be used with only the verbatim environment,
> then what happens?
>
> No actual reason for not writing fortran besides it is shorter... However it
> will produce the same error nonetheless.
>
> Another error in your above shown result, is that the listing should have
> been exported inside the enumerate environment. 

Very true.  I missed this.  Given the indentation, the listing should
indeed belong to the enumeration item.

Nicolas?

> I have speculated whether
> the error is due to fortran is not in language list.
> http://orgmode.org/worg/org-contrib/babel/languages.html

I doubt it.  #+begin_src ... #+end_src is somewhat generic; it's only
when you want babel to interpret the code that the language has to be
recognised.  I believe...

> As to my installation of org-mode, i downloaded and make, make install..
> Have installed correctly, i just couldn't figure out to setup the new
> installation of org (i.e. it still uses the old which is shipped by
> standard!).
> I think i can overcome this issue if i spend some more time on it. :)

You need to add the location of where you have installed the new version
to the load-path variable very early in the emacs initialisation file
which is ~/.emacs in my case; what system are you using?  Something
along the lines of

(add-to-list 'load-path "~/path/to/new/org")

should do the job.  Typing

M-x org-version RET

once emacs has started should show you the version that has actually
been loaded.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.415.g3f3fc.dirty)

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nick Papior Andersen]

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

I puzzled with it... And finally got it working... Wasn't a pretty work
around!

Well it all works now! Thanks for this!

I can see your point on the babel stuff.. :)

Kind regards Nick

2011/6/21 Eric S Fraga <e.fraga@ucl.ac.uk>

> Nick Papior Andersen <nickpapior@gmail.com> writes:
>
> > Hi Eric
> >
> > Thanks.
> >
> > I can see why the new thing would work as it utilizes the listing
> > environment. If the bug is fully removed then great.
> >
> > It shows when the verbatim environment is used in my version. If a newer
> > version of org-mode will ever be used with only the verbatim environment,
> > then what happens?
> >
> > No actual reason for not writing fortran besides it is shorter... However
> it
> > will produce the same error nonetheless.
> >
> > Another error in your above shown result, is that the listing should have
> > been exported inside the enumerate environment.
>
> Very true.  I missed this.  Given the indentation, the listing should
> indeed belong to the enumeration item.
>
> Nicolas?
>
> > I have speculated whether
> > the error is due to fortran is not in language list.
> > http://orgmode.org/worg/org-contrib/babel/languages.html
>
> I doubt it.  #+begin_src ... #+end_src is somewhat generic; it's only
> when you want babel to interpret the code that the language has to be
> recognised.  I believe...
>
> > As to my installation of org-mode, i downloaded and make, make install..
> > Have installed correctly, i just couldn't figure out to setup the new
> > installation of org (i.e. it still uses the old which is shipped by
> > standard!).
> > I think i can overcome this issue if i spend some more time on it. :)
>
> You need to add the location of where you have installed the new version
> to the load-path variable very early in the emacs initialisation file
> which is ~/.emacs in my case; what system are you using?  Something
> along the lines of
>
> (add-to-list 'load-path "~/path/to/new/org")
>
> should do the job.  Typing
>
> M-x org-version RET
>
> once emacs has started should show you the version that has actually
> been loaded.
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.5 (release_7.5.415.g3f3fc.dirty)
>

[-- Attachment #2: Type: text/html, Size: 3070 bytes --]

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric Schulte]

>
>> I have speculated whether the error is due to fortran is not in
>> language list.
>> http://orgmode.org/worg/org-contrib/babel/languages.html
>
> I doubt it.  #+begin_src ... #+end_src is somewhat generic; it's only
> when you want babel to interpret the code that the language has to be
> recognised.  I believe...
>

This is true. Unless you want to execute the code, the language does not
have to be known to Babel.  Although if you try to export to html with
syntax highlighting for language "foo", the syntax highlighting will
only work if emacs has a "foo-mode" defined.

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nicolas Goaziou]

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Very true.  I missed this.  Given the indentation, the listing should
> indeed belong to the enumeration item.
>
> Nicolas?

If I export this:

-----
* Test
1. Try and use =org-export-as-latex=, it will produce error segment.
   #+BEGIN_SRC C
   MODULE m_global_precision
     IMPLICIT NONE
     INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
   END MODULE m_global_precision
   #+END_SRC 
-----

I get this:

#+begin_src latex
\section{Test}
\label{sec-1}


\begin{enumerate}
\item Try and use \texttt{org-export-as-latex}, it will produce error segment.
  \lstset{language=C}
  \begin{lstlisting}
    MODULE m_global_precision
    IMPLICIT NONE
    INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
    END MODULE m_global_precision
  \end{lstlisting}
\end{enumerate}
#+end_src

It looks ok, or am I missing something?

Regards,

-- 
Nicolas Goaziou

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric S Fraga]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> Very true.  I missed this.  Given the indentation, the listing should
>> indeed belong to the enumeration item.
>>
>> Nicolas?
>
> If I export this:
>
> -----
> * Test
> 1. Try and use =org-export-as-latex=, it will produce error segment.
>    #+BEGIN_SRC C
>    MODULE m_global_precision
>      IMPLICIT NONE
>      INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
>    END MODULE m_global_precision
>    #+END_SRC 
> -----
>
> I get this:
>
> #+begin_src latex
> \section{Test}
> \label{sec-1}
>
>
> \begin{enumerate}
> \item Try and use \texttt{org-export-as-latex}, it will produce error segment.
>   \lstset{language=C}
>   \begin{lstlisting}
>     MODULE m_global_precision
>     IMPLICIT NONE
>     INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
>     END MODULE m_global_precision
>   \end{lstlisting}
> \end{enumerate}
> #+end_src
>
> It looks ok, or am I missing something?
>
> Regards,

Nicolas,

It does look okay but that's not what I get; same input, I get:

--8<---------------cut here---------------start------------->8---
\section{Test}
\label{sec-1}


\begin{enumerate}
\item Try and use \verb=org-export-as-latex=, it will produce error segment.
\end{enumerate}
\lstset{language=C}
\begin{lstlisting}
   MODULE m_global_precision
     IMPLICIT NONE
     INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
   END MODULE m_global_precision
\end{lstlisting}
 
ORG-LIST-END-MARKER

\end{document}
--8<---------------cut here---------------end--------------->8---

I guess I have some variable set that you do not or vice versa.  For
instance, I have org-list-end-marker set to 'both.  Are there any
variable settings you need to know to figure out why my behaviour is
different?  I'm at git head.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.418.ge860.dirty)

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nicolas Goaziou]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> It does look okay but that's not what I get; same input, I get:
>
>
> \section{Test}
> \label{sec-1}
>
>
> \begin{enumerate}
> \item Try and use \verb=org-export-as-latex=, it will produce error segment.
> \end{enumerate}
> \lstset{language=C}
> \begin{lstlisting}
>    MODULE m_global_precision
>      IMPLICIT NONE
>      INTEGER, PARAMETER :: SP = SELECTED_REAL_KIND(6,30)
>    END MODULE m_global_precision
> \end{lstlisting}
>  
> ORG-LIST-END-MARKER
>
> \end{document}
>
>
> I guess I have some variable set that you do not or vice versa.  For
> instance, I have org-list-end-marker set to 'both.  Are there any
> variable settings you need to know to figure out why my behaviour is
> different?  I'm at git head.

I've tried with a minimal setup, and I still get the correct export. If
you confirm this, we have two options left: either you bisect your
config until you get the offending variable, or you send me that config
so I can do the same.

Note that variable may even be unrelated to Org.

Regards,

-- 
Nicolas Goaziou

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric S Fraga]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

[...]

> I've tried with a minimal setup, and I still get the correct export. If
> you confirm this, we have two options left: either you bisect your
> config until you get the offending variable, or you send me that config
> so I can do the same.

I can confirm that it works fine with minimal setup.  Definitely
something wrong with my config.

> Note that variable may even be unrelated to Org.

Yes; I've found some strange behaviour that may be related to emacs
24.0.50.1 which I will follow up on in a different thread; for
completeness, what version of Emacs are you using?

thanks,
eric
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.418.ge860.dirty)

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
> 
> [...]
> 
> > I've tried with a minimal setup, and I still get the correct export. If
> > you confirm this, we have two options left: either you bisect your
> > config until you get the offending variable, or you send me that config
> > so I can do the same.
> 
> I can confirm that it works fine with minimal setup.  Definitely
> something wrong with my config.
> 
> > Note that variable may even be unrelated to Org.
> 
> Yes; I've found some strange behaviour that may be related to emacs
> 24.0.50.1 which I will follow up on in a different thread; for
> completeness, what version of Emacs are you using?
> 

I don't even have the variable (org-list-end-marker) defined at all.
Where is it defined? The only ones my emacs finds with that prefix are

,----
| Possible completions are:
| org-list-end-re
| org-list-end-regexp
| org-list-ending-method
`----

And, btw, I can't reproduce the problem either.

Nick

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nicolas Goaziou]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Yes; I've found some strange behaviour that may be related to emacs
> 24.0.50.1 which I will follow up on in a different thread; for
> completeness, what version of Emacs are you using?

The good ol' 23.3.1

-- 
Nicolas Goaziou

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nick Dokos]

Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> 
> > Yes; I've found some strange behaviour that may be related to emacs
> > 24.0.50.1 which I will follow up on in a different thread; for
> > completeness, what version of Emacs are you using?
> 
> The good ol' 23.3.1
> 

I'm on 24.0.50.1, so I don't think that's the problem.

Nick

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Eric S Fraga]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>> 
>> [...]
>> 
>> > I've tried with a minimal setup, and I still get the correct export. If
>> > you confirm this, we have two options left: either you bisect your
>> > config until you get the offending variable, or you send me that config
>> > so I can do the same.
>> 
>> I can confirm that it works fine with minimal setup.  Definitely
>> something wrong with my config.
>> 
>> > Note that variable may even be unrelated to Org.
>> 
>> Yes; I've found some strange behaviour that may be related to emacs
>> 24.0.50.1 which I will follow up on in a different thread; for
>> completeness, what version of Emacs are you using?
>> 
>
> I don't even have the variable (org-list-end-marker) defined at all.
> Where is it defined? The only ones my emacs finds with that prefix are
>
> ,----
> | Possible completions are:
> | org-list-end-re
> | org-list-end-regexp
> | org-list-ending-method
> `----

Apologies but that was my auto-completion completing on the wrong term!
ooops.  I have the same three org-list-end* variables as you.

I've gone through my whole config and have tracked down the problem:

: (setq org-src-preserve-indentation t)

if I have this line present, the latex export doesn't work; if I remove
this line, the export works as it should.  This would appear to be a bug
in the exporter?

thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.418.ge860.dirty)

Re: [bug] Latex export of lists (was Re: Problem with BEGIN_SRC export-as-latex and FORTRAN code)

[Nicolas Goaziou]

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I've gone through my whole config and have tracked down the problem:
>
> : (setq org-src-preserve-indentation t)

Nice. It helps a lot.

> if I have this line present, the latex export doesn't work; if I remove
> this line, the export works as it should.  This would appear to be a bug
> in the exporter?

The culprit is `org-export-blocks-preprocess' which sticks #+begin_src
and #+end_src to column 0 when org-src-preserve-indentation is non-nil.
It should at least keep original indentation of block, or set
original-indentation property to it.

Also, I think there may be a bug in
`org-export-replace-src-segments-and-examples' as indent local variable
is computed as the length of a white-spaces string. Indeed, this may
lead to problems when the indent string is made of tabs (i.e. 1 tab
doesn't mean indentation is 1). Untested, though.

Eric Schulte, do you have time to look at this problem, or shall
I investigate a bit more?

Regards,

-- 
Nicolas Goaziou

Problem with autoloads

[suvayu ali]

Hi,

After I updated yesterday I have been having this problem. This is how
I compile:

$ make cleanall && make all

and I load org from my init file like this:

;; the org repo is at ~/build/org-mode
(add-to-list 'load-path (expand-file-name "~/build/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "~/build/org-mode/contrib/lisp"))

(require 'org-install)

Now every time something needs to be loaded say org-latex during latex export
or org-table when turning on orgtbl minor mode, I get errors like these:

(file-error "Cannot open load file" "lisp/org")

I see lisp/org-install.el has autoloads like these:

(autoload 'org-mode "lisp/org" ...)

I have faced this once earlier, not sure how I resolved it back then. What am
I doing wrong here?

--
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 757 bytes --]

On 26 Jun 2011, suvayu ali wrote:

> $ make cleanall && make all
>
> and I load org from my init file like this:
>
> ;; the org repo is at ~/build/org-mode
> (add-to-list 'load-path (expand-file-name "~/build/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name "~/build/org-mode/contrib/lisp"))
>
> (require 'org-install)
>
> <snip>
>
> I have faced this once earlier, not sure how I resolved it back
> then. What am I doing wrong here?

I faced this, too.

A fix/workaround is to adjust the loadpath to:

(add-to-list 'load-path (expand-file-name "~/build/org-mode"))

After quick browsing through the logs I found nothing that could have
caused this, but my guess is that someone adjusted the autoloads from
"file.el" to "lisp/file.el".

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Suvayu Ali]

Hi Michael,

On Mon, 27 Jun 2011 18:51:01 +0200
Michael Markert <markert.michael@googlemail.com> wrote:

> A fix/workaround is to adjust the loadpath to:
> 
> (add-to-list 'load-path (expand-file-name "~/build/org-mode"))
> 
> After quick browsing through the logs I found nothing that could have
> caused this, but my guess is that someone adjusted the autoloads from
> "file.el" to "lisp/file.el".

That seems to work for now. But I think this should still be addressed.
At least if this is how org behaves now, the instructions on Worg
should reflect that.

Thanks a lot. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

On 27 Jun 2011, Michael Markert wrote:
> On 26 Jun 2011, suvayu ali wrote:
>
>> $ make cleanall && make all
>>
>> and I load org from my init file like this:
>>
>> ;; the org repo is at ~/build/org-mode (add-to-list 'load-path
>> (expand-file-name "~/build/org-mode/lisp")) (add-to-list 'load-path
>> (expand-file-name "~/build/org-mode/contrib/lisp"))
>>
>> (require 'org-install)
>>
>> <snip>
>>
>> I have faced this once earlier, not sure how I resolved it back
>> then. What am I doing wrong here?
>
> I faced this, too.
>
> A fix/workaround is to adjust the loadpath to:
>
> (add-to-list 'load-path (expand-file-name "~/build/org-mode"))

Scratch that. You need that line _additionally_ to the your other two.

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Suvayu Ali]

On Mon, 27 Jun 2011 20:08:26 +0200
Michael Markert <markert.michael@googlemail.com> wrote:

> > A fix/workaround is to adjust the loadpath to:
> >
> > (add-to-list 'load-path (expand-file-name "~/build/org-mode"))  
> 
> Scratch that. You need that line _additionally_ to the your other two.

I noticed something strange; if you do (load-library "org-capture") for
example (with the load path set to ~/build/orgmode/lisp), the
libraries get loaded without any errors and then on everything works as
usual. This seems like a strange behaviour to me.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On 27 Jun 2011, Suvayu Ali wrote:

> On Mon, 27 Jun 2011 20:08:26 +0200
> Michael Markert <markert.michael@googlemail.com> wrote:
>
>>> A fix/workaround is to adjust the loadpath to:
>>>
>>> (add-to-list 'load-path (expand-file-name "~/build/org-mode"))
>>
>> Scratch that. You need that line _additionally_ to the your other
>> two.
>
> I noticed something strange; if you do (load-library "org-capture")
> for example (with the load path set to ~/build/orgmode/lisp), the
> libraries get loaded without any errors and then on everything works
> as usual. This seems like a strange behaviour to me.

No, it's perfectly fine. With the autoloads you search for
`lisp/file.el' so the directory that includes the lisp directory has to
be in the load-path.
If you search only for the `file.el' the `lisp' directory itself has to
be in the load-path. This is exactly the problem if you change your
load-path according to my first mail: If you (or a file -- in my case it
was org-contacts.el) load the file directly, you'll fail.

With org-mode this is especially hairy, because the bundled org-mode is
by default still in the load-path, so you'll load the old ones -- in the
best case this results in cryptic and incomprehensible error messages on
load.

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

On 27 Jun 2011, Suvayu Ali wrote:
> Hi Michael,
>
> On Mon, 27 Jun 2011 18:51:01 +0200
> Michael Markert <markert.michael@googlemail.com> wrote:
>
>> A fix/workaround is to adjust the loadpath to:
>>
>> (add-to-list 'load-path (expand-file-name "~/build/org-mode"))
>>
>> After quick browsing through the logs I found nothing that could have
>> caused this, but my guess is that someone adjusted the autoloads from
>> "file.el" to "lisp/file.el".
>
> That seems to work for now. But I think this should still be
> addressed.  At least if this is how org behaves now, the instructions
> on Worg should reflect that.
>
> Thanks a lot. :)

I think I tracked it down: The problem is emacs24, that is the
autoload.el that it bundles.

With emacs23 it doesn't honor the path of the file it's passed, but with
emacs24 it does, resulting in "lisp/file" autoloads.

I don't see an easy solution, that's not plain dirty.[1]

Michael

I consider adding the base directory along with the `lisp' and maybe
`contrib/lisp' directories quite dirty ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Nick Dokos]

Michael Markert <markert.michael@googlemail.com> wrote:

> On 27 Jun 2011, Suvayu Ali wrote:
> > Hi Michael,
> >
> > On Mon, 27 Jun 2011 18:51:01 +0200
> > Michael Markert <markert.michael@googlemail.com> wrote:
> >
> >> A fix/workaround is to adjust the loadpath to:
> >>
> >> (add-to-list 'load-path (expand-file-name "~/build/org-mode"))
> >>
> >> After quick browsing through the logs I found nothing that could have
> >> caused this, but my guess is that someone adjusted the autoloads from
> >> "file.el" to "lisp/file.el".
> >
> > That seems to work for now. But I think this should still be
> > addressed.  At least if this is how org behaves now, the instructions
> > on Worg should reflect that.
> >
> > Thanks a lot. :)
> 
> I think I tracked it down: The problem is emacs24, that is the
> autoload.el that it bundles.
> 
> With emacs23 it doesn't honor the path of the file it's passed, but with
> emacs24 it does, resulting in "lisp/file" autoloads.
> 
> I don't see an easy solution, that's not plain dirty.[1]
> 
> Michael
> 
> I consider adding the base directory along with the `lisp' and maybe
> `contrib/lisp' directories quite dirty ;)

I run emacs24 and I don't have this problem - and I made sure that I was
running emacs24 by modifying the makefile appropriately:

,----
| $ make lisp/org-install.el
| /usr/local/bin/emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -eval "(message (emacs-version))" --eval "(require 'autoload)" \
| 		--eval '(find-file "org-install.el")'  \
| 		--eval '(erase-buffer)' \
| 		--eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote (lisp/org.el lisp/org-agenda.el lisp/org-ascii.el lisp/org-attach.el lisp/org-archive.el lisp/org-bbdb.el lisp/org-beamer.el lisp/org-bibtex.el lisp/org-capture.el lisp/org-clock.el lisp/org-colview.el lisp/org-colview-xemacs.el lisp/org-compat.el lisp/org-pcomplete.el lisp/org-crypt.el lisp/org-ctags.el lisp/org-datetree.el lisp/org-docview.el lisp/org-entities.el lisp/org-exp.el lisp/org-exp-blocks.el lisp/org-docbook.el lisp/org-faces.el lisp/org-feed.el lisp/org-footnote.el lisp/org-freemind.el lisp/org-gnus.el lisp/org-habit.el lisp/org-html.el lisp/org-icalendar.el lisp/org-id.el lisp/org-indent.el lisp/org-info.el lisp/org-inlinetask.el lisp/org-jsinfo.el lisp/org-irc.el lisp/org-latex.el lisp/org-list.e
 l lisp/org-mac-message.el lisp/org-macs.el lisp/org-mew.el lisp/org-mhe.el lisp/org-mks.el lisp/org-mobile.el lisp/org-mouse.el lisp/org-publish.el lisp/org-plot.el lisp/org-protocol.el lisp
 /org-remember.el lisp/org-rmail.el lisp/org-special-blocks.el lisp/org-src.el lisp/org-table.el lisp/org-taskjuggler.el lisp/org-timer.el lisp/org-vm.el lisp/org-w3m.el lisp/org-wl.el lisp/org-xoxo.el lisp/ob.el lisp/ob-table.el lisp/ob-lob.el lisp/ob-ref.el lisp/ob-exp.el lisp/ob-tangle.el lisp/ob-comint.el lisp/ob-eval.el lisp/ob-keys.el lisp/ob-awk.el lisp/ob-C.el lisp/ob-calc.el lisp/ob-ditaa.el lisp/ob-haskell.el lisp/ob-perl.el lisp/ob-sh.el lisp/ob-R.el lisp/ob-dot.el lisp/ob-mscgen.el lisp/ob-latex.el lisp/ob-lisp.el lisp/ob-ledger.el lisp/ob-python.el lisp/ob-sql.el lisp/ob-asymptote.el lisp/ob-emacs-lisp.el lisp/ob-matlab.el lisp/ob-ruby.el lisp/ob-sqlite.el lisp/ob-clojure.el lisp/ob-ocaml.el lisp/ob-sass.el lisp/ob-css.el lisp/ob-gnuplot.el lisp/ob-octave.el lisp/ob-screen.el 
 lisp/ob-plantuml.el lisp/ob-org.el lisp/ob-js.el lisp/ob-scheme.el)))' \
| 		--eval '(insert "\n(provide (quote org-install))\n")' \
| 		--eval '(save-buffer)'
| GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0)
|  of 2011-04-13 on alphaville.dokosmarshall.org
| Loading vc-git...
| Generating autoloads for lisp/org.el...
| Generating autoloads for lisp/org.el...done
| Generating autoloads for lisp/org-agenda.el...
| ...
`----

The generated org-install.el looks like this:

,----
| \f
| ;;;### (autoloads (org-customize org-reload org-require-autoloaded-modules
| ;;;;;;  org-submit-bug-report org-cycle-agenda-files org-switchb
| ;;;;;;  org-map-entries org-open-link-from-string org-open-at-point-global
| ;;;;;;  org-insert-link-global org-store-link org-run-like-in-org-mode
| ;;;;;;  turn-on-orgstruct++ turn-on-orgstruct orgstruct-mode org-global-cycle
| ;;;;;;  org-mode org-babel-do-load-languages) "org" "lisp/org.el"
| ;;;;;;  (19976 50297))
| ;;; Generated autoloads from lisp/org.el
| 
| (autoload 'org-babel-do-load-languages "org" "\
| Load the languages defined in `org-babel-load-languages'.
| 
| \(fn SYM VALUE)" nil nil)
| 
| (autoload 'org-mode "org" "\
| Outline-based notes management and organizer, alias
| \"Carsten's outline-mode for keeping track of everything.\"
| ...
`----

Nick

Re: Problem with autoloads

[Suvayu Ali]

Hi Nick,

On Mon, 27 Jun 2011 20:13:25 -0400
Nick Dokos <nicholas.dokos@hp.com> wrote:

> The generated org-install.el looks like this:
> 

[...]

> | 
> | (autoload 'org-mode "org" "\
> | Outline-based notes management and organizer, alias
> | \"Carsten's outline-mode for keeping track of everything.\"
> | ...
> `----
> 

I also run emacs24 and my autoloads look like this. Obviously the
leading lisp/ is the problem.

(autoload 'org-mode "lisp/org" ...)

This is my setup:

emacs 24 is installed in /opt/emacs-lisp I changed the Makefile to point
EMACS to /opt/emacs-lisp/bin/emacs and ran make. It still generates the
same autoloads (with the leading lisp/).

I setup org by evaluating the following lines in an emacs session
started as emacs -Q:

(add-to-list 'load-path (expand-file-name "~/build/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "~/build/org-mode/contrib/lisp"))

;; activate org
(require 'org-install)

I get the same error again, its trying to load lisp/org instead of org.
I tried this with a fresh clone of the org-mode repository. I can't see
where I could have gone wrong here.

> Nick

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi Nick,
> 
> On Mon, 27 Jun 2011 20:13:25 -0400
> Nick Dokos <nicholas.dokos@hp.com> wrote:
> 
> > The generated org-install.el looks like this:
> > 
> 
> [...]
> 
> > | 
> > | (autoload 'org-mode "org" "\
> > | Outline-based notes management and organizer, alias
> > | \"Carsten's outline-mode for keeping track of everything.\"
> > | ...
> > `----
> > 
> 
> I also run emacs24 and my autoloads look like this. Obviously the
> leading lisp/ is the problem.
> 
> (autoload 'org-mode "lisp/org" ...)
> 
> This is my setup:
> 
> emacs 24 is installed in /opt/emacs-lisp I changed the Makefile to point
> EMACS to /opt/emacs-lisp/bin/emacs and ran make. It still generates the
> same autoloads (with the leading lisp/).
> 
> I setup org by evaluating the following lines in an emacs session
> started as emacs -Q:
> 
> (add-to-list 'load-path (expand-file-name "~/build/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name "~/build/org-mode/contrib/lisp"))
> 
> ;; activate org
> (require 'org-install)
> 
> I get the same error again, its trying to load lisp/org instead of org.
> I tried this with a fresh clone of the org-mode repository. I can't see
> where I could have gone wrong here.
> 

Suvayu and I worked on this in an email exchange: it turns out that
Michael was right in that (recent) emacs 24 is indeed the culprit. In
particular, the variable generated-autoload-file is now initialized to
nil:

,----
| (defvar generated-autoload-file nil
|   "File into which to write autoload definitions.
| A Lisp file can set this in its local variables section to make
| its autoloads go somewhere else.
| 
| If this is a relative file name, the directory is determined as
| follows:
|  - If a Lisp file defined `generated-autoload-file' as a
|    file-local variable, use its containing directory.
|  - Otherwise use the \"lisp\" subdirectory of `source-directory'.
| 
| The autoload file is assumed to contain a trailer starting with a
| FormFeed character.")
`----

whereas before (e.g. in the version of emacs 24 that I'm running: GNU
Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of
2011-04-13) it was initialized to "loaddefs.el":


,----
| (defvar generated-autoload-file "loaddefs.el"
|    "*File \\[update-file-autoloads] puts autoloads into.
| A `.el' file can set this in its local variables section to make its
| autoloads go somewhere else.  The autoload file is assumed to contain a
| trailer starting with a FormFeed character.")
`----

The particular value is not that important: the fact that it was
a relative file name is, as indicated by the comment above.

I think the following patch fixes it and does not break any earlier
versions of org. Suvayu, Michael (and anybody else who cares to try it):
would you mind checking and reporting back?

Thanks,
Nick

diff --git a/Makefile b/Makefile
index 239ab2e..08e3a08 100644
--- a/Makefile
+++ b/Makefile
@@ -230,6 +230,7 @@ autoloads: lisp/org-install.el
 
 lisp/org-install.el: $(LISPFILES0) Makefile
 	$(BATCH) --eval "(require 'autoload)" \
+		--eval '(setq generated-autoload-file "org-install.el")' \
 		--eval '(find-file "org-install.el")'  \
 		--eval '(erase-buffer)' \
 		--eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote ($(LISPFILES0))))' \

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 2506 bytes --]

On 28 Jun 2011, Nick Dokos wrote:
> <snip>
>
> Suvayu and I worked on this in an email exchange: it turns out that
> Michael was right in that (recent) emacs 24 is indeed the culprit. In
> particular, the variable generated-autoload-file is now initialized to
> nil:
>
> ,----
> | (defvar generated-autoload-file nil
> |   "File into which to write autoload definitions.
> | A Lisp file can set this in its local variables section to make
> | its autoloads go somewhere else.
> |
> | If this is a relative file name, the directory is determined as
> | follows:
> |  - If a Lisp file defined `generated-autoload-file' as a
> |    file-local variable, use its containing directory.
> |  - Otherwise use the \"lisp\" subdirectory of `source-directory'.
> |
> | The autoload file is assumed to contain a trailer starting with a
> | FormFeed character.")
> `----
>
> whereas before (e.g. in the version of emacs 24 that I'm running: GNU
> Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of
> 2011-04-13) it was initialized to "loaddefs.el":
>
>
> ,---- | (defvar generated-autoload-file "loaddefs.el" | "*File
> \\[update-file-autoloads] puts autoloads into.  | A `.el' file can set
> this in its local variables section to make its | autoloads go
> somewhere else.  The autoload file is assumed to contain a | trailer
> starting with a FormFeed character.")  `----
>
> The particular value is not that important: the fact that it was
> a relative file name is, as indicated by the comment above.
>
> I think the following patch fixes it and does not break any earlier
> versions of org. Suvayu, Michael (and anybody else who cares to try
> it): would you mind checking and reporting back?

Hi Nick,

thanks for looking into it.

But the patch doesn't work. I think that stems from the fact, that the
first thing `generate-file-autoloads' does is to bind it new:

,----
| (defun generate-file-autoloads (file)
|   "Insert at point a loaddefs autoload section for FILE.
| Autoloads are generated for defuns and defmacros in FILE
| marked by `generate-autoload-cookie' (which see).
| If FILE is being visited in a buffer, the contents of the buffer
| are used.
| Return non-nil in the case where no autoloads were added at point."
|   (interactive "fGenerate autoloads for file: ")
|   (let ((generated-autoload-file buffer-file-name))
|     (autoload-generate-file-autoloads file (current-buffer))))
`----

And because we feed it a relative file name it's bound to a relative
file name.

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Suvayu Ali]

Hi Nick,

On Tue, 28 Jun 2011 08:56:59 +0200
Michael Markert <markert.michael@googlemail.com> wrote:

> Hi Nick,
> 
> thanks for looking into it.
> 
> But the patch doesn't work. I think that stems from the fact, that the
> first thing `generate-file-autoloads' does is to bind it new:

I can confirm, I still get the error:

Cannot open load file: lisp/org

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 3182 bytes --]

On 28 Jun 2011, Michael Markert wrote:

> [1  <text/plain; US-ASCII (7bit)>]
> On 28 Jun 2011, Nick Dokos wrote:
>> <snip>
>>
>> Suvayu and I worked on this in an email exchange: it turns out that
>> Michael was right in that (recent) emacs 24 is indeed the culprit. In
>> particular, the variable generated-autoload-file is now initialized
>> to nil:
>>
>> ,----
>> | (defvar generated-autoload-file nil
>> |   "File into which to write autoload definitions.
>> | A Lisp file can set this in its local variables section to make
>> | its autoloads go somewhere else.
>> |
>> | If this is a relative file name, the directory is determined as
>> | follows:
>> |  - If a Lisp file defined `generated-autoload-file' as a
>> |    file-local variable, use its containing directory.
>> |  - Otherwise use the \"lisp\" subdirectory of `source-directory'.
>> |
>> | The autoload file is assumed to contain a trailer starting with a
>> | FormFeed character.")
>> `----
>>
>> whereas before (e.g. in the version of emacs 24 that I'm running: GNU
>> Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of
>> 2011-04-13) it was initialized to "loaddefs.el":
>>
>>
>> ,---- | (defvar generated-autoload-file "loaddefs.el" | "*File
>> \\[update-file-autoloads] puts autoloads into.  | A `.el' file can
>> set this in its local variables section to make its | autoloads go
>> somewhere else.  The autoload file is assumed to contain a | trailer
>> starting with a FormFeed character.")  `----
>>
>> The particular value is not that important: the fact that it was
>> a relative file name is, as indicated by the comment above.
>>
>> I think the following patch fixes it and does not break any earlier
>> versions of org. Suvayu, Michael (and anybody else who cares to try
>> it): would you mind checking and reporting back?

With this patch for the makefile I can get it running:

-- <snap> ---

diff --git a/Makefile b/Makefile
index 239ab2e..2d1d324 100644
--- a/Makefile
+++ b/Makefile
@@ -230,12 +230,11 @@ autoloads: lisp/org-install.el

 lisp/org-install.el: $(LISPFILES0) Makefile
 	$(BATCH) --eval "(require 'autoload)" \
-		--eval '(find-file "org-install.el")'  \
+		--eval '(find-file "lisp/org-install.el")'  \
 		--eval '(erase-buffer)' \
-		--eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote ($(LISPFILES0))))' \
+		--eval '(mapc (lambda (x) (generate-file-autoloads (symbol-name x))) (quote ($(LISPF))))' \
 		--eval '(insert "\n(provide (quote org-install))\n")' \
 		--eval '(save-buffer)'
-	mv org-install.el lisp

 doc/org: doc/org.texi
 	(cd doc && $(MAKEINFO) --no-split org.texi -o org)

-- <snap> ---

I have some problems with writing org-install directly but otherwise
autoload.el generates lisp/ autoloads (with LISPFILES0) or fails to find
(with LISPF).

But because org-install is automatically generated I don't consider them
as such grave in the case it kills the old file and leaves garbage
(maybe use a backup file?).

I tried several things that all failed:
1. Let-bind `generated-autoload-load-name' per run
2. add `generated-autoload-file' to the elisp files
3. 1. with LISPFILES0
4. ...

I'll spare you the rest. :(

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Nick Dokos]

Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi Nick,
> 
> On Tue, 28 Jun 2011 08:56:59 +0200
> Michael Markert <markert.michael@googlemail.com> wrote:
> 
> > Hi Nick,
> > 
> > thanks for looking into it.
> > 
> > But the patch doesn't work. I think that stems from the fact, that the
> > first thing `generate-file-autoloads' does is to bind it new:
> 
> I can confirm, I still get the error:
> 
> Cannot open load file: lisp/org
> 

OK, thanks to both you and Michael for checking: back to the drawing
board. Things would be easier if I could reproduce it: I'll install
emacs latest and try again.

Nick

Re: Problem with autoloads

[Nick Dokos]

Nick Dokos <nicholas.dokos@hp.com> wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> 
> > Hi Nick,
> > 
> > On Tue, 28 Jun 2011 08:56:59 +0200
> > Michael Markert <markert.michael@googlemail.com> wrote:
> > 
> > > Hi Nick,
> > > 
> > > thanks for looking into it.
> > > 
> > > But the patch doesn't work. I think that stems from the fact, that the
> > > first thing `generate-file-autoloads' does is to bind it new:
> > 
> > I can confirm, I still get the error:
> > 
> > Cannot open load file: lisp/org
> > 
> 
> OK, thanks to both you and Michael for checking: back to the drawing
> board. Things would be easier if I could reproduce it: I'll install
> emacs latest and try again.
> 

I cannot reproduce it even with latest org, latest emacs: org-install.el
makes properly with autoloads that look like this:

,----
| (autoload 'org-mode "org" "\
| Outline-based notes management and organizer, alias
| \"Carsten's outline-mode for keeping track of everything.\"
`----

No lisp/org anywhere in sight (except in comments).

I also tried with Michael's patch and it still works for me, so if
it fixes things for him and Suvayu, it should probably be applied
(but I wish I understood what goes wrong and how the patch fixes it).

Nick

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On 28 Jun 2011, Nick Dokos wrote:
> <snip>
>
> I cannot reproduce it even with latest org, latest emacs:
> org-install.el makes properly with autoloads that look like this:
>
> ,----
> | (autoload 'org-mode "org" "\
> | Outline-based notes management and organizer, alias
> | \"Carsten's outline-mode for keeping track of everything.\"
> `----
>
> No lisp/org anywhere in sight (except in comments).

That sounds great. I'm running on Julien's emacs-snapshot so I'm not
using an latest version.

> I also tried with Michael's patch and it still works for me, so if
> it fixes things for him and Suvayu, it should probably be applied

I didn't test for compability and if the problem is only temporarily it
should not be applied.

> (but I wish I understood what goes wrong and how the patch fixes it).

I try to summarize (sorry for being incomprehensible in the other mail
-- it's to hot here):

Problem: autoload.el generates file names with lisp/ prefix.
Solution:
- We generate the autoloads file in the org directory.
- To get valid file names we use the non-prefixed file names.

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Nick Dokos]

Michael Markert <markert.michael@googlemail.com> wrote:

> On 28 Jun 2011, Nick Dokos wrote:
> > <snip>
> >
> > I cannot reproduce it even with latest org, latest emacs:
> > org-install.el makes properly with autoloads that look like this:
> >
> > ,----
> > | (autoload 'org-mode "org" "\
> > | Outline-based notes management and organizer, alias
> > | \"Carsten's outline-mode for keeping track of everything.\"
> > `----
> >
> > No lisp/org anywhere in sight (except in comments).
> 
> That sounds great. I'm running on Julien's emacs-snapshot so I'm not
> using an latest version.
> 
> > I also tried with Michael's patch and it still works for me, so if
> > it fixes things for him and Suvayu, it should probably be applied
> 
> I didn't test for compability and if the problem is only temporarily it
> should not be applied.
> 
> > (but I wish I understood what goes wrong and how the patch fixes it).
> 
> I try to summarize (sorry for being incomprehensible in the other mail
> -- it's to hot here):
> 
> Problem: autoload.el generates file names with lisp/ prefix.

For you and Suvayu, but not for me. It's the discrepancy
that bothers me.

> Solution:
> - We generate the autoloads file in the org directory.
> - To get valid file names we use the non-prefixed file names.

I would like to understand the root cause.

Nick

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]

On 28 Jun 2011, Nick Dokos wrote:

> Michael Markert <markert.michael@googlemail.com> wrote:
>> <snip>
>> Problem: autoload.el generates file names with lisp/ prefix.
>
> For you and Suvayu, but not for me. It's the discrepancy
> that bothers me.

I dug into emacs because I thought "Sure, there must be some change in
the meantime", well now I'm bothered, too.
The bzr autoloads.el is identical to mine.

But this code makes me curious:

#+begin_src emacs-lisp
(defun autoload-file-load-name (file)
  "Compute the name that will be used to load FILE."
  ;; OUTFILE should be the name of the global loaddefs.el file, which
  ;; is expected to be at the root directory of the files we're
  ;; scanning for autoloads and will be in the `load-path'.
  (let* ((outfile (default-value 'generated-autoload-file))
         (name (file-relative-name file (file-name-directory outfile)))
         (names '())
         (dir (file-name-directory outfile)))
    ;; If `name' has directory components, only keep the
    ;; last few that are really needed.
    (while name
      (setq name (directory-file-name name))
      (push (file-name-nondirectory name) names)
      (setq name (file-name-directory name)))
    (while (not name)
      (cond
       ((null (cdr names)) (setq name (car names)))
       ((file-exists-p (expand-file-name "subdirs.el" dir))
        ;; FIXME: here we only check the existence of subdirs.el,
        ;; without checking its content.  This makes it generate wrong load
        ;; names for cases like lisp/term which is not added to load-path.
        (setq dir (expand-file-name (pop names) dir)))
       (t (setq name (mapconcat 'identity names "/")))))
    (if (string-match "\\.elc?\\(\\.\\|\\'\\)" name)
        (substring name 0 (match-beginning 0))
      name)))
#+end_src emacs-lisp

if I read it correctly we decompose our path-name (say lisp/org.el), by
rebasing it on outfile (org-install.el, which gives lisp/org.el) and
split in dirs, which gives '("lisp" "org.el"), then we are in the else
branch, build "lisp/org.el" and then in the last if we chop of the
".el".

I can't see how you get there correct path names :(

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Suvayu Ali]

Hello Nick and Michael,

Sorry for the delayed response. I had an important appointment.

On Tue, 28 Jun 2011 14:39:13 +0200
Michael Markert <markert.michael@googlemail.com> wrote:

> 
> With this patch for the makefile I can get it running:
> 
> -- <snap> ---
> 
> diff --git a/Makefile b/Makefile
> index 239ab2e..2d1d324 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -230,12 +230,11 @@ autoloads: lisp/org-install.el
> 
>  lisp/org-install.el: $(LISPFILES0) Makefile
>  	$(BATCH) --eval "(require 'autoload)" \
> -		--eval '(find-file "org-install.el")'  \
> +		--eval '(find-file "lisp/org-install.el")'  \
>  		--eval '(erase-buffer)' \
> -		--eval '(mapc (lambda (x) (generate-file-autoloads
> (symbol-name x))) (quote ($(LISPFILES0))))' \
> +		--eval '(mapc (lambda (x) (generate-file-autoloads
> (symbol-name x))) (quote ($(LISPF))))' \ --eval '(insert "\n(provide
> (quote org-install))\n")' \ --eval '(save-buffer)'
> -	mv org-install.el lisp
> 
>  doc/org: doc/org.texi
>  	(cd doc && $(MAKEINFO) --no-split org.texi -o org)
> 
> -- <snap> ---

This patch to the Makefile generates the autoloads without the lisp/
prefix for me and works without errors. However as Nick says, maybe its
worthwhile to understand why this was happening in the first place. My
lisp knowledge is very little, but please let me know if I can help
track this down.

> 
> Michael

Thanks a lot. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Eric S Fraga]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

[...]

> prefix for me and works without errors. However as Nick says, maybe its
> worthwhile to understand why this was happening in the first place. My
> lisp knowledge is very little, but please let me know if I can help
> track this down.

I'm jumping late into this thread so apologies first but I just wanted
to add one data point: I had this problem as well (and did mention it in
passing in some message a few weeks ago) but it disappeared.  I track
Julien's Emacs 24 builds and it would *appear* that the change in
behaviour appeared and then disappeared.  At least, my org-install.el
file suddenly had "lisp/org" and then just as suddenly did not!

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

Re: Problem with autoloads

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> [...]
> 
> > prefix for me and works without errors. However as Nick says, maybe its
> > worthwhile to understand why this was happening in the first place. My
> > lisp knowledge is very little, but please let me know if I can help
> > track this down.
> 
> I'm jumping late into this thread so apologies first but I just wanted
> to add one data point: I had this problem as well (and did mention it in
> passing in some message a few weeks ago) but it disappeared.  I track
> Julien's Emacs 24 builds and it would *appear* that the change in
> behaviour appeared and then disappeared.  At least, my org-install.el
> file suddenly had "lisp/org" and then just as suddenly did not!
> 

Good info - thanks!

BTW, where can one get at Julien's emacs 24 builds?

Nick

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

On 29 Jun 2011, Eric S. Fraga wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> [...]
>
>> prefix for me and works without errors. However as Nick says, maybe
>> its worthwhile to understand why this was happening in the first
>> place. My lisp knowledge is very little, but please let me know if I
>> can help track this down.
>
> I'm jumping late into this thread so apologies first but I just wanted
> to add one data point: I had this problem as well (and did mention it
> in passing in some message a few weeks ago) but it disappeared.  I
> track Julien's Emacs 24 builds and it would *appear* that the change
> in behaviour appeared and then disappeared.  At least, my
> org-install.el file suddenly had "lisp/org" and then just as suddenly
> did not!

Uhh this is getting more weird with every new message.

From when is your package? And what is the current state of this
problem? With the package from yesterday I still see the problem.

Like I said in another message in this thread: From looking at the
source I see no way, that autoloads could generate the path we need.

@Suvayu Do you use Julien's emacs-snapshot, too?

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[Michael Markert]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On 29 Jun 2011, Nick Dokos wrote:

> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>>
>> [...]
>>
>>> prefix for me and works without errors. However as Nick says, maybe
>>> its worthwhile to understand why this was happening in the first
>>> place. My lisp knowledge is very little, but please let me know if I
>>> can help track this down.
>>
>> I'm jumping late into this thread so apologies first but I just
>> wanted to add one data point: I had this problem as well (and did
>> mention it in passing in some message a few weeks ago) but it
>> disappeared.  I track Julien's Emacs 24 builds and it would *appear*
>> that the change in behaviour appeared and then disappeared.  At
>> least, my org-install.el file suddenly had "lisp/org" and then just
>> as suddenly did not!
>>
>
> Good info - thanks!
>
> BTW, where can one get at Julien's emacs 24 builds?

http://emacs.naquadah.org/

Michael

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: Problem with autoloads

[suvayu ali]

Hi,

On Wed, Jun 29, 2011 at 11:24 AM, Michael Markert
<markert.michael@googlemail.com> wrote:
> @Suvayu Do you use Julien's emacs-snapshot, too?
>

No I usually follow the git mirror on repo.or.cz[1] unless there is some
bugfix that I want, in that case I use the bzr repo here[2].

> Michael

Footnotes:

[1] http://repo.or.cz/w/emacs.git

[2] http://bzr.savannah.gnu.org/lh/emacs/trunk/changes

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Eric S Fraga]

Michael Markert <markert.michael@googlemail.com> writes:

> On 29 Jun 2011, Eric S. Fraga wrote:
>
>> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>>
>> [...]
>>
>>> prefix for me and works without errors. However as Nick says, maybe
>>> its worthwhile to understand why this was happening in the first
>>> place. My lisp knowledge is very little, but please let me know if I
>>> can help track this down.
>>
>> I'm jumping late into this thread so apologies first but I just wanted
>> to add one data point: I had this problem as well (and did mention it
>> in passing in some message a few weeks ago) but it disappeared.  I
>> track Julien's Emacs 24 builds and it would *appear* that the change
>> in behaviour appeared and then disappeared.  At least, my
>> org-install.el file suddenly had "lisp/org" and then just as suddenly
>> did not!
>
> Uhh this is getting more weird with every new message.
>
> From when is your package? And what is the current state of this
> problem? With the package from yesterday I still see the problem.
>
> Like I said in another message in this thread: From looking at the
> source I see no way, that autoloads could generate the path we need.
>
> @Suvayu Do you use Julien's emacs-snapshot, too?
>
> Michael

Actually, it's getting even more confusing.  My summary above is wrong.
Sorry!  However, I have three systems:

|--------+------------------------+--------------------+-------------|
| system | emacs-snapshot version | org-install format | org version |
|--------+------------------------+--------------------+-------------|
|     1. |             20110620-1 | "org"              | 2b7dbee     |
|     2. |             20110620-1 | "lisp/org"         | 2b7dbee     |
|     3. |             20110628-1 | "lisp/org"         | 560804b     |
|--------+------------------------+--------------------+-------------|

These are all Debian testing/unstable systems with slightly different
mixes of packages and two (1,2) with one commit newer than the other
(3).

Two different versions of Emacs but the different method of specifying
the autoload not matching the version of Emacs.  There's something else
going on!  I'm happy to give versions of other packages if required, of
course!

Very very strange!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.511.g2b7d)

Re: Problem with autoloads

[Eric S Fraga]

Nick Dokos <nicholas.dokos@hp.com> writes:

[...]

> BTW, where can one get at Julien's emacs 24 builds?

I get them with the following line in my /etc/apt/sources.list:

deb http://emacs.naquadah.org/ unstable/
deb-src http://emacs.naquadah.org/ unstable/

Latest version is from yesterday.  Julien tends to do a weekly
snapshot.  There are some strange window/frame problems with the latest
versions, especially to do with popups, but not deal breaking (IMO).

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.511.g2b7d)

emacs snapshot on debian and ubuntu (was: Problem with autoloads)

[Memnon Anon]

Nick Dokos <nicholas.dokos@hp.com> writes:

> BTW, where can one get at Julien's emacs 24 builds?

http://emacs.naquadah.org/

hth
Memnon

Re: Problem with autoloads

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> [...]
> 
> > BTW, where can one get at Julien's emacs 24 builds?
> 
> I get them with the following line in my /etc/apt/sources.list:
> 
> deb http://emacs.naquadah.org/ unstable/
> deb-src http://emacs.naquadah.org/ unstable/
> 

Thanks! (and to Michael as well for the reference).

Like Suvauy, I use the git mirror on repo.or.cz. I'm allergic to bzr
so I try not to go too close to savanah.

> Latest version is from yesterday.  Julien tends to do a weekly
> snapshot.  There are some strange window/frame problems with the latest
> versions, especially to do with popups, but not deal breaking (IMO).
> 

Yes, I slammed into those head-first yesterday: I got a frame for each
message viewed (I use mh-e) and for each debug trace. I ran away as fast
as possible.

Nick

Re: Problem with autoloads

[suvayu ali]

On Wed, Jun 29, 2011 at 1:02 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> Latest version is from yesterday.  Julien tends to do a weekly
>> snapshot.  There are some strange window/frame problems with the latest
>> versions, especially to do with popups, but not deal breaking (IMO).
>>
>
> Yes, I slammed into those head-first yesterday: I got a frame for each
> message viewed (I use mh-e) and for each debug trace. I ran away as fast
> as possible.
>

Those were annoying me a lot[1]! However it has been fixed in the latest
Emacs 24. I had to use bzr for the bugfix since the git mirror is behind
by several days (not sure why that is though, until March it used to be
only a few days behind).

Footnotes:

[1] The pop-ups became intolerable when exporting files with lots of
babel blocks. The problem was switch-buffer-to-other-window was behaving
as switch-buffer-to-other-frame.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Skip Collins]

On Tue, Jun 28, 2011 at 3:09 PM, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
>> diff --git a/Makefile b/Makefile
>> index 239ab2e..2d1d324 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -230,12 +230,11 @@ autoloads: lisp/org-install.el
>>
>>  lisp/org-install.el: $(LISPFILES0) Makefile
>>       $(BATCH) --eval "(require 'autoload)" \
>> -             --eval '(find-file "org-install.el")'  \
>> +             --eval '(find-file "lisp/org-install.el")'  \
>>               --eval '(erase-buffer)' \
>> -             --eval '(mapc (lambda (x) (generate-file-autoloads
>> (symbol-name x))) (quote ($(LISPFILES0))))' \
>> +             --eval '(mapc (lambda (x) (generate-file-autoloads
>> (symbol-name x))) (quote ($(LISPF))))' \ --eval '(insert "\n(provide
>> (quote org-install))\n")' \ --eval '(save-buffer)'
>> -     mv org-install.el lisp
>>
>>  doc/org: doc/org.texi
>>       (cd doc && $(MAKEINFO) --no-split org.texi -o org)
>
> This patch to the Makefile generates the autoloads without the lisp/
> prefix for me and works without errors. However as Nick says, maybe its
> worthwhile to understand why this was happening in the first place. My
> lisp knowledge is very little, but please let me know if I can help
> track this down.

Is there any more progress on finding and fixing this problem with org
and emacs24? I just built the development version of Aquamacs (GNU
Emacs 24.0.50.3). The problem with the way org autoloads lisp files is
present. Should this patch be applied to org sources?

Re: Problem with autoloads

[suvayu ali]

On Thu, Jul 14, 2011 at 7:33 PM, Skip Collins <skip.collins@gmail.com> wrote:
>> This patch to the Makefile generates the autoloads without the lisp/
>> prefix for me and works without errors. However as Nick says, maybe its
>> worthwhile to understand why this was happening in the first place. My
>> lisp knowledge is very little, but please let me know if I can help
>> track this down.
>
> Is there any more progress on finding and fixing this problem with org
> and emacs24? I just built the development version of Aquamacs (GNU
> Emacs 24.0.50.3). The problem with the way org autoloads lisp files is
> present. Should this patch be applied to org sources?

I have been using this patch since my last post, I haven't had this
problem again. But of course that doesn't say whether that means the
problem isn't present without the patch. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Problem with autoloads

[Achim Gratz]

Skip Collins <skip.collins@gmail.com> writes:
> Is there any more progress on finding and fixing this problem with org
> and emacs24? I just built the development version of Aquamacs (GNU
> Emacs 24.0.50.3). The problem with the way org autoloads lisp files is
> present. Should this patch be applied to org sources?

I've cloned emacs.git and compiled Emacs24 yesterday just to find out.
I've not drilled down to the bottom of this yet, but it is a deliberate
change in autoload.el and I'm not sure if the change in behaviour that
org-mode affects was intended or not.  If anybody frequents the Emacs
developer list, you might ask Chong Yidong (I've already sent him an
email with that question, but the devlist might be quicker).

Anyway, I intend to fix this during the restructuring of the Makefile by
building those targets in a sub-make that runs in ./lisp (unless I run
into a problem with that).  Meanwhile the patch that has been posted
fixes the issue and does not break on older Emacsen, so this should
probably be applied by Bastien.


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

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: Problem with autoloads

[Jambunathan K]

Achim Gratz <Stromeko@nexgo.de> writes:

> Skip Collins <skip.collins@gmail.com> writes:
>> Is there any more progress on finding and fixing this problem with org
>> and emacs24? I just built the development version of Aquamacs (GNU
>> Emacs 24.0.50.3). The problem with the way org autoloads lisp files is
>> present. Should this patch be applied to org sources?
>
> I've cloned emacs.git and compiled Emacs24 yesterday just to find out.
> I've not drilled down to the bottom of this yet, but it is a deliberate
> change in autoload.el and I'm not sure if the change in behaviour that
> org-mode affects was intended or not.  If anybody frequents the Emacs
> developer list, you might ask Chong Yidong (I've already sent him an
> email with that question, but the devlist might be quicker).

May be these changes deserve a NEWS entry - C-h n 
The change has caused lots of confusion at least in this list.

> Anyway, I intend to fix this during the restructuring of the Makefile by
> building those targets in a sub-make that runs in ./lisp (unless I run
> into a problem with that).  Meanwhile the patch that has been posted
> fixes the issue and does not break on older Emacsen, so this should
> probably be applied by Bastien.
>
>
> Regards,
> Achim.

-- 

Re: Problem with autoloads

[Bastien]

Achim Gratz <Stromeko@nexgo.de> writes:

> Meanwhile the patch that has been posted fixes the issue and does not
> break on older Emacsen, so this should probably be applied by Bastien.

I somehow lost track of this patch (my .overview in Gnus got corrupted)
and I cannot access Gmane as the search.gmane.org seems to be down.

Can someone send me this patch again so that I apply it?

Thanks in advance,

-- 
 Bastien

Re: Problem with autoloads

[Bastien]

Bastien <bzg@altern.org> writes:

> Can someone send me this patch again so that I apply it?

Forget it -- I just found and applied the patch.

Thanks,

-- 
 Bastien

Latex Export: Place Caption Below Table

[Jakob Lombacher]

Hi,

if I export a document to latex, the caption of a table is always on the top.

How can I place it at the bottom? Is there a parameter to config it?

Thanks

Jakob

Examaple

#+LABEL: tbl:asdf
#+CAPTION: ?????
| | |

"leads to:"
---------------

\begin{table}[htb]
\caption{?????} \label{tbl:datenstrukturen}
.....
\end{table}

I need:
----------

\begin{table}[htb]
.....
\caption{?????} \label{tbl:datenstrukturen}
\end{table}

Re: Latex Export: Place Caption Below Table

[Eric S Fraga]

Jakob Lombacher <kontakt@lombacher.net> writes:

> Hi,
>
> if I export a document to latex, the caption of a table is always on the top.
>
> How can I place it at the bottom? Is there a parameter to config it?

No, the placement is (currently) fixed to come before the tabular (or
alternative) environment.  Line 1970 or thereabouts in
org-latex.el.  Should be straightforward to modify although it is a
quite common convention to have the caption above the table...

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.7 (release_7.7.329.g15c3)

Re: Latex Export: Place Caption Below Table

[Thomas S. Dye]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Jakob Lombacher <kontakt@lombacher.net> writes:
>
>> Hi,
>>
>> if I export a document to latex, the caption of a table is always on the top.
>>
>> How can I place it at the bottom? Is there a parameter to config it?
>
> No, the placement is (currently) fixed to come before the tabular (or
> alternative) environment.  Line 1970 or thereabouts in
> org-latex.el.  Should be straightforward to modify although it is a
> quite common convention to have the caption above the table...

Hi Eric,

Are you able to propose a patch?  This came up in my work recently with
a journal that puts captions below a table (and ends them with a
period!).  

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

Re: Latex Export: Place Caption Below Table

[Nick Dokos]

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

Thomas S. Dye <tsd@tsdye.com> wrote:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> 
> > Jakob Lombacher <kontakt@lombacher.net> writes:
> >
> >> Hi,
> >>
> >> if I export a document to latex, the caption of a table is always on the top.
> >>
> >> How can I place it at the bottom? Is there a parameter to config it?
> >
> > No, the placement is (currently) fixed to come before the tabular (or
> > alternative) environment.  Line 1970 or thereabouts in
> > org-latex.el.  Should be straightforward to modify although it is a
> > quite common convention to have the caption above the table...
> 
> Hi Eric,
> 
> Are you able to propose a patch?  This came up in my work recently with
> a journal that puts captions below a table (and ends them with a
> period!).  
> 

It's just a matter of emitting the \caption after the contents of the
table, rather than before:

,----
| \begin{table}[htb]
| \begin{center}
| \begin{tabular}{rr}
| ...
| \end{tabular}
| \end{center}
| \caption{Squares}
| \end{table}
`----

instead of

,----
| \begin{table}[htb]
| \caption{Squares}
| \begin{center}
| \begin{tabular}{rr}
| ...
| \end{tabular}
| \end{center}
| \end{table}
`----


The following patch (deliberately hidden as a binary octet-stream to keep it
out of patchwork) will do that - but IMO, it would be better to have yet another
user-settable option to control the placement.

Nick


[-- Attachment #2: caption below table patch --]
[-- Type: application/octet-stream, Size: 2046 bytes --]

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 17626b5..30aa2a4 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1965,12 +1965,6 @@ (defun org-export-latex-tables (insert)
                             (concat "\\begin{longtable}{" align "}\n")
                           (if floatp
 			      (format "\\begin{%s}%s\n" tblenv placement)))
-                        (if floatp
-                            (format
-                             "\\caption%s{%s} %s"
-                             (if shortn (concat "[" shortn "]") "")
-                             (or caption "")
-			     (if label (format "\\label{%s}" label) "")))
                         (if (and longtblp caption) "\\\\\n" "\n")
                         (if (and org-export-latex-tables-centered (not longtblp))
                             "\\begin{center}\n")
@@ -1993,6 +1987,12 @@ (defun org-export-latex-tables (insert)
                         (if (not longtblp) (format "\n\\end{%s}" tabular-env))
                         (if longtblp "\n" (if org-export-latex-tables-centered
                                               "\n\\end{center}\n" "\n"))
+                        (if floatp
+                            (format
+                             "\\caption%s{%s} %s"
+                             (if shortn (concat "[" shortn "]") "")
+                             (or caption "")
+			     (if label (format "\\label{%s}" label) "")))
                         (if longtblp
                             "\\end{longtable}"
                           (if floatp (format "\\end{%s}" tblenv)))))
@@ -2042,11 +2042,11 @@ (defun org-export-latex-convert-table.el-table ()
       (setq tbl (concat "\\begin{center}\n" tbl "\\end{center}")))
     (when floatp
       (setq tbl (concat "\\begin{table}\n"
+			tbl
 			(format "\\caption%s{%s%s}\n"
 				(if shortn (format "[%s]" shortn) "")
 				(if label (format "\\label{%s}" label) "")
 				(or caption ""))
-			tbl
 			"\n\\end{table}\n")))
     (insert (org-export-latex-protect-string tbl))))
 

[PATCH] Re: Latex Export: Place Caption Below Table

[Thomas S. Dye]

[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>> 
>> > Jakob Lombacher <kontakt@lombacher.net> writes:
>> >
>> >> Hi,
>> >>
>> >> if I export a document to latex, the caption of a table is always on the top.
>> >>
>> >> How can I place it at the bottom? Is there a parameter to config it?
>> >
>> > No, the placement is (currently) fixed to come before the tabular (or
>> > alternative) environment.  Line 1970 or thereabouts in
>> > org-latex.el.  Should be straightforward to modify although it is a
>> > quite common convention to have the caption above the table...
>> 
>> Hi Eric,
>> 
>> Are you able to propose a patch?  This came up in my work recently with
>> a journal that puts captions below a table (and ends them with a
>> period!).  
>> 
>
> It's just a matter of emitting the \caption after the contents of the
> table, rather than before:
>
> ,----
> | \begin{table}[htb]
> | \begin{center}
> | \begin{tabular}{rr}
> | ...
> | \end{tabular}
> | \end{center}
> | \caption{Squares}
> | \end{table}
> `----
>
> instead of
>
> ,----
> | \begin{table}[htb]
> | \caption{Squares}
> | \begin{center}
> | \begin{tabular}{rr}
> | ...
> | \end{tabular}
> | \end{center}
> | \end{table}
> `----
>
>
> The following patch (deliberately hidden as a binary octet-stream to keep it
> out of patchwork) will do that - but IMO, it would be better to have yet another
> user-settable option to control the placement.
>
> Nick
>
>

Aloha all,

The inlined patch introduces a variable
org-export-latex-table-caption-above to control the placement of table
captions.  Thanks to Nick Dokos for leading the way on this.

Tom


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Table caption patch --]
[-- Type: text/x-patch, Size: 3097 bytes --]

From 3809f751afb8fffab1e07f7f4d6e607ed5a77b5b Mon Sep 17 00:00:00 2001
From: Tom Dye <tsd@tsdye.com>
Date: Sun, 2 Oct 2011 05:49:52 -1000
Subject: [PATCH] * lisp/org-latex.el: added variable to toggle captions below tables

---
 lisp/org-latex.el |   15 +++++++++++----
 1 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 17626b5..f91b93e 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -73,7 +73,7 @@
 	  org-deadline-string "\\|"
 	  org-closed-string"\\)")
   "Regexp matching special time planning keywords plus the time after it.")
-
+(defvar org-export-latex-table-caption-above t)
 (defvar org-re-quote)  ; dynamically scoped from org.el
 (defvar org-commentsp) ; dynamically scoped from org.el
 
@@ -1965,13 +1965,13 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER."
                             (concat "\\begin{longtable}{" align "}\n")
                           (if floatp
 			      (format "\\begin{%s}%s\n" tblenv placement)))
-                        (if floatp
+                        (if (and floatp org-export-latex-table-caption-above) 
                             (format
                              "\\caption%s{%s} %s"
                              (if shortn (concat "[" shortn "]") "")
                              (or caption "")
 			     (if label (format "\\label{%s}" label) "")))
-                        (if (and longtblp caption) "\\\\\n" "\n")
+			(if (and longtblp caption) "\\\\\n" "\n")
                         (if (and org-export-latex-tables-centered (not longtblp))
                             "\\begin{center}\n")
                         (if (not longtblp)
@@ -1993,6 +1993,12 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER."
                         (if (not longtblp) (format "\n\\end{%s}" tabular-env))
                         (if longtblp "\n" (if org-export-latex-tables-centered
                                               "\n\\end{center}\n" "\n"))
+                        (if (and floatp (not org-export-latex-table-caption-above)) 
+                            (format
+                             "\\caption%s{%s} %s"
+                             (if shortn (concat "[" shortn "]") "")
+                             (or caption "")
+			     (if label (format "\\label{%s}" label) "")))
                         (if longtblp
                             "\\end{longtable}"
                           (if floatp (format "\\end{%s}" tblenv)))))
@@ -2042,11 +2048,12 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER."
       (setq tbl (concat "\\begin{center}\n" tbl "\\end{center}")))
     (when floatp
       (setq tbl (concat "\\begin{table}\n"
+			(if (not org-export-latex-table-caption-above) tbl) 
 			(format "\\caption%s{%s%s}\n"
 				(if shortn (format "[%s]" shortn) "")
 				(if label (format "\\label{%s}" label) "")
 				(or caption ""))
-			tbl
+			(if org-export-latex-table-caption-above tbl) 
 			"\n\\end{table}\n")))
     (insert (org-export-latex-protect-string tbl))))
 
-- 
1.7.1


[-- Attachment #3: Type: text/plain, Size: 40 bytes --]


-- 
Thomas S. Dye
http://www.tsdye.com

Re: [PATCH] Re: Latex Export: Place Caption Below Table

[Eric S Fraga]

tsd@tsdye.com (Thomas S. Dye) writes:

> Nick Dokos <nicholas.dokos@hp.com> writes:

>> The following patch (deliberately hidden as a binary octet-stream to keep it
>> out of patchwork) will do that - but IMO, it would be better to have yet another
>> user-settable option to control the placement.
>>
>> Nick
>>
>>
>
> Aloha all,
>
> The inlined patch introduces a variable
> org-export-latex-table-caption-above to control the placement of table
> captions.  Thanks to Nick Dokos for leading the way on this.
>
> Tom

Tom & Nick,

thanks for doing this -- I was swamped last week so had no chance of
following the thread until today!

One comment on the last version of the patch: would it not be better for
the variable to be a defcustom variable instead of defvar?  Otherwise,
the patch looks fine to me although I'm unlikely to use the new
functionality ;-)

Thanks again,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.7 (release_7.7.340.g80931)

Re: [PATCH] Re: Latex Export: Place Caption Below Table

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> tsd@tsdye.com (Thomas S. Dye) writes:
> 
> > Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> >> The following patch (deliberately hidden as a binary octet-stream to keep it
> >> out of patchwork) will do that - but IMO, it would be better to have yet another
> >> user-settable option to control the placement.
> >>
> >> Nick
> >>
> >>
> >
> > Aloha all,
> >
> > The inlined patch introduces a variable
> > org-export-latex-table-caption-above to control the placement of table
> > captions.  Thanks to Nick Dokos for leading the way on this.
> >
> > Tom
> 
> 
> thanks for doing this -- I was swamped last week so had no chance of
> following the thread until today!
> 
> One comment on the last version of the patch: would it not be better for
> the variable to be a defcustom variable instead of defvar?

I agree - being able to customize variables without resorting to lisp is
generally preferable: it is friendlier to newcomers and it allows even
experienced users to find the various knobs.

If the patch is deemed acceptable, it might also be nice to be able to
set the variable per-file through the OPTIONS line, but that can
certainly wait.

> Otherwise,
> the patch looks fine to me although I'm unlikely to use the new
> functionality ;-)

Unless you try to publish an article in a journal with a perverse layout
policy :-)

I applied the patch and took it for a short spin. git complained about
trailing whitespace:

,----
| /home/nick/Mail/inbox/1021:197: trailing whitespace.
|                         (if (and floatp org-export-latex-table-caption-above) 
| /home/nick/Mail/inbox/1021:212: trailing whitespace.
|                         (if (and floatp (not org-export-latex-table-caption-above)) 
| /home/nick/Mail/inbox/1021:225: trailing whitespace.
| 			(if (not org-export-latex-table-caption-above) tbl) 
| /home/nick/Mail/inbox/1021:231: trailing whitespace.
| 			(if org-export-latex-table-caption-above tbl) 
| warning: 4 lines add whitespace errors.
`----

but other than that the patch worked fine.

Thanks, Tom!
Nick

Re: [PATCH] Re: Latex Export: Place Caption Below Table

[Carsten Dominik]

On 3.10.2011, at 16:43, Nick Dokos wrote:

> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> 
>> tsd@tsdye.com (Thomas S. Dye) writes:
>> 
>>> Nick Dokos <nicholas.dokos@hp.com> writes:
>> 
>>>> The following patch (deliberately hidden as a binary octet-stream to keep it
>>>> out of patchwork) will do that - but IMO, it would be better to have yet another
>>>> user-settable option to control the placement.
>>>> 
>>>> Nick
>>>> 
>>>> 
>>> 
>>> Aloha all,
>>> 
>>> The inlined patch introduces a variable
>>> org-export-latex-table-caption-above to control the placement of table
>>> captions.  Thanks to Nick Dokos for leading the way on this.
>>> 
>>> Tom
>> 
>> 
>> thanks for doing this -- I was swamped last week so had no chance of
>> following the thread until today!
>> 
>> One comment on the last version of the patch: would it not be better for
>> the variable to be a defcustom variable instead of defvar?
> 
> I agree - being able to customize variables without resorting to lisp is
> generally preferable: it is friendlier to newcomers and it allows even
> experienced users to find the various knobs.

If you provide a new patch doing a defcustom, I think this patch would be
good to have.  Please go ahead and check it in!

- Carsten

> 
> If the patch is deemed acceptable, it might also be nice to be able to
> set the variable per-file through the OPTIONS line, but that can
> certainly wait.
> 
>> Otherwise,
>> the patch looks fine to me although I'm unlikely to use the new
>> functionality ;-)
> 
> Unless you try to publish an article in a journal with a perverse layout
> policy :-)
> 
> I applied the patch and took it for a short spin. git complained about
> trailing whitespace:
> 
> ,----
> | /home/nick/Mail/inbox/1021:197: trailing whitespace.
> |                         (if (and floatp org-export-latex-table-caption-above) 
> | /home/nick/Mail/inbox/1021:212: trailing whitespace.
> |                         (if (and floatp (not org-export-latex-table-caption-above)) 
> | /home/nick/Mail/inbox/1021:225: trailing whitespace.
> | 			(if (not org-export-latex-table-caption-above) tbl) 
> | /home/nick/Mail/inbox/1021:231: trailing whitespace.
> | 			(if org-export-latex-table-caption-above tbl) 
> | warning: 4 lines add whitespace errors.
> `----
> 
> but other than that the patch worked fine.
> 
> Thanks, Tom!
> Nick
> 
> 
> 

Re: [PATCH] Re: Latex Export: Place Caption Below Table

[Thomas S. Dye]

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On 3.10.2011, at 16:43, Nick Dokos wrote:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>> 
>>> tsd@tsdye.com (Thomas S. Dye) writes:
>>> 
>>>> Nick Dokos <nicholas.dokos@hp.com> writes:
>>> 
>>>>> The following patch (deliberately hidden as a binary octet-stream to keep it
>>>>> out of patchwork) will do that - but IMO, it would be better to have yet another
>>>>> user-settable option to control the placement.
>>>>> 
>>>>> Nick
>>>>> 
>>>>> 
>>>> 
>>>> Aloha all,
>>>> 
>>>> The inlined patch introduces a variable
>>>> org-export-latex-table-caption-above to control the placement of table
>>>> captions.  Thanks to Nick Dokos for leading the way on this.
>>>> 
>>>> Tom
>>> 
>>> 
>>> thanks for doing this -- I was swamped last week so had no chance of
>>> following the thread until today!
>>> 
>>> One comment on the last version of the patch: would it not be better for
>>> the variable to be a defcustom variable instead of defvar?
>> 
>> I agree - being able to customize variables without resorting to lisp is
>> generally preferable: it is friendlier to newcomers and it allows even
>> experienced users to find the various knobs.
>
> If you provide a new patch doing a defcustom, I think this patch would be
> good to have.  Please go ahead and check it in!
>
> - Carsten
>

Aloha Carsten,

The inlined patch changes the defvar to a defcustom.  It is meant to be
applied after the first patch.

All the best,
Tom


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch 2 of 2 --]
[-- Type: text/x-patch, Size: 1476 bytes --]

From af153cdaa827903e4ada316b99adef25a735ada7 Mon Sep 17 00:00:00 2001
From: Tom Dye <tsd@tsdye.com>
Date: Sun, 9 Oct 2011 13:09:02 -1000
Subject: [PATCH 2/2] LaTeX export: Add switch to place captions above or below tables

* lisp/org-latex.el (org-export-latex-tables): Add new variable
  org-export-latex-table-caption-above

Modified from an idea suggested by Eric Fraga and fleshed out by Nick Dokos.
---
 lisp/org-latex.el |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index f91b93e..7957ffe 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -73,7 +73,6 @@
 	  org-deadline-string "\\|"
 	  org-closed-string"\\)")
   "Regexp matching special time planning keywords plus the time after it.")
-(defvar org-export-latex-table-caption-above t)
 (defvar org-re-quote)  ; dynamically scoped from org.el
 (defvar org-commentsp) ; dynamically scoped from org.el
 
@@ -364,6 +363,12 @@ When nil, grouping causes only separation lines between groups."
   :group 'org-export-latex
   :type 'boolean)
 
+(defcustom org-export-latex-table-caption-above t
+  "When non-nil, the caption is set above the table.  When nil,
+the caption is set below the table."
+  :group 'org-export-latex
+  :type 'boolean)
+
 (defcustom org-export-latex-low-levels 'itemize
   "How to convert sections below the current level of sectioning.
 This is specified by the `org-export-headline-levels' option or the
-- 
1.7.1


[-- Attachment #3: Type: text/plain, Size: 1197 bytes --]



>> 
>> If the patch is deemed acceptable, it might also be nice to be able to
>> set the variable per-file through the OPTIONS line, but that can
>> certainly wait.
>> 
>>> Otherwise,
>>> the patch looks fine to me although I'm unlikely to use the new
>>> functionality ;-)
>> 
>> Unless you try to publish an article in a journal with a perverse layout
>> policy :-)
>> 
>> I applied the patch and took it for a short spin. git complained about
>> trailing whitespace:
>> 
>> ,----
>> | /home/nick/Mail/inbox/1021:197: trailing whitespace.
>> |                         (if (and floatp org-export-latex-table-caption-above) 
>> | /home/nick/Mail/inbox/1021:212: trailing whitespace.
>> |                         (if (and floatp (not org-export-latex-table-caption-above)) 
>> | /home/nick/Mail/inbox/1021:225: trailing whitespace.
>> | 			(if (not org-export-latex-table-caption-above) tbl) 
>> | /home/nick/Mail/inbox/1021:231: trailing whitespace.
>> | 			(if org-export-latex-table-caption-above tbl) 
>> | warning: 4 lines add whitespace errors.
>> `----
>> 
>> but other than that the patch worked fine.
>> 
>> Thanks, Tom!
>> Nick
>> 
>> 
>> 
>
>
>

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [PATCH] Re: Latex Export: Place Caption Below Table

[Carsten Dominik]

Applied, thanks.

- Carsten

On 10.10.2011, at 01:24, Thomas S. Dye wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
> 
>> On 3.10.2011, at 16:43, Nick Dokos wrote:
>> 
>>> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>>> 
>>>> tsd@tsdye.com (Thomas S. Dye) writes:
>>>> 
>>>>> Nick Dokos <nicholas.dokos@hp.com> writes:
>>>> 
>>>>>> The following patch (deliberately hidden as a binary octet-stream to keep it
>>>>>> out of patchwork) will do that - but IMO, it would be better to have yet another
>>>>>> user-settable option to control the placement.
>>>>>> 
>>>>>> Nick
>>>>>> 
>>>>>> 
>>>>> 
>>>>> Aloha all,
>>>>> 
>>>>> The inlined patch introduces a variable
>>>>> org-export-latex-table-caption-above to control the placement of table
>>>>> captions.  Thanks to Nick Dokos for leading the way on this.
>>>>> 
>>>>> Tom
>>>> 
>>>> 
>>>> thanks for doing this -- I was swamped last week so had no chance of
>>>> following the thread until today!
>>>> 
>>>> One comment on the last version of the patch: would it not be better for
>>>> the variable to be a defcustom variable instead of defvar?
>>> 
>>> I agree - being able to customize variables without resorting to lisp is
>>> generally preferable: it is friendlier to newcomers and it allows even
>>> experienced users to find the various knobs.
>> 
>> If you provide a new patch doing a defcustom, I think this patch would be
>> good to have.  Please go ahead and check it in!
>> 
>> - Carsten
>> 
> 
> Aloha Carsten,
> 
> The inlined patch changes the defvar to a defcustom.  It is meant to be
> applied after the first patch.
> 
> All the best,
> Tom
> 
> From af153cdaa827903e4ada316b99adef25a735ada7 Mon Sep 17 00:00:00 2001
> From: Tom Dye <tsd@tsdye.com>
> Date: Sun, 9 Oct 2011 13:09:02 -1000
> Subject: [PATCH 2/2] LaTeX export: Add switch to place captions above or below tables
> 
> * lisp/org-latex.el (org-export-latex-tables): Add new variable
>  org-export-latex-table-caption-above
> 
> Modified from an idea suggested by Eric Fraga and fleshed out by Nick Dokos.
> ---
> lisp/org-latex.el |    7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
> 
> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
> index f91b93e..7957ffe 100644
> --- a/lisp/org-latex.el
> +++ b/lisp/org-latex.el
> @@ -73,7 +73,6 @@
> 	  org-deadline-string "\\|"
> 	  org-closed-string"\\)")
>   "Regexp matching special time planning keywords plus the time after it.")
> -(defvar org-export-latex-table-caption-above t)
> (defvar org-re-quote)  ; dynamically scoped from org.el
> (defvar org-commentsp) ; dynamically scoped from org.el
> 
> @@ -364,6 +363,12 @@ When nil, grouping causes only separation lines between groups."
>   :group 'org-export-latex
>   :type 'boolean)
> 
> +(defcustom org-export-latex-table-caption-above t
> +  "When non-nil, the caption is set above the table.  When nil,
> +the caption is set below the table."
> +  :group 'org-export-latex
> +  :type 'boolean)
> +
> (defcustom org-export-latex-low-levels 'itemize
>   "How to convert sections below the current level of sectioning.
> This is specified by the `org-export-headline-levels' option or the
> -- 
> 1.7.1
> 
> 
> 
>>> 
>>> If the patch is deemed acceptable, it might also be nice to be able to
>>> set the variable per-file through the OPTIONS line, but that can
>>> certainly wait.
>>> 
>>>> Otherwise,
>>>> the patch looks fine to me although I'm unlikely to use the new
>>>> functionality ;-)
>>> 
>>> Unless you try to publish an article in a journal with a perverse layout
>>> policy :-)
>>> 
>>> I applied the patch and took it for a short spin. git complained about
>>> trailing whitespace:
>>> 
>>> ,----
>>> | /home/nick/Mail/inbox/1021:197: trailing whitespace.
>>> |                         (if (and floatp org-export-latex-table-caption-above) 
>>> | /home/nick/Mail/inbox/1021:212: trailing whitespace.
>>> |                         (if (and floatp (not org-export-latex-table-caption-above)) 
>>> | /home/nick/Mail/inbox/1021:225: trailing whitespace.
>>> | 			(if (not org-export-latex-table-caption-above) tbl) 
>>> | /home/nick/Mail/inbox/1021:231: trailing whitespace.
>>> | 			(if org-export-latex-table-caption-above tbl) 
>>> | warning: 4 lines add whitespace errors.
>>> `----
>>> 
>>> but other than that the patch worked fine.
>>> 
>>> Thanks, Tom!
>>> Nick
>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> -- 
> Thomas S. Dye
> http://www.tsdye.com

Can't have tags with a dash

[Marcelo de Moraes Serpa]

[-- Attachment #1: Type: text/plain, Size: 228 bytes --]

Hi guys,

I've noticed org can't handle a single tag with a dash in it. If I try to
tag an item with 'payment-integration' for example, org turns it into two
tags - ':payment:integration'. Is that intended?

Cheers,

- Marcelo.

[-- Attachment #2: Type: text/html, Size: 325 bytes --]

Re: Can't have tags with a dash

[suvayu ali]

On Wed, Oct 12, 2011 at 7:37 PM, Marcelo de Moraes Serpa
<celoserpa@gmail.com> wrote:
> I've noticed org can't handle a single tag with a dash in it. If I try to
> tag an item with 'payment-integration' for example, org turns it into two
> tags - ':payment:integration'. Is that intended?

I believe so.

-- 
Suvayu

Open source is the future. It sets us free.

Re: Can't have tags with a dash

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> On Wed, Oct 12, 2011 at 7:37 PM, Marcelo de Moraes Serpa
> <celoserpa@gmail.com> wrote:
> > I've noticed org can't handle a single tag with a dash in it. If I try to
> > tag an item with 'payment-integration' for example, org turns it into two
> > tags - ':payment:integration'. Is that intended?
> 
> I believe so.
> 

Yes - look at the match syntax for tags: (info "(org) Matching tags and properties")

Nick

Re: Can't have tags with a dash

[Marcelo de Moraes Serpa]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

Thanks.

On Wed, Oct 12, 2011 at 1:08 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
> > On Wed, Oct 12, 2011 at 7:37 PM, Marcelo de Moraes Serpa
> > <celoserpa@gmail.com> wrote:
> > > I've noticed org can't handle a single tag with a dash in it. If I try
> to
> > > tag an item with 'payment-integration' for example, org turns it into
> two
> > > tags - ':payment:integration'. Is that intended?
> >
> > I believe so.
> >
>
> Yes - look at the match syntax for tags: (info "(org) Matching tags and
> properties")
>
> Nick
>
>

[-- Attachment #2: Type: text/html, Size: 1078 bytes --]

Variable settings in .emacs VS cross device portability.

[Yu]

Hello!

I was wondering if there is a possibility to make org-files fully
portable in behaviour (especially when exporting) between different
emacs installations.

When reading the mailing list or other writing about org-mode,
commonly suggestions of the type "just add (setq org-foo bar) to your
.emacs". This however creates a dependency on the local setup of the
variables, which likely will be a problem, when sharing the file with
someone.

My current solution is to use a template file with #+BIND: and
#+PROPERTY: lines in a setup section rather than setting anything in
configuration files.

However, is there some way to turn a user-variable dependent file into
a portable file? I was thinking of something along the lines of
"dumping user-specified variables into a list of #+BIND lines" and, if
necessary, the magic "-*- var: value -*-" line at the start of the
file (or, less elegant because of spreading options across different
positions in the file) the commented "local variables" structure near
the end of the file. The latter two variants only apply if I am right
about #+BIND lines applying only during export (whereas the magic
emacs lines should create buffer-local bindings).

king regards, Yu

Re: Variable settings in .emacs VS cross device portability.

[Thomas S. Dye]

Yu <yu_icq@gmx.at> writes:

> Hello!
>
> I was wondering if there is a possibility to make org-files fully
> portable in behaviour (especially when exporting) between different
> emacs installations.
>
> When reading the mailing list or other writing about org-mode,
> commonly suggestions of the type "just add (setq org-foo bar) to your
> .emacs". This however creates a dependency on the local setup of the
> variables, which likely will be a problem, when sharing the file with
> someone.
>
> My current solution is to use a template file with #+BIND: and
> #+PROPERTY: lines in a setup section rather than setting anything in
> configuration files.
>
> However, is there some way to turn a user-variable dependent file into
> a portable file? I was thinking of something along the lines of
> "dumping user-specified variables into a list of #+BIND lines" and, if
> necessary, the magic "-*- var: value -*-" line at the start of the
> file (or, less elegant because of spreading options across different
> positions in the file) the commented "local variables" structure near
> the end of the file. The latter two variants only apply if I am right
> about #+BIND lines applying only during export (whereas the magic
> emacs lines should create buffer-local bindings).

Aloha Yu,

I favor Eric Schulte's solution for reproducible research, which you can
find here:

http://www.jstatsoft.org/v46/i03

The trick is to launch a fresh instance of Emacs and supply it with an
initialization file tailored to the content.  Eric uses a Makefile for
this, and I've been able to copy and tweak his Makefile for use on other
projects. 

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Variable settings in .emacs VS cross device portability.

[Eric Schulte]

Yu <yu_icq@gmx.at> writes:

> Hello!
>
> I was wondering if there is a possibility to make org-files fully
> portable in behaviour (especially when exporting) between different
> emacs installations.
>

File Local Variables [1] make it possible to explicitly specify the
values of variables from within the text of a .org file.  This can be
placed in a single line at the top of a file for small changes or in a
larger section at the end of the file.

Cheers,

>
> When reading the mailing list or other writing about org-mode,
> commonly suggestions of the type "just add (setq org-foo bar) to your
> .emacs". This however creates a dependency on the local setup of the
> variables, which likely will be a problem, when sharing the file with
> someone.
>
> My current solution is to use a template file with #+BIND: and
> #+PROPERTY: lines in a setup section rather than setting anything in
> configuration files.
>
> However, is there some way to turn a user-variable dependent file into
> a portable file? I was thinking of something along the lines of
> "dumping user-specified variables into a list of #+BIND lines" and, if
> necessary, the magic "-*- var: value -*-" line at the start of the
> file (or, less elegant because of spreading options across different
> positions in the file) the commented "local variables" structure near
> the end of the file. The latter two variants only apply if I am right
> about #+BIND lines applying only during export (whereas the magic
> emacs lines should create buffer-local bindings).
>
> king regards, Yu
>


Footnotes: 
[1]  http://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

Eric Schulte <eric.schulte@gmx.com> writes:

[...]

> File Local Variables [1] make it possible to explicitly specify the
> values of variables from within the text of a .org file.  This can be
> placed in a single line at the top of a file for small changes or in a
> larger section at the end of the file.

Eric,

this doesn't always seem to work, at least not for me.  BIND always
works but certain org variables seem to be ignored when set using local
file variables.

The variables I refer to are often, maybe always (?), related to export
functions.  My gut feeling is that this has something to do with a copy
of the file being made for the export and maybe emacs not getting a
chance to set local variables for that copy?  Grasping at straws here,
mind you ;-)

I have no idea how to debug such behaviour but I have experienced this
for a long time now.  Any hints would be welcome, of course!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.283.g171ea)

Re: Variable settings in .emacs VS cross device portability.

[Yu]

2012/1/31 Eric S Fraga <e.fraga@ucl.ac.uk>:
> Eric Schulte <eric.schulte@gmx.com> writes:
>
> [...]
>
>> File Local Variables [1] make it possible to explicitly specify the
>> values of variables from within the text of a .org file.  This can be
>> placed in a single line at the top of a file for small changes or in a
>> larger section at the end of the file.
>
> Eric,
>
> this doesn't always seem to work, at least not for me.  BIND always
> works but certain org variables seem to be ignored when set using local
> file variables.
>
> The variables I refer to are often, maybe always (?), related to export
> functions.  My gut feeling is that this has something to do with a copy
> of the file being made for the export and maybe emacs not getting a
> chance to set local variables for that copy?  Grasping at straws here,
> mind you ;-)

For #+BIND the org manual is probably not quite clear.

The "Concept Index" page says:
: * #+BIND:                                Export options.      (line  19)

"12.2 Export options" says:
:      #+BIND:        lisp-var lisp-val, e.g.:
org-export-latex-low-levels itemize
:                     You need to confirm using these, or configure
`org-export-allow-BIND'

So basically, #+BIND only applies to export, though the manual maybe
slightly underemphasizes that fact.

Did you try the general emacs syntax for file variables, Eric Schulte
mentioned? [1] For me that worked (except that non-safe variables
require confirmation in order to avoid text files executing harmful
code). The emacs-documentation doesn't mention it, but apparently this
works also in shebang'ed files, by moving the single line form (`-*-
... -*-') to the second line. [2]

[1] http://www.gnu.org/software/emacs/manual/html_node/emacs/File-Variables.html
[2] http://www.lugaru.com/man/File.Variables.html

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

Yu <yu_icq@gmx.at> writes:

[...]

> Did you try the general emacs syntax for file variables, Eric Schulte
> mentioned? [1] For me that worked (except that non-safe variables
> require confirmation in order to avoid text files executing harmful
> code). The emacs-documentation doesn't mention it, but apparently this
> works also in shebang'ed files, by moving the single line form (`-*-
> ... -*-') to the second line. [2]
>
> [1] http://www.gnu.org/software/emacs/manual/html_node/emacs/File-Variables.html
> [2] http://www.lugaru.com/man/File.Variables.html

Yu,

Thanks for this.

I use file local variables all the time, both with and without org, and
have done so for years!  I also use BIND successfully.

My point was that org seems to ignore some variables that have been set
using file local variables and I think it's only those that affect the
export behaviour that are ignored.  Hence my gut feeling regarding
whether exporting doesn't actually set file local variables due to the
export working on a copy of the buffer.  But I am not entirely sure what
the interaction between the export process and Emacs may be in this
case.

Maybe others have a better intuition.

I'll try to come up with a minimal example that illustrates the problem.


-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.285.g646b3)

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

Hello all,

herewith is a minimal example that illustrates the problem I have with
exporting and file local variables.  The attached file re-defines
org-export-latex-tag-markup to use a box instead of bold for tags.  When
I visit the file, Emacs does indeed set the variable to what I
want. However, this setting is ignored on export.

Actually, in this case, the BIND is also ignored on export even though
the variable does change to the specified value after export!

I am very confused, to say the least.  *How* can I get file local
behaviour when exporting with org?  Am I doing something silly
somewhere?  (highly likely given my past track record ;-)  Do others see
different behaviour?

I'm up to date (as of this morning) with org and latest emacs as of last
week.

Thanks,
eric


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: export variables ignored --]
[-- Type: text/orgmode, Size: 399 bytes --]

# -*- org-export-latex-tag-markup: "locally set: \\fbox{%s}"; -*-
#+TITLE:     examplebug.org
#+AUTHOR:    Eric S Fraga
#+EMAIL:     e.fraga@ucl.ac.uk
#+DATE:      2012-01-09 Mon

#+bind: org-export-latex-tag-markup  "bound: \\fbox{%s}"

* Formatting tags                                                   :example:
  When exporting, the default is to put tags in bold.  I want a box around them.



[-- Attachment #3: Type: text/plain, Size: 128 bytes --]



-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.285.g646b3)

Re: Variable settings in .emacs VS cross device portability.

[Sebastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> herewith is a minimal example that illustrates the problem I have with
> exporting and file local variables.  The attached file re-defines
> org-export-latex-tag-markup to use a box instead of bold for tags.  When
> I visit the file, Emacs does indeed set the variable to what I
> want. However, this setting is ignored on export.
>
> Actually, in this case, the BIND is also ignored on export even though
> the variable does change to the specified value after export!
>
> I am very confused, to say the least.  *How* can I get file local
> behaviour when exporting with org?  Am I doing something silly
> somewhere?  (highly likely given my past track record ;-)  Do others see
> different behaviour?
>
> I'm up to date (as of this morning) with org and latest emacs as of last
> week.
>
> Thanks,
> eric
>
>
> # -*- org-export-latex-tag-markup: "locally set: \\fbox{%s}"; -*-
> #+TITLE:     examplebug.org
> #+AUTHOR:    Eric S Fraga
> #+EMAIL:     e.fraga-hclig2XLE9Zaa/9Udqfwiw@public.gmane.org
> #+DATE:      2012-01-09 Mon
>
> #+bind: org-export-latex-tag-markup  "bound: \\fbox{%s}"
>
> * Formatting tags                                                   :example:
>   When exporting, the default is to put tags in bold.  I want a box around them.

I almost never play(ed) with local variables and bind variables, but I wanted
to confirm what you see:

the local variable is the one set by your bind; but it has no impact on the
exported LaTeX file...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

[...]

> I almost never play(ed) with local variables and bind variables, but I wanted
> to confirm what you see:
>
> the local variable is the one set by your bind; but it has no impact on the
> exported LaTeX file...
>
> Best regards,
>   Seb

Thanks for the confirmation.  At least I am not going completely crazy
;-)

Does the local variable setting defined in the file take effect before
you export?

Thanks again,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.288.ga3e5f)

Re: Variable settings in .emacs VS cross device portability.

[Sebastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> I almost never play(ed) with local variables and bind variables, but I
>> wanted to confirm what you see:
>>
>> the local variable is the one set by your bind; but it has no impact on the
>> exported LaTeX file...
>
> Thanks for the confirmation.  At least I am not going completely crazy
> ;-)
>
> Does the local variable setting defined in the file take effect before
> you export?

After saving your file to disk, and opening it:

    ┏━━━━
    ┃ org-export-latex-tag-markup is a variable defined in `org-latex.el'.
    ┃ Its value is "locally set: \\fbox{%s}"
    ┃ Original value was "\\textbf{%s}"
    ┃ Local in buffer examplebug.org; global value is 
    ┃ "<what is in my Emacs config file>"
    ┃ 
    ┃   This variable is a file local variable.
    ┗━━━━

After exporting it to LaTeX, answering yes to the question about allowing to
BIND variables:

    ┏━━━━
    ┃ org-export-latex-tag-markup is a variable defined in `org-latex.el'.
    ┃ Its value is "bound: \\fbox{%s}"
    ┃ Original value was "\\textbf{%s}"
    ┃ Local in buffer examplebug.org; global value is 
    ┃ "<what is in my Emacs config file>"
    ┗━━━━

So, yes to your above question...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Variable settings in .emacs VS cross device portability.

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Hello all,
> 
> herewith is a minimal example that illustrates the problem I have with
> exporting and file local variables.  The attached file re-defines
> org-export-latex-tag-markup to use a box instead of bold for tags.  When
> I visit the file, Emacs does indeed set the variable to what I
> want. However, this setting is ignored on export.
> 
> Actually, in this case, the BIND is also ignored on export even though
> the variable does change to the specified value after export!
> 
> I am very confused, to say the least.  *How* can I get file local
> behaviour when exporting with org?  Am I doing something silly
> somewhere?  (highly likely given my past track record ;-)  Do others see
> different behaviour?
> 

Good question (I mean the *How* question): I believe this is a bug and
it has to do with the problem that Dan Davison identified and (as it
turns out) partially fixed a year ago (see
http://thread.gmane.org/gmane.emacs.orgmode/35439/focus=36878 for those
details).

In a nutshell, the problem is that many export operations happen in
temporary buffers.  These buffers do not automatically inherit local
variables, so the global setting is in force. Dan introduced a "clone
local variables" function and arranged for it to be called in
org-export-preprocess-string. However, the latter function operates on a
temp buffer, so when it returns (it returns the contents of the temp
buffer as as a string), the buffer is gone - and so are the local
variables.

The latex exporter then continues mucking around with the returned
string. The org-export-latex-markup variable is used in the function
org-export-latex-keywords-maybe.  At the relevant moment, the call stack
looks like this:


,----
|   org-export-latex-keywords-maybe()
|   org-export-latex-fontify-headline(#(" Formatting tags :example:" 1 16 ...))
|   org-export-latex-subcontent(...)
|   org-export-latex-sub(...)
|   org-export-latex-global(...)
|   (let* (...) (set-buffer buffer) (erase-buffer) (org-install-letbind) ... (org-export-latex-global (with-temp-buffer (insert string-for-export)) ...) ...)
|   org-export-as-latex(nil nil nil "*Org LaTeX Export*")
|   org-export-as-latex-to-buffer(nil)
|   call-interactively(org-export-as-latex-to-buffer)
`----

Note that org-export-latex-global is called with a temp buffer and
neither it nor any of its successors clones local variables. So you end
up in org-export-latex-keywords-maybe with the global settings in force.

The quick-and-dirty hack would be to call Dan's cloning function in the
call to with-temp-buffer, but that's not enough:
org-export-latex-fontify-headline does the temp-buffer thingie as well
and needs the same treatment. That seems to make *this* case work but I'm
almost 100% sure that that won't be enough in the general case either:
there are probably other places where temp buffers are created to do
some processing like this. They will also be subject to this problem.

Nick

> I'm up to date (as of this morning) with org and latest emacs as of last
> week.
> 
> Thanks,
> eric
> 
> 
> 
> -- 
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
> : using Org-mode version 7.8.03 (release_7.8.03.285.g646b3)

Emacs/Org-mode configs spread over multiple accounts/machines (was: Variable settings in .emacs VS cross device portability.)

[Karl Voit]

* Yu <yu_icq@gmx.at> wrote:
> Hello!
>
> I was wondering if there is a possibility to make org-files fully
> portable in behaviour (especially when exporting) between different
> emacs installations.

The Tread has turned into BIND and local variables only.  I wanted
to add my current solution which uses a different approach.

My ~/.emacs is a symlink to ~/hosts/${HOSTNAME}/emacs where
host-specific or platform-specific configuration is stored. The
directory ~/hosts is synchronized[1] on all of my machines and
accounts.

In ~/hosts/all/emacs.d/* I have got myorgmode.el, mycommon.el,
myauctex.el, myedit-server.el, mypython.el, and so forth.

As you can imagine, the ~/hosts/${HOSTNAME}/emacs contains a load
command for mycommon.el which refers to all the other el files.

Therefore mycommon.el and all the others are identical on all my
machines whereas ~/.emacs contains (only few) platform-specific
things.

Maybe this is a possible attempt to overcome your problems when
using Org-mode on different machines.

  1. I am currently using Unison File Synchronizer[2] in combination
     with crond/LaunchCtl but git or something like dvcs-autosync[3] 
     or even Dropbox will work too.
  2. http://www.cis.upenn.edu/~bcpierce/unison/
  3. http://www.mayrhofer.eu.org/dvcs-autosync
-- 
Karl Voit

Re: Emacs/Org-mode configs spread over multiple accounts/machines (was: Variable settings in .emacs VS cross device portability.)

[Alan E. Davis]

[-- Attachment #1: Type: text/plain, Size: 2631 bytes --]

My setup, while far from ideal, is working pretty well.  It does require a
modicum of manual oversight.

I have a directory, ~/WorkBench , in which all of my going work is
located.  Dozens of subdirectories including every project I have worked on
or am working on, with PDFs, etc.  In ~/WorkBench/org are some setup files:

   org-init-settings.el
   org-local-init-settings.el         (included in .gitignore)
   emacs-common-settings.el   (all machines)
   emacs-local-settings.el         (local machine --- included in
.gitignore)
   emacs-frame-setup-magic.el

The directory ~/WorkBench and all subdirectories are under git supervision,
so long as it stays smaller than about 3 GB.  In that case, it can be
carried around on an 8GB flash drive, and cloned on other machines, though
I've had to delete and reclone, once the repo got too large.   It could be
cloned to Dropbox if I wanted to spend money on it, and trusted it.

I really like this setup, the use of git.  However, I am using git at the
most trivial level, and perhaps there are more direct ways to do this.

The next step is to encrypt the whole thing.  I have encrypted a couple of
sensitive files using bcrypt.

Alan



On Thu, Feb 2, 2012 at 5:59 AM, Karl Voit <devnull@karl-voit.at> wrote:

> * Yu <yu_icq@gmx.at> wrote:
> > Hello!
> >
> > I was wondering if there is a possibility to make org-files fully
> > portable in behaviour (especially when exporting) between different
> > emacs installations.
>
> The Tread has turned into BIND and local variables only.  I wanted
> to add my current solution which uses a different approach.
>
> My ~/.emacs is a symlink to ~/hosts/${HOSTNAME}/emacs where
> host-specific or platform-specific configuration is stored. The
> directory ~/hosts is synchronized[1] on all of my machines and
> accounts.
>
> In ~/hosts/all/emacs.d/* I have got myorgmode.el, mycommon.el,
> myauctex.el, myedit-server.el, mypython.el, and so forth.
>
> As you can imagine, the ~/hosts/${HOSTNAME}/emacs contains a load
> command for mycommon.el which refers to all the other el files.
>
> Therefore mycommon.el and all the others are identical on all my
> machines whereas ~/.emacs contains (only few) platform-specific
> things.
>
> Maybe this is a possible attempt to overcome your problems when
> using Org-mode on different machines.
>
>  1. I am currently using Unison File Synchronizer[2] in combination
>     with crond/LaunchCtl but git or something like dvcs-autosync[3]
>     or even Dropbox will work too.
>  2. http://www.cis.upenn.edu/~bcpierce/unison/
>  3. http://www.mayrhofer.eu.org/dvcs-autosync
> --
> Karl Voit
>
>
>

[-- Attachment #2: Type: text/html, Size: 3330 bytes --]

Re: Emacs/Org-mode configs spread over multiple accounts/machines (was: Variable settings in .emacs VS cross device portability.)

[Alan E. Davis]

[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]

By the way, all of these are called from .emacs.el .   Another point, I
have elected not to byte-compile the loaded elisp files in
~/WorkBench/Emacs , so they will load ok on multiple versions of emacs.

On Thu, Feb 2, 2012 at 7:16 AM, Alan E. Davis <lngndvs@gmail.com> wrote:

> My setup, while far from ideal, is working pretty well.  It does require a
> modicum of manual oversight.
>
> I have a directory, ~/WorkBench , in which all of my going work is
> located.  Dozens of subdirectories including every project I have worked on
> or am working on, with PDFs, etc.  In ~/WorkBench/org are some setup files:
>
>    org-init-settings.el
>    org-local-init-settings.el         (included in .gitignore)
>    emacs-common-settings.el   (all machines)
>    emacs-local-settings.el         (local machine --- included in
> .gitignore)
>    emacs-frame-setup-magic.el
>
> The directory ~/WorkBench and all subdirectories are under git
> supervision, so long as it stays smaller than about 3 GB.  In that case, it
> can be carried around on an 8GB flash drive, and cloned on other machines,
> though I've had to delete and reclone, once the repo got too large.   It
> could be cloned to Dropbox if I wanted to spend money on it, and trusted
> it.
>
> I really like this setup, the use of git.  However, I am using git at the
> most trivial level, and perhaps there are more direct ways to do this.
>
> The next step is to encrypt the whole thing.  I have encrypted a couple of
> sensitive files using bcrypt.
>
> Alan
>
>
>
>
> On Thu, Feb 2, 2012 at 5:59 AM, Karl Voit <devnull@karl-voit.at> wrote:
>
>> * Yu <yu_icq@gmx.at> wrote:
>> > Hello!
>> >
>> > I was wondering if there is a possibility to make org-files fully
>> > portable in behaviour (especially when exporting) between different
>> > emacs installations.
>>
>> The Tread has turned into BIND and local variables only.  I wanted
>> to add my current solution which uses a different approach.
>>
>> My ~/.emacs is a symlink to ~/hosts/${HOSTNAME}/emacs where
>> host-specific or platform-specific configuration is stored. The
>> directory ~/hosts is synchronized[1] on all of my machines and
>> accounts.
>>
>> In ~/hosts/all/emacs.d/* I have got myorgmode.el, mycommon.el,
>> myauctex.el, myedit-server.el, mypython.el, and so forth.
>>
>> As you can imagine, the ~/hosts/${HOSTNAME}/emacs contains a load
>> command for mycommon.el which refers to all the other el files.
>>
>> Therefore mycommon.el and all the others are identical on all my
>> machines whereas ~/.emacs contains (only few) platform-specific
>> things.
>>
>> Maybe this is a possible attempt to overcome your problems when
>> using Org-mode on different machines.
>>
>>  1. I am currently using Unison File Synchronizer[2] in combination
>>     with crond/LaunchCtl but git or something like dvcs-autosync[3]
>>     or even Dropbox will work too.
>>  2. http://www.cis.upenn.edu/~bcpierce/unison/
>>  3. http://www.mayrhofer.eu.org/dvcs-autosync
>> --
>> Karl Voit
>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 3976 bytes --]

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 2660 bytes --]

Nick Dokos <nicholas.dokos@hp.com> writes:

[...]

> Good question (I mean the *How* question): I believe this is a bug and
> it has to do with the problem that Dan Davison identified and (as it
> turns out) partially fixed a year ago (see
> http://thread.gmane.org/gmane.emacs.orgmode/35439/focus=36878 for those
> details).
>
> In a nutshell, the problem is that many export operations happen in
> temporary buffers.  These buffers do not automatically inherit local

[...]

Nick,

Many thanks for this analysis.  My gut feeling was indeed correct
(whew!), probably because I subconsciously remembered reading the thread
from Dan Davison.

> The quick-and-dirty hack would be to call Dan's cloning function in the
> call to with-temp-buffer, but that's not enough:
> org-export-latex-fontify-headline does the temp-buffer thingie as well
> and needs the same treatment. That seems to make *this* case work but I'm
> almost 100% sure that that won't be enough in the general case either:
> there are probably other places where temp buffers are created to do
> some processing like this. They will also be subject to this problem.

I must admit I am confused as to the point of #+BIND now.  I had thought
the whole purpose was to set variables to be used during the export
process but now it seems this is not the case.  Or it is only the case
for some subset of the variables that may affect the export process.

I don't care whether I need to use file local variables, #+BIND, or any
other mechanism but it would be nice to have some mechanism!  So, can
anybody suggest any hack around this problem?  I am not terribly worried
about this as it only causes me difficulties now and again when I have a
specific type of document I need to generate for
dissemination.  Usually, my default settings are fine.  However, it
would be nice to have some solution to this.

I can have an emacs lisp code block which gets executed to set
the values of those variables.  This works (see attachment), so long as
I don't have any other controls for settings these variables, including
file local variables or #+BIND.  However, I need to manually execute
this code block if it is hidden away in a not-exported region of the
document.  Otherwise, it clogs up the text (but such is life!).

Note, however, that this changes the variable value globally and so will
affect exporting of any other subsequent org documents unless they have
their own settings.  Not *good* but good enough for my own use case for
the moment... and, actually, having explicit settings for export
variables in every *important* document is probably not a bad
idea.  Ummm, need to think about this.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: examplebug.org --]
[-- Type: text/org, Size: 503 bytes --]

#+TITLE:     examplebug.org
#+AUTHOR:    Eric S Fraga
#+EMAIL:     e.fraga@ucl.ac.uk
#+DATE:      2012-01-09 Mon

* Formatting tags                                                   :example:
  When exporting, the default is to put tags in bold.  I want a box around them.


# the following is used to set some variables which affect export to latex
  #+name: export-settings
  #+begin_src emacs-lisp :exports results :results silent
(setq org-export-latex-tag-markup "babel: \\fbox{%s}")
  #+end_src



[-- Attachment #3: Type: text/plain, Size: 154 bytes --]


Anyway, thanks again,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.293.g36cc)

Re: Variable settings in .emacs VS cross device portability.

[Thomas S. Dye]

Hi Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Nick Dokos <nicholas.dokos@hp.com> writes:
>
> [...]
>
>> Good question (I mean the *How* question): I believe this is a bug and
>> it has to do with the problem that Dan Davison identified and (as it
>> turns out) partially fixed a year ago (see
>> http://thread.gmane.org/gmane.emacs.orgmode/35439/focus=36878 for those
>> details).
>>
>> In a nutshell, the problem is that many export operations happen in
>> temporary buffers.  These buffers do not automatically inherit local
>
> [...]
>
> Nick,
>
> Many thanks for this analysis.  My gut feeling was indeed correct
> (whew!), probably because I subconsciously remembered reading the thread
> from Dan Davison.
>
>> The quick-and-dirty hack would be to call Dan's cloning function in the
>> call to with-temp-buffer, but that's not enough:
>> org-export-latex-fontify-headline does the temp-buffer thingie as well
>> and needs the same treatment. That seems to make *this* case work but I'm
>> almost 100% sure that that won't be enough in the general case either:
>> there are probably other places where temp buffers are created to do
>> some processing like this. They will also be subject to this problem.
>
> I must admit I am confused as to the point of #+BIND now.  I had thought
> the whole purpose was to set variables to be used during the export
> process but now it seems this is not the case.  Or it is only the case
> for some subset of the variables that may affect the export process.
>
> I don't care whether I need to use file local variables, #+BIND, or any
> other mechanism but it would be nice to have some mechanism!  So, can
> anybody suggest any hack around this problem?  I am not terribly worried
> about this as it only causes me difficulties now and again when I have a
> specific type of document I need to generate for
> dissemination.  Usually, my default settings are fine.  However, it
> would be nice to have some solution to this.
>
> I can have an emacs lisp code block which gets executed to set
> the values of those variables.  This works (see attachment), so long as
> I don't have any other controls for settings these variables, including
> file local variables or #+BIND.  However, I need to manually execute
> this code block if it is hidden away in a not-exported region of the
> document.  Otherwise, it clogs up the text (but such is life!).
>
> Note, however, that this changes the variable value globally and so will
> affect exporting of any other subsequent org documents unless they have
> their own settings.  Not *good* but good enough for my own use case for
> the moment... and, actually, having explicit settings for export
> variables in every *important* document is probably not a bad
> idea.  Ummm, need to think about this.

If you (and the receiver) tangle your export-settings source code block
to init.el (:tangle init.el), then execute something like the following
source code block

#+begin_src sh
emacs -Q -l init.el examplebug.org
#+end_src

you should be able to ensure that the receiver will get the same result
you get.

Of course, anything in your .emacs (or other initialization files) that
is needed to produce the results will need to be included in
export-settings.  

hth,
Tom

>
>
> #+TITLE:     examplebug.org
> #+AUTHOR:    Eric S Fraga
> #+EMAIL:     e.fraga@ucl.ac.uk
> #+DATE:      2012-01-09 Mon
>
> * Formatting tags                                                   :example:
>   When exporting, the default is to put tags in bold.  I want a box around them.
>
>
> # the following is used to set some variables which affect export to latex
>   #+name: export-settings
>   #+begin_src emacs-lisp :exports results :results silent
> (setq org-export-latex-tag-markup "babel: \\fbox{%s}")
>   #+end_src
>
>
>
> Anyway, thanks again,
> eric

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Variable settings in .emacs VS cross device portability.

[Eric S Fraga]

"Thomas S. Dye" <tsd@tsdye.com> writes:


[...]

> If you (and the receiver) tangle your export-settings source code block
> to init.el (:tangle init.el), then execute something like the following
> source code block
>
> #+begin_src sh
> emacs -Q -l init.el examplebug.org
> #+end_src
>
> you should be able to ensure that the receiver will get the same result
> you get.
>
> Of course, anything in your .emacs (or other initialization files) that
> is needed to produce the results will need to be included in
> export-settings.  
>
> hth,
> Tom

Thanks Tom!

Actually, I must apologise.  Your message addresses the OP's initial
question but somehow the thread has diverged from that and it's probably
my fault it has...  Sorry!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.300.g9b820)

Re: Emacs/Org-mode configs spread over multiple accounts/machines

[Eric Schulte]

One more option in this space is the technique used in the emacs starter
kit, in which specialized config files named after both the user and the
machine hostname are loaded on startup.  This allows sharing of config
across users and machines.

http://eschulte.me/emacs24-starter-kit/
https://github.com/eschulte/emacs24-starter-kit

Best,

"Alan E. Davis" <lngndvs@gmail.com> writes:

> By the way, all of these are called from .emacs.el .   Another point, I
> have elected not to byte-compile the loaded elisp files in
> ~/WorkBench/Emacs , so they will load ok on multiple versions of emacs.
>
> On Thu, Feb 2, 2012 at 7:16 AM, Alan E. Davis <lngndvs@gmail.com> wrote:
>
>> My setup, while far from ideal, is working pretty well.  It does require a
>> modicum of manual oversight.
>>
>> I have a directory, ~/WorkBench , in which all of my going work is
>> located.  Dozens of subdirectories including every project I have worked on
>> or am working on, with PDFs, etc.  In ~/WorkBench/org are some setup files:
>>
>>    org-init-settings.el
>>    org-local-init-settings.el         (included in .gitignore)
>>    emacs-common-settings.el   (all machines)
>>    emacs-local-settings.el         (local machine --- included in
>> .gitignore)
>>    emacs-frame-setup-magic.el
>>
>> The directory ~/WorkBench and all subdirectories are under git
>> supervision, so long as it stays smaller than about 3 GB.  In that case, it
>> can be carried around on an 8GB flash drive, and cloned on other machines,
>> though I've had to delete and reclone, once the repo got too large.   It
>> could be cloned to Dropbox if I wanted to spend money on it, and trusted
>> it.
>>
>> I really like this setup, the use of git.  However, I am using git at the
>> most trivial level, and perhaps there are more direct ways to do this.
>>
>> The next step is to encrypt the whole thing.  I have encrypted a couple of
>> sensitive files using bcrypt.
>>
>> Alan
>>
>>
>>
>>
>> On Thu, Feb 2, 2012 at 5:59 AM, Karl Voit <devnull@karl-voit.at> wrote:
>>
>>> * Yu <yu_icq@gmx.at> wrote:
>>> > Hello!
>>> >
>>> > I was wondering if there is a possibility to make org-files fully
>>> > portable in behaviour (especially when exporting) between different
>>> > emacs installations.
>>>
>>> The Tread has turned into BIND and local variables only.  I wanted
>>> to add my current solution which uses a different approach.
>>>
>>> My ~/.emacs is a symlink to ~/hosts/${HOSTNAME}/emacs where
>>> host-specific or platform-specific configuration is stored. The
>>> directory ~/hosts is synchronized[1] on all of my machines and
>>> accounts.
>>>
>>> In ~/hosts/all/emacs.d/* I have got myorgmode.el, mycommon.el,
>>> myauctex.el, myedit-server.el, mypython.el, and so forth.
>>>
>>> As you can imagine, the ~/hosts/${HOSTNAME}/emacs contains a load
>>> command for mycommon.el which refers to all the other el files.
>>>
>>> Therefore mycommon.el and all the others are identical on all my
>>> machines whereas ~/.emacs contains (only few) platform-specific
>>> things.
>>>
>>> Maybe this is a possible attempt to overcome your problems when
>>> using Org-mode on different machines.
>>>
>>>  1. I am currently using Unison File Synchronizer[2] in combination
>>>     with crond/LaunchCtl but git or something like dvcs-autosync[3]
>>>     or even Dropbox will work too.
>>>  2. http://www.cis.upenn.edu/~bcpierce/unison/
>>>  3. http://www.mayrhofer.eu.org/dvcs-autosync
>>> --
>>> Karl Voit
>>>
>>>
>>>
>>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

[BUG] cannot open menu when in an org buffer

[suvayu ali]

Hi,

In a minimal Emacs session when I open _any_ org file and try to access
the GUI menu with a mouse, I get the following back trace:

Debugger entered--Lisp error: (void-function org-in-clocktable-p)
  org-in-clocktable-p()
  org-context()
  (assq :todo-keyword (org-context))

Switching to a non-org buffer (e.g. scratch) the problem disappears. Can
someone take a look?

Thanks,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [BUG] cannot open menu when in an org buffer

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi,
> 
> In a minimal Emacs session when I open _any_ org file and try to access
> the GUI menu with a mouse, I get the following back trace:
> 
> Debugger entered--Lisp error: (void-function org-in-clocktable-p)
>   org-in-clocktable-p()
>   org-context()
>   (assq :todo-keyword (org-context))
> 
> Switching to a non-org buffer (e.g. scratch) the problem disappears. Can
> someone take a look?
> 

Confirmed. If I add

(require 'org-clock)

to my minimal .emacs, it goes away. So it seems to be a missing dependency.

Nick

Re: Variable settings in .emacs VS cross device portability.

[Thomas S. Dye]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> "Thomas S. Dye" <tsd@tsdye.com> writes:
>
>
> [...]
>
>> If you (and the receiver) tangle your export-settings source code block
>> to init.el (:tangle init.el), then execute something like the following
>> source code block
>>
>> #+begin_src sh
>> emacs -Q -l init.el examplebug.org
>> #+end_src
>>
>> you should be able to ensure that the receiver will get the same result
>> you get.
>>
>> Of course, anything in your .emacs (or other initialization files) that
>> is needed to produce the results will need to be included in
>> export-settings.  
>>
>> hth,
>> Tom
>
> Thanks Tom!
>
> Actually, I must apologise.  Your message addresses the OP's initial
> question but somehow the thread has diverged from that and it's probably
> my fault it has...  Sorry!

Hi Eric,

No worries.  I tried and failed to get buffer local variables to do what
I wanted, as it appears you have, too.  My failure probably has to do
with my ignorance as much as anything, but Dan's analysis and your
thread convinced me that it wasn't all me.  

I found it liberating to work on an Org mode file that would run in a
precisely defined environment, separate from the environmental mish-mash
that feels comfortable to me in my everyday work.

At any rate, I appreciate your good humor, even when I sound dull and
off point.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Variable settings in .emacs VS cross device portability.

[janek]

Yu <yu_icq@gmx.at> writes:

> code). The emacs-documentation doesn't mention it, but apparently this
> works also in shebang'ed files, by moving the single line form (`-*-
> ... -*-') to the second line. [2]
>
> [1] http://www.gnu.org/software/emacs/manual/html_node/emacs/File-Variables.html
> [2] http://www.lugaru.com/man/File.Variables.html

Choosing File Modes

(info "(emacs) Choosing Modes")
info:emacs#Choosing%20Modes

   When the first line starts with `#!', you usually cannot use the
`-*-' feature on the first line, because the system would get confused
when running the interpreter.  So Emacs looks for `-*-' on the second
line in such files as well as on the first line.

Re: [BUG] cannot open menu when in an org buffer

[suvayu ali]

On Sat, Feb 4, 2012 at 18:46, Nick Dokos <nicholas.dokos@hp.com> wrote:
> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> Hi,
>>
>> In a minimal Emacs session when I open _any_ org file and try to access
>> the GUI menu with a mouse, I get the following back trace:
>>
>> Debugger entered--Lisp error: (void-function org-in-clocktable-p)
>>   org-in-clocktable-p()
>>   org-context()
>>   (assq :todo-keyword (org-context))
>>
>> Switching to a non-org buffer (e.g. scratch) the problem disappears. Can
>> someone take a look?
>>
>
> Confirmed. If I add
>
> (require 'org-clock)
>
> to my minimal .emacs, it goes away. So it seems to be a missing dependency.
>

It seems an odd dependency to have. Anyway, I noticed something;
pressing F10 does bring up the menu as expected without any backtrace.
After that I can select anything on the menu with a mouse without
problems. The error occurs only when bringing up the menu for the
first time with a mouse.

> Nick

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [BUG] cannot open menu when in an org buffer

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> On Sat, Feb 4, 2012 at 18:46, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >
> > Confirmed. If I add
> >
> > (require 'org-clock)
> >
> > to my minimal .emacs, it goes away. So it seems to be a missing dependenc=
> y.
> >
> 
> It seems an odd dependency to have.

True - org-in-clocktable-p does not have anything to do with clocks, but
it ended up in org-clock.el. All of these "where am I" functions should
probably be in org.el. In fact, they all are except for
org-in-clocktable-p and org-at-item-p. The latter is in org-list.el and
it is not giving an error a) because org-in-clocktable-p errors out
first and b) because org.el contains a (require 'org-list). So having a
(require 'org-clock) in org.el does have a precedent, but of course this
way you end up defeating autoloads: the moment org.el is loaded, all of
these things are too. There might be a better arrangement but it's like
Pascal's letter[fn:1] : it would require time to find it :-) 

> Anyway, I noticed something;
> pressing F10 does bring up the menu as expected without any backtrace.
> After that I can select anything on the menu with a mouse without
> problems.

That's true: org-context is only called from mouse code, so if you drop
the menu without the mouse, there is no problem: selecting a menu item
with the mouse, once the menu has dropped, is all widget code and does
not invoke org code at all.

> The error occurs only when bringing up the menu for the
> first time with a mouse.
> 

That I find surprising though: I would expect that if you try to
click on the menu again, you'd get the error again: nothing is done
to define the function, so why should anything be different the
second time?

Nick

PS. In fact, I tried it out: I get the same error the second time.

Footnotes:

[fn:1] Approximately: "Forgive the length of this letter: I did not have
       time to make it shorter."

Re: [BUG] cannot open menu when in an org buffer

[Gustav Wikström]

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

On Sat, Feb 4, 2012 at 6:46 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
> > Hi,
> >
> > In a minimal Emacs session when I open _any_ org file and try to access
> > the GUI menu with a mouse, I get the following back trace:
> >
> > Debugger entered--Lisp error: (void-function org-in-clocktable-p)
> >   org-in-clocktable-p()
> >   org-context()
> >   (assq :todo-keyword (org-context))
> >
> > Switching to a non-org buffer (e.g. scratch) the problem disappears. Can
> > someone take a look?
> >
>
> Confirmed. If I add
>
> (require 'org-clock)
>
> to my minimal .emacs, it goes away. So it seems to be a missing dependency.
>
> Nick
>
>
I see the same problem when using org-goto with the latest revision of Org
(ELPA from 20120206). As Nick suggests, adding (require 'org-clock) fixes
the problem.

/Gustav

[-- Attachment #2: Type: text/html, Size: 1387 bytes --]

Re: [BUG] cannot open menu when in an org buffer

[suvayu ali]

Hi Nick,

On Tue, Feb 7, 2012 at 03:31, Nick Dokos <nicholas.dokos@hp.com> wrote:
> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
>> On Sat, Feb 4, 2012 at 18:46, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> >
>> > Confirmed. If I add
>> >
>> > (require 'org-clock)
>> >
>> > to my minimal .emacs, it goes away. So it seems to be a missing dependenc=
>> y.
>> >
>>
>> It seems an odd dependency to have.
>
> True - org-in-clocktable-p does not have anything to do with clocks, but
> it ended up in org-clock.el. All of these "where am I" functions should
> probably be in org.el. In fact, they all are except for
> org-in-clocktable-p and org-at-item-p. The latter is in org-list.el and
> it is not giving an error a) because org-in-clocktable-p errors out
> first and b) because org.el contains a (require 'org-list). So having a
> (require 'org-clock) in org.el does have a precedent, but of course this
> way you end up defeating autoloads: the moment org.el is loaded, all of
> these things are too. There might be a better arrangement but it's like
> Pascal's letter[fn:1] : it would require time to find it :-)
>

True, actually this is one of my only gripes (if you could call it that)
about org. Loading my org customisation is a fair part of my emacs start
time. If I could improve this, it would be perfect. :)

>> Anyway, I noticed something;
>> pressing F10 does bring up the menu as expected without any backtrace.
>> After that I can select anything on the menu with a mouse without
>> problems.
>
> That's true: org-context is only called from mouse code, so if you drop
> the menu without the mouse, there is no problem: selecting a menu item
> with the mouse, once the menu has dropped, is all widget code and does
> not invoke org code at all.
>

Thanks for clearing that up. I was always hazy about the emacs interface
libraries. I think I'll look into them someday when I have some time.

>> The error occurs only when bringing up the menu for the
>> first time with a mouse.
>>
>
> That I find surprising though: I would expect that if you try to
> click on the menu again, you'd get the error again: nothing is done
> to define the function, so why should anything be different the
> second time?
>

Ah, sorry my mistake. I did not word it correctly. I didn't mean
bringing up the menu with a mouse a second time. I meant once the menu
was up (lets say the "File" menu), going to a different one by hovering
over the menu (say "Edit" or "Options") with a mouse doesn't trigger
the backtrace. Clearly it is obvious now why it would be so from your
explanation above. :)

> [fn:1] Approximately: "Forgive the length of this letter: I did not have
>       time to make it shorter."

This is a very interesting and true remark. I was not familiar with
it before. :)

-- 
Suvayu

Open source is the future. It sets us free.

OrgMode - Export Simple Chinese text to Latex/PDF

[Haisheng Wu]

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hi guys,
  What I'd like to do is exporting a Chinese file into latex then convert
to a pdf file.
  It failed to display Chinese characters then I search google for help and
finding I need CJK package according to this post.
  http://www.math.nus.edu.sg/aslaksen/cs/cjk.html

  Unfortunately it is not that simple to make a UTF8 encoding file which I
have.
  Then I found another way is like this:
\documentclass{article}
\usepackage{CJK}
\begin{document}
\begin{CJK}{UTF8}{gbsn}
非常感 test
\end{CJK} (this is a test)
\end{document}

  Therefore I add those two lines into the org file:
#+LaTeX_HEADER: \usepackage{CJK}
#+LaTeX_HEADER: \begin{CJK}{UTF8}{gbsn}

  it WORKS.
  However, you might already notice, the `\begin` command is not closed
when I check with the generated tex file.
  Any hints / suggestions on this case?

Thanks a lot.
-Simon

[-- Attachment #2: Type: text/html, Size: 1823 bytes --]

Re: [BUG] cannot open menu when in an org buffer

[David Maus]

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]

Hi,

At Tue, 7 Feb 2012 14:26:41 +0100,
suvayu ali wrote:
>
> Hi Nick,
>
> On Tue, Feb 7, 2012 at 03:31, Nick Dokos <nicholas.dokos@hp.com> wrote:
> > suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
> >
> >> On Sat, Feb 4, 2012 at 18:46, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >> >
> >> > Confirmed. If I add
> >> >
> >> > (require 'org-clock)
> >> >
> >> > to my minimal .emacs, it goes away. So it seems to be a missing dependenc=
> >> y.
> >> >
> >>
> >> It seems an odd dependency to have.
> >
> > True - org-in-clocktable-p does not have anything to do with clocks, but
> > it ended up in org-clock.el. All of these "where am I" functions should
> > probably be in org.el. In fact, they all are except for
> > org-in-clocktable-p and org-at-item-p. The latter is in org-list.el and
> > it is not giving an error a) because org-in-clocktable-p errors out
> > first and b) because org.el contains a (require 'org-list). So having a
> > (require 'org-clock) in org.el does have a precedent, but of course this
> > way you end up defeating autoloads: the moment org.el is loaded, all of
> > these things are too. There might be a better arrangement but it's like
> > Pascal's letter[fn:1] : it would require time to find it :-)
> >

I pushed a fix to master that relocates org-in-clocktable-p from
org-clock.el to org.el -- the problem should be fixed now. This
shouldn't break things because org-clock requires org.

Best,
  -- David

[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

Re: [BUG] cannot open menu when in an org buffer

[suvayu ali]

Hi David,

On Wed, Feb 8, 2012 at 20:14, David Maus <dmaus@ictsoc.de> wrote:
>
> I pushed a fix to master that relocates org-in-clocktable-p from
> org-clock.el to org.el -- the problem should be fixed now. This
> shouldn't break things because org-clock requires org.
>

I can confirm the issue is fixed now.

> Best,
>  -- David

Thanks a lot. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[suvayu ali]

Hi,

On Wed, Feb 8, 2012 at 10:07, Haisheng Wu <freizl@gmail.com> wrote:
> #+LaTeX_HEADER: \usepackage{CJK}
> #+LaTeX_HEADER: \begin{CJK}{UTF8}{gbsn}

Have you tried the following instead?

#+LaTeX_HEADER: \usepackage{CJK}

#LaTeX: \begin{CJK}{UTF8}{gbsn}

<some text in chinese>

#LaTeX: \end{CJK}{test}

GL

-- 
Suvayu

Open source is the future. It sets us free.

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi,
> 
> On Wed, Feb 8, 2012 at 10:07, Haisheng Wu <freizl@gmail.com> wrote:
> > #+LaTeX_HEADER: \usepackage{CJK}
> > #+LaTeX_HEADER: \begin{CJK}{UTF8}{gbsn}
> 
> Have you tried the following instead?
> 
> #+LaTeX_HEADER: \usepackage{CJK}
> 
> #LaTeX: \begin{CJK}{UTF8}{gbsn}
> 
> <some text in chinese>
> 
> #LaTeX: \end{CJK}{test}

The {test} should probably not be there:

#LaTeX: \end{CJK}

but the rest is all good, I think.

Nick

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Haisheng Wu]

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

I think it is `#+Latex` rather than `#Latex`.
The former one works for me.

Thanks a lot!

-Simon


On Thu, Feb 9, 2012 at 10:04 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
> > Hi,
> >
> > On Wed, Feb 8, 2012 at 10:07, Haisheng Wu <freizl@gmail.com> wrote:
> > > #+LaTeX_HEADER: \usepackage{CJK}
> > > #+LaTeX_HEADER: \begin{CJK}{UTF8}{gbsn}
> >
> > Have you tried the following instead?
> >
> > #+LaTeX_HEADER: \usepackage{CJK}
> >
> > #LaTeX: \begin{CJK}{UTF8}{gbsn}
> >
> > <some text in chinese>
> >
> > #LaTeX: \end{CJK}{test}
>
> The {test} should probably not be there:
>
> #LaTeX: \end{CJK}
>
> but the rest is all good, I think.
>
> Nick
>

[-- Attachment #2: Type: text/html, Size: 1287 bytes --]

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[suvayu ali]

On Thu, Feb 9, 2012 at 03:21, Haisheng Wu <freizl@gmail.com> wrote:
> I think it is `#+Latex` rather than `#Latex`.
> The former one works for me.

Yes, both you and Nick are correct. :)

Sorry for the typo.

-- 
Suvayu

Open source is the future. It sets us free.

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> On Thu, Feb 9, 2012 at 03:21, Haisheng Wu <freizl@gmail.com> wrote:
> > I think it is `#+Latex` rather than `#Latex`.
> > The former one works for me.
> 
Yes, indeed.

> Yes, both you and Nick are correct. :)
> 
> Sorry for the typo.
> 

Didn't catch the typo either.

Nick

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Haisheng Wu]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

aha...actually I just found one exception.
By using the approach you suggested, the generated tex will be like:

\title{吴海生}
\begin{document}
\maketitle
\begin{CJK}{UTF8}{gbsn}
...
...

As you would see, the `CJK` is nested in the `document`,
therefore, title which is in Chinese as well can not display correctly.
Any ideas?

Thanks a lot.

-Haisheng


On Thu, Feb 9, 2012 at 10:56 AM, Nick Dokos <nicholas.dokos@hp.com> wrote:

> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>
> > On Thu, Feb 9, 2012 at 03:21, Haisheng Wu <freizl@gmail.com> wrote:
> > > I think it is `#+Latex` rather than `#Latex`.
> > > The former one works for me.
> >
> Yes, indeed.
>
> > Yes, both you and Nick are correct. :)
> >
> > Sorry for the typo.
> >
>
> Didn't catch the typo either.
>
> Nick
>
>
>

[-- Attachment #2: Type: text/html, Size: 1943 bytes --]

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[suvayu ali]

Hi,

On Thu, Feb 9, 2012 at 04:12, Haisheng Wu <freizl@gmail.com> wrote:
> As you would see, the `CJK` is nested in the `document`,
> therefore, title which is in Chinese as well can not display correctly.
> Any ideas?

Well, when it comes to utf8 export, I always recommend xelatex or
lualatex. :) Recently there was a thread on devanagari (for Sanskrit
and its derivatives like Hindi) which proved useful to the OP.

<http://thread.gmane.org/gmane.emacs.orgmode/51914>

Hope this helps.

-- 
Suvayu

Open source is the future. It sets us free.

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Eric Abrahamsen]

On Thu, Feb 09 2012, suvayu ali wrote:

> Hi,
>
> On Thu, Feb 9, 2012 at 04:12, Haisheng Wu <freizl@gmail.com> wrote:
>> As you would see, the `CJK` is nested in the `document`,
>> therefore, title which is in Chinese as well can not display correctly.
>> Any ideas?
>
> Well, when it comes to utf8 export, I always recommend xelatex or
> lualatex. :) Recently there was a thread on devanagari (for Sanskrit
> and its derivatives like Hindi) which proved useful to the OP.

I do a lot of org to latex export with Chinese in it, and would
absolutely second using Xelatex, it just makes so many things simpler.
Use these headers, and compile with xelatex, you might need a pretty
recent texlive installation.

\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\usepackage{xeCJK}
\setmainfont{Janson Text LT Pro} % or whatever
\setCJKmainfont{文泉驿正黑} % or whatever


-- 
GNU Emacs 24.0.93.1 (i686-pc-linux-gnu, GTK+ Version 2.24.10)
 of 2012-02-07 on pellet
Org-mode version 7.8.03 (release_7.8.03.324.gc4b233)

Re: OrgMode - Export Simple Chinese text to Latex/PDF

[Haisheng Wu]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

What mentioned in the thread is really helpful.
The only difference is I need figure out proper font for Chinese.
I use command `fc-list` (ubuntu) to figure it out.

PS: Not sure how to figure out such easily in Windows.

Thanks a lot!
-Haisheng


On Thu, Feb 9, 2012 at 8:25 PM, suvayu ali <fatkasuvayu+linux@gmail.com>wrote:

> Hi,
>
> On Thu, Feb 9, 2012 at 04:12, Haisheng Wu <freizl@gmail.com> wrote:
> > As you would see, the `CJK` is nested in the `document`,
> > therefore, title which is in Chinese as well can not display correctly.
> > Any ideas?
>
> Well, when it comes to utf8 export, I always recommend xelatex or
> lualatex. :) Recently there was a thread on devanagari (for Sanskrit
> and its derivatives like Hindi) which proved useful to the OP.
>
> <http://thread.gmane.org/gmane.emacs.orgmode/51914>
>
> Hope this helps.
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>

[-- Attachment #2: Type: text/html, Size: 1514 bytes --]

AUCTeX conflicting with org-mode

[suvayu ali]

Hi,

I am having conflicts AUCTeX when I try to open plain latex files after
I exporting an org file to latex. These are the exact steps.

1. Start Emacs as: emacs -q (so that the site files load and I have
   auctex available).
2. Open any org file and export to latex, C-c C-e l.
3. Open another plain latex file.

At this point I see this backtrace:

Debugger entered--Lisp error: (void-variable TeX-master)
  #[nil "\301\302 !\203
  \303=\203  \304\305\211\306#\210\307\306!\207" [TeX-master
file-exists-p buffer-file-name shared TeX-master-file nil t
TeX-update-style] 4]()
  run-hooks(find-file-hook)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer velo-links.tex>
"~/graphics/velo-links.tex" nil nil "~/graphics/velo-links.tex"
(263573 64770))
  find-file-noselect("~/graphics/velo-links.tex" nil nil t)
  find-file("~/graphics/velo-links.tex" t)
  call-interactively(find-file nil nil)

Since removing the auctex site files out of the site-lisp directory
resolves the conflict I am assuming the problem stems from my auctex
installation.

Can someone help me trouble shoot this?

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Yagnesh Raghava Yakkala]

Hi Suvayu,

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> Hi,
>
> I am having conflicts AUCTeX when I try to open plain latex files after
> I exporting an org file to latex. These are the exact steps.
>
> 1. Start Emacs as: emacs -q (so that the site files load and I have
>    auctex available).
> 2. Open any org file and export to latex, C-c C-e l.
> 3. Open another plain latex file.
>
> At this point I see this backtrace:
>
> Debugger entered--Lisp error: (void-variable TeX-master)
>   #[nil "\301\302 !\203
>   \303=\203  \304\305\211\306#\210\307\306!\207" [TeX-master
> file-exists-p buffer-file-name shared TeX-master-file nil t
> TeX-update-style] 4]()
>   run-hooks(find-file-hook)
>   after-find-file(nil t)
>   find-file-noselect-1(#<buffer velo-links.tex>
> "~/graphics/velo-links.tex" nil nil "~/graphics/velo-links.tex"
> (263573 64770))
>   find-file-noselect("~/graphics/velo-links.tex" nil nil t)
>   find-file("~/graphics/velo-links.tex" t)
>   call-interactively(find-file nil nil)
>
> Since removing the auctex site files out of the site-lisp directory
> resolves the conflict I am assuming the problem stems from my auctex
> installation.
>
> Can someone help me trouble shoot this?

I can reproduce this., I think your auctex installation is fine. Its
definitely from org.

In org-latex.el Tex-master is set to t to suppress auctex from asking for
that variable while exporting with org-latex..(IIRC there was a discussion and
Carsten made that change)

Some how org leaving that to void at the end of org-latex export (I coundn't
figure out how?).

-- 
YYR

Re: AUCTeX conflicting with org-mode

[suvayu ali]

On Wed, Mar 7, 2012 at 06:08, Yagnesh Raghava Yakkala <yagnesh@live.com> wrote:
> I can reproduce this., I think your auctex installation is fine. Its
> definitely from org.

Thanks a lot for taking a look and confirming. :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Nick Dokos]

Yagnesh Raghava Yakkala <yagnesh@live.com> wrote:

> 
> Hi Suvayu,
> 
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > Hi,
> >
> > I am having conflicts AUCTeX when I try to open plain latex files after
> > I exporting an org file to latex. These are the exact steps.
> >
> > 1. Start Emacs as: emacs -q (so that the site files load and I have
> >    auctex available).
> > 2. Open any org file and export to latex, C-c C-e l.
> > 3. Open another plain latex file.
> >
> > At this point I see this backtrace:
> >
> > Debugger entered--Lisp error: (void-variable TeX-master)
> >   #[nil "\301\302 !\203
> >   \303=\203  \304\305\211\306#\210\307\306!\207" [TeX-master
> > file-exists-p buffer-file-name shared TeX-master-file nil t
> > TeX-update-style] 4]()
> >   run-hooks(find-file-hook)
> >   after-find-file(nil t)
> >   find-file-noselect-1(#<buffer velo-links.tex>
> > "~/graphics/velo-links.tex" nil nil "~/graphics/velo-links.tex"
> > (263573 64770))
> >   find-file-noselect("~/graphics/velo-links.tex" nil nil t)
> >   find-file("~/graphics/velo-links.tex" t)
> >   call-interactively(find-file nil nil)
> >
> > Since removing the auctex site files out of the site-lisp directory
> > resolves the conflict I am assuming the problem stems from my auctex
> > installation.
> >
> > Can someone help me trouble shoot this?
> 
> I can reproduce this., I think your auctex installation is fine. Its
> definitely from org.
> 
> In org-latex.el Tex-master is set to t to suppress auctex from asking for
> that variable while exporting with org-latex..(IIRC there was a discussion and
> Carsten made that change)
> 
> Some how org leaving that to void at the end of org-latex export (I coundn't
> figure out how?).
> 

That sounds far-fetched to me: once TeX-master is bound, one has to go
to some lengths to unbind it (see makunbound - but I'm pretty sure
that's not used anywhere in org code - there are a few instances of the
function analog, fmakunbound).

It seems much more likely that in these cases, it never got bound in the
first place, possibly because of dependency problems in the loading of
packages. But I cannot reproduce the problem, so I'm speaking
theoretically only and my imagination may be failing me.

Nick

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Nick,

On Wed, Mar 7, 2012 at 16:39, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> In org-latex.el Tex-master is set to t to suppress auctex from asking for
>> that variable while exporting with org-latex..(IIRC there was a discussion and
>> Carsten made that change)
>>
>> Some how org leaving that to void at the end of org-latex export (I coundn't
>> figure out how?).
>>
>
> That sounds far-fetched to me: once TeX-master is bound, one has to go
> to some lengths to unbind it (see makunbound - but I'm pretty sure
> that's not used anywhere in org code - there are a few instances of the
> function analog, fmakunbound).
>
> It seems much more likely that in these cases, it never got bound in the
> first place, possibly because of dependency problems in the loading of
> packages. But I cannot reproduce the problem, so I'm speaking
> theoretically only and my imagination may be failing me.

I think Yagnesh is talking about this thread:
<http://thread.gmane.org/gmane.emacs.orgmode/48512/focus=48526>

I took a quick look at the commit (ca49e89) and the source (org-latex.el
line 888), but everything looks good to me. To add more information,
while exporting to latex I get the following warning when auctex site
files are present.

Export buffer:
Exporting to LaTeX...
Warning: defvar ignored because TeX-master is let-bound
Making TeX-master buffer-local while let-bound!

Hope this clearly explains the problem I am facing.

PS: BTW, why is AUCTeX not part of Emacs?

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi Nick,
> 
> On Wed, Mar 7, 2012 at 16:39, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >> In org-latex.el Tex-master is set to t to suppress auctex from asking for
> >> that variable while exporting with org-latex..(IIRC there was a discussion and
> >> Carsten made that change)
> >>
> >> Some how org leaving that to void at the end of org-latex export (I coundn't
> >> figure out how?).
> >>
> >
> > That sounds far-fetched to me: once TeX-master is bound, one has to go
> > to some lengths to unbind it (see makunbound - but I'm pretty sure
> > that's not used anywhere in org code - there are a few instances of the
> > function analog, fmakunbound).
> >
> > It seems much more likely that in these cases, it never got bound in the
> > first place, possibly because of dependency problems in the loading of
> > packages. But I cannot reproduce the problem, so I'm speaking
> > theoretically only and my imagination may be failing me.
> 
> I think Yagnesh is talking about this thread:
> <http://thread.gmane.org/gmane.emacs.orgmode/48512/focus=48526>
> 
> I took a quick look at the commit (ca49e89) and the source (org-latex.el
> line 888), but everything looks good to me. To add more information,
> while exporting to latex I get the following warning when auctex site
> files are present.
> 
> Export buffer:
> Exporting to LaTeX...
> Warning: defvar ignored because TeX-master is let-bound
> Making TeX-master buffer-local while let-bound!
> 
> Hope this clearly explains the problem I am facing.
> 

Yup - that shows that tex.el has not been loaded by the time you try the
export, so the let-bind (Carsten's fix) happens first and then the
defvar (from tex.el) complains because that's usually not what you want:
you want to get to the global binding (which doesn't exist at that point
in time). That's what the doc for defvar warns about:

,----
| ...
| If SYMBOL has a local binding, then this form affects the local
| binding.  This is usually not what you want.  Thus, if you need to
| load a file defining variables, with this form or with `defconst' or
| `defcustom', you should always load that file _outside_ any bindings
| for these variables.  (`defconst' and `defcustom' behave similarly in
| this respect.)
`----


As a workaround-and-proof-of-concept, try

(load "tex")

before loading org. Assuming that that works, you will probably want
to arrange things that this is always done.

It might also be the case that Carsten's fix needs to be modified to
check whether TeX-master is bound already - then it can let-bind it
without problems; but I'm not sure what to do if that's not the case.

The question I have is what exactly causes tex.el to be loaded at that
point in time. If you can figure that out, then that might lead to a
more permanent solution.

> PS: BTW, why is AUCTeX not part of Emacs?
> 

I thought it had to do with the glacial release schedule of emacs 21/22/23:
at the time, auctex/preview-latex was undergoing changes at a much faster
pace, so waiting for emacs releases was just not feasible. Whether it
could be integrated now is a good question, but I don't have a good answer
for it. 

There is also a recent thread that implies that the copyrights were not
assigned to the FSF, but that seems to have changed. See

  http://lists.gnu.org/archive/html/emacs-devel/2012-01/msg00847.html

Nick

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Nick,

On Wed, Mar 7, 2012 at 21:00, Nick Dokos <nicholas.dokos@hp.com> wrote:
> As a workaround-and-proof-of-concept, try
>
> (load "tex")
>
> before loading org. Assuming that that works, you will probably want
> to arrange things that this is always done.
>

This worked as you hypothesised. :)

> It might also be the case that Carsten's fix needs to be modified to
> check whether TeX-master is bound already - then it can let-bind it
> without problems; but I'm not sure what to do if that's not the case.
>
> The question I have is what exactly causes tex.el to be loaded at that
> point in time. If you can figure that out, then that might lead to a
> more permanent solution.

I am not sure how I can conclusively confirm that, but I think when I
export to latex, the exported latex buffer loads it. For example, I
don't see this issue when say I go through these steps:

1. Open a tex file.
2. Open and export an org file to latex.
3. Open a new tex file.

In this case step (1) must be loading tex.el, circumventing the issue.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi Nick,
> 
> On Wed, Mar 7, 2012 at 21:00, Nick Dokos <nicholas.dokos@hp.com> wrote:
> > As a workaround-and-proof-of-concept, try
> >
> > (load "tex")
> >
> > before loading org. Assuming that that works, you will probably want
> > to arrange things that this is always done.
> >
> 
> This worked as you hypothesised. :)
> 
> > It might also be the case that Carsten's fix needs to be modified to
> > check whether TeX-master is bound already - then it can let-bind it
> > without problems; but I'm not sure what to do if that's not the case.
> >
> > The question I have is what exactly causes tex.el to be loaded at that
> > point in time. If you can figure that out, then that might lead to a
> > more permanent solution.
> 
> I am not sure how I can conclusively confirm that, but I think when I
> export to latex, the exported latex buffer loads it. For example, I
> don't see this issue when say I go through these steps:
> 
> 1. Open a tex file.
> 2. Open and export an org file to latex.
> 3. Open a new tex file.
> 
> In this case step (1) must be loading tex.el, circumventing the issue.
> 

Actually, your backtrace in the original post makes things clearer now.

org-export-as-latex calls find-file-noselect on the .tex file, which
calls after-find-file which runs the find-file-hook.  Somehow the
find-file-hook is set up[fn:1] as in VirTeX-common-initialization to
call TeX-master-file - although your backtrace shows compiled code, it's
pretty clear that that's the setting of the find-file-hook that
VirTeX-common-initialization has done. So it looks as if tex.el is
partially loaded: the initialization is done, the hook is set up but the
defvar has failed, probably because of the let-bind.

Nick

Footnotes:

[fn:1]  à la Sidney Harris - cf. http://www.sciencecartoonsplus.com/index.php

Re: AUCTeX conflicting with org-mode

[Yagnesh Raghava Yakkala]

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]


Hello Nick.,

Nick Dokos <nicholas.dokos@hp.com> writes:

> suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
>

[snipped]

>
> Actually, your backtrace in the original post makes things clearer now.
>
> org-export-as-latex calls find-file-noselect on the .tex file, which
> calls after-find-file which runs the find-file-hook.  Somehow the
> find-file-hook is set up[fn:1] as in VirTeX-common-initialization to
> call TeX-master-file - although your backtrace shows compiled code, it's
> pretty clear that that's the setting of the find-file-hook that
> VirTeX-common-initialization has done. So it looks as if tex.el is
> partially loaded: the initialization is done, the hook is set up but the
> defvar has failed, probably because of the let-bind.


Thanks for the analysis. I think you are right. With my limited elisp skills I
would say its a *bug* and coming from org.

If I take that let-binding off and setting the TeX-master by checking with
if it ever bound seems fixing this problem.

this patch fixing the problem. (can be further improved)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org-latex.diff --]
[-- Type: text/x-diff, Size: 813 bytes --]

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 03664b4..9e53849 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -885,7 +885,6 @@ when PUB-DIR is set, use this as the publishing directory."
 		   (concat filename ".tex")
 		 filename)))
 	 (auto-insert nil); Avoid any auto-insert stuff for the new file
-	 (TeX-master t) ; Avoid the Query for TeX master from AUCTeX
 	 (buffer (if to-buffer
 		     (cond
 		      ((eq to-buffer 'string) (get-buffer-create
@@ -958,6 +957,8 @@ when PUB-DIR is set, use this as the publishing directory."
 	   :exclude-tags (plist-get opt-plist :exclude-tags)
 	   :LaTeX-fragments nil)))
 
+    (if (boundp 'TeX-master) (setq TeX-master t)) ; Avoid the Query for TeX master from AUCTeX
+
     (set-buffer buffer)
     (erase-buffer)
     (org-install-letbind)

[-- Attachment #3: Type: text/plain, Size: 10 bytes --]



-- 
YYR

Re: AUCTeX conflicting with org-mode

[Bastien]

Hi Yagnesh,

Yagnesh Raghava Yakkala <yagnesh@live.com> writes:

> Thanks for the analysis. I think you are right. With my limited elisp skills I
> would say its a *bug* and coming from org.
>
> If I take that let-binding off and setting the TeX-master by checking with
> if it ever bound seems fixing this problem.
>
> this patch fixing the problem. (can be further improved)

Applied, thanks.

-- 
 Bastien

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Bastien and Yagnesh,

On Tue, Mar 20, 2012 at 12:02, Bastien <bzg@gnu.org> wrote:
> Hi Yagnesh,
>
> Yagnesh Raghava Yakkala <yagnesh@live.com> writes:
>
>> Thanks for the analysis. I think you are right. With my limited elisp skills I
>> would say its a *bug* and coming from org.
>>
>> If I take that let-binding off and setting the TeX-master by checking with
>> if it ever bound seems fixing this problem.
>>
>> this patch fixing the problem. (can be further improved)
>
> Applied, thanks.
>

I wanted to comment earlier but it slipped my mind, sorry about that.

I am not sure if this patch is quite corect. It removes the let bind and
instead conditionally uses setq to bind it to t. From the docs I see the
variable becomes buffer local when set in any fashion, but does that
still mean it is okay to use setq?

I can imagine in a complicated publishing project, an org file might
need to set the value to something. I suppose this will override any
such custom config. Is my analysis correct? It might be worth thinking
about before applying the patch.

Is a conditional let binding possible, it might be the safer choice in
that case.

Thanks,

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Bastien]

Hi Suvayu,

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> I wanted to comment earlier but it slipped my mind, sorry about that.
>
> I am not sure if this patch is quite corect. It removes the let bind and
> instead conditionally uses setq to bind it to t. From the docs I see the
> variable becomes buffer local when set in any fashion, but does that
> still mean it is okay to use setq?
>
> I can imagine in a complicated publishing project, an org file might
> need to set the value to something. I suppose this will override any
> such custom config. Is my analysis correct? It might be worth thinking
> about before applying the patch.
>
> Is a conditional let binding possible, it might be the safer choice in
> that case.

I applied a patch into hotfix-7.8.06 using the let binding -- let me
know if this works correctly.

Thanks!

-- 
 Bastien

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Bastien,

On Tue, Mar 20, 2012 at 17:23, Bastien <bzg@gnu.org> wrote:
> Hi Suvayu,
>
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>
>> I wanted to comment earlier but it slipped my mind, sorry about that.
>>
>> I am not sure if this patch is quite corect. It removes the let bind and
>> instead conditionally uses setq to bind it to t. From the docs I see the
>> variable becomes buffer local when set in any fashion, but does that
>> still mean it is okay to use setq?
>>
>> I can imagine in a complicated publishing project, an org file might
>> need to set the value to something. I suppose this will override any
>> such custom config. Is my analysis correct? It might be worth thinking
>> about before applying the patch.
>>
>> Is a conditional let binding possible, it might be the safer choice in
>> that case.
>
> I applied a patch into hotfix-7.8.06 using the let binding -- let me
> know if this works correctly.

I don't think this works. The problem (thanks to Nick again for the
analysis earlier in the thread[1] :-)) is the let bind happens before
tex.el is loaded. So when it is loaded eventually, the defvar fails
which in turn triggers the backtrace. The setq in the body works but
could possibly mess up someone's custom config as I mentioned in my
earlier post.

I hope you see the no-win situation now (:-p), hence my apprehension
about the fix earlier. That said, I guess you have two choices:

1. Leave the bug unsolved, hoping there will be a cleaner solution
   later. After all, there is a very simple workaround on the user side,
   do (load "tex.el") before using org-latex.
2. The second choice would be to partially fix the bug with the setq,
   but potentially break a future unsuspecting user with a non-standard
   config.

If it were up to me, I would probably prefer option one.

I hope this clears up everything.

Footnotes:

[1] <http://thread.gmane.org/gmane.emacs.orgmode/53128/focus=53152>
    <http://thread.gmane.org/gmane.emacs.orgmode/53128/focus=53156>

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Yagnesh Raghava Yakkala]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]


Hi Bastien and Suvayu,

suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>
[snipped 35 lines]
>
> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>    later. After all, there is a very simple workaround on the user side,
>    do (load "tex.el") before using org-latex.

how about this patch (to hotfix branch). 


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org-latex.el.diff --]
[-- Type: text/x-diff, Size: 522 bytes --]

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 2e11ca4..438e5a4 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -871,6 +871,7 @@ when PUB-DIR is set, use this as the publishing directory."
 		 filename)))
 	 (auto-insert nil); Avoid any auto-insert stuff for the new file
 	 (TeX-master (boundp 'TeX-master))
+	 (dummy (unless TeX-master (makunbound 'TeX-master))) ; make sure we are not introducing TeX-master
 	 (buffer (if to-buffer
 		     (cond
 		      ((eq to-buffer 'string) (get-buffer-create

[-- Attachment #3: Type: text/plain, Size: 9 bytes --]


-- 
YYR

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Yagnesh,

On Wed, Mar 21, 2012 at 07:01, Yagnesh Raghava Yakkala <yagnesh@live.com> wrote:
> Hi Bastien and Suvayu,
>
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>>
> [snipped 35 lines]
>>
>> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>>    later. After all, there is a very simple workaround on the user side,
>>    do (load "tex.el") before using org-latex.
>
> how about this patch (to hotfix branch).
>

I tested it, the problem is still there. I don't think you can put
arbitrary code within a let* bind and expect to retain the effect in
the main body.

The only possible solution I can see seems to be ensuring tex.el is
loaded properly. More importantly though, if more users cannot
replicate this bug this might as well be a detail specific to how the
AUCTeX site files behave in my setup (I use AUCTeX from the Fedora
repositories). Not sure if that is something org should handle.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Yagnesh Raghava Yakkala]

Hello Suvayu.,

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> Hi Yagnesh,
>
> On Wed, Mar 21, 2012 at 07:01, Yagnesh Raghava Yakkala <yagnesh@live.com> wrote:
>> Hi Bastien and Suvayu,
>>
>> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>>>
>> [snipped 35 lines]
>>>
>>> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>>>    later. After all, there is a very simple workaround on the user side,
>>>    do (load "tex.el") before using org-latex.
>>
>> how about this patch (to hotfix branch).
>>
>
> I tested it, the problem is still there. 

That's odd. My tests have passed.

>I don't think you can put
> arbitrary code within a let* bind and expect to retain the effect in the
> main body.

I don't understand what you mean here. Anyway it seems poking into 
variables from other packages is not a good idea in elisp.

-- 
YYR

[OT] Issue with exported html on webserver

[suvayu ali]

Hi,

I labelled this OT since I am having the problem with only one
web server. Since I am not well versed with html, I was hoping the good
people of this list can help.

Now to my issue. When I export any org file to html and open it in my
browser, everything works well. But when I put it on my institute's
public_html/ directory, I see a blank page. I asked for help at the IT
help desk, they tracked down the problem to the very first tag in the
html file.

  <?xml version="1.0" encoding="iso-8859-1"?>

This generates the following error in the Apache logs:

PHP Parse error:  syntax error, unexpected T_STRING in
/user/sali/public_html/bug.html on line 1

Removing the line renders the page properly.

For an example, look in the following directory.

<http://www.nikhef.nl/~sali/>

+ bug.html renders correctly (the first line has been removed)
+ fails-bug.html shows a blank page (this is as org exports it)

This is rather perplexing, since I have successfully used html exported
by org before on other webservers (e.g. the public_html directory in my
previous university). Can someone help me find out what is the issue
here?

Thanks a bunch.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [OT] Issue with exported html on webserver

[Christian Moe]

Hi

See if this explains it:

http://www.000webhost.com/forum/web-design-html/25365-xhtml-not-recognised-parse-error-syntax-error-unexpected-t_string-line-1-a.html

Yours,
Christian

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

>Hi,
>
>I labelled this OT since I am having the problem with only one
>web server. Since I am not well versed with html, I was hoping the good
>people of this list can help.
>
>Now to my issue. When I export any org file to html and open it in my
>browser, everything works well. But when I put it on my institute's
>public_html/ directory, I see a blank page. I asked for help at the IT
>help desk, they tracked down the problem to the very first tag in the
>html file.
>
>  <?xml version="1.0" encoding="iso-8859-1"?>
>
>This generates the following error in the Apache logs:
>
>PHP Parse error:  syntax error, unexpected T_STRING in
>/user/sali/public_html/bug.html on line 1
>
>Removing the line renders the page properly.
>
>For an example, look in the following directory.
>
><http://www.nikhef.nl/~sali/>
>
>+ bug.html renders correctly (the first line has been removed)
>+ fails-bug.html shows a blank page (this is as org exports it)
>
>This is rather perplexing, since I have successfully used html exported
>by org before on other webservers (e.g. the public_html directory in my
>previous university). Can someone help me find out what is the issue
>here?
>
>Thanks a bunch.
>
>--
>Suvayu
>
>Open source is the future. It sets us free.

---

Sent from mobile.
Please excuse my brevity.

Re: [OT] Issue with exported html on webserver

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

>   <?xml version="1.0" encoding="iso-8859-1"?>
> 
> This generates the following error in the Apache logs:
> 
> PHP Parse error:  syntax error, unexpected T_STRING in
> /user/sali/public_html/bug.html on line 1
> 
> Removing the line renders the page properly.
> 
> For an example, look in the following directory.
> 
> <http://www.nikhef.nl/~sali/>
> 
> + bug.html renders correctly (the first line has been removed)
> + fails-bug.html shows a blank page (this is as org exports it)
> 
> This is rather perplexing, since I have successfully used html exported
> by org before on other webservers (e.g. the public_html directory in my
> previous university). Can someone help me find out what is the issue
> here?
> 

The server seems misconfigured to me: why is PHP entering into the
picture at all?

Nick

Re: [OT] Issue with exported html on webserver

[suvayu ali]

Hi Christian,

On Sun, Mar 25, 2012 at 23:21, Christian Moe <mail@christianmoe.com> wrote:
> Hi
>
> See if this explains it:
>
> http://www.000webhost.com/forum/web-design-html/25365-xhtml-not-recognised-parse-error-syntax-error-unexpected-t_string-line-1-a.html
>

That resolved it! I will take this up with our IT department. Thanks a
lot. :)

> Yours,
> Christian

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [OT] Issue with exported html on webserver

[suvayu ali]

Hi Nick,

On Sun, Mar 25, 2012 at 23:25, Nick Dokos <nicholas.dokos@hp.com> wrote:
>
> The server seems misconfigured to me: why is PHP entering into the
> picture at all?

Christian's response resolved the issue. The page he pointed to, says
this happens when the "short_open_tag" server configuration is not
turned off. I will take this up with our IT department.

Thanks a lot.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [OT] Issue with exported html on webserver

[Nick Dokos]

suvayu ali <fatkasuvayu+linux@gmail.com> wrote:

> Hi Nick,
> 
> On Sun, Mar 25, 2012 at 23:25, Nick Dokos <nicholas.dokos@hp.com> wrote:
> >
> > The server seems misconfigured to me: why is PHP entering into the
> > picture at all?
> 
> Christian's response resolved the issue. The page he pointed to, says
> this happens when the "short_open_tag" server configuration is not
> turned off. I will take this up with our IT department.
> 

Yes, I went to the link that Christian posted. I was particularly
confused/intrigued/flabbergasted by the admin's response:

#+BEGIN_QUOTE
	on 000webhost, all web pages are interpreted as php pages and
	short_open_tag is off and that is the reason the propose
	solution works on 000webhost.
#+END_QUOTE

Why on earth would anybody set it up so that "all web pages are
interpreted as php pages"? Seems crazy to me, but I'm probably
naive.

Nick

Re: [OT] Issue with exported html on webserver

[Christian Moe]

> Why on earth would anybody set it up so that "all web pages are
> interpreted as php pages"? Seems crazy to me, but I'm probably
> naive.
>
> Nick

Apparently, so they can get by with typing <? ... ?> instead of <?php 
... ?>. HTML doesn't care, and PHP predates XML, so I imagine it's a 
legacy of early shortcuts that were unproblematic at the time.

But if people R 2 lazy 2 type 3 xtra chars, why not just use Perl?
:)

Yours,
Christian

Re: [OT] Issue with exported html on webserver

[Sebastien Vauban]

Hi Nick,

Nick Dokos wrote:
> Why on earth would anybody set it up so that "all web pages are interpreted
> as php pages"? Seems crazy to me, but I'm probably naive.

The problem can be a config which applies on a too wide range of directories.

An easy way to circumvent this is:

#+begin_src emacs-lisp
  ;; XML encoding
  (setq org-export-html-xml-declaration
        '(("html" . "<!-- <xml version="1.0" encoding="utf-8"> -->")))
#+end_src

This eliminates the =T_STRING= error and you have a page that will still pass
W3C validation...

And, this way, you don't care about what the IT department does or needs to
do.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [OT] Issue with exported html on webserver

[Sebastien Vauban]

Hi,

"Sebastien Vauban" wrote:
> Nick Dokos wrote:
>> Why on earth would anybody set it up so that "all web pages are interpreted
>> as php pages"? Seems crazy to me, but I'm probably naive.
>
> The problem can be a config which applies on a too wide range of directories.
>
> An easy way to circumvent this is:
>
> #+begin_src emacs-lisp
>   ;; XML encoding
>   (setq org-export-html-xml-declaration
>         '(("html" . "<!-- <xml version="1.0" encoding="utf-8"> -->")))
> #+end_src

Missing escaping of slashes...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [OT] Issue with exported html on webserver

[suvayu ali]

Hi Seb,

On Mon, Mar 26, 2012 at 14:58, Sebastien Vauban
<wxhgmqzgwmuf@spammotel.com> wrote:
> Hi,
>
> "Sebastien Vauban" wrote:
>> Nick Dokos wrote:
>>> Why on earth would anybody set it up so that "all web pages are interpreted
>>> as php pages"? Seems crazy to me, but I'm probably naive.
>>
>> The problem can be a config which applies on a too wide range of directories.
>>
>> An easy way to circumvent this is:
>>
>> #+begin_src emacs-lisp
>>   ;; XML encoding
>>   (setq org-export-html-xml-declaration
>>         '(("html" . "<!-- <xml version="1.0" encoding="utf-8"> -->")))
>> #+end_src
>
> Missing escaping of slashes...
>

This works like a charm. :) Thank you so much.

-- 
Suvayu

Open source is the future. It sets us free.

Re: AUCTeX conflicting with org-mode

[Bastien]

Hi Suvayu,

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> I hope you see the no-win situation now (:-p), hence my apprehension
> about the fix earlier. That said, I guess you have two choices:
>
> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>    later. After all, there is a very simple workaround on the user side,
>    do (load "tex.el") before using org-latex.

Okay, let's do this.  I've marked the patch as "Requesting For Comments"
in the patchwork:  http://patchwork.newartisans.com/patch/1232/

Thanks!

-- 
 Bastien

Re: AUCTeX conflicting with org-mode

[suvayu ali]

Hi Bastien,

On Mon, Mar 26, 2012 at 19:47, Bastien <bzg@gnu.org> wrote:
> Hi Suvayu,
>
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>
>> I hope you see the no-win situation now (:-p), hence my apprehension
>> about the fix earlier. That said, I guess you have two choices:
>>
>> 1. Leave the bug unsolved, hoping there will be a cleaner solution
>>    later. After all, there is a very simple workaround on the user side,
>>    do (load "tex.el") before using org-latex.
>
> Okay, let's do this.  I've marked the patch as "Requesting For Comments"
> in the patchwork:  http://patchwork.newartisans.com/patch/1232/
>

Thanks! As I stated earlier, IMO this is the safer choice. Good to see
"the maintainer" agrees. ;)

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

[bug] org-habit-show-all-today undefined

[Eric S Fraga]

With the most recent update to org,

,----
| Author: Max Mikhanosha <max@openchat.com>
| Date:   Mon May 28 14:55:32 2012 -0400
| 
|     Add ability to show all (even unscheduled) habits on today agenda, by
|     setting `org-habit-show-all-today' to t.
|     
|     * lisp/org-agenda.el (defvar org-habit-show-all-today): new variable
|     (org-agenda-get-scheduled): show all habits if user wants it
|     * lisp/org-habit.el (defcustom org-habit-show-all-today): new variable
`----

I get the following error as soon as I try to view my agenda.  I don't
use habits at all.

,----
| Debugger entered--Lisp error: (void-variable org-habit-show-all-today)
|   (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p))))
|   (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p)))))
|   (if (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p))))) (progn (save-excursion (setq donep (member todo-state org-done-keywords)) (if (and donep (or org-agenda-skip-scheduled-if-done (not (= diff 0)) (and (functionp ...) (org-is-habit-p)))) (setq txt nil) (setq habitp (if did-habit-check-p habitp (and (functionp ...) (org-is-habit-p)))) (setq category (org-get-category) org-category-pos (get-text-property (point) (quote org-category-position))) (if (not (re-search-backward "^\\*+[ 	]+" nil t)) (setq txt org-agenda-no-heading-message) (goto-char (match-end 0)) (setq pos1 (match-beginning 0)) (if habitp (if (or ... ...) (throw :skip nil)) (if (and ... ...) (throw :skip nil))) (setq tags (org-get-tags-at)) (setq head (buffer-substring-no-properties (point) (progn ... ...))) (if (string-match " \\([012]?[0-9]:[0-9][0-9]\\)" s) (setq timestr (concat ... " ")) (setq timestr (quote time))) (setq txt (org-agenda-format-item (if ... ... ...) head category tags (if ... nil timestr) nil habitp)))) (when txt (setq face (cond ((and ... pastschedp) (quote org-scheduled-previously)) (todayp (quote org-scheduled-today)) (t (quote org-scheduled))) habitp (and habitp (org-habit-parse-todo))) (org-add-props txt props (quote undone-face) face (quote face) (if donep (quote org-agenda-done) face) (quote org-marker) (org-agenda-new-marker pos) (quote org-hd-marker) (org-agenda-new-marker pos1) (quote type) (if pastschedp "past-scheduled" "scheduled") (quote date) (if pastschedp d2 date) (quote priority) (if habitp (org-habit-get-priority habitp) (+ 94 (- 5 diff) (org-get-priority txt))) (quote org-category) category (quote org-category-position) org-category-pos (quote org-habit-p) habitp (quote todo-state) todo-state) (push txt ee)))))
|   (when (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p))))) (save-excursion (setq donep (member todo-state org-done-keywords)) (if (and donep (or org-agenda-skip-scheduled-if-done (not (= diff 0)) (and (functionp (quote org-is-habit-p)) (org-is-habit-p)))) (setq txt nil) (setq habitp (if did-habit-check-p habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p)))) (setq category (org-get-category) org-category-pos (get-text-property (point) (quote org-category-position))) (if (not (re-search-backward "^\\*+[ 	]+" nil t)) (setq txt org-agenda-no-heading-message) (goto-char (match-end 0)) (setq pos1 (match-beginning 0)) (if habitp (if (or (not org-habit-show-habits) (and ... org-habit-show-habits-only-for-today)) (throw :skip nil)) (if (and (or ... ...) (setq mm ...)) (throw :skip nil))) (setq tags (org-get-tags-at)) (setq head (buffer-substring-no-properties (point) (progn (skip-chars-forward "^\n") (point)))) (if (string-match " \\([012]?[0-9]:[0-9][0-9]\\)" s) (setq timestr (concat (substring s ...) " ")) (setq timestr (quote time))) (setq txt (org-agenda-format-item (if (= diff 0) (car org-agenda-scheduled-leaders) (format ... ...)) head category tags (if (not ...) nil timestr) nil habitp)))) (when txt (setq face (cond ((and (not habitp) pastschedp) (quote org-scheduled-previously)) (todayp (quote org-scheduled-today)) (t (quote org-scheduled))) habitp (and habitp (org-habit-parse-todo))) (org-add-props txt props (quote undone-face) face (quote face) (if donep (quote org-agenda-done) face) (quote org-marker) (org-agenda-new-marker pos) (quote org-hd-marker) (org-agenda-new-marker pos1) (quote type) (if pastschedp "past-scheduled" "scheduled") (quote date) (if pastschedp d2 date) (quote priority) (if habitp (org-habit-get-priority habitp) (+ 94 (- 5 diff) (org-get-priority txt))) (quote org-category) category (quote org-category-position) org-category-pos (quote org-habit-p) habitp (quote todo-state) todo-state) (push txt ee))))
|   (catch :skip (org-agenda-skip) (setq s (match-string 1) txt nil pos (1- (match-beginning 1)) todo-state (save-match-data (org-get-todo-state)) show-all (or (eq org-agenda-repeating-timestamp-show-all t) (member todo-state org-agenda-repeating-timestamp-show-all)) d2 (org-time-string-to-absolute (match-string 1) d1 (quote past) show-all (current-buffer) pos) diff (- d2 d1)) (setq pastschedp (and todayp (< diff 0))) (setq did-habit-check-p nil) (when (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp (quote org-is-habit-p)) (org-is-habit-p))))) (save-excursion (setq donep (member todo-state org-done-keywords)) (if (and donep (or org-agenda-skip-scheduled-if-done (not (= diff 0)) (and (functionp ...) (org-is-habit-p)))) (setq txt nil) (setq habitp (if did-habit-check-p habitp (and (functionp ...) (org-is-habit-p)))) (setq category (org-get-category) org-category-pos (get-text-property (point) (quote org-category-position))) (if (not (re-search-backward "^\\*+[ 	]+" nil t)) (setq txt org-agenda-no-heading-message) (goto-char (match-end 0)) (setq pos1 (match-beginning 0)) (if habitp (if (or ... ...) (throw :skip nil)) (if (and ... ...) (throw :skip nil))) (setq tags (org-get-tags-at)) (setq head (buffer-substring-no-properties (point) (progn ... ...))) (if (string-match " \\([012]?[0-9]:[0-9][0-9]\\)" s) (setq timestr (concat ... " ")) (setq timestr (quote time))) (setq txt (org-agenda-format-item (if ... ... ...) head category tags (if ... nil timestr) nil habitp)))) (when txt (setq face (cond ((and ... pastschedp) (quote org-scheduled-previously)) (todayp (quote org-scheduled-today)) (t (quote org-scheduled))) habitp (and habitp (org-habit-parse-todo))) (org-add-props txt props (quote undone-face) face (quote face) (if donep (quote org-agenda-done) face) (quote org-marker) (org-agenda-new-marker pos) (quote org-hd-marker) (org-agenda-new-marker pos1) (quote type) (if pastschedp "past-scheduled" "scheduled") (quote date) (if pastschedp d2 date) (quote priority) (if habitp (org-habit-get-priority habitp) (+ 94 (- 5 diff) (org-get-priority txt))) (quote org-category) category (quote org-category-position) org-category-pos (quote org-habit-p) habitp (quote todo-state) todo-state) (push txt ee)))))
|   (while (re-search-forward regexp nil t) (catch :skip (org-agenda-skip) (setq s (match-string 1) txt nil pos (1- (match-beginning 1)) todo-state (save-match-data (org-get-todo-state)) show-all (or (eq org-agenda-repeating-timestamp-show-all t) (member todo-state org-agenda-repeating-timestamp-show-all)) d2 (org-time-string-to-absolute (match-string 1) d1 (quote past) show-all (current-buffer) pos) diff (- d2 d1)) (setq pastschedp (and todayp (< diff 0))) (setq did-habit-check-p nil) (when (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and (functionp ...) (org-is-habit-p))))) (save-excursion (setq donep (member todo-state org-done-keywords)) (if (and donep (or org-agenda-skip-scheduled-if-done (not ...) (and ... ...))) (setq txt nil) (setq habitp (if did-habit-check-p habitp (and ... ...))) (setq category (org-get-category) org-category-pos (get-text-property (point) (quote org-category-position))) (if (not (re-search-backward "^\\*+[ 	]+" nil t)) (setq txt org-agenda-no-heading-message) (goto-char (match-end 0)) (setq pos1 (match-beginning 0)) (if habitp (if ... ...) (if ... ...)) (setq tags (org-get-tags-at)) (setq head (buffer-substring-no-properties ... ...)) (if (string-match " \\([012]?[0-9]:[0-9][0-9]\\)" s) (setq timestr ...) (setq timestr ...)) (setq txt (org-agenda-format-item ... head category tags ... nil habitp)))) (when txt (setq face (cond (... ...) (todayp ...) (t ...)) habitp (and habitp (org-habit-parse-todo))) (org-add-props txt props (quote undone-face) face (quote face) (if donep (quote org-agenda-done) face) (quote org-marker) (org-agenda-new-marker pos) (quote org-hd-marker) (org-agenda-new-marker pos1) (quote type) (if pastschedp "past-scheduled" "scheduled") (quote date) (if pastschedp d2 date) (quote priority) (if habitp (org-habit-get-priority habitp) (+ 94 ... ...)) (quote org-category) category (quote org-category-position) org-category-pos (quote org-habit-p) habitp (quote todo-state) todo-state) (push txt ee))))))
|   (let* ((props (list (quote org-not-done-regexp) org-not-done-regexp (quote org-todo-regexp) org-todo-regexp (quote org-complex-heading-regexp) org-complex-heading-regexp (quote done-face) (quote org-agenda-done) (quote mouse-face) (quote highlight) (quote help-echo) (format "mouse-2 or RET jump to org file %s" (abbreviate-file-name buffer-file-name)))) (regexp org-scheduled-time-regexp) (todayp (org-agenda-todayp date)) (d1 (calendar-absolute-from-gregorian date)) mm (deadline-position-alist (mapcar (lambda (a) (and (setq mm (get-text-property 0 ... a)) (cons (marker-position mm) a))) deadline-results)) d2 diff pos pos1 category org-category-pos tags donep ee txt head pastschedp todo-state face timestr s habitp show-all did-habit-check-p) (goto-char (point-min)) (while (re-search-forward regexp nil t) (catch :skip (org-agenda-skip) (setq s (match-string 1) txt nil pos (1- (match-beginning 1)) todo-state (save-match-data (org-get-todo-state)) show-all (or (eq org-agenda-repeating-timestamp-show-all t) (member todo-state org-agenda-repeating-timestamp-show-all)) d2 (org-time-string-to-absolute (match-string 1) d1 (quote past) show-all (current-buffer) pos) diff (- d2 d1)) (setq pastschedp (and todayp (< diff 0))) (setq did-habit-check-p nil) (when (or (and (< diff 0) (< (abs diff) org-scheduled-past-days) (and todayp (not org-agenda-only-exact-dates))) (= diff 0) (and todayp org-habit-show-all-today (setq did-habit-check-p t) (setq habitp (and ... ...)))) (save-excursion (setq donep (member todo-state org-done-keywords)) (if (and donep (or org-agenda-skip-scheduled-if-done ... ...)) (setq txt nil) (setq habitp (if did-habit-check-p habitp ...)) (setq category (org-get-category) org-category-pos (get-text-property ... ...)) (if (not ...) (setq txt org-agenda-no-heading-message) (goto-char ...) (setq pos1 ...) (if habitp ... ...) (setq tags ...) (setq head ...) (if ... ... ...) (setq txt ...))) (when txt (setq face (cond ... ... ...) habitp (and habitp ...)) (org-add-props txt props (quote undone-face) face (quote face) (if donep ... face) (quote org-marker) (org-agenda-new-marker pos) (quote org-hd-marker) (org-agenda-new-marker pos1) (quote type) (if pastschedp "past-scheduled" "scheduled") (quote date) (if pastschedp d2 date) (quote priority) (if habitp ... ...) (quote org-category) category (quote org-category-position) org-category-pos (quote org-habit-p) habitp (quote todo-state) todo-state) (push txt ee)))))) (nreverse ee))
|   org-agenda-get-scheduled(nil)
|   (setq rtn (org-agenda-get-scheduled deadline-results))
|   (cond ((and (eq arg :todo) (equal date (calendar-gregorian-from-absolute (org-today)))) (setq rtn (org-agenda-get-todos)) (setq results (append results rtn))) ((eq arg :timestamp) (setq rtn (org-agenda-get-blocks)) (setq results (append results rtn)) (setq rtn (org-agenda-get-timestamps deadline-results)) (setq results (append results rtn))) ((eq arg :sexp) (setq rtn (org-agenda-get-sexps)) (setq results (append results rtn))) ((eq arg :scheduled) (setq rtn (org-agenda-get-scheduled deadline-results)) (setq results (append results rtn))) ((eq arg :closed) (setq rtn (org-agenda-get-progress)) (setq results (append results rtn))) ((eq arg :deadline) (setq rtn (org-agenda-get-deadlines)) (setq deadline-results (copy-sequence rtn)) (setq results (append results rtn))))
|   (while (setq arg (pop args)) (cond ((and (eq arg :todo) (equal date (calendar-gregorian-from-absolute (org-today)))) (setq rtn (org-agenda-get-todos)) (setq results (append results rtn))) ((eq arg :timestamp) (setq rtn (org-agenda-get-blocks)) (setq results (append results rtn)) (setq rtn (org-agenda-get-timestamps deadline-results)) (setq results (append results rtn))) ((eq arg :sexp) (setq rtn (org-agenda-get-sexps)) (setq results (append results rtn))) ((eq arg :scheduled) (setq rtn (org-agenda-get-scheduled deadline-results)) (setq results (append results rtn))) ((eq arg :closed) (setq rtn (org-agenda-get-progress)) (setq results (append results rtn))) ((eq arg :deadline) (setq rtn (org-agenda-get-deadlines)) (setq deadline-results (copy-sequence rtn)) (setq results (append results rtn)))))
|   (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond ((and (eq arg :todo) (equal date (calendar-gregorian-from-absolute (org-today)))) (setq rtn (org-agenda-get-todos)) (setq results (append results rtn))) ((eq arg :timestamp) (setq rtn (org-agenda-get-blocks)) (setq results (append results rtn)) (setq rtn (org-agenda-get-timestamps deadline-results)) (setq results (append results rtn))) ((eq arg :sexp) (setq rtn (org-agenda-get-sexps)) (setq results (append results rtn))) ((eq arg :scheduled) (setq rtn (org-agenda-get-scheduled deadline-results)) (setq results (append results rtn))) ((eq arg :closed) (setq rtn (org-agenda-get-progress)) (setq results (append results rtn))) ((eq arg :deadline) (setq rtn (org-agenda-get-deadlines)) (setq deadline-results (copy-sequence rtn)) (setq results (append results rtn))))))
|   (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond ((and (eq arg :todo) (equal date (calendar-gregorian-from-absolute ...))) (setq rtn (org-agenda-get-todos)) (setq results (append results rtn))) ((eq arg :timestamp) (setq rtn (org-agenda-get-blocks)) (setq results (append results rtn)) (setq rtn (org-agenda-get-timestamps deadline-results)) (setq results (append results rtn))) ((eq arg :sexp) (setq rtn (org-agenda-get-sexps)) (setq results (append results rtn))) ((eq arg :scheduled) (setq rtn (org-agenda-get-scheduled deadline-results)) (setq results (append results rtn))) ((eq arg :closed) (setq rtn (org-agenda-get-progress)) (setq results (append results rtn))) ((eq arg :deadline) (setq rtn (org-agenda-get-deadlines)) (setq deadline-results (copy-sequence rtn)) (setq results (append results rtn)))))))
|   (let ((case-fold-search nil)) (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond ((and (eq arg :todo) (equal date ...)) (setq rtn (org-agenda-get-todos)) (setq results (append results rtn))) ((eq arg :timestamp) (setq rtn (org-agenda-get-blocks)) (setq results (append results rtn)) (setq rtn (org-agenda-get-timestamps deadline-results)) (setq results (append results rtn))) ((eq arg :sexp) (setq rtn (org-agenda-get-sexps)) (setq results (append results rtn))) ((eq arg :scheduled) (setq rtn (org-agenda-get-scheduled deadline-results)) (setq results (append results rtn))) ((eq arg :closed) (setq rtn (org-agenda-get-progress)) (setq results (append results rtn))) ((eq arg :deadline) (setq rtn (org-agenda-get-deadlines)) (setq deadline-results (copy-sequence rtn)) (setq results (append results rtn))))))))
|   (save-current-buffer (set-buffer buffer) (unless (derived-mode-p (quote org-mode)) (error "Agenda file %s is not in `org-mode'" file)) (let ((case-fold-search nil)) (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond ((and ... ...) (setq rtn ...) (setq results ...)) ((eq arg :timestamp) (setq rtn ...) (setq results ...) (setq rtn ...) (setq results ...)) ((eq arg :sexp) (setq rtn ...) (setq results ...)) ((eq arg :scheduled) (setq rtn ...) (setq results ...)) ((eq arg :closed) (setq rtn ...) (setq results ...)) ((eq arg :deadline) (setq rtn ...) (setq deadline-results ...) (setq results ...))))))) results)
|   (with-current-buffer buffer (unless (derived-mode-p (quote org-mode)) (error "Agenda file %s is not in `org-mode'" file)) (let ((case-fold-search nil)) (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond ((and ... ...) (setq rtn ...) (setq results ...)) ((eq arg :timestamp) (setq rtn ...) (setq results ...) (setq rtn ...) (setq results ...)) ((eq arg :sexp) (setq rtn ...) (setq results ...)) ((eq arg :scheduled) (setq rtn ...) (setq results ...)) ((eq arg :closed) (setq rtn ...) (setq results ...)) ((eq arg :deadline) (setq rtn ...) (setq deadline-results ...) (setq results ...))))))) results)
|   (if (not buffer) (list (format "ORG-AGENDA-ERROR: No such org-file %s" file)) (with-current-buffer buffer (unless (derived-mode-p (quote org-mode)) (error "Agenda file %s is not in `org-mode'" file)) (let ((case-fold-search nil)) (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg (pop args)) (cond (... ... ...) (... ... ... ... ...) (... ... ...) (... ... ...) (... ... ...) (... ... ... ...)))))) results))
|   (let* ((org-startup-folded nil) (org-startup-align-all-tables nil) (buffer (if (file-exists-p file) (org-get-agenda-file-buffer file) (error "No such file %s" file))) arg results rtn deadline-results) (if (not buffer) (list (format "ORG-AGENDA-ERROR: No such org-file %s" file)) (with-current-buffer buffer (unless (derived-mode-p (quote org-mode)) (error "Agenda file %s is not in `org-mode'" file)) (let ((case-fold-search nil)) (save-excursion (save-restriction (if org-agenda-restrict (narrow-to-region org-agenda-restrict-begin org-agenda-restrict-end) (widen)) (while (setq arg ...) (cond ... ... ... ... ... ...))))) results)))
|   org-agenda-get-day-entries("~/s/notes/notes.org" (5 29 2012) :deadline :scheduled :timestamp)
`----

thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 + Ma Gnus v0.6

Re: [bug] org-habit-show-all-today undefined

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> With the most recent update to org,
> 
> ,----
> | Author: Max Mikhanosha <max@openchat.com>
> | Date:   Mon May 28 14:55:32 2012 -0400
> |=20
> |     Add ability to show all (even unscheduled) habits on today agenda, by
> |     setting `org-habit-show-all-today' to t.
> |=20=20=20=20=20
> |     * lisp/org-agenda.el (defvar org-habit-show-all-today): new variable
> |     (org-agenda-get-scheduled): show all habits if user wants it
> |     * lisp/org-habit.el (defcustom org-habit-show-all-today): new variable
> `----
> 
> I get the following error as soon as I try to view my agenda.  I don't
> use habits at all.
> 
> ,----
> | Debugger entered--Lisp error: (void-variable org-habit-show-all-today)


Me too, with the version just pulled earlier today:

Org-mode version 7.8.10 (release_7.8.10-626-g8a83e3 @ /home/nick/elisp/org-mode/lisp/)


I fixed it (or maybe I should say: I "fixed" it :-) ) by giving an
initial value to the variable in org-agenda.el:

(defvar org-habit-show-all-today nil
	"... doc string ...")

Nick

Re: [bug] org-habit-show-all-today undefined

[Max Mikhanosha]

At Tue, 29 May 2012 11:33:35 -0400,
Nick Dokos wrote:
> 
> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> 
> > I get the following error as soon as I try to view my agenda.  I don't
> > use habits at all.
> > 
> > ,----
> > | Debugger entered--Lisp error: (void-variable org-habit-show-all-today)
> 
> I fixed it (or maybe I should say: I "fixed" it :-) ) by giving an
> initial value to the variable in org-agenda.el:
> 
> (defvar org-habit-show-all-today nil
> 	"... doc string ...")

Sorry, forgot to test without 'org-habit loaded, should be fixed now.

Regards,
  Max

Re: [bug] org-habit-show-all-today undefined

[Nick Dokos]

Max Mikhanosha <max@openchat.com> wrote:

> At Tue, 29 May 2012 11:33:35 -0400,
> Nick Dokos wrote:
> > 
> > Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> > 
> > > I get the following error as soon as I try to view my agenda.  I don't
> > > use habits at all.
> > > 
> > > ,----
> > > | Debugger entered--Lisp error: (void-variable org-habit-show-all-today)
> > 
> > I fixed it (or maybe I should say: I "fixed" it :-) ) by giving an
> > initial value to the variable in org-agenda.el:
> > 
> > (defvar org-habit-show-all-today nil
> > 	"... doc string ...")
> 
> Sorry, forgot to test without 'org-habit loaded, should be fixed now.
> 

Yup, I think it is: thanks!

Nick

Error when changing todo-state [7.8.11]

[salome.soedergran]

Hi!

I recently upgraded to emacs24 and org 7.8.11. Since this upgrade, when I set or change a todo-state, I get an error message (void-variable state). The desired todo-state is being set all the same. I guess there's some kind of conflict between my config and the new org-version -- but what is it and what can I do about it?
Please find the backtrace and parts of my init-file below.

Best, Salome


BACKTRACE
Debugger entered--Lisp error: (void-variable state)
  (member state org-done-keywords)
  (if (member state org-done-keywords) (progn (org-make-checklist-export) (org-reset-checkbox-state-maybe)))
  (when (member state org-done-keywords) (org-make-checklist-export) (org-reset-checkbox-state-maybe))
  org-checklist()
  run-hooks(org-after-todo-state-change-hook)
  byte-code("\306\307!\210\310\b!\203\x0f\0\311\225Sb\210\310\312	\313Q!\204\x1c\0\310\314!\210\302 \x1a\315 ^[\302 \x1c\316\216\317\320\321\307\211$*\x1d\x0e@\x1e@\x0eA\x1eA\x0eB\x1eB\x0eC\311\232\203I\0\320\x16C\322\202K\0\x0eD\x1eD\323\324!\x1eE\311\224\x1eF\325\x0eE!\x1eG\326\x0eG\x0eH\"\211\x1eIA@\x1eJ\327\x0eI8\x1eK\330\x0eI8\x1eL\x0eE\206{\0\331\x1eM\307\x1eN\x0eE\x0eO\235\211\x1ePA\x1eQ\x0eR\203\264\0\x0eC\332\232\203\236\0\x0eS\333=\204\257\0\x0eC\204\264\0\x0eS\203\264\0\x0eS\333=\204\264\0\334 \202	\x02\x0eC\335\232\203\322\0\x0eS\203\305\0\x0eR\204\322\0\336\337\340\341\x0eO\"\320\307$\202	\x02\x0eC\342=\203\357\0\x0eE\203\351\0\x0eQ\205	\x02\x0eQ@\202	\x02\x0eO@\202	\x02\x0eC\343=\203 \x01\x0eP\x0eO\232?\205	\x02\x0eE\203\x13\x01\344\x0eOG\x0eQG\345#\x0eO8\202	\x02\x0eO\x1eT\346\x0eT!@)\202	\x02\x0eS\307=\2035\x01\x0eC\347\232\2035\x01\320\211\x16C\206	\x02\x0eC\203\271\x01\x0eC\331\232\203E\x01\320\202	\x02\x0eC\350=\203P\x01\320\202	\x02\x0eC\351=\203b\x01\x0eK\206	\x02\x0eU@\202	\x02\x0eC\352=\203y\x01\x0eG\x0eV\235A@\206	\x02\x0eV@\202	\x02\x0eC\353=\203\227\x01\354\x0eV!\x1eV\x0eG\x0eV\235A@\206\223\x01\x0eV@)\202	\x02\x0eC\x0eO\235@\206	\x02\x0eC;\203\256\x01\355\356\x0eC\"\202	\x02\357\x0eC!S\x0eO8\202	\x02\x0eP\204\311\x01\x0eG\206	\x02\x0eO@\202	\x02\x0eE\x0eL\232\203\325\x01\320\202	\x02\x0eQ\204\336\x01\320\202	\x02\x0eJ\360>\203\x06\x02\x0eW\x0eX=\203\363\x01\x0eQ@\202	\x02\x0eQG\311V\205	\x02\x0eK\206	\x02\x0eU@\202	\x02\x0eQ@\x1eY\361\362\x0eY\x0eM#\206\x17\x02\x0eY\211\x1eY\203%\x02\363\x0eY\363Q\202&\x02\363\x1eZ\364\365\366\x0eE\367\x0eY\370\v\257\b\x1e[\320\211\x1e\\\x1e]\x0e;\203~\x02\x0eE\x0eU\235?\x16^\212\302 \x1c\371\216\212\214~\210\372\373\x0e[\"-\204~\x02\374\375!\203m\x02\355\376\x0eE\x0eY#\210\202~\x02\377\376\x0eE\x0eY#\210\201g\0\201h\0\320\"\210\201i\0\n!\210\201j\0\x0eZ\307\211#\210\201k\0\x0eF!\204\242\x02\377\201l\0\201m\0\x0eZ!\"\210\x0eG\204\306\x02\325\x0eY!\x16G\326\x0eG\x0eH\"\211\x16IA@\x16J\327\x0eI8\x16K\330\x0eI8\x16L\x0eC\201n\0>\203\370\x02\377\201o\0\344\x0e_G\201p\0\326\x0eY\x0e_\"\x0e_>G#\x0e_G\201q\0\201r\0\326\x0eY\x0e_\"\363#$\210\x0eY\x0eU\235?\x16^\x0eY\x0eU\235\205\x0e\x03\x0eE\x0eU\235?\x16]\r\203\x1a\x03\201s\0\r!\210\x0eB\204$\x03\x0e@\203\305\x03\x0eD\307=\204\305\x03\x0eC\201t\0>\204\305\x03\326\x0eY\x0eB\"A@\206G\x03\345\326\x0eE\x0eB\"8\211\x16\\\322=\203[\x03\x0eD\322=\203[\x03\201u\0\x16\\\x0eY\203z\x03\x0eY\x0e`\235\203z\x03\x0eE\x0e`\235\204z\x03\201v\0\320\211\201w\0#\210\x0e]\203\252\x03\x0e@\203\252\x03\201v\0\201w\0\201x\0 \"\210\x0e\\\204\252\x03\x0e@\322=\203\252\x03\201y\0\351\x0eY\x0eE\201z\0\322%\210\x0eY\203\305\x03\x0e\\\203\305\x03\201y\0\201{\0\x0eY\x0eE\201z\0\x0e\\%\210\201|\0\x0eY!\210\x0ea\203\335\x03\x0eb\204\335\x03\201}\0\320\307\"\210\x0ec\203\347\x03\201~\0 \210\201\x7f\0\201\200\0!\210\x0eC\203\x02\x04\x0eY\x0eU\235\204\x02\x04\325\x0eY!\x16G\201\201\0\315 \201\202\0 \201\203\0\x0eG$\210\x0e]\2036\x04\201\204\0\201d\0!\203/\x04\302 \x1c\201\205\0\216\201\206\0 \x16d*\201\207\0\x0eY!\210\201\210\0 \203r\x04n\204r\x04\212\201\211\0\324!\210\310\x0ee!)\203r\x04`\345\211\225\206Y\x04\324\225\\W\203r\x04\345\225\206e\x04\324\225b\210\310\363!\203r\x04\201\212\0 \210\x0ef\205\202\x04\212\201\213\0\201f\0\x0e[\").\x18\207" [org-outline-regexp org-todo-regexp match-data startpos save-match-data-internal logging org-back-to-heading t looking-at 0 " +" "\\( +\\|[ 	]*$\\)" "\\(?: *\\|[ 	]*$\\)" point-at-bol ((byte-code "\301\b\302\"\207" [save-match-data-internal set-match-data evaporate] 3)) org-entry-get nil "LOGGING" note match-string 1 org-get-todo-sequence-head assoc 3 4 "" (4) prefix org-fast-todo-selection (4) org-icompleting-read "State: " mapcar #[(x) "\bC\207" [x] 1] right left - 2 last (4) none done nextset previousset reverse error "State `%s' not valid in this file" prefix-numeric-value (type priority) run-hook-with-args-until-success ...] 10)
  org-todo(nil)
  call-interactively(org-todo nil nil)


Emacs  : GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 3.4.2)
 of 2012-06-16 on platinum, modified by Debian
Package: Org-mode version 7.8.11

INIT-FILE (part)
(setq
 org-clock-persist 'history
 org-agenda-window-setup 'current-window
 org-goto-max-level 10
 org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code)
 org-tab-first-hook '(org-hide-block-toggle-maybe
		      org-src-native-tab-command-maybe
		      org-babel-hide-result-toggle-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
		  org-cycle-show-empty-lines
		  org-optimize-window-after-visibility-change)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-speed-command-hook '(org-speed-command-default-hook
			  org-babel-speed-command-hook)
 org-show-following-heading t
 org-agenda-restore-windows-after-quit t
 org-babel-pre-tangle-hook '(save-buffer)
 org-occur-hook '(org-first-headline-recenter)
 org-export-interblocks '((src org-babel-exp-non-block-elements))
 org-cycle-separator-lines 0
 org-use-sub-superscripts nil
 org-clock-out-remove-zero-time-clocks t
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-export-latex-format-toc-function 'org-export-latex-format-toc-default
 org-hide-leading-stars t
 org-log-into-drawer "LOGBOOK"
 org-columns-default-format "%25ITEM(Details) %15TAGS(Context) %7TODO(To Do) %5Effort(Time){:} %6CLOCKSUM(Clock){Total}"
 org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers)
 org-show-siblings nil
 org-checklist-export-function 'org-export-as-ascii
 org-attach-method '(link)
 org-blank-before-new-entry '((heading) (plain-list-item))
 org-global-properties '(("Effort_ALL" .
			  "0 0:10 0:30 1:00 2:00 3:00 4:00 6:00 8:00")
			 )
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-agenda-prefix-format '((agenda . "%?-12t% s") (timeline . "  % s")
			    (todo . "%-12:c") (tags . "%-12:c %i")
			    (search . " %i %-12:c"))
 org-agenda-skip-deadline-if-done t
 org-export-first-hook '(org-beamer-initialize-open-trackers)
 org-mode-hook '((lambda nil (local-set-key [f11] (quote org2blog/wp-mode)))
		 org-clock-load
		 #[nil "\300\301\302\303\304$\207"
		   [org-add-hook change-major-mode-hook org-show-block-all
		    append local]
		   5]
		 #[nil "\300\301\302\303\304$\207"
		   [org-add-hook change-major-mode-hook
		    org-babel-show-result-all append local]
		   5]
		 org-babel-result-hide-spec org-babel-hide-all-hashes
		 (lambda nil (subword-mode 1)))
 org-export-latex-low-levels '("\\begin{itemize}" "\\end{itemize}" "\\item %s")
 org-show-hierarchy-above t
 org-agenda-remove-tags t
 org-clock-idle-time 15
 org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
			       org-beamer-auto-fragile-frames
			       org-beamer-place-default-actions-for-lists)
 org-export-html-coding-system 'utf-8
 org-agenda-repeating-timestamp-show-all nil
 org-tags-column -75
 org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
 org-cycle-emulate-tab '(whitestart)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-todo-keywords '((sequence "APPT(a!)" "NEXT(n!)" "WAITING(w@)" "INBOX(i)"
		      "|" "DONE(d!)" "CANCELLED(c!)" "MAYBE/LATER(m!)")
		     )
 org-agenda-weekend-days '(0)
 org-agenda-files '("~/org/gtd.org")
 org-drawers '("ZIEL" "PROPERTIES" "LOGBOOK" "CLOCK")
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
		     org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-checklist org-clock-out-if-current)
 org-bbdb-anniversary-format-alist '(("birthday" lambda (name years suffix)
				      (concat "[[bbdb:" name "][" name
				       "]] ist " (number-to-string years)
				       " Jahre alt")
				      )
				     ("wedding" lambda (name years suffix)
				      (concat "[[bbdb:" name "][" name "]]"
				       (number-to-string years)
				       ". Hochzeitstag")
				      )
				     )
 org-agenda-tags-todo-honor-ignore-options t
 org-confirm-shell-link-function 'yes-or-no-p
 )

Re: Error when changing todo-state [7.8.11]

[Eric S Fraga]

<salome.soedergran@gmx.ch> writes:

> Hi!
>
> I recently upgraded to emacs24 and org 7.8.11. Since this upgrade,
> when I set or change a todo-state, I get an error message
> (void-variable state). The desired todo-state is being set all the
> same. I guess there's some kind of conflict between my config and the
> new org-version -- but what is it and what can I do about it?
> Please find the backtrace and parts of my init-file below.

"state" has been changed to "org-state".
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96

Re: Error when changing todo-state [7.8.11]

[Charles Philip Chan]

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

salome.soedergran@gmx.ch writes:

Hi Salome:

> I recently upgraded to emacs24 and org 7.8.11. Since this upgrade,
> when I set or change a todo-state, I get an error message
> (void-variable state). 

I had the same problem. It turned out that the problem is some
customization that I have in "org-after-todo-state-change-hook". IIRC,
the offending code (at least for me) is:

,----
| ;;Add category to todos
|     (add-hook 'org-after-todo-state-change-hook
|               (lambda ()
|                       (if (string= state "CATEGORY")
|                           (save-excursion
|                                 (org-back-to-heading)
|                                 (org-set-property "CATEGORY"
|                                        (nth 4 (org-heading-components)))))))
`----

YMMV.

Charles

-- 
I've run DOOM more in the last few days than I have the last few
months.  I just love debugging ;-)
(Linus Torvalds)

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: Error when changing todo-state [7.8.11]

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> <salome.soedergran@gmx.ch> writes:
> 
> > Hi!
> >
> > I recently upgraded to emacs24 and org 7.8.11. Since this upgrade,
> > when I set or change a todo-state, I get an error message
> > (void-variable state). The desired todo-state is being set all the
> > same. I guess there's some kind of conflict between my config and the
> > new org-version -- but what is it and what can I do about it?
> > Please find the backtrace and parts of my init-file below.
> 
> "state" has been changed to "org-state".

That's probably the cause of the problem, but there is still the question
of whether "state" is used in some customization that the OP has done
or whether there are inconsistencies in the update (i.e. old bits lying
around and being used in preference to the new ones).

If tne cure is not obvious given the hints that various people have
given, I would suggest M-x toggle-debug-on-error and posting the
backtrace.

Nick

From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi all,

there is no need to (require 'org-install) anymore from the maint
and master branches.

When using the Org distribution that comes with Emacs, Emacs will add
Org's autoloaded core functions to [emacs]/lisp/loaddefs.el and the rest
of the autoloaded functions to [emacs]/lisp/org/org-loaddefs.el.  This
is an improvement over the present situation, where *all* autoloaded
functions where added to Emacs' loaddefs.el -- too much.  This is not
yet in Emacs trunk but will be in Emacs 24.3.

When getting Org as a .tar.gz/.zip archive file, you'll have a file
org-loaddefs.el in the lisp/ directory -- this file is now loaded when
org.el is loaded.

When getting Org from ELPA (either "org" or "org-plus-contrib"),
org-loaddefs.el will also be in the load-path.

When getting Org from git, you *HAVE* to created org-loaddefs.el with
`make autoloads' (which is also run by a simple `make'), otherwise
some needed functions will not be autoloaded.

You can check whether org-loaddefs.el has been correctly been loaded
with M-x org-version RET.

Thanks,

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[Torsten Wagner]

Hi Bastien,

nice. One line less in uhhhh .... how long is my emacs config, but it
was a constant trap for people and hence this is smoothed out... good
job ;)
Anyhow I just realized that ELPA contains
"org" and "org-plus-contrib"
I stupidly overlooked that and always read
"org" or "org-contrib"

Well, thats the way many Linux distros does that kind of things. Sure
enough org-contrib would need org as a requirement.
Maybe thats not possible in ELPA yet?!

Anyhow any reason for the above way?

Greetings

Torsten


On 2 October 2012 22:15, Bastien <bzg@altern.org> wrote:
> Hi all,
>
> there is no need to (require 'org-install) anymore from the maint
> and master branches.
>
> When using the Org distribution that comes with Emacs, Emacs will add
> Org's autoloaded core functions to [emacs]/lisp/loaddefs.el and the rest
> of the autoloaded functions to [emacs]/lisp/org/org-loaddefs.el.  This
> is an improvement over the present situation, where *all* autoloaded
> functions where added to Emacs' loaddefs.el -- too much.  This is not
> yet in Emacs trunk but will be in Emacs 24.3.
>
> When getting Org as a .tar.gz/.zip archive file, you'll have a file
> org-loaddefs.el in the lisp/ directory -- this file is now loaded when
> org.el is loaded.
>
> When getting Org from ELPA (either "org" or "org-plus-contrib"),
> org-loaddefs.el will also be in the load-path.
>
> When getting Org from git, you *HAVE* to created org-loaddefs.el with
> `make autoloads' (which is also run by a simple `make'), otherwise
> some needed functions will not be autoloaded.
>
> You can check whether org-loaddefs.el has been correctly been loaded
> with M-x org-version RET.
>
> Thanks,
>
> --
>  Bastien
>
>

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi Torsten,

Torsten Wagner <torsten.wagner@gmail.com> writes:

> Anyhow I just realized that ELPA contains
> "org" and "org-plus-contrib"
> I stupidly overlooked that and always read
> "org" or "org-contrib"
>
> Well, thats the way many Linux distros does that kind of things. Sure
> enough org-contrib would need org as a requirement.
> Maybe thats not possible in ELPA yet?!

org-plus-contrib has this lenghthy name precisely to make sure that
people know this is Org + Contributed files, not just contributed files.

> Anyhow any reason for the above way?

Apparently it's not possible/easy to handle dependancies between ELPA
packages so we're good like this (for now.)

All best,

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[Rainer M Krug]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/10/12 15:15, Bastien wrote:
> Hi all,
> 
> there is no need to (require 'org-install) anymore from the maint and master branches.
> 
> When using the Org distribution that comes with Emacs, Emacs will add Org's autoloaded core 
> functions to [emacs]/lisp/loaddefs.el and the rest of the autoloaded functions to 
> [emacs]/lisp/org/org-loaddefs.el.  This is an improvement over the present situation, where 
> *all* autoloaded functions where added to Emacs' loaddefs.el -- too much.  This is not yet in 
> Emacs trunk but will be in Emacs 24.3.
> 
> When getting Org as a .tar.gz/.zip archive file, you'll have a file org-loaddefs.el in the 
> lisp/ directory -- this file is now loaded when org.el is loaded.
> 
> When getting Org from ELPA (either "org" or "org-plus-contrib"), org-loaddefs.el will also be 
> in the load-path.
> 
> When getting Org from git, you *HAVE* to created org-loaddefs.el with `make autoloads' (which 
> is also run by a simple `make'), otherwise some needed functions will not be autoloaded.
> 
> You can check whether org-loaddefs.el has been correctly been loaded with M-x org-version RET.

But how do I see it? I get:

Org-mode version 7.9.2 (release_7.9.2-352-g7f74da.dirty @ /home/rkrug/.emacs.d/org-mode/lisp/) [2
times]

I am getting confused.

I use org mode from git, and my update script for org from git is:

#!/bin/sh
cd ~/.emacs.d/org-mode-git/org-mode

git checkout master
git fetch --tags origin

# git clone git://repo.or.cz/org-mode.git
git pull
git gc

git checkout master

make clean
make
make autoloads
make doc
make info

# make install

Is this OK, or should I change something in the script? Or switch to ELPA (emacs 24.2.1)?

Rainer
> 
> Thanks,
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBq8i8ACgkQoYgNqgF2egqrNwCdGy9+Lz2biQWGWIQcZJzYy+4Q
2IgAoIHL2JxB+MVu3ZvKszB4wZXvBJnr
=RDan
-----END PGP SIGNATURE-----

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi Rainer,

Rainer M Krug <r.m.krug@gmail.com> writes:

> Org-mode version 7.9.2 (release_7.9.2-352-g7f74da.dirty @
> /home/rkrug/.emacs.d/org-mode/lisp/)

Looks fine.

> I use org mode from git, and my update script for org from git is:
>
> #!/bin/sh
> cd ~/.emacs.d/org-mode-git/org-mode

Okay.

> git checkout master
> git fetch --tags origin
>
> # git clone git://repo.or.cz/org-mode.git
> git pull
> git gc
>
> git checkout master
>
> make clean
> make
> make autoloads
> make doc
> make info
>
> # make install

Instead of the above quote you can simply use

make update

(And you can clone from git://orgmode.org/org-mode.git
it will be faster and more recent. repo.or.cz is behind
by one hour.) 

> Is this OK, or should I change something in the script? Or switch to ELPA (emacs 24.2.1)?

Things look okay.  My suggestions are just to spare some lines.

Best,

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[Rainer M Krug]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/10/12 16:20, Bastien wrote:
> Hi Rainer,
> 
> Rainer M Krug <r.m.krug@gmail.com> writes:
> 
>> Org-mode version 7.9.2 (release_7.9.2-352-g7f74da.dirty @ 
>> /home/rkrug/.emacs.d/org-mode/lisp/)
> 
> Looks fine.

Good to know.

> 
>> I use org mode from git, and my update script for org from git is:
>> 
>> #!/bin/sh cd ~/.emacs.d/org-mode-git/org-mode
> 
> Okay.

> 
>> git checkout master git fetch --tags origin
>> 
>> # git clone git://repo.or.cz/org-mode.git git pull git gc
>> 
>> git checkout master
>> 
>> make clean make make autoloads make doc make info
>> 
>> # make install
> 
> Instead of the above quote you can simply use
> 
> make update

I guess you mean instead of the make ... commands - right? The git ... have to stay I assume?

> 
> (And you can clone from git://orgmode.org/org-mode.git it will be faster and more recent.
> repo.or.cz is behind by one hour.)

Switched some time ago - the repo.or.cz in the comment is just a leftover.

> 
>> Is this OK, or should I change something in the script? Or switch to ELPA (emacs 24.2.1)?
> 
> Things look okay.  My suggestions are just to spare some lines.

Thanks a lot,

now I can sleep a little better,

Rainer

> 
> Best,
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBq/6AACgkQoYgNqgF2egpPoQCfYYHZ+t+tP5s6Sg4TICTQwigA
jSMAn21qlfBzymy0vCM4p63Y0QFdeEzg
=GFcW
-----END PGP SIGNATURE-----

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Rainer Stengele]

Am 02.10.2012 16:20, schrieb Bastien:
> Hi Rainer,
> 
> Rainer M Krug <r.m.krug@gmail.com> writes:
> 
>> Org-mode version 7.9.2 (release_7.9.2-352-g7f74da.dirty @
>> /home/rkrug/.emacs.d/org-mode/lisp/)
> 
> Looks fine.
> 
>> I use org mode from git, and my update script for org from git is:
>>
>> #!/bin/sh
>> cd ~/.emacs.d/org-mode-git/org-mode
> 
> Okay.
> 
>> git checkout master
>> git fetch --tags origin
>>
>> # git clone git://repo.or.cz/org-mode.git
>> git pull
>> git gc
>>
>> git checkout master
>>
>> make clean
>> make
>> make autoloads
>> make doc
>> make info
>>
>> # make install
> 
> Instead of the above quote you can simply use
> 
> make update
> 
> (And you can clone from git://orgmode.org/org-mode.git
> it will be faster and more recent. repo.or.cz is behind
> by one hour.) 
> 
>> Is this OK, or should I change something in the script? Or switch to ELPA (emacs 24.2.1)?
> 
> Things look okay.  My suggestions are just to spare some lines.
> 
> Best,
> 
Hi!

I tried "make update" and ended up here:

Debugger entered--Lisp error: (error "Required feature `org-version' was
not provided")
  require(org-version
"c:/Users/rainer/AppData/Roaming/.emacs.d/org/lisp/org-version.el" noerror)
  (if (require (quote org-version) org-version\.el (quote noerror))
(quote (progn (autoload (quote org-release) "org-version.el") (autoload
(quote org-git-version) "org-version.el"))) (if (require (quote
org-fixup) org-fixup\.el (quote noerror)) (quote (org-fixup)) (warn
"Could not define org version correctly.  Check installation!") (quote
(progn (defun org-release nil "N/A") (defun org-git-version nil "N/A
!!check installation!!")))))
  (let* ((org-dir (org-find-library-dir "org")) (org-version\.el (concat
org-dir "org-version.el")) (org-fixup\.el (concat org-dir
"../mk/org-fixup.el"))) (if (require (quote org-version) org-version\.el
(quote noerror)) (quote (progn (autoload (quote org-release)
"org-version.el") (autoload (quote org-git-version) "org-version.el")))
(if (require (quote org-fixup) org-fixup\.el (quote noerror)) (quote
(org-fixup)) (warn "Could not define org version correctly.  Check
installation!") (quote (progn (defun org-release nil "N/A") (defun
org-git-version nil "N/A !!check installation!!"))))))
  (lambda nil "Try very hard to provide sensible version strings." (let*
((org-dir (org-find-library-dir "org")) (org-version\.el (concat org-dir
"org-version.el")) (org-fixup\.el (concat org-dir
"../mk/org-fixup.el"))) (if (require (quote org-version) org-version\.el
(quote noerror)) (quote (progn (autoload (quote org-release)
"org-version.el") (autoload (quote org-git-version) "org-version.el")))
(if (require (quote org-fixup) org-fixup\.el (quote noerror)) (quote
(org-fixup)) (warn "Could not define org version correctly.  Check
installation!") (quote (progn (defun org-release nil "N/A") (defun
org-git-version nil "N/A !!check installation!!")))))))()
  (org-check-version)
  eval-buffer(#<buffer  *load*<2>> nil
"c:/Users/rainer/AppData/Roaming/.emacs.d/org/lisp/org.el" nil t)  ;
Reading at buffer position 9046

load-with-code-conversion("c:/Users/rainer/AppData/Roaming/.emacs.d/org/lisp/org.el"
"c:/Users/rainer/AppData/Roaming/.emacs.d/org/lisp/org.el" nil t)
  require(org)
  byte-code("\300\301!\210\300\302!\207" [require org find-func] 2)
  require(org-exp-blocks)
  eval-buffer(#<buffer  *load*> nil
"c:/Users/rainer/AppData/Roaming/.emacs" nil t)  ; Reading at buffer
position 6546
  load-with-code-conversion("c:/Users/rainer/AppData/Roaming/.emacs"
"c:/Users/rainer/AppData/Roaming/.emacs" t t)
  load("~/.emacs" t t)
  #[0 "\b\205\262


What is wrong in my setup?

Rainer

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Rainer M Krug <r.m.krug@gmail.com> writes:

> I guess you mean instead of the make ... commands - right? The git
> ... have to stay I assume?

Nope... `make update' will do everything for you.

Try `make helpall' to get more info.

> now I can sleep a little better,

:)

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Bastien]

Rainer Stengele <rainer.stengele@online.de> writes:

> What is wrong in my setup?

run

make autoloads 

at least once before 

make update

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Rainer Stengele]

Am 02.10.2012 17:20, schrieb Bastien:
> Rainer Stengele <rainer.stengele@online.de> writes:
> 
>> What is wrong in my setup?
> 
> run
> 
> make autoloads 
> 
> at least once before 
> 
> make update
> 
sorry but no.

Still complaining about org-version ..

Rainer

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Bastien]

Rainer Stengele <rainer.stengele@online.de> writes:

> Still complaining about org-version ..

Dong!  Fixed.  Please pull again.

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[johnlist]

On 02.10.2012 11:28, Rainer Stengele wrote:
>> run
>>
>> make autoloads
>>
>> at least once before
>>
>> make update
>>
> sorry but no.
>
> Still complaining about org-version ..
>
> Rainer

fwiw, I updated via git this morning and entered the same problem with 
the same error message. I'm swamped and didn't have time to debug 
further (though I did check list-load-path-shadows and didn't see a 
problem there).

I reverted to current stable version (tar.gz) and this loads fine.

emacs 24.2.1
Org-mode version 7.9.2 (7.9.2-dist @ /home/me/elisp/org-mode/lisp/)

-- 
John

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Achim Gratz]

johnlist@johnrakestraw.com writes:
> fwiw, I updated via git this morning and entered the same problem with
> the same error message. I'm swamped and didn't have time to debug
> further (though I did check list-load-path-shadows and didn't see a
> problem there).

That's what Git is for:

git reflog -5 HEAD

will show you where your branch head was for the last five operations
that moved it.  If you want to go back 2 steps you'd say

git checkout HEAD@{2}

for instance.  No need to deal with pesky tar files.


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

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

Re: From latest maint/master, no need to (require 'org-install)

[Charles]

Bastien,

Early this morning, i.e. before your message, I pulled from git, ran 
make update2 and at the end of compiling org-loaddefs.el was mentioned 
as  not loaded. This in cygwin.

This evening I followed your instructions (I think!)  and ran 
~/elisp/org-mode  && make autoloads

Then make update2; at the end of this it complained about org-version.el

I ran make autoloads again and then make update2 - no complaints this time.

Was this to be expected?

Windows 7 HP 64
Emacs 24.2.1
cygwin 1.7.16
org version 7.9.2 (release_7.9.2-383-g09d6bc) (which I obtained by M-x 
org-version)

Charlie Millar

On 10/2/2012 9:15 AM, Bastien wrote:
> Hi all,
>
> there is no need to (require 'org-install) anymore from the maint
> and master branches.
>
> When using the Org distribution that comes with Emacs, Emacs will add
> Org's autoloaded core functions to [emacs]/lisp/loaddefs.el and the rest
> of the autoloaded functions to [emacs]/lisp/org/org-loaddefs.el.  This
> is an improvement over the present situation, where *all* autoloaded
> functions where added to Emacs' loaddefs.el -- too much.  This is not
> yet in Emacs trunk but will be in Emacs 24.3.
>
> When getting Org as a .tar.gz/.zip archive file, you'll have a file
> org-loaddefs.el in the lisp/ directory -- this file is now loaded when
> org.el is loaded.
>
> When getting Org from ELPA (either "org" or "org-plus-contrib"),
> org-loaddefs.el will also be in the load-path.
>
> When getting Org from git, you *HAVE* to created org-loaddefs.el with
> `make autoloads' (which is also run by a simple `make'), otherwise
> some needed functions will not be autoloaded.
>
> You can check whether org-loaddefs.el has been correctly been loaded
> with M-x org-version RET.
>
> Thanks,
>

Re: From latest maint/master, no need to (require 'org-install)

[Torsten Wagner]

On 2 October 2012 22:49, Bastien <bzg@altern.org> wrote:
> Hi Torsten,
>
> Torsten Wagner <torsten.wagner@gmail.com> writes:
>
>> Anyhow I just realized that ELPA contains
>> "org" and "org-plus-contrib"
>> I stupidly overlooked that and always read
>> "org" or "org-contrib"
>>
>> Well, thats the way many Linux distros does that kind of things. Sure
>> enough org-contrib would need org as a requirement.
>> Maybe thats not possible in ELPA yet?!
>
> org-plus-contrib has this lenghthy name precisely to make sure that
> people know this is Org + Contributed files, not just contributed files.

Well I said  "I stupidly overlooked that", did I ;)

Greetings

Torsten

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi all again,

Bastien <bzg@altern.org> writes:

> there is no need to (require 'org-install) anymore from the maint
> and master branches.

... and you should actually remove (require 'org-install) from your
configuration, since this file is not automatically created anymore.

Thanks,

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi Charles,

Charles <millarc@verizon.net> writes:

> I ran make autoloads again and then make update2 - no complaints this time.
>
> Was this to be expected?

There might be some hicups in the transition from the old org-install
way to the new org-loaddefs way, but if things are fine then it's fine.

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[John Hendy]

On Wed, Oct 3, 2012 at 4:26 AM, Bastien <bzg@altern.org> wrote:
> Hi Charles,
>
> Charles <millarc@verizon.net> writes:
>
>> I ran make autoloads again and then make update2 - no complaints this time.
>>
>> Was this to be expected?
>
> There might be some hicups in the transition from the old org-install
> way to the new org-loaddefs way, but if things are fine then it's fine.

Or does this have to do with Emacs version. In your original
announcement, you said:

,---
| This is not yet in Emacs trunk but will be in Emacs 24.3.
`---

I didn't follow if that was about removing (require 'org-install) or
only about something having to do with autoloading. Charles mentioned
he is using Emacs 24.2.1, so I just thought to mention this. For
finality... will *all* versions of Emacs now allow for removing
(require 'org-install) with a fresh git pull of orgmode, or does one
need to be using Emacs 24.3?


Thanks,
John

>
> --
>  Bastien
>

Re: From latest maint/master, no need to (require 'org-install)

[Achim Gratz]

John Hendy writes:
> will *all* versions of Emacs now allow for removing
> (require 'org-install) with a fresh git pull of orgmode, or does one
> need to be using Emacs 24.3?

Yes, all of them.  Emacs 24.3 is just the first to be released with a
change that triggered this.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: From latest maint/master, no need to (require 'org-install)

[Eric Fraga]

Bastien <bzg@altern.org> writes:

> Hi all again,
>
> Bastien <bzg@altern.org> writes:
>
>> there is no need to (require 'org-install) anymore from the maint
>> and master branches.
>
> ... and you should actually remove (require 'org-install) from your
> configuration, since this file is not automatically created anymore.
>
> Thanks,

Okay but with what should I replace this, if anything?

Specifically, I currently have (in my organically grown customisation
file ;-):

--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "~/git/org-mode")
(add-to-list 'load-path "~/git/org-mode/lisp")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
(require 'org-install)
(require 'org-e-latex)
(require 'org-e-odt)
(require 'org-latex)
(require 'org-mime)
(require 'ob-jacaranda)
(require 'ob-python)
(require 'ob-R)
(require 'ob-sh)
(require 'org-crypt) (org-crypt-use-before-save-magic)
(require 'org-inlinetask)		;binding C-c C-x t
(require 'org-protocol)
(require 'org-wc) 
;; customisations follow
--8<---------------cut here---------------end--------------->8---

What should I or could I remove from this?

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-350-g934208

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Rainer Stengele]

Am 02.10.2012 17:39, schrieb Bastien:
> Rainer Stengele <rainer.stengele@online.de> writes:
> 
>> Still complaining about org-version ..
> 
> Dong!  Fixed.  Please pull again.
> 
Thanks Bastien,

works perfectly now.
Actually I am confused - I did not quite understand - why do I no more
require 'org-install and also not 'org. Can you point me to some docs
about this?

Rainer

Re: From latest maint/master, no need to (require 'org-install): Lisp error

[Achim Gratz]

Rainer Stengele writes:
> Actually I am confused - I did not quite understand - why do I no more
> require 'org-install and also not 'org. Can you point me to some docs
> about this?

If you need anything at all, you now need to use (require 'org),
regardless of whether it's the Org version that comes with Emacs (which
has been using this in favor of org-install.el for some time) or from
Git.  However, you don't need any (require 'org) whatsoever if you don't
happen to use customizations in your initialization file that require
Org to be loaded already, since simply using any of the autoloaded
functions will now arrange for the necesary files being loaded.


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

Re: From latest maint/master, no need to (require 'org-install)

[Thomas S. Dye]

Eric Fraga <e.fraga@ucl.ac.uk> writes:

> Bastien <bzg@altern.org> writes:
>
>> Hi all again,
>>
>> Bastien <bzg@altern.org> writes:
>>
>>> there is no need to (require 'org-install) anymore from the maint
>>> and master branches.
>>
>> ... and you should actually remove (require 'org-install) from your
>> configuration, since this file is not automatically created anymore.
>>
>> Thanks,
>
> Okay but with what should I replace this, if anything?
>
> Specifically, I currently have (in my organically grown customisation
> file ;-):
>
> (add-to-list 'load-path "~/git/org-mode")
> (add-to-list 'load-path "~/git/org-mode/lisp")
> (add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
> (require 'org-install)
> (require 'org-e-latex)
> (require 'org-e-odt)
> (require 'org-latex)
> (require 'org-mime)
> (require 'ob-jacaranda)
> (require 'ob-python)
> (require 'ob-R)
> (require 'ob-sh)
> (require 'org-crypt) (org-crypt-use-before-save-magic)
> (require 'org-inlinetask)		;binding C-c C-x t
> (require 'org-protocol)
> (require 'org-wc) 
> ;; customisations follow
>
> What should I or could I remove from this?
>
> Thanks,
> eric

Hi Eric,

ob-jacaranda?  Any chance this might swell the list of babel supported
languages? 

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

Re: From latest maint/master, no need to (require 'org-install)

[Rainer M Krug]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/10/12 11:25, Bastien wrote:
> Hi all again,
> 
> Bastien <bzg@altern.org> writes:
> 
>> there is no need to (require 'org-install) anymore from the maint and master branches.
> 
> ... and you should actually remove (require 'org-install) from your configuration, since this
> file is not automatically created anymore.

OK - now I am getting slightly confused again.

Could you please give some example configuration code? For example, in
my case, I am using org mode from git, I am using the script posted
above in the thread to update org-mode git:

#!/bin/sh
cd ~/.emacs.d/org-mode-git/org-mode

git checkout master
git fetch --tags origin

# git clone git://repo.or.cz/org-mode.git
git pull
git gc

git checkout master

make clean
make
make autoloads
make doc
make info

# make install



in my .emacs.d/init.el I have:

;; Load up Org Mode and Org Babel for elisp embedded in Org Mode files
(add-to-list 'load-path "~/.emacs.d/org-mode/lisp")
(add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp")

;; load up Org-mode and Org-babel
(require 'org-install)

;; load up the main file
(org-babel-load-file "~/.emacs.d/emacs.org")

And i my emacs.org, I have at the beginning:

* ELPA settings
#+begin_src emacs-lisp
  ;; set package-load-list -- default is all
  (setq package-archives '(
                           ("ELPA" . "http://tromey.com/elpa/")
                           ("gnu" . "http://elpa.gnu.org/packages/")
                           ("suco" . "http://joseito.republika.pl/sunrise-commander/")
                           ("marmalade" . "http://marmalade-repo.org/packages/")
                           )
        )
(package-initialize)
#+end_src

Later on, I have some customizations.


So do I have to change something?
What should I do with the (require 'org-install)?

Rainer

> 
> Thanks,
> 

From: Rainer@krugs.de (Rainer M. Krug)
Date: Fri, 05 Oct 2012 09:57:30 +0200
Message-ID: <87txu9z6z9.fsf@krugs.de>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBuk0UACgkQoYgNqgF2egrCrQCdEAZA42TLb4Xs48fIkairYgxO
IEYAnA74GEV64O3TkVIwsCWP0UuVKpZa
=etPk
-----END PGP SIGNATURE-----

Re: From latest maint/master, no need to (require 'org-install)

[Sebastien Vauban]

Hi Eric,

Eric Fraga wrote:
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>>> there is no need to (require 'org-install) anymore from the maint and
>>> master branches.
>>
>> ... and you should actually remove (require 'org-install) from your
>> configuration, since this file is not automatically created anymore.
>
> Okay but with what should I replace this, if anything?
>
> Specifically, I currently have (in my organically grown customisation file
> ;-):
>
> (add-to-list 'load-path "~/git/org-mode")

Why that one?

> (add-to-list 'load-path "~/git/org-mode/lisp")
> (add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
> (require 'org-install)
> (require 'org-e-latex)
> (require 'org-e-odt)
> (require 'org-latex)
> (require 'org-mime)
> (require 'ob-jacaranda)
> (require 'ob-python)
> (require 'ob-R)
> (require 'ob-sh)
> (require 'org-crypt) (org-crypt-use-before-save-magic)
> (require 'org-inlinetask)		;binding C-c C-x t
> (require 'org-protocol)
> (require 'org-wc) 
> ;; customisations follow
>
> What should I or could I remove from this?

What I do is:

#+begin_src emacs-lisp
  (when (locate-library "org-install")
    (require 'org-install))
#+end_src

That way, if it's still present (and maybe necessary[1]), it will be loaded.

If not, it simply has no effect.

Best regards,
  Seb

[1] On old Emacs/Org versions, for people using my .emacs configuration file.

-- 
Sebastien Vauban

Re: From latest maint/master, no need to (require 'org-install)

[Eric Fraga]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> Hi Eric,
>
> Eric Fraga wrote:
>> (add-to-list 'load-path "~/git/org-mode")
>
> Why that one?

Ahh, that's a bit of historical garbage.  There was a point a while back
where org-install seemed to have lisp/org-xxx paths and the easiest fix
was to add the root to the list of paths.  The problem was fixed fairly
quickly but I forgot to remove my temporary fix.

>> What should I or could I remove from this?
>
> What I do is:
>
> #+begin_src emacs-lisp
>   (when (locate-library "org-install")
>     (require 'org-install))
> #+end_src

Actually, I now have

#+begin_src emacs-lisp
(add-to-list 'load-path "~/git/org-mode/lisp")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
(require 'org)
#+end_src

with a number of other =require= calls for specific ob- and org-e-
packages.  This seems to work just fine.

My question now is whether I should replace the =(require 'org)= by
=(require 'org-loaddefs)= which seems to be the way that Emacs is moving
for packages?

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca

Re: From latest maint/master, no need to (require 'org-install)

[Nick Dokos]

Eric Fraga <e.fraga@ucl.ac.uk> wrote:

> Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> 
> > Hi Eric,
> >
> > Eric Fraga wrote:
> >> (add-to-list 'load-path "~/git/org-mode")
> >
> > Why that one?
> 
> Ahh, that's a bit of historical garbage.  There was a point a while back
> where org-install seemed to have lisp/org-xxx paths and the easiest fix
> was to add the root to the list of paths.  The problem was fixed fairly
> quickly but I forgot to remove my temporary fix.
> 
> >> What should I or could I remove from this?
> >
> > What I do is:
> >
> > #+begin_src emacs-lisp
> >   (when (locate-library "org-install")
> >     (require 'org-install))
> > #+end_src
> 
> Actually, I now have
> 
> #+begin_src emacs-lisp
> (add-to-list 'load-path "~/git/org-mode/lisp")
> (add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
> (require 'org)
> #+end_src
> 
> with a number of other =require= calls for specific ob- and org-e-
> packages.  This seems to work just fine.
> 

Note however that this way, the contrib directory will be found before
the main lisp directory and that may cause occasional problems. This was
recently discussed in this thread:

     http://thread.gmane.org/gmane.emacs.orgmode/60929/focus=61131

Nick

> My question now is whether I should replace the =(require 'org)= by
> =(require 'org-loaddefs)= which seems to be the way that Emacs is moving
> for packages?
> 
> Thanks,
> eric
> 
> -- 
> : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
> : in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca
> 
>

Re: From latest maint/master, no need to (require 'org-install)

[Achim Gratz]

Eric Fraga writes:
> My question now is whether I should replace the =(require 'org)= by
> =(require 'org-loaddefs)= which seems to be the way that Emacs is moving
> for packages?

No.  The definitions in org-loaddefs are require'd from org internally,
you should never reference to it directly.  What Emacs and package
managers are doing is not exactly the same thing, but again they should
setup things in a way that only =(require 'org)= is needed.


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

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: From latest maint/master, no need to (require 'org-install)

[Eric S Fraga]

Achim Gratz <Stromeko@nexgo.de> writes:

> Eric Fraga writes:
>> My question now is whether I should replace the =(require 'org)= by
>> =(require 'org-loaddefs)= which seems to be the way that Emacs is moving
>> for packages?
>
> No.  The definitions in org-loaddefs are require'd from org internally,
> you should never reference to it directly.  What Emacs and package
> managers are doing is not exactly the same thing, but again they should
> setup things in a way that only =(require 'org)= is needed.
>
>
> Regards,
> Achim.

Thanks Achim for the clarification!

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-402-ge5e49e

Re: From latest maint/master, no need to (require 'org-install)

[Sebastien Vauban]

Hi Achim,

Achim Gratz wrote:
> Eric Fraga writes:
>> My question now is whether I should replace the =(require 'org)= by
>> =(require 'org-loaddefs)= which seems to be the way that Emacs is moving
>> for packages?
>
> No. The definitions in org-loaddefs are require'd from org internally, you
> should never reference to it directly. What Emacs and package managers are
> doing is not exactly the same thing, but again they should setup things in a
> way that only =(require 'org)= is needed.

You mean we must require Org in our .emacs file (instead of just loading the
autoload definitions)?

IIUC, (in my case at least) that could seriously impact the Emacs startup
time?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: From latest maint/master, no need to (require 'org-install)

[Sebastien Vauban]

Hi Achim,

"Sebastien Vauban" wrote:
> Achim Gratz wrote:
>> only =(require 'org)= is needed.
>
> You mean we must require Org in our .emacs file (instead of just loading the
> autoload definitions)?
>
> IIUC, (in my case at least) that could seriously impact the Emacs startup
> time?

Confirmed with Org-mode version 7.9.2 (release_7.9.2-425-g8ec79b @
d:/home/sva/src/org-mode/lisp/).

Starting Emacs now requires ~18 seconds vs 2 seconds before.

Some culprits are:

- loading some of my 45 Org agenda files (not all, though -- maybe, the one in
  which I'm currently clocking and the ones I clocked in before, from the
  clock history?)

- loading lots of extra packages which I don't necessarily need when I just
  fire up Emacs for doing non-Org related work, such as gnus-sum (hence, all
  of Gnus, along with MIME utils, URL stuff, etc.)

- loading all my Org config (Babel, LOB, exporters, etc.), which is in an
  (eval-after-load "org" ...).

Best regards,
  Seb

-- 
Sebastien Vauban

Re: From latest maint/master, no need to (require 'org-install)

[Achim Gratz]

Sebastien Vauban writes:
> Starting Emacs now requires ~18 seconds vs 2 seconds before.

That is one of the consequences of how org.el is currently structured.
If you know exactly what you're doing when in your init file, you can at
the moment still do a

(require 'org-loaddefs)

where you formerly did require org-install.  Of course this will then
not work if you fall back to the built-in Org version of an old Emacs,
so maybe you'd want

(require 'org-loaddefs nil 'noerror)

I'm not sure how Bastien wants this to work going forward, but by the
way it's been announced and implemented the need to do this should go
away.


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

Re: From latest maint/master, no need to (require 'org-install)

[Michael Brand]

Hi Achim

On Tue, Oct 9, 2012 at 7:47 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> I'm not sure how Bastien wants this to work going forward, but by the
> way it's been announced and implemented the need to do this should go
> away.

Would it be possible/reasonable to have org-version available before
(require 'org)? I would like to put the Org version into the Message
Buffer at Emacs startup without the need of loading the entire Org
yet.

Michael

Re: From latest maint/master, no need to (require 'org-install)

[Sebastien Vauban]

Hi Achim,

Achim Gratz wrote:
> Sebastien Vauban writes:
>> Starting Emacs now requires ~18 seconds vs 2 seconds before.
>
> That is one of the consequences of how org.el is currently structured.
> If you know exactly what you're doing when in your init file, you can at
> the moment still do a
>
> (require 'org-loaddefs)
>
> where you formerly did require org-install.

Good to know...

> Of course this will then not work if you fall back to the built-in Org
> version of an old Emacs, so maybe you'd want
>
> (require 'org-loaddefs nil 'noerror)

I guess the risk of falling to the built-in Org version is no bigger than it
was with org-install?

Anyway, I always protect all require's of stuff which can be absent from some
distribution (as my .emacs is used by colleagues).

> I'm not sure how Bastien wants this to work going forward, but by the
> way it's been announced and implemented the need to do this should go
> away.

OK. We'll see with him as soon as he comes back online.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Hi Michael,

Michael Brand <michael.ch.brand@gmail.com> writes:

> Would it be possible/reasonable to have org-version available before
> (require 'org)? I would like to put the Org version into the Message
> Buffer at Emacs startup without the need of loading the entire Org
> yet.

Yes, you can call (org-version) before any (require 'org).
This will call the org-version that is autoloaded in Emacs.

-- 
 Bastien

Re: From latest maint/master, no need to (require 'org-install)

[Bastien]

Achim Gratz <Stromeko@nexgo.de> writes:

>> Starting Emacs now requires ~18 seconds vs 2 seconds before.
>
> That is one of the consequences of how org.el is currently structured.

The move to using org-loaddefs.el was to optimize things within Emacs.

Before org-loaddefs.el, all Org's autoloads were added to loaddefs.el.
This had the effect of preloading too many Org's functions in a bare
"emacs -Q".

After org-loaddefs.el, only the core Org functions are added to Emacs'
loaddefs.el.

The time you spare by not preloading all autoloads in loaddefs.el is
lost when you require org for the first time -- either in your config
or by simply finding a new .org file.

But on the overall, I think it's cleaner that way.

The next step to optimize things a bit is to have less autoloads
in org-autoloads.el... any suggestion is welcome in this area!

-- 
 Bastien

[bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Hello,

I am trying to use org-tree-slide for an interactive session I have to
facilitate soon.  This works quite well, in a geeky kind of way ;-)

However, I do want to display a couple of equations and using latex
fragments is the most appealing mechanism.  When I try to use
org-preview-latex-fragment, the latex image is
generated.  Unfortunately, as I use a black background on my display, I
cannot see the fragment as it is being generated with black text on a
transparent background by default.  Note, I am using dvipng for the
image conversion.

I can customise org-format-latex-options to fix this, or so I
thought.  No matter what I do, the resulting latex fragment has black
text.  The problem appears to be that the -fg option to dvipng does not
work so it doesn't matter how I customise org-format-latex-options.

Can anybody suggest a workaround (without changing the actual latex
itself)?  I can customise the above variable to set the background for
latex images to white, which at least allows the equations to be seen,
but this is a mildly ugly solution.  :( And ruins any geek street cred I
might have had ;-)

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-874-gf11acc

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Hello,
> 
> I am trying to use org-tree-slide for an interactive session I have to
> facilitate soon.  This works quite well, in a geeky kind of way ;-)
> 
> However, I do want to display a couple of equations and using latex
> fragments is the most appealing mechanism.  When I try to use
> org-preview-latex-fragment, the latex image is
> generated.  Unfortunately, as I use a black background on my display, I
> cannot see the fragment as it is being generated with black text on a
> transparent background by default.  Note, I am using dvipng for the
> image conversion.
> 
> I can customise org-format-latex-options to fix this, or so I
> thought.  No matter what I do, the resulting latex fragment has black
> text.  The problem appears to be that the -fg option to dvipng does not
> work so it doesn't matter how I customise org-format-latex-options.
> 

I think that's true. Using dvipng from the command line, I can change
the background but not the foreground.

> Can anybody suggest a workaround (without changing the actual latex
> itself)?  I can customise the above variable to set the background for
> latex images to white, which at least allows the equations to be seen,
> but this is a mildly ugly solution.  :( And ruins any geek street cred I
> might have had ;-)
> 

Use a light background emacs for the presentation. And don't tell
anybody that you switched. Street creds intact, you can switch back to
the cool dark background afterwards. If you get caught, you can argue
that you switched for projection purposes (assuming that you are going
to use a projector): studies show that dark letters on a light
background are easier to see from a distance (citation: J.WhlClthFab,
Vol. 3.14159, p. 2.7182818, Apr. 1, 1999)

Nick

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Hello,
> 
> I am trying to use org-tree-slide for an interactive session I have to
> facilitate soon.  This works quite well, in a geeky kind of way ;-)
> 
> However, I do want to display a couple of equations and using latex
> fragments is the most appealing mechanism.  When I try to use
> org-preview-latex-fragment, the latex image is
> generated.  Unfortunately, as I use a black background on my display, I
> cannot see the fragment as it is being generated with black text on a
> transparent background by default.  Note, I am using dvipng for the
> image conversion.
> 

I tried the imagemagick setting, set the options variable to black background
and red foreground - lo and behold, that's what I get in the preview.

Nick

> I can customise org-format-latex-options to fix this, or so I
> thought.  No matter what I do, the resulting latex fragment has black
> text.  The problem appears to be that the -fg option to dvipng does not
> work so it doesn't matter how I customise org-format-latex-options.
> 
> Can anybody suggest a workaround (without changing the actual latex
> itself)?  I can customise the above variable to set the background for
> latex images to white, which at least allows the equations to be seen,
> but this is a mildly ugly solution.  :( And ruins any geek street cred I
> might have had ;-)
> 
> Thanks,
> eric
> 
> -- 
> : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
> : in Emacs 24.3.50.1 and Org release_7.9.3d-874-gf11acc
> 
> 

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Nick Dokos <nicholas.dokos@hp.com> writes:

[...]

> Use a light background emacs for the presentation. And don't tell
> anybody that you switched. Street creds intact, you can switch back to
> the cool dark background afterwards. If you get caught, you can argue
> that you switched for projection purposes (assuming that you are going
> to use a projector): studies show that dark letters on a light
> background are easier to see from a distance (citation: J.WhlClthFab,
> Vol. 3.14159, p. 2.7182818, Apr. 1, 1999)

Love the citation... may try to pass this by some reviewer at some point.
;-)

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-874-gf11acc

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>> fragments is the most appealing mechanism.  When I try to use
>> org-preview-latex-fragment, the latex image is
>> generated.  Unfortunately, as I use a black background on my display, I
>> cannot see the fragment as it is being generated with black text on a
>> transparent background by default.  Note, I am using dvipng for the
>> image conversion.
>> 
>
> I tried the imagemagick setting, set the options variable to black background
> and red foreground - lo and behold, that's what I get in the preview.

Thanks for the suggestion.  Should have tried that! <blush>

However, it's not working for me; very strange.  I have tried switching
from dvipng to imagemagick but I get the same result (having cleaned out
the ltxpng directory, restarted emacs, tried both #+OPTIONS: and direct
variable setting, ...).  Mind you, it's very late at night so I'm
probably doing something stupid...  I'm going to bed; I'll check again
in the morning and will follow this up.

Thanks again,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-874-gf11acc

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Nick Dokos <nicholas.dokos@hp.com> writes:

> I tried the imagemagick setting, set the options variable to black background
> and red foreground - lo and behold, that's what I get in the preview.

I was correct in my conclusion last night that I needed to go to
bed...  I was making a silly mistake (and I won't go into details ;-).

This does indeed work!  Thanks again.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-874-gf11acc

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Myles English]

Hi Eric,

Eric S Fraga writes:

> Nick Dokos <nicholas.dokos@hp.com> writes:
>
>> I tried the imagemagick setting, set the options variable to black background
>> and red foreground - lo and behold, that's what I get in the preview.
>
> I was correct in my conclusion last night that I needed to go to
> bed...  I was making a silly mistake (and I won't go into details ;-).
>
> This does indeed work!  Thanks again.

Please could you clarify a couple of things for me?

From your investigations can you say if there is a bug in the orgmode
use of dvipng, or has dvipng changed so that the expected behaviour is
no longer supported?  I too use a dark display (emacs theme
zenburn-emacs), get the black fragments in normal latex blocks in org
files (i.e. not beamer), and org-format-latex-options has no visible
effect, how can I have white formulae again?

Thanks,

Myles

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Myles English <mylesenglish@gmail.com> writes:

> Hi Eric,
>
> Eric S Fraga writes:
>
>> Nick Dokos <nicholas.dokos@hp.com> writes:
>>
>>> I tried the imagemagick setting, set the options variable to black background
>>> and red foreground - lo and behold, that's what I get in the preview.
>>
>> I was correct in my conclusion last night that I needed to go to
>> bed...  I was making a silly mistake (and I won't go into details ;-).
>>
>> This does indeed work!  Thanks again.
>
> Please could you clarify a couple of things for me?
>
> From your investigations can you say if there is a bug in the orgmode
> use of dvipng, or has dvipng changed so that the expected behaviour is
> no longer supported?  I too use a dark display (emacs theme
> zenburn-emacs), get the black fragments in normal latex blocks in org
> files (i.e. not beamer), and org-format-latex-options has no visible
> effect, how can I have white formulae again?
>
> Thanks,
>
> Myles
>

Hi Myles,

Thanks for prompting me on this.  I've explored the code a bit
further.  The two approaches, i.e. dvipng vs imagemagick, differ not
only in the tool used to create the image and the source of the image
(dvi versus pdf) but also in the latex code actually created to generate
the image in the first place.

The dvipng route does not specify any colours in the latex and relies on
dvipng to change explicitly the background and foreground colours.  The
imagemagick route, however, creates a latex file that has the colour
specifications directly and the conversion does change any colours.

So, it could be that dvipng has changed and no longer changes the
colours correctly or it may be that latex has changed in how the dvi
file specifies colours?

However, I have verified that dvipng will work just fine, without asking
for colour changes, if the dvi is created using the latex code used for
the imagemagick case.  This leads me to suggest that both cases (dvipng
and imagemagick) use the same latex code and, in fact, it may be
possible to fold both functions org-create-formula-image-with-dvipng and
org-create-formula-image-with-imagemagick into one...  but maybe this
has other repercussions.  One such repercussion could be the use of
transparent colour specifications: dvipng would appear to support this
but imagemagick might not (as org appears to use white when transparent
is specified for a background colour, if I understood the code.

eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-891-gf52600

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Myles English]

Eric S Fraga writes:

> Myles English <mylesenglish@gmail.com> writes:

>> Please could you clarify a couple of things for me?
>>
>> From your investigations can you say if there is a bug in the orgmode
>> use of dvipng, or has dvipng changed so that the expected behaviour is
>> no longer supported?  I too use a dark display (emacs theme
>> zenburn-emacs), get the black fragments in normal latex blocks in org
>> files (i.e. not beamer), and org-format-latex-options has no visible
>> effect, how can I have white formulae again?

> Thanks for prompting me on this.  I've explored the code a bit
> further.  The two approaches, i.e. dvipng vs imagemagick, differ not
> only in the tool used to create the image and the source of the image
> (dvi versus pdf) but also in the latex code actually created to generate
> the image in the first place.
>
> The dvipng route does not specify any colours in the latex and relies on
> dvipng to change explicitly the background and foreground colours.  The
> imagemagick route, however, creates a latex file that has the colour
> specifications directly and the conversion does change any colours.
>
> So, it could be that dvipng has changed and no longer changes the
> colours correctly or it may be that latex has changed in how the dvi
> file specifies colours?
>
> However, I have verified that dvipng will work just fine, without asking
> for colour changes, if the dvi is created using the latex code used for
> the imagemagick case.  This leads me to suggest that both cases (dvipng
> and imagemagick) use the same latex code and, in fact, it may be
> possible to fold both functions org-create-formula-image-with-dvipng and
> org-create-formula-image-with-imagemagick into one...  but maybe this
> has other repercussions.  One such repercussion could be the use of
> transparent colour specifications: dvipng would appear to support this
> but imagemagick might not (as org appears to use white when transparent
> is specified for a background colour, if I understood the code.

Thanks for looking into it.  Until a conclusion is reached with dvipng
this gets things back to normal for me:

(setq org-latex-create-formula-image-program 'imagemagick)

Myles

How to improve Org startup time?

[Sebastien Vauban]

Hello,

Please find here an enriched log of the packages which are loaded for Org, and
the time it takes.

--8<---------------cut here---------------start------------->8---
[2013-01-29 21:20:18] (info) +-> Requiring `appt'...
[2013-01-29 21:20:18] (info)   +-> Requiring `diary-lib'...
[2013-01-29 21:20:18] (info)     +-> Requiring `calendar'...
[2013-01-29 21:20:18] (info) Loading c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/cal-loaddefs.el...
[2013-01-29 21:20:18] (info)       +-> Requiring `cal-menu'...
[2013-01-29 21:20:18] (info)         +-> Requiring `calendar'... already loaded
[2013-01-29 21:20:18] (info)       +-> Requiring `cal-menu'... c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/cal-menu.elc (loaded in 0.08 s)
[2013-01-29 21:20:18] (info)     +-> Requiring `calendar'... c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/calendar.elc (loaded in 0.33 s)
[2013-01-29 21:20:18] (info) Loading c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/diary-loaddefs.el...
[2013-01-29 21:20:19] (info)   +-> Requiring `diary-lib'... c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/diary-lib.elc (loaded in 0.55 s)
[2013-01-29 21:20:19] (info) +-> Requiring `appt'... c:/Program Files (x86)/emacs-24.2.91/lisp/calendar/appt.elc (loaded in 0.64 s)
[2013-01-29 21:20:19] (info) Enable appointment reminders...
[2013-01-29 21:20:19] Appointment reminders enabled (no diary file found)
[2013-01-29 21:20:19] (info) Enable appointment reminders... Done
[2013-01-29 21:20:19] (info) +-> Requiring `org-clock'...
[2013-01-29 21:20:19] (info)   +-> Requiring `org-exp'...
[2013-01-29 21:20:19] (info)     +-> Requiring `org'...
[2013-01-29 21:20:19] (info)       +-> Requiring `cl'... already loaded
[2013-01-29 21:20:19] (info)       +-> Requiring `gnus-sum'...
[2013-01-29 21:20:19] (info)         +-> Requiring `gnus'...
[2013-01-29 21:20:19] (info)           +-> Requiring `wid-edit'... c:/Program Files (x86)/emacs-24.2.91/lisp/wid-edit.elc (loaded in 0.08 s)
[2013-01-29 21:20:19] (info)           +-> Requiring `mm-util'...
[2013-01-29 21:20:19] (info)             +-> Requiring `mail-prsvr'... d:/home/sva/Public/Repositories/gnus/lisp/mail-prsvr.elc (loaded in 0.02 s)
[2013-01-29 21:20:19] (info)             +-> Requiring `timer'... already loaded
[2013-01-29 21:20:19] (info)           +-> Requiring `mm-util'... d:/home/sva/Public/Repositories/gnus/lisp/mm-util.elc (loaded in 0.14 s)
[2013-01-29 21:20:19] (info)           +-> Requiring `nnheader'...
[2013-01-29 21:20:19] (info)             +-> Requiring `mail-utils'... c:/Program Files (x86)/emacs-24.2.91/lisp/mail/mail-utils.elc (loaded in 0.05 s)
[2013-01-29 21:20:19] (info)             +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:19] (info)             +-> Requiring `gnus-util'...
[2013-01-29 21:20:19] (info)               +-> Requiring `time-date'... already loaded
[2013-01-29 21:20:19] (info)             +-> Requiring `gnus-util'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-util.elc (loaded in 0.08 s)
[2013-01-29 21:20:19] (info)           +-> Requiring `nnheader'... d:/home/sva/Public/Repositories/gnus/lisp/nnheader.elc (loaded in 0.16 s)
[2013-01-29 21:20:19] (info)           +-> Requiring `gnus-compat'...
[2013-01-29 21:20:19] (info)             +-> Requiring `help-fns'... already loaded
[2013-01-29 21:20:19] (info)             +-> Requiring `url'...
[2013-01-29 21:20:19] (info)               +-> Requiring `mailcap'... d:/home/sva/Public/Repositories/gnus/lisp/mailcap.elc (loaded in 0.02 s)
[2013-01-29 21:20:19] (info)               +-> Requiring `url-vars'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-vars.elc (loaded in 0.05 s)
[2013-01-29 21:20:19] (info)               +-> Requiring `url-cookie'...
[2013-01-29 21:20:19] (info)                 +-> Requiring `url-util'...
[2013-01-29 21:20:19] (info)                   +-> Requiring `url-parse'...
[2013-01-29 21:20:19] (info)                     +-> Requiring `url-vars'... already loaded
[2013-01-29 21:20:19] (info)                     +-> Requiring `auth-source'...
[2013-01-29 21:20:19] (info)                       +-> Requiring `password-cache'...
[2013-01-29 21:20:20] (info)                       +-> Requiring `password-cache'... d:/home/sva/Public/Repositories/gnus/lisp/password-cache.elc (loaded in 0.03 s)
[2013-01-29 21:20:20] (info)                       +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:20] (info)                       +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:20] (info)                       +-> Requiring `eieio'...
[2013-01-29 21:20:20] (info)                         +-> Requiring `bytecomp'...
[2013-01-29 21:20:20] (info)                           +-> Requiring `backquote'... already loaded
[2013-01-29 21:20:20] (info)                           +-> Requiring `macroexp'... already loaded
[2013-01-29 21:20:20] (info)                           +-> Requiring `cconv'... c:/Program Files (x86)/emacs-24.2.91/lisp/emacs-lisp/cconv.elc (loaded in 0.05 s)
[2013-01-29 21:20:20] (info)                         +-> Requiring `bytecomp'... already loaded
[2013-01-29 21:20:20] (info)                         +-> Requiring `macroexp'... already loaded
[2013-01-29 21:20:20] (info)                         +-> Requiring `bytecomp'... already loaded [9 times]
[2013-01-29 21:20:20] (info)                       +-> Requiring `eieio'... c:/Program Files (x86)/emacs-24.2.91/lisp/emacs-lisp/eieio.elc (loaded in 0.45 s)
[2013-01-29 21:20:20] (info)                     +-> Requiring `auth-source'... d:/home/sva/Public/Repositories/gnus/lisp/auth-source.elc (loaded in 0.56 s)
[2013-01-29 21:20:20] (info)                   +-> Requiring `url-parse'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-parse.elc (loaded in 0.67 s)
[2013-01-29 21:20:20] (info)                   +-> Requiring `url-vars'... already loaded
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-util'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-util.elc (loaded in 0.73 s)
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-domsuf'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-domsuf.elc (loaded in 0.03 s)
[2013-01-29 21:20:20] (info)               +-> Requiring `url-cookie'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-cookie.elc (loaded in 0.83 s)
[2013-01-29 21:20:20] (info)               +-> Requiring `url-history'...
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:20] (info)               +-> Requiring `url-history'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-history.elc (loaded in 0.05 s)
[2013-01-29 21:20:20] (info)               +-> Requiring `url-expand'...
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-methods'...
[2013-01-29 21:20:20] (info)                   +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-methods'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-methods.elc (loaded in 0.03 s)
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-util'... already loaded
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:20] (info)               +-> Requiring `url-expand'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-expand.elc (loaded in 0.13 s)
[2013-01-29 21:20:20] (info)               +-> Requiring `url-privacy'...
[2013-01-29 21:20:20] (info)                 +-> Requiring `url-vars'... already loaded
[2013-01-29 21:20:20] (info)               +-> Requiring `url-privacy'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-privacy.elc (loaded in 0.05 s)
[2013-01-29 21:20:20] (info)               +-> Requiring `url-methods'... already loaded
[2013-01-29 21:20:21] (info)               +-> Requiring `url-proxy'...
[2013-01-29 21:20:21] (info)                 +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:21] (info)               +-> Requiring `url-proxy'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url-proxy.elc (loaded in 0.03 s)
[2013-01-29 21:20:21] (info)               +-> Requiring `url-parse'... already loaded
[2013-01-29 21:20:21] (info)               +-> Requiring `url-util'... already loaded
[2013-01-29 21:20:21] (info)             +-> Requiring `url'... c:/Program Files (x86)/emacs-24.2.91/lisp/url/url.elc (loaded in 1.34 s)
[2013-01-29 21:20:21] (info)           +-> Requiring `gnus-compat'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-compat.elc (loaded in 1.38 s)
[2013-01-29 21:20:21] (info)           +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:21] (info)           +-> Requiring `nnheader'... already loaded
[2013-01-29 21:20:21] (info)           +-> Requiring `gnus-ems'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-ems.elc (loaded in 0.05 s)
[2013-01-29 21:20:21] (info)         +-> Requiring `gnus'... d:/home/sva/Public/Repositories/gnus/lisp/gnus.elc (loaded in 1.98 s)
[2013-01-29 21:20:21] (info)         +-> Requiring `gnus-group'...
[2013-01-29 21:20:21] (info)           +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:21] (info)           +-> Requiring `gnus-start'...
[2013-01-29 21:20:21] (info)             +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:21] (info)             +-> Requiring `gnus-win'...
[2013-01-29 21:20:21] (info)               +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:21] (info)               +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:21] (info)             +-> Requiring `gnus-win'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-win.elc (loaded in 0.03 s)
[2013-01-29 21:20:21] (info)             +-> Requiring `gnus-int'...
[2013-01-29 21:20:21] (info)               +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:21] (info)               +-> Requiring `message'...
[2013-01-29 21:20:21] (info)                 +-> Requiring `mailheader'... c:/Program Files (x86)/emacs-24.2.91/lisp/mail/mailheader.elc (loaded in 0.09 s)
[2013-01-29 21:20:21] (info)                 +-> Requiring `gmm-utils'... d:/home/sva/Public/Repositories/gnus/lisp/gmm-utils.elc (loaded in 0.03 s)
[2013-01-29 21:20:21] (info)                 +-> Requiring `mail-utils'... already loaded
[2013-01-29 21:20:21] (info)                 +-> Requiring `mailabbrev'... c:/Program Files (x86)/emacs-24.2.91/lisp/mail/mailabbrev.elc (loaded in 0.06 s)
[2013-01-29 21:20:21] (info)                 +-> Requiring `mail-parse'...
[2013-01-29 21:20:21] (info)                   +-> Requiring `mail-prsvr'... already loaded
[2013-01-29 21:20:21] (info)                   +-> Requiring `ietf-drums'...
[2013-01-29 21:20:21] (info)                     +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:21] (info)                   +-> Requiring `ietf-drums'... d:/home/sva/Public/Repositories/gnus/lisp/ietf-drums.elc (loaded in 0.03 s)
[2013-01-29 21:20:21] (info)                   +-> Requiring `rfc2231'...
[2013-01-29 21:20:21] (info)                     +-> Requiring `ietf-drums'... already loaded
[2013-01-29 21:20:21] (info)                     +-> Requiring `rfc2047'...
[2013-01-29 21:20:21] (info)                       +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:21] (info)                       +-> Requiring `ietf-drums'... already loaded
[2013-01-29 21:20:21] (info)                       +-> Requiring `mail-prsvr'... already loaded
[2013-01-29 21:20:21] (info)                       +-> Requiring `rfc2045'...
[2013-01-29 21:20:21] (info)                         +-> Requiring `ietf-drums'... already loaded
[2013-01-29 21:20:21] (info)                       +-> Requiring `rfc2045'... d:/home/sva/Public/Repositories/gnus/lisp/rfc2045.elc (loaded in 0.03 s)
[2013-01-29 21:20:21] (info)                     +-> Requiring `rfc2047'... d:/home/sva/Public/Repositories/gnus/lisp/rfc2047.elc (loaded in 0.11 s)
[2013-01-29 21:20:21] (info)                   +-> Requiring `rfc2231'... d:/home/sva/Public/Repositories/gnus/lisp/rfc2231.elc (loaded in 0.14 s)
[2013-01-29 21:20:21] (info)                   +-> Requiring `rfc2047'... already loaded
[2013-01-29 21:20:21] (info)                   +-> Requiring `rfc2045'... already loaded
[2013-01-29 21:20:21] (info)                 +-> Requiring `mail-parse'... d:/home/sva/Public/Repositories/gnus/lisp/mail-parse.elc (loaded in 0.20 s)
[2013-01-29 21:20:21] (info)                 +-> Requiring `mml'...
[2013-01-29 21:20:21] (info)                   +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:21] (info)                   +-> Requiring `mm-bodies'...
[2013-01-29 21:20:21] (info)                     +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:21] (info)                     +-> Requiring `rfc2047'... already loaded
[2013-01-29 21:20:21] (info)                     +-> Requiring `mm-encode'...
[2013-01-29 21:20:21] (info)                       +-> Requiring `mail-parse'... already loaded
[2013-01-29 21:20:21] (info)                     +-> Requiring `mm-encode'... d:/home/sva/Public/Repositories/gnus/lisp/mm-encode.elc (loaded in 0.02 s)
[2013-01-29 21:20:21] (info)                   +-> Requiring `mm-bodies'... d:/home/sva/Public/Repositories/gnus/lisp/mm-bodies.elc (loaded in 0.06 s)
[2013-01-29 21:20:21] (info)                   +-> Requiring `mm-encode'... already loaded
[2013-01-29 21:20:21] (info)                   +-> Requiring `mm-decode'...
[2013-01-29 21:20:21] (info)                     +-> Requiring `mail-parse'... already loaded
[2013-01-29 21:20:21] (info)                     +-> Requiring `mm-bodies'... already loaded
[2013-01-29 21:20:22] (info)                   +-> Requiring `mm-decode'... d:/home/sva/Public/Repositories/gnus/lisp/mm-decode.elc (loaded in 0.08 s)
[2013-01-29 21:20:22] (info)                   +-> Requiring `mml-sec'... d:/home/sva/Public/Repositories/gnus/lisp/mml-sec.elc (loaded in 0.02 s)
[2013-01-29 21:20:22] (info)                 +-> Requiring `mml'... d:/home/sva/Public/Repositories/gnus/lisp/mml.elc (loaded in 0.23 s)
[2013-01-29 21:20:22] (info)                 +-> Requiring `rfc822'... c:/Program Files (x86)/emacs-24.2.91/lisp/mail/rfc822.elc (loaded in 0.05 s)
[2013-01-29 21:20:22] (info)                 +-> Requiring `format-spec'... d:/home/sva/Public/Repositories/gnus/lisp/format-spec.elc (loaded in 0.06 s)
[2013-01-29 21:20:22] (info)                 +-> Requiring `idna'...
[2013-01-29 21:20:22] (info)               +-> Requiring `message'... d:/home/sva/Public/Repositories/gnus/lisp/message.elc (loaded in 1.00 s)
[2013-01-29 21:20:22] (info)               +-> Requiring `gnus-range'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-range.elc (loaded in 0.02 s)
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-int'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-int.elc (loaded in 1.11 s)
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-spec'...
[2013-01-29 21:20:22] (info)               +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-spec'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-spec.elc (loaded in 0.03 s)
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-range'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-start'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-start.elc (loaded in 1.27 s)
[2013-01-29 21:20:22] (info)           +-> Requiring `nnmail'...
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `nnheader'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `message'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `mail-source'...
[2013-01-29 21:20:22] (info)               +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:22] (info)               +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:22] (info)               +-> Requiring `message'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `mail-source'... d:/home/sva/Public/Repositories/gnus/lisp/mail-source.elc (loaded in 0.05 s)
[2013-01-29 21:20:22] (info)             +-> Requiring `mm-util'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-int'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `nnmail'... d:/home/sva/Public/Repositories/gnus/lisp/nnmail.elc (loaded in 0.14 s)
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-spec'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-int'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-range'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-win'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-undo'...
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:22] (info)             +-> Requiring `gnus'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-undo'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-undo.elc (loaded in 0.03 s)
[2013-01-29 21:20:22] (info)           +-> Requiring `gmm-utils'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `time-date'... already loaded
[2013-01-29 21:20:22] (info)           +-> Requiring `gnus-ems'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-group'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-group.elc (loaded in 1.61 s)
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-spec'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-range'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-int'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-undo'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `gmm-utils'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `mm-decode'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `nnoo'...
[2013-01-29 21:20:22] (info)           +-> Requiring `nnheader'... already loaded
[2013-01-29 21:20:22] (info)         +-> Requiring `nnoo'... d:/home/sva/Public/Repositories/gnus/lisp/nnoo.elc (loaded in 0.02 s)
[2013-01-29 21:20:23] (info)       +-> Requiring `gnus-sum'... d:/home/sva/Public/Repositories/gnus/lisp/gnus-sum.elc (loaded in 3.92 s)
[2013-01-29 21:20:23] (info)       +-> Requiring `calendar'... already loaded
[2013-01-29 21:20:23] (info)       +-> Requiring `find-func'... c:/Program Files (x86)/emacs-24.2.91/lisp/emacs-lisp/find-func.elc (loaded in 0.06 s)
[2013-01-29 21:20:23] (info)       +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:23] (info) Loading d:/home/sva/Public/Repositories/org-mode/lisp/org-loaddefs.el...
[2013-01-29 21:20:23] (info)       +-> Requiring `org-macs'... d:/home/sva/Public/Repositories/org-mode/lisp/org-macs.el (loaded in 0.03 s)
[2013-01-29 21:20:23] (info)       +-> Requiring `org-compat'...
[2013-01-29 21:20:23] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:23] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:23] (info)       +-> Requiring `org-compat'... d:/home/sva/Public/Repositories/org-mode/lisp/org-compat.el (loaded in 0.05 s)
[2013-01-29 21:20:23] (info)       +-> Requiring `ob-emacs-lisp'...
[2013-01-29 21:20:23] (info)         +-> Requiring `ob'...
[2013-01-29 21:20:23] (info)           +-> Requiring `ob-eval'...
[2013-01-29 21:20:23] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:23] (info)           +-> Requiring `ob-eval'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-eval.el (loaded in 0.03 s)
[2013-01-29 21:20:23] (info)           +-> Requiring `ob-core'...
[2013-01-29 21:20:23] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:23] (info)             +-> Requiring `ob-eval'... already loaded
[2013-01-29 21:20:23] (info)             +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:23] (info)             +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:23] (info)           +-> Requiring `ob-core'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-core.el (loaded in 0.19 s)
[2013-01-29 21:20:23] (info)           +-> Requiring `ob-comint'...
[2013-01-29 21:20:23] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:23] (info)             +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:23] (info)             +-> Requiring `comint'...
[2013-01-29 21:20:23] (info)               +-> Requiring `ring'... c:/Program Files (x86)/emacs-24.2.91/lisp/emacs-lisp/ring.elc (loaded in 0.06 s)
[2013-01-29 21:20:23] (info)               +-> Requiring `ansi-color'... c:/Program Files (x86)/emacs-24.2.91/lisp/ansi-color.elc (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)               +-> Requiring `regexp-opt'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `comint'... c:/Program Files (x86)/emacs-24.2.91/lisp/comint.elc (loaded in 0.20 s)
[2013-01-29 21:20:24] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-comint'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-comint.el (loaded in 0.34 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-exp'...
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-exp'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-exp.el (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-keys'...
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-keys'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-keys.el (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-table'...
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-table'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-table.el (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-lob'...
[2013-01-29 21:20:24] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-table'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-lob'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-lob.el (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-ref'...
[2013-01-29 21:20:24] (info)             +-> Requiring `ob-core'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-ref'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-ref.el (loaded in 0.03 s)
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-tangle'...
[2013-01-29 21:20:24] (info)             +-> Requiring `org-src'...
[2013-01-29 21:20:24] (info)               +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:24] (info)               +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:24] (info)               +-> Requiring `ob-keys'... already loaded
[2013-01-29 21:20:24] (info)               +-> Requiring `ob-comint'... already loaded
[2013-01-29 21:20:24] (info)               +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)             +-> Requiring `org-src'... d:/home/sva/Public/Repositories/org-mode/lisp/org-src.el (loaded in 0.13 s)
[2013-01-29 21:20:24] (info)             +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)           +-> Requiring `ob-tangle'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-tangle.el (loaded in 0.16 s)
[2013-01-29 21:20:24] (info)         +-> Requiring `ob'... d:/home/sva/Public/Repositories/org-mode/lisp/ob.el (loaded in 0.98 s)
[2013-01-29 21:20:24] (info)       +-> Requiring `ob-emacs-lisp'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-emacs-lisp.el (loaded in 0.98 s)
[2013-01-29 21:20:24] (info)       +-> Requiring `org-version'... d:/home/sva/Public/Repositories/org-mode/lisp/org-version.el (loaded in 0.00 s)
[2013-01-29 21:20:24] (info)       +-> Requiring `outline'... c:/Program Files (x86)/emacs-24.2.91/lisp/outline.elc (loaded in 0.06 s)
[2013-01-29 21:20:24] (info)       +-> Requiring `noutline'... already loaded
[2013-01-29 21:20:24] (info)       +-> Requiring `time-date'... already loaded
[2013-01-29 21:20:24] (info)       +-> Requiring `easymenu'... already loaded
[2013-01-29 21:20:24] (info)       +-> Requiring `overlay'... already loaded
[2013-01-29 21:20:24] (info)       +-> Requiring `org-entities'...
[2013-01-29 21:20:24] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:24] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:24] (info)       +-> Requiring `org-entities'... d:/home/sva/Public/Repositories/org-mode/lisp/org-entities.el (loaded in 0.09 s)
[2013-01-29 21:20:24] (info)       +-> Requiring `org-faces'...
[2013-01-29 21:20:24] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:24] (info)         +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `org-faces'... d:/home/sva/Public/Repositories/org-mode/lisp/org-faces.el (loaded in 0.13 s)
[2013-01-29 21:20:25] (info)       +-> Requiring `org-list'...
[2013-01-29 21:20:25] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `org-list'... d:/home/sva/Public/Repositories/org-mode/lisp/org-list.el (loaded in 0.17 s)
[2013-01-29 21:20:25] (info)       +-> Requiring `org-pcomplete'...
[2013-01-29 21:20:25] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `pcomplete'...
[2013-01-29 21:20:25] (info)           +-> Requiring `comint'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `pcomplete'... c:/Program Files (x86)/emacs-24.2.91/lisp/pcomplete.elc (loaded in 0.05 s)
[2013-01-29 21:20:25] (info)       +-> Requiring `org-pcomplete'... d:/home/sva/Public/Repositories/org-mode/lisp/org-pcomplete.el (loaded in 0.11 s)
[2013-01-29 21:20:25] (info)       +-> Requiring `org-src'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `org-footnote'...
[2013-01-29 21:20:25] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:25] (info)         +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `org-footnote'... d:/home/sva/Public/Repositories/org-mode/lisp/org-footnote.el (loaded in 0.13 s)
[2013-01-29 21:20:25] (info)       +-> Requiring `ob'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `font-lock'... already loaded
[2013-01-29 21:20:25] (info)       +-> Requiring `macroexp'... already loaded [2 times]
[2013-01-29 21:20:26] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:26] (info)       +-> Requiring `bytecomp'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `warnings'... c:/Program Files (x86)/emacs-24.2.91/lisp/emacs-lisp/warnings.elc (loaded in 0.05 s)
[2013-01-29 21:20:26] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:26] (info)       +-> Requiring `macroexp'... already loaded [2 times]
[2013-01-29 21:20:26] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:26] (info)       +-> Requiring `bytecomp'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `warnings'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:26] (info)     +-> Requiring `org'... d:/home/sva/Public/Repositories/org-mode/lisp/org.el (loaded in 7.30 s)
[2013-01-29 21:20:26] (info)     +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:26] (info)     +-> Requiring `org-agenda'...
[2013-01-29 21:20:26] (info)       +-> Requiring `org'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `cl'... already loaded
[2013-01-29 21:20:26] (info)       +-> Requiring `macroexp'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:27] (info)       +-> Requiring `bytecomp'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `warnings'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `help-fns'... already loaded [2 times]
[2013-01-29 21:20:27] (info)       +-> Requiring `org-bbdb'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-bbdb'... d:/home/sva/Public/Repositories/org-mode/lisp/org-bbdb.el (loaded in 0.05 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-bibtex'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `bibtex'...
[2013-01-29 21:20:27] (info)           +-> Requiring `button'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `bibtex'... c:/Program Files (x86)/emacs-24.2.91/lisp/textmodes/bibtex.elc (loaded in 0.17 s)
[2013-01-29 21:20:27] (info)         +-> Requiring `cl'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-bibtex'... d:/home/sva/Public/Repositories/org-mode/lisp/org-bibtex.el (loaded in 0.25 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-docview'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-docview'... d:/home/sva/Public/Repositories/org-mode/lisp/org-docview.el (loaded in 0.02 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-gnus'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `gnus-util'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `gnus-sum'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-gnus'... d:/home/sva/Public/Repositories/org-mode/lisp/org-gnus.el (loaded in 0.03 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-info'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-info'... d:/home/sva/Public/Repositories/org-mode/lisp/org-info.el (loaded in 0.03 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-jsinfo'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org-exp'...
[2013-01-29 21:20:27] (info)           +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `org-macs'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `org-agenda'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `ob-exp'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `org-src'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `cl'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `macroexp'... already loaded [2 times]
[2013-01-29 21:20:27] (info)         +-> Requiring `org-exp'... d:/home/sva/Public/Repositories/org-mode/lisp/org-exp.el (loaded in 0.24 s)
[2013-01-29 21:20:27] (info)         +-> Requiring `org-html'...
[2013-01-29 21:20:27] (info)           +-> Requiring `org-exp'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:27] (info)           +-> Requiring `cl'... already loaded
[2013-01-29 21:20:27] (info)         +-> Requiring `org-html'... d:/home/sva/Public/Repositories/org-mode/lisp/org-html.el (loaded in 0.09 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-jsinfo'... d:/home/sva/Public/Repositories/org-mode/lisp/org-jsinfo.el (loaded in 0.38 s)
[2013-01-29 21:20:27] (info)       +-> Requiring `org-irc'...
[2013-01-29 21:20:27] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:27] (info)       +-> Requiring `org-irc'... d:/home/sva/Public/Repositories/org-mode/lisp/org-irc.el (loaded in 0.11 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-mew'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-mew'... d:/home/sva/Public/Repositories/org-mode/lisp/org-mew.el (loaded in 0.01 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-mhe'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-mhe'... d:/home/sva/Public/Repositories/org-mode/lisp/org-mhe.el (loaded in 0.02 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-rmail'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-rmail'... d:/home/sva/Public/Repositories/org-mode/lisp/org-rmail.el (loaded in 0.02 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-vm'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-vm'... d:/home/sva/Public/Repositories/org-mode/lisp/org-vm.el (loaded in 0.03 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-w3m'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-w3m'... d:/home/sva/Public/Repositories/org-mode/lisp/org-w3m.el (loaded in 0.03 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `org-wl'...
[2013-01-29 21:20:28] (info)         +-> Requiring `org'... already loaded
[2013-01-29 21:20:28] (info)       +-> Requiring `org-wl'... d:/home/sva/Public/Repositories/org-mode/lisp/org-wl.el (loaded in 0.03 s)
[2013-01-29 21:20:28] (info)       +-> Requiring `image'... already loaded
[2013-01-29 21:20:28] (info) Loading c:/Program Files (x86)/emacs-24.2.91/lisp/vc/vc-git.elc...
Loading vc-git...done
[2013-01-29 21:20:28] (info)       +-> Requiring `vc-git'... already loaded [2 times]
[2013-01-29 21:20:30] (info)       +-> Requiring `cl'... already loaded
[2013-01-29 21:20:30] (info)       +-> Requiring `org'... already loaded
[2013-01-29 21:20:46] (info)       +-> Requiring `diary-lib'... already loaded [2 times]
[2013-01-29 21:20:46] No event to add
[2013-01-29 21:20:46] (info)     +-> Requiring `org-agenda'... d:/home/sva/Public/Repositories/org-mode/lisp/org-agenda.el (loaded in 19.70 s)
[2013-01-29 21:20:46] (info)     +-> Requiring `ob-exp'... already loaded
[2013-01-29 21:20:46] (info)     +-> Requiring `org-src'... already loaded
[2013-01-29 21:20:46] (info)     +-> Requiring `cl'... already loaded
[2013-01-29 21:20:46] (info)     +-> Requiring `macroexp'... already loaded [2 times]
[2013-01-29 21:20:46] (info)   +-> Requiring `org-exp'... d:/home/sva/Public/Repositories/org-mode/lisp/org-exp.el (loaded in 27.17 s)
[2013-01-29 21:20:46] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:46] (info) +-> Requiring `org-clock'... already loaded
[2013-01-29 21:20:46] (info) +-> Requiring `org-habit'...
[2013-01-29 21:20:46] (info)   +-> Requiring `org'... already loaded
[2013-01-29 21:20:46] (info)   +-> Requiring `org-agenda'... already loaded
[2013-01-29 21:20:46] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:46] (info) +-> Requiring `org-habit'... d:/home/sva/Public/Repositories/org-mode/lisp/org-habit.el (loaded in 0.05 s)
[2013-01-29 21:20:46] (info) +-> Requiring `org-protocol'...
[2013-01-29 21:20:46] (info)   +-> Requiring `org'... already loaded
[2013-01-29 21:20:46] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:46] (info) +-> Requiring `org-protocol'... d:/home/sva/Public/Repositories/org-mode/lisp/org-protocol.el (loaded in 0.05 s)
[2013-01-29 21:20:46] (info) Found 36 entries in `org-agenda-files'
[2013-01-29 21:20:47] (info) +-> Requiring `org-e-ascii'...
[2013-01-29 21:20:47] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:47] (info)   +-> Requiring `org-export'...
[2013-01-29 21:20:47] (info)     +-> Requiring `cl'... already loaded
[2013-01-29 21:20:47] (info)     +-> Requiring `org-element'... already loaded
[2013-01-29 21:20:47] (info)     +-> Requiring `ob-exp'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-export'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-export.el (loaded in 0.27 s)
[2013-01-29 21:20:48] (info)   +-> Requiring `org-e-publish'...
[2013-01-29 21:20:48] (info)     +-> Requiring `cl'... already loaded
[2013-01-29 21:20:48] (info)     +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:48] (info)     +-> Requiring `org-export'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-e-publish'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-publish.el (loaded in 0.08 s)
[2013-01-29 21:20:48] (info)   +-> Requiring `macroexp'... already loaded
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-ascii'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-ascii.el (loaded in 0.52 s)
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-html'...
[2013-01-29 21:20:48] (info)   +-> Requiring `org-export'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-e-publish'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `table'...
[2013-01-29 21:20:48] (info)     +-> Requiring `regexp-opt'... already loaded
[2013-01-29 21:20:48] (info)     +-> Requiring `easymenu'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `table'... c:/Program Files (x86)/emacs-24.2.91/lisp/textmodes/table.elc (loaded in 0.14 s)
[2013-01-29 21:20:48] (info)   +-> Requiring `help-fns'... already loaded [3 times]
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-html'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-html.el (loaded in 0.36 s)
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-latex'...
[2013-01-29 21:20:48] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-export'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-e-publish'... already loaded
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-latex'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-latex.el (loaded in 0.09 s)
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-beamer'...
[2013-01-29 21:20:48] (info)   +-> Requiring `org-e-latex'... already loaded
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-beamer'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-beamer.el (loaded in 0.06 s)
[2013-01-29 21:20:48] (info) +-> Requiring `org-e-odt'...
[2013-01-29 21:20:48] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `table'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `format-spec'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-export'... already loaded
[2013-01-29 21:20:48] (info)   +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:48] Debug (org-e-odt): Searching for OpenDocument styles files...
[2013-01-29 21:20:48] Debug (org-e-odt): Trying d:/home/sva/Public/Repositories/org-mode/etc/styles/...
[2013-01-29 21:20:48] Debug (org-e-odt): Using styles under d:/home/sva/Public/Repositories/org-mode/etc/styles/
[2013-01-29 21:20:48] Debug (org-e-odt): Searching for OpenDocument schema files...
[2013-01-29 21:20:48] Debug (org-e-odt): Trying d:/home/sva/Public/Repositories/org-mode/etc/schema/...
[2013-01-29 21:20:48] Debug (org-e-odt): Using schema files under d:/home/sva/Public/Repositories/org-mode/etc/schema/
[2013-01-29 21:20:49] (info)   +-> Requiring `help-fns'... already loaded [3 times]
[2013-01-29 21:20:49] (info) +-> Requiring `org-e-odt'... d:/home/sva/Public/Repositories/org-mode/contrib/lisp/org-e-odt.el (loaded in 0.31 s)
[2013-01-29 21:20:49] (info) +-> Requiring `ob-R'...
[2013-01-29 21:20:49] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:49] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:49] (info) +-> Requiring `ob-R'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-R.el (loaded in 0.05 s)
[2013-01-29 21:20:49] (info) +-> Requiring `ob-awk'...
[2013-01-29 21:20:49] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:49] (info)   +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:49] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:49] (info) +-> Requiring `ob-awk'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-awk.el (loaded in 0.03 s)
[2013-01-29 21:20:49] (info) +-> Requiring `ob-calc'...
[2013-01-29 21:20:49] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:49] (info)   +-> Requiring `calc'...
[2013-01-29 21:20:49] (info)     +-> Requiring `calc-macs'... c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc-macs.elc (loaded in 0.17 s)
[2013-01-29 21:20:49] (info) Loading c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc-loaddefs.el...
[2013-01-29 21:20:49] (info)   +-> Requiring `calc'... c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc.elc (loaded in 0.38 s)
[2013-01-29 21:20:49] (info)   +-> Requiring `calc-trail'...
[2013-01-29 21:20:49] (info)     +-> Requiring `calc-ext'...
[2013-01-29 21:20:49] (info)       +-> Requiring `calc'... already loaded
[2013-01-29 21:20:49] (info)       +-> Requiring `calc-macs'... already loaded
[2013-01-29 21:20:49] (info)     +-> Requiring `calc-ext'... c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc-ext.elc (loaded in 0.22 s)
[2013-01-29 21:20:49] (info)     +-> Requiring `calc-macs'... already loaded
[2013-01-29 21:20:49] (info)   +-> Requiring `calc-trail'... c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc-trail.elc (loaded in 0.30 s)
[2013-01-29 21:20:49] (info)   +-> Requiring `calc-store'...
[2013-01-29 21:20:50] (info)     +-> Requiring `calc-ext'... already loaded
[2013-01-29 21:20:50] (info)     +-> Requiring `calc-macs'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `calc-store'... c:/Program Files (x86)/emacs-24.2.91/lisp/calc/calc-store.elc (loaded in 0.09 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-calc'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-calc.el (loaded in 0.81 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-ditaa'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `org-compat'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-ditaa'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-ditaa.el (loaded in 0.03 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-dot'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-dot'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-dot.el (loaded in 0.02 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-emacs-lisp'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-gnuplot'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-gnuplot'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-gnuplot.el (loaded in 0.03 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-latex'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-latex'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-latex.el (loaded in 0.03 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-ledger'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-ledger'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-ledger.el (loaded in 0.02 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-org'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-org'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-org.el (loaded in 0.02 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-python'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-python'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-python.el (loaded in 0.03 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-sh'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `shell'...
[2013-01-29 21:20:50] (info)     +-> Requiring `comint'... already loaded
[2013-01-29 21:20:50] (info)     +-> Requiring `pcomplete'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `shell'... c:/Program Files (x86)/emacs-24.2.91/lisp/shell.elc (loaded in 0.16 s)
[2013-01-29 21:20:50] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-sh'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-sh.el (loaded in 0.19 s)
[2013-01-29 21:20:50] (info) +-> Requiring `ob-sql'...
[2013-01-29 21:20:50] (info)   +-> Requiring `ob'... already loaded
[2013-01-29 21:20:50] (info)   +-> Requiring `cl'... already loaded
[2013-01-29 21:20:50] (info) +-> Requiring `ob-sql'... d:/home/sva/Public/Repositories/org-mode/lisp/ob-sql.el (loaded in 0.03 s)
--8<---------------cut here---------------end--------------->8---

In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
21:20:46. They correspond to the executiong of just *one line*:

#+begin_src emacs-lisp
  (org-agenda-to-appt)
#+end_src

This may have something to do with my big amount of Org files in
`org-agenda-files': 36 at this point. But is that so big??

OK, let's find a way to delay that computation (filling in the calendar
system with today's appointments) up to when org-agenda will be loaded, with
the following block of code:

#+begin_src emacs-lisp
(eval-after-load "org-agenda"
 '(when org-agenda-files
      (org-agenda-to-appt)))
#+end_src

Results?  No change, nothing...

Why?  Because, as you can see in the above tree, org-agenda is in fact already
loaded, hence the eval-after-load running as well.

Call tree for org-agenda:

                             Requiring `org'...
[2013-01-29 21:20:19] (info) +-> Requiring `org-clock'...
[2013-01-29 21:20:19] (info)   +-> Requiring `org-exp'...
[2013-01-29 21:20:26] (info)     +-> Requiring `org-agenda'...

I must admit I don't understand[1] why `org-agenda' must be called during Org
startup.

I would like to have:

- the minimal Org config loaded when opening any .org file; IOW, certainly not
  the agenda files!

- all files in `org-agenda-files' when calling any agenda view (C-c a ...)

- the current clocked file when resume Org's clock mechanism.

I'm ready to look at where to cut branches of the Org tree, if that does make
sense to you. Does it?

Best regards,
  Seb

[1] Don't assume it's not related to some problem in my config. But, for this
point, AFAIU, it's not the case.

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Daimrod]

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

> Hello,

Hello Sebastien,

> I would like to have:
>
> - the minimal Org config loaded when opening any .org file; IOW, certainly not
>   the agenda files!
>
> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>
> - the current clocked file when resume Org's clock mechanism.
>
> I'm ready to look at where to cut branches of the Org tree, if that does make
> sense to you. Does it?

You could try to pull from the main branch and test the latest option
pushed by Bastien to improve the agenda startup.

This option, `org-agenda-inhibit-startup', is set by default to t so
shouldn't have anything to configure.

Here is the original thread: http://comments.gmane.org/gmane.emacs.orgmode/65215

> Best regards,
>   Seb
>
> [1] Don't assume it's not related to some problem in my config. But, for this
> point, AFAIU, it's not the case.

-- 
Daimrod/Greg

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: How to improve Org startup time?

[Sebastien Vauban]

Hello Daimrod,

Daimrod wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> I would like to have:
>>
>> - the minimal Org config loaded when opening any .org file; IOW, certainly not
>>   the agenda files!
>>
>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>
>> - the current clocked file when resume Org's clock mechanism.
>>
>> I'm ready to look at where to cut branches of the Org tree, if that does make
>> sense to you. Does it?
>
> You could try to pull from the main branch and test the latest option
> pushed by Bastien to improve the agenda startup.
>
> This option, `org-agenda-inhibit-startup', is set by default to t so
> shouldn't have anything to configure.

Thanks for your notice -- it could (have) help(ed)... if I wasn't already
(quite) up-to-date; here's the results of `git log':

--8<---------------cut here---------------start------------->8---
commit f52600a43908d5b246901780b9a761e477ec5604
Author: Eric Schulte <schulte.eric-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date:   Sat Jan 26 13:58:15 2013 -0700

    fix bug: tangling #+headers: lines w/prefix arg

commit bb40d29b45e091f3a4226c890e1130299c4dffd4
Author: Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date:   Sat Jan 26 18:05:56 2013 +0100

    org-export: Fix subtree export when parent section is empty

    * contrib/lisp/org-export.el (org-export--get-subtree-options): When
      point is at an headline and subtree export is called, make sure
      export properties are extracted from parent headline.
    * testing/lisp/test-org-export.el: Add test.

commit 5e11659e66845e918a047f4a89d171f599729174
Merge: 714b372 a119649
Author: Bastien Guerry <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org>
Date:   Sat Jan 26 15:11:21 2013 +0100

    Merge branch 'maint'

    Conflicts:
        lisp/org.el

commit a1196499237b6a0389fba2d21b69c34068404519
Author: Bastien Guerry <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org>
Date:   Sat Jan 26 15:10:43 2013 +0100

    org.el (org-agenda-inhibit-startup): Rename from `org-agenda-inhibit-startup-visibility-cycling'

    * org.el (org-agenda-inhibit-startup): Rename from
    `org-agenda-inhibit-startup-visibility-cycling'.
    (org-agenda-prepare-buffers): Bind `org-inhibit-startup' to
    `org-agenda-inhibit-startup'.
--8<---------------cut here---------------end--------------->8---

I must admit I did not see any improvement -- at least, even if I did not make
any measures before and after that, I did not feel any improvement.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Nick Dokos]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:


> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
> 21:20:46. They correspond to the executiong of just *one line*:
> 
> #+begin_src emacs-lisp
>   (org-agenda-to-appt)
> #+end_src
> 
> This may have something to do with my big amount of Org files in
> `org-agenda-files': 36 at this point. But is that so big??
> 

I don't think so.

Can you get a profile?

M-x elp-instrument-package RET org-agenda RET
M-x org-agenda-to-appt
M-x elp-results

In my (admittedly unchallenging, run-of-the-mill) setup, I get
(with everything already loaded):

org-agenda-to-appt                                            1           0.053846964   0.053846964
org-agenda-prepare-buffers                                    1           0.028483817   0.028483817
org-agenda-get-day-entries                                    8           0.024222044   0.0030277555
org-agenda-get-scheduled                                      8           0.0154506449  0.0019313306
org-agenda-get-timestamps                                     8           0.004179949   0.0005224936
org-agenda-skip                                               184         0.0027937810  1.518...e-05
org-agenda-files                                              2           0.001386068   0.000693034
org-agenda-get-deadlines                                      8           0.001288303   0.0001610378
org-agenda-format-item                                        22          0.0012140690  5.518...e-05
org-agenda-get-blocks                                         8           0.0007851970  9.814...e-05
org-agenda-new-marker                                         44          0.0006114019  1.389...e-05
org-agenda-skip-eval                                          368         0.0001511950  4.108...e-07
org-agenda-todayp                                             16          0.0001342800  8.392...e-06
org-agenda-fix-displayed-tags                                 22          7.2914e-05    3.314...e-06
org-agenda-get-category-icon                                  22          1.8382e-05    8.355...e-07
org-agenda-time-of-day-to-ampm-maybe                          6           3.347e-06     5.578...e-07

A factor of 300: maybe it's real, but let's make sure first.

Nick

Re: How to improve Org startup time?

[Daimrod]

[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

> Hello Daimrod,
>
> Daimrod wrote:
>> "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
>>> I would like to have:
>>>
>>> - the minimal Org config loaded when opening any .org file; IOW, certainly not
>>>   the agenda files!
>>>
>>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>>
>>> - the current clocked file when resume Org's clock mechanism.
>>>
>>> I'm ready to look at where to cut branches of the Org tree, if that does make
>>> sense to you. Does it?
>>
>> You could try to pull from the main branch and test the latest option
>> pushed by Bastien to improve the agenda startup.
>>
>> This option, `org-agenda-inhibit-startup', is set by default to t so
>> shouldn't have anything to configure.
>
> Thanks for your notice -- it could (have) help(ed)... if I wasn't already
> (quite) up-to-date; here's the results of `git log':
>
> commit f52600a43908d5b246901780b9a761e477ec5604
> Author: Eric Schulte <schulte.eric@gmail.com>
> Date:   Sat Jan 26 13:58:15 2013 -0700
>
>     fix bug: tangling #+headers: lines w/prefix arg
>
> commit bb40d29b45e091f3a4226c890e1130299c4dffd4
> Author: Nicolas Goaziou <n.goaziou@gmail.com>
> Date:   Sat Jan 26 18:05:56 2013 +0100
>
>     org-export: Fix subtree export when parent section is empty
>
>     * contrib/lisp/org-export.el (org-export--get-subtree-options): When
>       point is at an headline and subtree export is called, make sure
>       export properties are extracted from parent headline.
>     * testing/lisp/test-org-export.el: Add test.
>
> commit 5e11659e66845e918a047f4a89d171f599729174
> Merge: 714b372 a119649
> Author: Bastien Guerry <bzg@altern.org>
> Date:   Sat Jan 26 15:11:21 2013 +0100
>
>     Merge branch 'maint'
>
>     Conflicts:
>         lisp/org.el
>
> commit a1196499237b6a0389fba2d21b69c34068404519
> Author: Bastien Guerry <bzg@altern.org>
> Date:   Sat Jan 26 15:10:43 2013 +0100
>
>     org.el (org-agenda-inhibit-startup): Rename from `org-agenda-inhibit-startup-visibility-cycling'
>
>     * org.el (org-agenda-inhibit-startup): Rename from
>     `org-agenda-inhibit-startup-visibility-cycling'.
>     (org-agenda-prepare-buffers): Bind `org-inhibit-startup' to
>     `org-agenda-inhibit-startup'.
>
> I must admit I did not see any improvement -- at least, even if I did not make
> any measures before and after that, I did not feel any improvement.

Per chance, you did not forget to M-x compile ? ;)

Joking aside, I'm sad it didn't any sensible improvement.

-- 
Daimrod/Greg

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Nick,

Thanks for looking into this as well!

Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
>> 21:20:46. They correspond to the executiong of just *one line*:
>> 
>> #+begin_src emacs-lisp
>>   (org-agenda-to-appt)
>> #+end_src
>> 
>> This may have something to do with my big amount of Org files in
>> `org-agenda-files': 36 at this point. But is that so big??
>
> I don't think so.

I'm sure it is, as I wrote (removed from the joined log) a "message" call
before and after that line, and those time-stamps were 16 seconds one from the
other.

> Can you get a profile?

You're right I should use real tools for that...

> M-x elp-instrument-package RET org-agenda RET
> M-x org-agenda-to-appt
> M-x elp-results
>
> In my (admittedly unchallenging, run-of-the-mill) setup, I get
> (with everything already loaded):
>
> org-agenda-to-appt                                            1           0.053846964   0.053846964
> org-agenda-prepare-buffers                                    1           0.028483817   0.028483817
> org-agenda-get-day-entries                                    8           0.024222044   0.0030277555
> org-agenda-get-scheduled                                      8           0.0154506449  0.0019313306
> org-agenda-get-timestamps                                     8           0.004179949   0.0005224936
> org-agenda-skip                                               184         0.0027937810  1.518...e-05
> org-agenda-files                                              2           0.001386068   0.000693034
> org-agenda-get-deadlines                                      8           0.001288303   0.0001610378
> org-agenda-format-item                                        22          0.0012140690  5.518...e-05
> org-agenda-get-blocks                                         8           0.0007851970  9.814...e-05
> org-agenda-new-marker                                         44          0.0006114019  1.389...e-05
> org-agenda-skip-eval                                          368         0.0001511950  4.108...e-07
> org-agenda-todayp                                             16          0.0001342800  8.392...e-06
> org-agenda-fix-displayed-tags                                 22          7.2914e-05    3.314...e-06
> org-agenda-get-category-icon                                  22          1.8382e-05    8.355...e-07
> org-agenda-time-of-day-to-ampm-maybe                          6           3.347e-06     5.578...e-07
>
> A factor of 300: maybe it's real, but let's make sure first.

Here it is. I don't know how to interpret that difference, tho.

--8<---------------cut here---------------start------------->8---
org-agenda-to-appt                                            1           19.673        19.673
org-agenda-prepare-buffers                                    1           18.86         18.86
org-agenda-get-day-entries                                    36          0.7970000000  0.0221388888
org-agenda-files                                              37          0.5440000000  0.0147027027
org-agenda-get-scheduled                                      36          0.5150000000  0.0143055555
org-agenda-get-deadlines                                      36          0.1580000000  0.0043888888
org-agenda-skip                                               612         0.1410000000  0.0002303921
org-agenda-get-timestamps                                     36          0.047         0.0013055555
org-agenda-get-blocks                                         36          0.046         0.0012777777
org-agenda-format-item                                        42          0.031         0.0007380952
org-agenda-skip-eval                                          1204        0.016         1.32...e-005
org-agenda-fix-displayed-tags                                 42          0.0           0.0
org-agenda-todayp                                             72          0.0           0.0
org-agenda-new-marker                                         89          0.0           0.0
org-agenda-deadline-face                                      2           0.0           0.0
org-agenda-get-category-icon                                  42          0.0           0.0
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Daimrod,

Daimrod wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Daimrod wrote:
>>> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>>> I would like to have:
>>>>
>>>> - the minimal Org config loaded when opening any .org file; IOW, certainly not
>>>>   the agenda files!
>>>>
>>>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>>>
>>>> - the current clocked file when resume Org's clock mechanism.
>>>>
>>>> I'm ready to look at where to cut branches of the Org tree, if that does make
>>>> sense to you. Does it?
>>>
>>> You could try to pull from the main branch and test the latest option
>>> pushed by Bastien to improve the agenda startup.
>>>
>>> This option, `org-agenda-inhibit-startup', is set by default to t so
>>> shouldn't have anything to configure.
>>
>> Thanks for your notice -- it could (have) help(ed)... if I wasn't already
>> (quite) up-to-date.
>>
>> I must admit I did not see any improvement -- at least, even if I did not make
>> any measures before and after that, I did not feel any improvement.
>
> Per chance, you did not forget to M-x compile ? ;)

Good to remind me/us with that, but, once again, no, as I do not use compiled
Org files. That way, I'm sure not to forget such recompile step -- which I
would definitely do once in a while!

> Joking aside, I'm sad it didn't any sensible improvement.

Not for me. Not now, at least. But apparently well for others (Eric Fraga).

And, anyway, I'm always welcoming a lot any such effort to improve stuff, even
if that's not always visible as such.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Bastien]

HI Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
> 21:20:46. They correspond to the executiong of just *one line*:
>
> #+begin_src emacs-lisp
>   (org-agenda-to-appt)
> #+end_src
>
> This may have something to do with my big amount of Org files in
> `org-agenda-files': 36 at this point. But is that so big??

There are basically two factors that can slow down the agenda
generation: the number of agenda files, the number of entries
to check in all agenda files.

Can you compare the time spent by the initialization process
before and after commit 582cca5806 ?

It should improve things sensibly, I'd be curious to know
why it does not improve anything -- if that's the case.

Also, do you have any hooks in org-mode-hook?

Finally, org-agenda-to-appt is very slow by default, it
uses org-agenda-get-day-entries and check every entry...
see the docstring on how to make it check only the ones
you really need.

HTH!

-- 
 Bastien

Re: How to improve Org startup time?

[Nick Dokos]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:

> >> This may have something to do with my big amount of Org files in
> >> `org-agenda-files': 36 at this point. But is that so big??
> >
> > I don't think so.
> 
> I'm sure it is, as I wrote (removed from the joined log) a "message" call
> before and after that line, and those time-stamps were 16 seconds one from the
> other.
> 

Small misunderstanding here: the "I don't think so" was a reply
to the "is that so big?" question.

> > Can you get a profile?
> 
> You're right I should use real tools for that...
> 
> > M-x elp-instrument-package RET org-agenda RET
> > M-x org-agenda-to-appt
> > M-x elp-results
> >
> > In my (admittedly unchallenging, run-of-the-mill) setup, I get
> > (with everything already loaded):
> >
> > org-agenda-to-appt                                            1           0.053846964   0.053846964
> > org-agenda-prepare-buffers                                    1           0.028483817   0.028483817
> > org-agenda-get-day-entries                                    8           0.024222044   0.0030277555
> > org-agenda-get-scheduled                                      8           0.0154506449  0.0019313306
> > org-agenda-get-timestamps                                     8           0.004179949   0.0005224936
> > org-agenda-skip                                               184         0.0027937810  1.518...e-05
> > org-agenda-files                                              2           0.001386068   0.000693034
> > org-agenda-get-deadlines                                      8           0.001288303   0.0001610378
> > org-agenda-format-item                                        22          0.0012140690  5.518...e-05
> > org-agenda-get-blocks                                         8           0.0007851970  9.814...e-05
> > org-agenda-new-marker                                         44          0.0006114019  1.389...e-05
> > org-agenda-skip-eval                                          368         0.0001511950  4.108...e-07
> > org-agenda-todayp                                             16          0.0001342800  8.392...e-06
> > org-agenda-fix-displayed-tags                                 22          7.2914e-05    3.314...e-06
> > org-agenda-get-category-icon                                  22          1.8382e-05    8.355...e-07
> > org-agenda-time-of-day-to-ampm-maybe                          6           3.347e-06     5.578...e-07
> >
> > A factor of 300: maybe it's real, but let's make sure first.
>
> Here it is. I don't know how to interpret that difference, tho.
> 
> org-agenda-to-appt                                            1           19.673        19.673
> org-agenda-prepare-buffers                                    1           18.86         18.86
> org-agenda-get-day-entries                                    36          0.7970000000  0.0221388888
> org-agenda-files                                              37          0.5440000000  0.0147027027
> org-agenda-get-scheduled                                      36          0.5150000000  0.0143055555
> org-agenda-get-deadlines                                      36          0.1580000000  0.0043888888
> org-agenda-skip                                               612         0.1410000000  0.0002303921
> org-agenda-get-timestamps                                     36          0.047         0.0013055555
> org-agenda-get-blocks                                         36          0.046         0.0012777777
> org-agenda-format-item                                        42          0.031         0.0007380952
> org-agenda-skip-eval                                          1204        0.016         1.32...e-005
> org-agenda-fix-displayed-tags                                 42          0.0           0.0
> org-agenda-todayp                                             72          0.0           0.0
> org-agenda-new-marker                                         89          0.0           0.0
> org-agenda-deadline-face                                      2           0.0           0.0
> org-agenda-get-category-icon                                  42          0.0           0.0
> 

Well, you have a bigger agenda by a factor of 4-5 and I guess a slower
machine, but it all takes less than a second except for one thing: the
big difference seems to be org-agend-prepare-buffers which
opens the files, reads them in and gets the buffers ready. 
Once the files are open however, they should be cached, so doing it
again should not take very long at all: is that the case?

If so, my guess is that either you have a very slow disk or you have
disk problems. Were things fast at some point in the past? In that case,
I would worry about the disk. Also, what happens if you copy your agenda
files to some other machine and try it there? If that's fast, then again
I would worry about this disk.

An anecdote to illustrate: at one point, it would take me a couple of
minutes to log in whereas previously it was a few seconds.  The kernel
log contained a few disk errors. The disk errors apparently caused multiple
retries, both in the kernel but also (and most probably more
time-consumingly) in the disk firmware. The errors all happened to be in
the file that contained my desktop background image. When I changed
backgrounds (leaving the old file in place so that the bad spots would
not be used by some other file), my login time went back to a few
seconds. I replaced the disk and (knock on wood) the problem has not
reappeared.

So check your kernel logs and maybe run a disk diagnostic program as well.
If there are errors, try backing up the agenda files (copying them
should take a long time if my suspicion is correct): do the equivalent
of

	mv file1.org file1.org.bak
	# the following might take a long time
	cp file1.org.bak file1.org

so that the backups will still occupy the error loci. If the disk is
not too far gone, that might restore the speed of the agenda, but if
that's the case, don't wait too long to replace the disk: once a disk
goes a little bad, it tends to go a *lot* bad pretty fast.

Nick

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Nick,

Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>> >> This may have something to do with my big amount of Org files in
>> >> `org-agenda-files': 36 at this point. But is that so big??
>> >
>> > I don't think so.
>>
>> I'm sure it is, as I wrote (removed from the joined log) a "message" call
>> before and after that line, and those time-stamps were 16 seconds one from the
>> other.
>
> Small misunderstanding here: the "I don't think so" was a reply
> to the "is that so big?" question.

It was already late for me it seems. Yes, I misunderstood your point. Anyway,
I don't mind getting reminded of things which could have escaped me!

>> > Can you get a profile?
>>
>> You're right I should use real tools for that...
>>
>> > M-x elp-instrument-package RET org-agenda RET
>> > M-x org-agenda-to-appt
>> > M-x elp-results
>> >
>> > In my (admittedly unchallenging, run-of-the-mill) setup, I get
>> > (with everything already loaded):
>> >
>> > org-agenda-to-appt                                            1           0.053846964   0.053846964
>> > org-agenda-prepare-buffers                                    1           0.028483817   0.028483817
>> > org-agenda-get-day-entries                                    8           0.024222044   0.0030277555
>> > org-agenda-get-scheduled                                      8           0.0154506449  0.0019313306
>> > org-agenda-get-timestamps                                     8           0.004179949   0.0005224936
>> > org-agenda-skip                                               184         0.0027937810  1.518...e-05
>> > org-agenda-files                                              2           0.001386068   0.000693034
>> > org-agenda-get-deadlines                                      8           0.001288303   0.0001610378
>> > org-agenda-format-item                                        22          0.0012140690  5.518...e-05
>> > org-agenda-get-blocks                                         8           0.0007851970  9.814...e-05
>> > org-agenda-new-marker                                         44          0.0006114019  1.389...e-05
>> > org-agenda-skip-eval                                          368         0.0001511950  4.108...e-07
>> > org-agenda-todayp                                             16          0.0001342800  8.392...e-06
>> > org-agenda-fix-displayed-tags                                 22          7.2914e-05    3.314...e-06
>> > org-agenda-get-category-icon                                  22          1.8382e-05    8.355...e-07
>> > org-agenda-time-of-day-to-ampm-maybe                          6           3.347e-06     5.578...e-07
>> >
>> > A factor of 300: maybe it's real, but let's make sure first.
>>
>> Here it is. I don't know how to interpret that difference, tho.
>>
>> org-agenda-to-appt                                            1           19.673        19.673
>> org-agenda-prepare-buffers                                    1           18.86         18.86
>> org-agenda-get-day-entries                                    36          0.7970000000  0.0221388888
>> org-agenda-files                                              37          0.5440000000  0.0147027027
>> org-agenda-get-scheduled                                      36          0.5150000000  0.0143055555
>> org-agenda-get-deadlines                                      36          0.1580000000  0.0043888888
>> org-agenda-skip                                               612         0.1410000000  0.0002303921
>> org-agenda-get-timestamps                                     36          0.047         0.0013055555
>> org-agenda-get-blocks                                         36          0.046         0.0012777777
>> org-agenda-format-item                                        42          0.031         0.0007380952
>> org-agenda-skip-eval                                          1204        0.016         1.32...e-005
>> org-agenda-fix-displayed-tags                                 42          0.0           0.0
>> org-agenda-todayp                                             72          0.0           0.0
>> org-agenda-new-marker                                         89          0.0           0.0
>> org-agenda-deadline-face                                      2           0.0           0.0
>> org-agenda-get-category-icon                                  42          0.0           0.0
>
> Well, you have a bigger agenda by a factor of 4-5

Well, I'm still under the floating line, for what concerns GTD (in the sense
of getting things _DONE_).

> and I guess a slower machine, but it all takes less than a second except for
> one thing: the big difference seems to be org-agend-prepare-buffers which
> opens the files, reads them in and gets the buffers ready.

Well, I did have a slow machine (6-year old, 2 GB RAM and plain old HD) up to
last month. Now, I do have a brand new Asus laptop with 4 GB RAM and 256 GB
SSD... It can't be that slow. Not possible...

I have to admit working most of the time without the laptop being powered,
which I know (from observation) is 2 to 3 times slower. But, if I do that,
it's because:

- I want to save my battery life, by making full charges and discharges, hence
  being unpowered is how I work 5 hours out of 7 (charging takes 2 hours).

- I want to be in a situation similar to the one of my colleagues, who are
  using Org (because of me) and don't especially have a machine which is that
  new.

> Once the files are open however, they should be cached, so doing it again
> should not take very long at all: is that the case?

Yes, it is the case.

> If so, my guess is that either you have a very slow disk or you have
> disk problems.

I can't imagine how, but?

> Were things fast at some point in the past?

No, it always has been (too) slow for me, hence my efforts to look at how to
separate different Org functions (fontifying a buffer + Org search support,
from generating an agenda, among others) at different points in time.

For me, loading Org when opening an Org file should not trigger the agenda
stuff (requiring org-agenda and the like). This latter should be triggered by
the autoloads when pressing C-c a, for example.

> In that case, I would worry about the disk. Also, what happens if you copy
> your agenda files to some other machine and try it there? If that's fast,
> then again I would worry about this disk.
>
> An anecdote to illustrate: at one point, it would take me a couple of
> minutes to log in whereas previously it was a few seconds.  The kernel
> log contained a few disk errors. The disk errors apparently caused multiple
> retries, both in the kernel but also (and most probably more
> time-consumingly) in the disk firmware. The errors all happened to be in
> the file that contained my desktop background image. When I changed
> backgrounds (leaving the old file in place so that the bad spots would
> not be used by some other file), my login time went back to a few
> seconds. I replaced the disk and (knock on wood) the problem has not
> reappeared.
>
> So check your kernel logs and maybe run a disk diagnostic program as well.
> If there are errors, try backing up the agenda files (copying them
> should take a long time if my suspicion is correct): do the equivalent
> of
>
> 	mv file1.org file1.org.bak
> 	# the following might take a long time
> 	cp file1.org.bak file1.org
>
> so that the backups will still occupy the error loci. If the disk is
> not too far gone, that might restore the speed of the agenda, but if
> that's the case, don't wait too long to replace the disk: once a disk
> goes a little bad, it tends to go a *lot* bad pretty fast.

I'm on Windows 8, so I think I have less control on such log events than you
do. Tho, I looked in the Event Viewer (tabs "System" and "Hardware Events"),
but did not find anything suspect at this point.

Best regards,
  Seb

--
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban" writes:
>
>> In particular, you'll see that *16 seconds* are "lost" between 21:20:30 and
>> 21:20:46. They correspond to the executiong of just *one line*:
>>
>> #+begin_src emacs-lisp
>>   (org-agenda-to-appt)
>> #+end_src
>>
>> This may have something to do with my big amount of Org files in
>> `org-agenda-files': 36 at this point. But is that so big??
>
> There are basically two factors that can slow down the agenda generation:
> the number of agenda files, the number of entries to check in all agenda
> files.
>
> Can you compare the time spent by the initialization process before and
> after commit 582cca5806 ?

I'll do at noon.

> It should improve things sensibly, I'd be curious to know why it does not
> improve anything -- if that's the case.
>
> Also, do you have any hooks in org-mode-hook?

Of course ;-)

Here, the full collection (in real life, they're at different spots of my
.emacs file):

--8<---------------cut here---------------start------------->8---
;; whitespace mode
(add-hook 'text-mode-hook
          (lambda ()
            (whitespace-mode 1)))

;; activate Auto Fill for all text mode buffers
(add-hook 'text-mode-hook 'turn-on-auto-fill)

(add-hook 'org-mode-hook
          (lambda ()
            (local-set-key (kbd "\C-\M-n") 'outline-next-visible-heading)
            (local-set-key (kbd "\C-\M-p") 'outline-previous-visible-heading)
            (local-set-key (kbd "\C-\M-u") 'outline-up-heading)))

(add-hook 'org-mode-hook
          (lambda ()
            ;; (local-set-key "\M-n" 'outline-next-visible-heading)
            ;; (local-set-key "\M-p" 'outline-previous-visible-heading)

            (local-set-key (kbd "C-c h") 'hide-other)

            ;; table
            (local-set-key "\M-\C-w" 'org-table-copy-region)
            (local-set-key "\M-\C-y" 'org-table-paste-rectangle)
            (local-set-key "\M-\C-l" 'org-table-sort-lines)))

(add-hook 'org-mode-hook
          (lambda() (add-to-list 'mode-line-format
                                 '(:eval (org-propertize
                                          (org-display-outline-path nil t " / " t)
                                         'face 'mode-line-emphasis
                                         'help-echo "Outline path")) t)))

(add-hook 'org-mode-hook
          (lambda ()
            (define-key org-agenda-keymap
              "L" 'lvn/org-agenda-toggle-list-category)
            (define-key org-agenda-mode-map
              "L" 'lvn/org-agenda-toggle-list-category)))

(add-hook 'org-mode-hook
          (lambda ()
            (setq imenu-generic-expression
                  org-src-blocks-imenu-generic-expression))))

(add-hook 'org-mode-hook
          (lambda ()
            ;; YASnippet (using the new org-cycle hooks)
            (set (make-local-variable 'yas/trigger-key) (kbd "tab")) ;; needed?
            (add-to-list 'org-tab-first-hook
                         'yas/org-very-safe-expand)
            (define-key yas/keymap (kbd "tab") 'yas/next-field) ;; needed?
            )))

(add-hook 'org-mode-hook
          (lambda ()
            (local-set-key (kbd "C-c m") 'org-mime-subtree)))
--8<---------------cut here---------------end--------------->8---

This is the result of searching for the following strings:

- text-mode-hook
- outline-mode-hook
- org-mode-hook

> Finally, org-agenda-to-appt is very slow by default, it uses
> org-agenda-get-day-entries and check every entry... see the docstring on how
> to make it check only the ones you really need.

Euh...

    ╭────
    │ org-agenda-get-day-entries is a Lisp function in `org-agenda.el'.
    │
    │ (org-agenda-get-day-entries &rest ARGS)
    │
    │ Not documented.
    ╰────

    ╭────
    │ org-agenda-to-appt is an interactive autoloaded Lisp function in
    │ `org-agenda.el'.
    │
    │ (org-agenda-to-appt &optional REFRESH FILTER &rest ARGS)
    │
    │ Not documented.
    ╰────

What am I missing?

Best regards,
  Seb

--
Sebastien Vauban

Re: How to improve Org startup time?

[Daimrod]

[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

>> Finally, org-agenda-to-appt is very slow by default, it uses
>> org-agenda-get-day-entries and check every entry... see the docstring on how
>> to make it check only the ones you really need.
>
> Euh...
>
>     ╭────
>     │ org-agenda-get-day-entries is a Lisp function in `org-agenda.el'.
>     │
>     │ (org-agenda-get-day-entries &rest ARGS)
>     │
>     │ Not documented.
>     ╰────
>
>     ╭────
>     │ org-agenda-to-appt is an interactive autoloaded Lisp function in
>     │ `org-agenda.el'.
>     │
>     │ (org-agenda-to-appt &optional REFRESH FILTER &rest ARGS)
>     │
>     │ Not documented.
>     ╰────
>
> What am I missing?

Those functions should be documented. Here is what I have:

> org-agenda-get-day-entries is a compiled Lisp function in
> `org-agenda.el'.
> 
> (org-agenda-get-day-entries FILE DATE &rest ARGS)
> 
> Does the work for `org-diary' and `org-agenda'.
> FILE is the path to a file to be checked for entries.  DATE is date like
> the one returned by `calendar-current-date'.  ARGS are symbols indicating
> which kind of entries should be extracted.  For details about these, see
> the documentation of `org-diary'.

> org-agenda-to-appt is an interactive autoloaded compiled Lisp function
> in `org-agenda.el'.
> 
> (org-agenda-to-appt &optional REFRESH FILTER &rest ARGS)
> 
> Activate appointments found in `org-agenda-files'.
> With a C-u prefix, refresh the list of
> appointments.
> 
> If FILTER is t, interactively prompt the user for a regular
> expression, and filter out entries that don't match it.
> 
> If FILTER is a string, use this string as a regular expression
> for filtering entries out.
> 
> If FILTER is a function, filter out entries against which
> calling the function returns nil.  This function takes one
> argument: an entry from `org-agenda-get-day-entries'.
> 
> FILTER can also be an alist with the car of each cell being
> either 'headline or 'category.  For example:
> 
>   '((headline "IMPORTANT")
>     (category "Work"))
> 
> will only add headlines containing IMPORTANT or headlines
> belonging to the "Work" category.
> 
> ARGS are symbols indicating what kind of entries to consider.
> By default `org-agenda-to-appt' will use :deadline, :scheduled
> and :timestamp entries.  See the docstring of `org-diary' for
> details and examples.
> 
> If an entry as a APPT_WARNTIME property, its value will be used
> to override `appt-message-warning-time'.

-- 
Daimrod/Greg

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: How to improve Org startup time?

[Florian Beck]

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> I have to admit working most of the time without the laptop being powered,
> which I know (from observation) is 2 to 3 times slower. 

So maybe your disk is powered down or in a "sleep mode" in order to save
power? Could you check whether you get the same result with your laptop
powered? 

Re: How to improve Org startup time?

[Daniel Clemente]

> > Per chance, you did not forget to M-x compile ? ;)
> 
> Good to remind me/us with that, but, once again, no, as I do not use compiled
> Org files. That way, I'm sure not to forget such recompile step -- which I
> would definitely do once in a while!
> 

  If you are worried about speed, you should always byte-compile, because it's easy and byte-compiled code is faster.
  Just do a "make" after each "git pull".

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Bastien,

Bastien wrote:
> Can you compare the time spent by the initialization process before and
> after commit 582cca5806 ?
>
> It should improve things sensibly, I'd be curious to know why it does not
> improve anything -- if that's the case.

Before giving the results, let me tell you I've now tested as well with the
laptop being "powered" or not. That does change things in a factor "1 to 3".
However, still far behind Nick's results.

Here the results of the jury (elapsed time of `org-agenda-to-appt'):

    | commit | date   | time (not powered) | time (powered) | ratio |
    |--------+--------+--------------------+----------------+-------|
    | f52600 | Jan 26 |              19.27 |           5.56 |   3.5 |
    | 0cf717 | Jan 21 |              19.74 |           5.84 |   3.4 |
    #+TBLFM: $5=$3/$4;%.1f

These are the means over a couple of tests. But the maximum variance (over
that small number of tests) is only about 0.04 s -- in powered mode.

That is: yes, things are better, up to 5%. But, on this example, not quite
significant... ;-(

FYI, I tried the ultimately current version (f518bc8) but there is a parsing
error in `org-e-odt.el' -- I guess since commit 35f944a of this morning?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Daniel,

Daniel Clemente wrote:
>>> Per chance, you did not forget to M-x compile ? ;)
>>
>> Good to remind me/us with that, but, once again, no, as I do not use compiled
>> Org files. That way, I'm sure not to forget such recompile step -- which I
>> would definitely do once in a while!
>
> If you are worried about speed, you should always byte-compile, because it's
> easy and byte-compiled code is faster.
> Just do a "make" after each "git pull".

I know it's easy, but I know myself, and I'm sure to lose hours of work
because, at some point in time, I'll forget to compile the stuff after having
made one change.

Plus, from the speed comparisons I had done once, I felt the difference as
being completely marginal.

Do you really notice a speed improvement when using the compiled files?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Bastien]

Hi Sébastien,

put your .emacs on diet :)  More seriously, I would start by checking
org-agenda-to-appt documentation.  It should be on your system.  If it 
is not, check online.  That's what really slows down your config.

Then, when this is done, I would try to use only those hooks that are
really necessary.  

My 2 cts of course,

-- 
 Bastien

Re: How to improve Org startup time?

[Bastien]

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> Plus, from the speed comparisons I had done once, I felt the difference as
> being completely marginal.

FWIW this is also what I observed, I don't compile anymore.

-- 
 Bastien

Re: How to improve Org startup time?

[Achim Gratz]

Sebastien Vauban writes:
> These are the means over a couple of tests. But the maximum variance (over
> that small number of tests) is only about 0.04 s -- in powered mode.

File operations on Windows _are_ slow to start with and since a virus
scanner is more or less required these days, opening a file is getting
slower yet.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Bastien,

Bastien wrote:
> put your .emacs on diet :) More seriously, I would start by checking
> org-agenda-to-appt documentation. It should be on your system. If it is not,
> check online.

I tried to filter to only "timestamp" entries with the following:

#+begin_src emacs-lisp
  (org-agenda-to-appt nil nil '(:timestamp))
#+end_src

But that does not work -- no error, but no event added to the appt list!

I must not understand the &rest parameter, I guess.

> That's what really slows down your config.

Yes and no.

Yes, because it's currently run at startup time, even if I put that command
inside an eval-after-load "org-agenda" (as `org-agenda' is ultimately called
when `org-clock-persist' is set).

No, because no running that does not change the fact that, sooner or later,
the Org agenda files will have to be loaded and scanned through.

Not having that done at startup simply _add_ another 16 seconds delay to the
computation of the first agenda view; not a gain IMO.

> Then, when this is done, I would try to use only those hooks that are really
> necessary.

Are you referring to something in particular?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Achim,

Achim Gratz wrote:
> Sebastien Vauban writes:
>> These are the means over a couple of tests. But the maximum variance (over
>> that small number of tests) is only about 0.04 s -- in powered mode.
>
> File operations on Windows _are_ slow to start with and since a virus
> scanner is more or less required these days, opening a file is getting
> slower yet.

You may be right, but I guess that I'm not alone using Windows 8, so my
performance observations must be shared by others as well. It may even be
worse for some who have more Org files, and a less powerful computer.

So, I'm trying to think what could be done to split the full Org load time
(loading the packages, loading the Org agenda files, scanning them, computing
an agenda view, etc.) into smaller chunks, that the user would experience
depending on his current actions.

For example, why do all the Org agenda files have to be loaded when I'm simply
opening a plain common (I mean: not part of the agenda) Org file?

I don't know if that's possible (or maybe it's already done so), but the
opposite question could make sense: why would have Org agenda buffers to be
fully fontified when the only useful information for building an agenda view
is the "time" information the entries contain (deadline, scheduled,
timestamp).

Hence, my initial request for information:

>> I would like to have:
>>
>> - the minimal Org config loaded when opening any .org file; IOW, certainly
>>   not the agenda files!
>>
>> - all files in `org-agenda-files' when calling any agenda view (C-c a ...)
>>
>> - the current clocked file when resume Org's clock mechanism.
>>
>> I'm ready to look at where to cut branches of the Org tree, if that does
>> make sense to you. Does it?

on which I had no comment.

Best regards,
  Seb

--
Sebastien Vauban

Re: How to improve Org startup time?

[Eric S Fraga]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> Hello,
>
> Please find here an enriched log of the packages which are loaded for Org, and
> the time it takes.
>
> [2013-01-29 21:20:18] (info) +-> Requiring `appt'...
> [2013-01-29 21:20:18] (info)   +-> Requiring `diary-lib'...
> [2013-01-29 21:20:18] (info)     +-> Requiring `calendar'...

Seb,

how do you get this output?  It looks very useful!

In terms of the actual topic of this thread, I can say that the recent
changes to org for startup have led to a significant decrease in my
emacs startup time.  Thanks to all that have done this!

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-917-gb9c506

Re: How to improve Org startup time?

[Eric S Fraga]

Daniel Clemente <n142857@gmail.com> writes:

>   If you are worried about speed, you should always byte-compile, because it's easy and byte-compiled code is faster.
>   Just do a "make" after each "git pull".

I do compile org but I do not compile any of my start-up files; this is
a practice I got into when I was running different versions of emacs
(e.g. 22 vs 23 vs 24) on different systems (from a wee N800 to a huge
multi-core system) but with shared startup files.

I say this in case the speedups I am observing are more noticeable if
using non-compiled code and others are wondering why they don't observe
any speedups.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-917-gb9c506

Re: How to improve Org startup time?

[Eric S Fraga]

Some timings on a 3-4 (?) year old netbook with Intel N450 Atom @1.66GHz
dual core powered:

With old org, actually from October 2012 (!) as this system acts as a
cloud server for me so I don't actually use it interactively much:

| org-agenda-to-appt         |   1 | 12.525722775  | 12.525722775  |
| org-agenda-prepare-buffers |   2 | 10.719484861  |  5.3597424305 |
| org-agenda-get-day-entries |  15 |  1.4113181819 |  0.0940878787 |
| org-agenda-get-scheduled   |  15 |  1.032943071  |  0.0688628714 |
| org-agenda-get-deadlines   |  14 |  0.2688785840 |  0.0192056131 |
| org-agenda-skip            | 797 |  0.1879489969 |  0.0002358205 |

and with up to date org as of a few minutes ago:

| org-agenda-to-appt         |   1 | 9.168879079  | 9.168879079  |
| org-agenda-prepare-buffers |   2 | 8.1717637810 | 4.0858818905 |
| org-agenda-get-day-entries |  15 | 0.5261351449 | 0.0350756763 |
| org-agenda-get-deadlines   |  14 | 0.253867925  | 0.0181334232 |
| org-agenda-get-scheduled   |  15 | 0.1835072029 | 0.0122338135 |
| org-agenda-skip            | 797 | 0.0482942050 | 6.059...e-05 |
                                                                                                                                                                                 
I.e. an approximately 25% reduction in time overall so I think
org-agenda is significantly faster (okay, not orders of magnitude) but
the time taken is dominated by org-agenda-prepare-buffers on this
system.

However, more interestingly, on a 1 year old desktop computer Intel Core
i5-2500 @ 3.30 GHz, I get very different behaviour:

| org-agenda-to-appt         |   1 | 0.182718048  | 0.182718048  |
| org-agenda-get-day-entries |  14 | 0.095832824  | 0.0068452017 |
| org-agenda-prepare-buffers |   1 | 0.086104933  | 0.086104933  |
| org-agenda-get-scheduled   |  14 | 0.067475949  | 0.0048197106 |
| org-agenda-skip            | 794 | 0.0475198030 | 5.984...e-05 |
| org-agenda-get-deadlines   |  14 | 0.014998552  | 0.0010713251 |

[note: slightly different agenda files as the cloud server copy of my
agenda files is a couple of hours behind my desktop]

Notice the big change in org-agenda-prepare-buffers relative to the
other calls.  Disk performance is almost likely the key here and I think
the recent improvements are quite dramatic but I haven't had a chance to
time these yet.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-917-gb9c506

Re: How to improve Org startup time?

[Bastien]

Hi Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> #+begin_src emacs-lisp
>   (org-agenda-to-appt nil nil '(:timestamp))
> #+end_src

Try this:

#+begin_src emacs-lisp
  (org-agenda-to-appt nil nil :timestamp)
#+end_src

HTH,

-- 
 Bastien

Re: How to improve Org startup time?

[Bastien]

Hi Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> For example, why do all the Org agenda files have to be loaded when I'm simply
> opening a plain common (I mean: not part of the agenda) Org file?

They don't.  Can you reproduce the problem with a minimal config?

Thanks,

-- 
 Bastien

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> Please find here an enriched log of the packages which are loaded for Org, and
>> the time it takes.
>>
>> [2013-01-29 21:20:18] (info) +-> Requiring `appt'...
>> [2013-01-29 21:20:18] (info)   +-> Requiring `diary-lib'...
>> [2013-01-29 21:20:18] (info)     +-> Requiring `calendar'...
>
> how do you get this output?  It looks very useful!

The timestamp stuff comes from EmacsWiki:

#+begin_src emacs-lisp
  (defadvice message (before when-was-that activate)
    "Add timestamps to `message' output."
    (ad-set-arg 0 (concat (format-time-string "[%Y-%m-%d %T] ")
                          (ad-get-arg 0))))
#+end_src

The "call tree" between packages is originally written by me:

#+begin_src emacs-lisp
  (defadvice require (around require-around activate)
    "Leave a trace of packages being loaded."
    (let* ((feature (ad-get-arg 0))
           (require-depth (or (and (boundp 'require-depth) require-depth)
                              0))
           (prefix (concat (make-string (* 2 require-depth) ? ) "+-> ")))
      (cond ((featurep feature)
             (message "(info) %sRequiring `%s'... already loaded"
                      prefix feature)
             ;; in the case `ad-do-it' is not called, you have to set the
             ;; return value yourself!
             (setq ad-return-value feature))
            (t
             (let ((lvn/time-start))
               (message "(info) %sRequiring `%s'..." prefix feature)
               (setq lvn/time-start (float-time))
               (let ((require-depth (1+ require-depth)))
                 ad-do-it)
               (message "(info) %sRequiring `%s'... %s (loaded in %.2f s)"
                        prefix feature
                        (locate-library (symbol-name feature))
                        (- (float-time) lvn/time-start)))))))
#+end_src

You can further improve what you see in the echo area with:

#+begin_src emacs-lisp
  (defadvice load (before debug-log activate)
    (message "(info) Loading %s..." (locate-library (ad-get-arg 0))))

  (defadvice load-library (before debug-log activate)
    (message "(info) Loading library `%s'..." (locate-library (ad-get-arg 0))))

  (defadvice load-file (before debug-log activate)
    (message "(info) Loading file `%s'..." (locate-library (ad-get-arg 0))))

  (defadvice find-file (around find-file-around activate)
    "Open FILENAME and report time spent."
    (let ((filename (ad-get-arg 0))
          (find-file-time-start (float-time)))
      (message "(info) Finding file %s..." filename)
      ad-do-it
      (message "(info) Found file %s in %.2f s." filename
               (- (float-time) find-file-time-start))))
#+end_src

Adapt it to your taste (and report it!)...

> In terms of the actual topic of this thread, I can say that the recent
> changes to org for startup have led to a significant decrease in my
> emacs startup time.  Thanks to all that have done this!

I hope to benefit from all that soon, as well...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> Some timings on a 3-4 (?) year old netbook with Intel N450 Atom @1.66GHz
> dual core powered:
>
> With old org, actually from October 2012 (!) as this system acts as a
> cloud server for me so I don't actually use it interactively much:
>
> | org-agenda-to-appt         |   1 | 12.525722775  | 12.525722775  |
> | org-agenda-prepare-buffers |   2 | 10.719484861  |  5.3597424305 |
> | org-agenda-get-day-entries |  15 |  1.4113181819 |  0.0940878787 |
> | org-agenda-get-scheduled   |  15 |  1.032943071  |  0.0688628714 |
> | org-agenda-get-deadlines   |  14 |  0.2688785840 |  0.0192056131 |
> | org-agenda-skip            | 797 |  0.1879489969 |  0.0002358205 |
>
> and with up to date org as of a few minutes ago:
>
> | org-agenda-to-appt         |   1 | 9.168879079  | 9.168879079  |
> | org-agenda-prepare-buffers |   2 | 8.1717637810 | 4.0858818905 |
> | org-agenda-get-day-entries |  15 | 0.5261351449 | 0.0350756763 |
> | org-agenda-get-deadlines   |  14 | 0.253867925  | 0.0181334232 |
> | org-agenda-get-scheduled   |  15 | 0.1835072029 | 0.0122338135 |
> | org-agenda-skip            | 797 | 0.0482942050 | 6.059...e-05 |
>
> I.e. an approximately 25% reduction in time overall so I think
> org-agenda is significantly faster (okay, not orders of magnitude) but
> the time taken is dominated by org-agenda-prepare-buffers on this
> system.
>
> However, more interestingly, on a 1 year old desktop computer Intel Core
> i5-2500 @ 3.30 GHz, I get very different behaviour:
>
> | org-agenda-to-appt         |   1 | 0.182718048  | 0.182718048  |
> | org-agenda-get-day-entries |  14 | 0.095832824  | 0.0068452017 |
> | org-agenda-prepare-buffers |   1 | 0.086104933  | 0.086104933  |
> | org-agenda-get-scheduled   |  14 | 0.067475949  | 0.0048197106 |
> | org-agenda-skip            | 794 | 0.0475198030 | 5.984...e-05 |
> | org-agenda-get-deadlines   |  14 | 0.014998552  | 0.0010713251 |
>
> Notice the big change in org-agenda-prepare-buffers relative to the
> other calls.  Disk performance is almost likely the key here and I think
> the recent improvements are quite dramatic but I haven't had a chance to
> time these yet.

Dividing the figures by 50, just for the disks, seems too big for me, nope?

Just to be sure: are you sure that, in this last test, `org-agenda-to-appt'
was called without having first opening the agenda files?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Sebastien Vauban]

Bastien,

"Sebastien Vauban" wrote:
> Bastien wrote:
>> put your .emacs on diet :) More seriously, I would start by checking
>> org-agenda-to-appt documentation. It should be on your system. If it is not,
>> check online.
>
> I tried to filter to only "timestamp" entries with the following:
>
> #+begin_src emacs-lisp
>   (org-agenda-to-appt nil nil '(:timestamp))
> #+end_src
>
> But that does not work -- no error, but no event added to the appt list!
>
> I must not understand the &rest parameter, I guess.
>
>> That's what really slows down your config.
>
> Yes and no.
>
> Yes, because it's currently run at startup time, even if I put that command
> inside an eval-after-load "org-agenda" (as `org-agenda' is ultimately called
> when `org-clock-persist' is set).
>
> No, because no running that does not change the fact that, sooner or later,
> the Org agenda files will have to be loaded and scanned through.
>
> Not having that done at startup simply _add_ another 16 seconds delay to the
> computation of the first agenda view; not a gain IMO.

To be coherent with what I'm telling in this thread... that is:

- we can use Org just for note-taking, and exporting to HTML/LaTeX/etc.
- we can use it for agenda purpose only
- we can use if for clocking purpose only
- we can use it for any mix of these (at different moments in time)

... I've removed the explicit call of `(org-agenda-to-appt)' from my .emacs:
it makes no sense to search for event notifications at startup time if my
primary purpose, now, of firing up Emacs is to work on notes and documents.

However, I've left it in the `org-finalize-agenda-hook' hook, so that the
`appt-list' is fed up as soon as I begin using agenda functions.

That way, I have well removed 16 seconds from my Emacs startup time, but
they're moved for the creation of the _first_ agenda view.

IOW, the time is lost where it makes more sense, but I still have to search on
how to reduce that time.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Achim Gratz]

Sebastien Vauban writes:
> You may be right, but I guess that I'm not alone using Windows 8, so my
> performance observations must be shared by others as well. It may even be
> worse for some who have more Org files, and a less powerful computer.

Take Emacs and Org out of the picture and check how fast you can open
random files.  That will tell you if the performance degradation you see
is caused (at least in part) by those low-level operations.  I've had
two incidents the past year where some group policy changes done by IT
would result in a file-open time of close to two seconds (no joke).  Now
imagine what happens when you need to open some 10k files…

As to how Org implements its agenda operations: I don't know and I don't
have a comment.


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

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: How to improve Org startup time?

[Bastien]

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> However, I've left it in the `org-finalize-agenda-hook' hook, so that the
> `appt-list' is fed up as soon as I begin using agenda functions.

But then org-agenda-to-appt will be called each time your generate
a new agenda... not sure you really want this right.

Why not simply calling it interactively when you need it?

-- 
 Bastien

Re: How to improve Org startup time?

[Sebastien Vauban]

Bastien,

Bastien wrote:
> "Sebastien Vauban" writes:
>
>> However, I've left it in the `org-finalize-agenda-hook' hook, so that the
>> `appt-list' is fed up as soon as I begin using agenda functions.
>
> But then org-agenda-to-appt will be called each time your generate
> a new agenda... not sure you really want this right.
>
> Why not simply calling it interactively when you need it?

I can't count on myself to do it at a regular enough interval (at least
daily).

Then, this is the only (?) solution found so that the appt-list is still quite
up-to-date.

This is how Bernt does it as well in his tutorial:

  http://doc.norang.ca/org-mode.html#Reminders

Best regards,
  Seb

-- 
Sebastien Vauban

Re: How to improve Org startup time?

[Eric S Fraga]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>
> The timestamp stuff comes from EmacsWiki:
>
> #+begin_src emacs-lisp
>   (defadvice message (before when-was-that activate)
>     "Add timestamps to `message' output."
>     (ad-set-arg 0 (concat (format-time-string "[%Y-%m-%d %T] ")
>                           (ad-get-arg 0))))
> #+end_src
>
> The "call tree" between packages is originally written by me:
> [...]

Thanks!  Very useful.
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-917-gb9c506

Re: How to improve Org startup time?

[Eric S Fraga]

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> Hi Eric,
>

[...]

> Dividing the figures by 50, just for the disks, seems too big for me, nope?

Hi Seb, yes, it does seem dramatic.

> Just to be sure: are you sure that, in this last test, `org-agenda-to-appt'
> was called without having first opening the agenda files?

Ummm, I thought I was sure but I have just done it again and get
different results so I must have done something wrong in the last
test.  Ooops...  Doing it again, using this procedure:

- start emacs
- M-x elp-instrument-package RET org-agenda RET
- M-x org-agenda-to-apt RET
- M-x elp-results
- quit emacs

now gives me

| org-agenda-to-appt         |   1 |  1.602924479 |  1.602924479 |
| org-agenda-prepare-buffers |   1 |  1.510812568 |  1.510812568 |
| org-agenda-get-day-entries |  14 |  0.088741138 | 0.0063386527 |
| org-agenda-get-scheduled   |  14 |  0.027990309 | 0.0019993077 |
| org-agenda-get-deadlines   |  14 | 0.0154423710 | 0.0011030265 |
| org-agenda-skip            | 797 |  0.008103603 | 1.016...e-05 |

so the reduction is not quite as dramatic (factor of 5, not 50).


-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3d-917-gb9c506

Re: How to improve Org startup time?

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> - start emacs
> - M-x elp-instrument-package RET org-agenda RET
> - M-x org-agenda-to-apt RET
> - M-x elp-results
> - quit emacs
> 
> now gives me
> 
> | org-agenda-to-appt         |   1 |  1.602924479 |  1.602924479 |
> | org-agenda-prepare-buffers |   1 |  1.510812568 |  1.510812568 |
> | org-agenda-get-day-entries |  14 |  0.088741138 | 0.0063386527 |
> | org-agenda-get-scheduled   |  14 |  0.027990309 | 0.0019993077 |
> | org-agenda-get-deadlines   |  14 | 0.0154423710 | 0.0011030265 |
> | org-agenda-skip            | 797 |  0.008103603 | 1.016...e-05 |
> 
> so the reduction is not quite as dramatic (factor of 5, not 50).
> 
> 

That's roughly the kind of numbers I see as well.

Nick

Re: How to improve Org startup time?

[Tassilo Horn]

"Sebastien Vauban"
<wxhgmqzgwmuf@spammotel.com> writes:

>> But then org-agenda-to-appt will be called each time your generate
>> a new agenda... not sure you really want this right.
>>
>> Why not simply calling it interactively when you need it?
>
> I can't count on myself to do it at a regular enough interval (at least
> daily).
>
> Then, this is the only (?) solution found so that the appt-list is
> still quite up-to-date.

I call it once at emacs startup and then only when I save an agenda
file.

--8<---------------cut here---------------start------------->8---
(defun th-org-agenda-to-appt ()
  (org-agenda-to-appt t)
  (appt-activate 1))

(defun th-org-mode-init ()
  ;; ...
  (when (and (org-agenda-file-p)
	     (not (string= (file-name-nondirectory (buffer-file-name))
			   org-mobile-capture-file))
	     (not (string= (buffer-file-name)
			   org-mobile-inbox-for-pull)))
    (add-hook 'after-save-hook 'th-org-agenda-to-appt t t)))

(add-hook 'org-mode-hook 'th-org-mode-init)
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Tassilo,

Tassilo Horn wrote:
> "Sebastien Vauban" writes:
>
>>> But then org-agenda-to-appt will be called each time your generate a new
>>> agenda... not sure you really want this right.
>>>
>>> Why not simply calling it interactively when you need it?
>>
>> I can't count on myself to do it at a regular enough interval (at least
>> daily).
>>
>> Then, this is the only (?) solution found so that the appt-list is still
>> quite up-to-date.
>
> I call it once at emacs startup

I don't do it anymore, for not requiring Org libraries anymore, would I simply
fire up an Emacs for non-Org tasks (such as reading my mails with Gnus).

> and then only when I save an agenda file.

Pretty smart alternative (instead of doing it at every agenda build)...

> (defun th-org-agenda-to-appt ()
>   (org-agenda-to-appt t)
>   (appt-activate 1))

Why re-activating appt each time?  Why not simply once in your .emacs?

> (defun th-org-mode-init ()
>   ;; ...
>   (when (and (org-agenda-file-p)
> 	     (not (string= (file-name-nondirectory (buffer-file-name))
> 			   org-mobile-capture-file))
> 	     (not (string= (buffer-file-name)
> 			   org-mobile-inbox-for-pull)))
>     (add-hook 'after-save-hook 'th-org-agenda-to-appt t t)))
>
> (add-hook 'org-mode-hook 'th-org-mode-init)

*I* don't understand why you put the addition to `after-save-hook' inside a
complex when about some type of file. Your `after-save-hook' is global, right?

Would something like the following not be sufficient -- eventually put in an
`(eval-after-load "org")'...?

#+begin_src emacs-lisp
  (add-hook 'after-save-hook
            (lambda ()
              (when (and (eq major-mode 'org-mode)
                         (org-agenda-file-p))
                (org-agenda-to-appt))))
#+end_src

Best regards,
  Seb

--
Sebastien Vauban

Re: How to improve Org startup time?

[Memnon Anon]

"Sebastien Vauban"
<wxhgmqzgwmuf@spammotel.com> writes:
> Bastien wrote:
>> "Sebastien Vauban" writes:
>>
>>> However, I've left it in the `org-finalize-agenda-hook' hook, so that the
>>> `appt-list' is fed up as soon as I begin using agenda functions.
>>
>> But then org-agenda-to-appt will be called each time your generate
>> a new agenda... not sure you really want this right.
>>
>> Why not simply calling it interactively when you need it?
>
> I can't count on myself to do it at a regular enough interval (at least
> daily).
>
> Then, this is the only (?) solution found so that the appt-list is still quite
> up-to-date.

I am using the same setup (thanks Bernt :):
- Initialize on Startup
- Update on midnight for next day with run-at-time
- Update frequently via org-finalize-agenda-hook

The last piece eats up quite some time (couple of seconds on my ancient
machine), so what about a different solution just for the last bit. 
E.g., updating, when an item gets scheduled/timestamped for today.

Something like (pseudo code!):

(defadvice org-schedule (after my-adv-update-appt activate)
  "org-agenda-to-appt when org-last-timestamp todayp"
  (when (= (time-to-days 
	     (org-time-string-to-time org-last-inserted-timestamp))
	    (org-today))

    (message "Updating appt!")
    (org-agenda-to-appt)))

(defadvice org-time-stamp (after my-adv-update-appt activate)
  "org-agenda-to-appt when org-last-timestamp todayp"
  (when (= (time-to-days 
	     (org-time-string-to-time org-last-inserted-timestamp))
	    (org-today))

    (message "Updating appt!")
    (org-agenda-to-appt)))

Would that work?
I agree, calling it interactively feels error prone and I would probably
forget it ... 

Memnon

Re: How to improve Org startup time?

[Sebastien Vauban]

Hi Memnon,

Memnon Anon wrote:
> "Sebastien Vauban" writes:
>> Bastien wrote:
>>> "Sebastien Vauban" writes:
>>>
>>>> However, I've left it in the `org-finalize-agenda-hook' hook, so that the
>>>> `appt-list' is fed up as soon as I begin using agenda functions.
>>>
>>> But then org-agenda-to-appt will be called each time your generate
>>> a new agenda... not sure you really want this right.
>>>
>>> Why not simply calling it interactively when you need it?
>>
>> I can't count on myself to do it at a regular enough interval (at least
>> daily).
>>
>> Then, this is the only (?) solution found so that the appt-list is still quite
>> up-to-date.
>
> I am using the same setup (thanks Bernt :):
> - Initialize on Startup
> - Update on midnight for next day with run-at-time
> - Update frequently via org-finalize-agenda-hook
>
> The last piece eats up quite some time (couple of seconds on my ancient
> machine), so what about a different solution just for the last bit.

That's another way of thinking out of the box.

> E.g., updating, when an item gets scheduled/timestamped for today.
>
> Something like (pseudo code!):
>
> (defadvice org-schedule (after my-adv-update-appt activate)
>   "org-agenda-to-appt when org-last-timestamp todayp"
>   (when (= (time-to-days 
> 	     (org-time-string-to-time org-last-inserted-timestamp))
> 	    (org-today))
>
>     (message "Updating appt!")
>     (org-agenda-to-appt)))
>
> (defadvice org-time-stamp (after my-adv-update-appt activate)
>   "org-agenda-to-appt when org-last-timestamp todayp"
>   (when (= (time-to-days 
> 	     (org-time-string-to-time org-last-inserted-timestamp))
> 	    (org-today))
>
>     (message "Updating appt!")
>     (org-agenda-to-appt)))
>
> Would that work?
> I agree, calling it interactively feels error prone and I would probably
> forget it ...

Not in my habits, as I more often use S-up than C-c C-s. OK, one could argue
that if I move a timestamp from one day (or more), there is certainly no hours
attached to it. Rigth. But a bit fragile.

In fact, not in general, as it happens sometimes that I type the keyword
SCHEDULED by hand.

And, in fact, your code would be called (much) more often than if the
org-agenda-to-appt is called when saving an Org agenda file, what was the
solution of Tassilo. Do you see drawbacks in his solution?

Best regards,
  Seb

-- 
Sebastien Vauban

[new exporter] ignoring a headline on export to PDF via latex

[Eric S Fraga]

Hello,

I used to use the following to ignore a headline when exporting to PDF:

#+begin_src emacs-lisp
(defun my-e-latex-headline (headline contents info)
  (if (member "ignoreheading" (org-element-property :tags headline)) contents
    (org-latex-headline headline contents info)))
(add-to-list 'org-latex-translate-alist '(headline . my-e-latex-headline))
#+end_src

With the new exporter, this no longer works.

On the mailing list, I found this thread from a couple of months ago:

http://comments.gmane.org/gmane.emacs.orgmode/62742

but I do not want to create a new backend just for this.  Is there an
equivalent solution to the above with the new exporter?  Nicolas, you do
imply that there is but you leave it as an exercise for the reader.  As
much as I appreciate the pedagogical nature of your response, this
reader is not up to the task and a solution would be greatly
appreciated!

Thanks,
eric

-- 
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)

Re: [new exporter] ignoring a headline on export to PDF via latex

[Suvayu Ali]

On Tue, Mar 05, 2013 at 02:43:30PM +0000, Eric S Fraga wrote:
> Hello,
> 
> I used to use the following to ignore a headline when exporting to PDF:
> 
> #+begin_src emacs-lisp
> (defun my-e-latex-headline (headline contents info)
>   (if (member "ignoreheading" (org-element-property :tags headline)) contents
>     (org-latex-headline headline contents info)))
> (add-to-list 'org-latex-translate-alist '(headline . my-e-latex-headline))
> #+end_src
> 
> With the new exporter, this no longer works.
> 

Try using your function with a filter.  This filter might work:
org-export-filter-headline-functions.  Of course it goes without saying
you will have to update your function.

A very simple test tells me this is probably going to be backend
specific.  I have had this query about filters for a while now, how to
write filters that are backend agnostic.  I think I'll start a new
thread once I have formulated my question more clearly.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [new exporter] ignoring a headline on export to PDF via latex

[Eric S Fraga]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

[...]

> Try using your function with a filter.  This filter might work:
> org-export-filter-headline-functions.  Of course it goes without saying
> you will have to update your function.

Thanks Suvayu.  It is this update that I need help with!  The
documentation of that variable is close to impenetrable to me (e.g. what
is a /communication channel/?).

I can manage without this feature for the moment so I'm not panicking
but I do hope to find a solution eventually.

Thanks again,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55

Re: [new exporter] ignoring a headline on export to PDF via latex

[Nick Dokos]

Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> [...]
> 
> > Try using your function with a filter.  This filter might work:
> > org-export-filter-headline-functions.  Of course it goes without saying
> > you will have to update your function.
> 
> Thanks Suvayu.  It is this update that I need help with!  The
> documentation of that variable is close to impenetrable to me (e.g. what
> is a /communication channel/?).
> 

Reading the commentary in ox.el might help, at least to shed light on
some terminology.

Nick

> I can manage without this feature for the moment so I'm not panicking
> but I do hope to find a solution eventually.
> 
> Thanks again,
> eric
> -- 
> : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
> : in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55
> 
> 

Re: [new exporter] ignoring a headline on export to PDF via latex

[Suvayu Ali]

On Tue, Mar 05, 2013 at 01:25:03PM -0500, Nick Dokos wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> 
> > Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> > 
> > [...]
> > 
> > > Try using your function with a filter.  This filter might work:
> > > org-export-filter-headline-functions.  Of course it goes without saying
> > > you will have to update your function.
> > 
> > Thanks Suvayu.  It is this update that I need help with!  The
> > documentation of that variable is close to impenetrable to me (e.g. what
> > is a /communication channel/?).
> > 
> 
> Reading the commentary in ox.el might help, at least to shed light on
> some terminology.

As far as know, it is a property list returned by the parser.  Look in
lisp/ox.el:1094.  Beyond that my understanding is also a bit hazy.  I
think I have gone through that bit of the comments at least once, but it
is a little difficult to follow for me (my lack of understanding of lisp
is probably to blame :-p).

Good Luck,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [new exporter] ignoring a headline on export to PDF via latex

[Charles Berry]

Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:

> 
> On Tue, Mar 05, 2013 at 01:25:03PM -0500, Nick Dokos wrote:
> > Eric S Fraga <e.fraga <at> ucl.ac.uk> wrote:
> > 
> > > Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:
> > > 
> > > [...]
> > > 
> > > > Try using your function with a filter.  This filter might work:
> > > > org-export-filter-headline-functions.  Of course it goes without saying
> > > > you will have to update your function.
> > > 
> > > Thanks Suvayu.  It is this update that I need help with!  The
> > > documentation of that variable is close to impenetrable to me (e.g. what
> > > is a /communication channel/?).
> > > 
> > 
> > Reading the commentary in ox.el might help, at least to shed light on
> > some terminology.
> 
> As far as know, it is a property list returned by the parser.  Look in
> lisp/ox.el:1094.  Beyond that my understanding is also a bit hazy.  I
> think I have gone through that bit of the comments at least once, but it
> is a little difficult to follow for me (my lack of understanding of lisp
> is probably to blame :-p).

If you just want the latex to have "\section{}" you can do this


#+BEGIN_SRC emacs-lisp
  (defun org-latex-ignore-heading-filter-headline
    (headline backend info)
    "Strip headline from HEADLINE. Ignore BACKEND and INFO."
    (replace-regexp-in-string
     "^[\\]section\\[.*\\textsc{ignoreheading}}$"
     "\\section{}" headline nil t))
#+END_SRC

#+BEGIN_SRC emacs-lisp
  (require 'ox-latex)
  (org-export-define-derived-backend latex3 latex
    :filters-alist (
                    (:filter-headline . org-latex-ignore-heading-filter-headline))) 
#+END_SRC


then (org-export-to-buffer 'latex3 "a-buffer-name")

should do it.


The so-called 'headline' is actually a lot more than I would have thought.

If you use this filter instead:

#+BEGIN_SRC emacs-lisp
  (defun filter-headline-show
    (text back-end info)
    (format "<hdln>%s</hdln>" text))
#+END_SRC

you will see that the headline --- enclosed in 

   <hdln> .... <\hdln>

will typically contain within it an entire "section" (in exporter
`:filter-section' terms - not latex's \section{})

FWIW, I defun'ed filters like the above for all of the filter functions that can
take (text backend info) as arguments. Then using a derived backend like the
above `latex3', I can see where the filterable elements are. It is trivial to
do, but if anyone is interested, I can post or upload somewhere.

Chuck

Re: [new exporter] ignoring a headline on export to PDF via?latex

[Suvayu Ali]

On Tue, Mar 05, 2013 at 08:58:28PM +0000, Charles Berry wrote:

[...]

> FWIW, I defun'ed filters like the above for all of the filter functions that can
> take (text backend info) as arguments. Then using a derived backend like the
> above `latex3', I can see where the filterable elements are. It is trivial to
> do, but if anyone is interested, I can post or upload somewhere.

That would be wonderful!

You could put them up on Worg.  This section on org-hacks would be
appropriate: <http://orgmode.org/worg/org-hacks.html#sec-1-10>.  If you
do not have access to Worg, you can post the content in Org format on
the list and I can add it.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [new exporter] ignoring a headline on export to PDF via latex

[Nicolas Goaziou]

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> [...]
>
>> Try using your function with a filter.  This filter might work:
>> org-export-filter-headline-functions.  Of course it goes without saying
>> you will have to update your function.
>
> Thanks Suvayu.  It is this update that I need help with!  The
> documentation of that variable is close to impenetrable to me 

A TYPE filter is called each time transcoding process is over of an
element of type TYPE. Here, each time a headline is transcoded (along
with its contents), functions in `org-export-filter-headline-functions'
are called with the resulting string as the first argument (i.e. the
LaTeX code for the headline and all its contents).

There's a filter for each type of element/object, and a couple of
special filters.

> (e.g. what is a /communication channel/?).

The communication channel is basically a plist containing data available
for all transcoding functions. 99% of its properties have constant
values during export process (like export options, or pre-computed
values from the parse tree).

Nevertheless, it can be used to store some data at some point in time
and retrieve it from another transcoding function later, effectively
allowing communication between parts of the export system.


Regards,

-- 
Nicolas Goaziou

Re: [new exporter] ignoring a headline on export to PDF via latex

[Nicolas Goaziou]

Hello,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I used to use the following to ignore a headline when exporting to PDF:
>
> #+begin_src emacs-lisp
> (defun my-e-latex-headline (headline contents info)
>   (if (member "ignoreheading" (org-element-property :tags headline)) contents
>     (org-latex-headline headline contents info)))
> (add-to-list 'org-latex-translate-alist '(headline . my-e-latex-headline))
> #+end_src
>
> With the new exporter, this no longer works.
>
> On the mailing list, I found this thread from a couple of months ago:
>
> http://comments.gmane.org/gmane.emacs.orgmode/62742
>
> but I do not want to create a new backend just for this.  Is there an
> equivalent solution to the above with the new exporter?  Nicolas, you do
> imply that there is but you leave it as an exercise for the reader.  As
> much as I appreciate the pedagogical nature of your response, this
> reader is not up to the task and a solution would be greatly
> appreciated!

Indeed, this won't work anymore: `org-latex-translate-alist' has been
removed. The equivalent would just be to use a defadvice:

#+begin_src emacs-lisp
(defadvice org-latex-headline (around my-latex-skip-headlines
                                      (headline contents info) activate)
  (if (member "ignoreheading" (org-element-property :tags headline))
      (setq ad-return-value contents)
    ad-do-it))
#+end_src

Another approach is, as mentioned by Charles Berry, to remove the first
line of transcoded headline when it contains "ignoreheading".

#+begin_src emacs-lisp
(defun org-latex-ignore-heading-filter-headline (headline backend info)
    "Strip headline from HEADLINE. Ignore BACKEND and INFO."
    (when (and (org-export-derived-backend-p backend 'latex)
               (string-match "\\`.*ignoreheading.*\n" headline))
      (replace-match "" nil nil headline)))
(add-to-list 'org-export-filter-headline-functions
             'org-latex-ignore-heading-filter-headline)
#+end_src


Regards,

-- 
Nicolas Goaziou

Re: [new exporter] ignoring a headline on export to PDF via?latex

[Charles Berry]

Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:

> 
> On Tue, Mar 05, 2013 at 08:58:28PM +0000, Charles Berry wrote:
> 
> [...]
> 
> > FWIW, I defun'ed filters like the above for all of the filter functions

[...]

> > if anyone is interested, I can post or upload somewhere.
> 
> That would be wonderful!
> 
> You could put them up on Worg.  This section on org-hacks would be
> appropriate: <http://orgmode.org/worg/org-hacks.html#sec-1-10>.  If you
> do not have access to Worg, you can post the content in Org format on
> the list and I can add it.

I added to org-hacks.org at the bottom of ** Exporting org files. I tried to
push to worg but got a permission error - its been years since I last pushed
anything, so something on my end probably needs to be updated.

I've posted the file at:

https://raw.github.com/chasberry/orgmode-accessories/master/filter-markup.org

If you would like to put it in org-hacks, I'd appreciate it.

Re: [new exporter] ignoring a headline on export to PDF via latex

[Eric S Fraga]

Charles Berry <ccberry@ucsd.edu> writes:

[...]

> If you just want the latex to have "\section{}" you can do this

[...]

Chuck,

thanks for this.  It makes sense and I will give it a try.  This
approach still does require creating a new backend.  The implications of
this are not clear to me but I will play with this to see.

Thanks again,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55

Re: [new exporter] ignoring a headline on export to PDF via latex

[Eric S Fraga]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

[...]

> Indeed, this won't work anymore: `org-latex-translate-alist' has been
> removed. The equivalent would just be to use a defadvice:
>
> #+begin_src emacs-lisp
> (defadvice org-latex-headline (around my-latex-skip-headlines
>                                       (headline contents info) activate)
>   (if (member "ignoreheading" (org-element-property :tags headline))
>       (setq ad-return-value contents)
>     ad-do-it))
> #+end_src
>
> Another approach is, as mentioned by Charles Berry, to remove the first
> line of transcoded headline when it contains "ignoreheading".
>
> #+begin_src emacs-lisp
> (defun org-latex-ignore-heading-filter-headline (headline backend info)
>     "Strip headline from HEADLINE. Ignore BACKEND and INFO."
>     (when (and (org-export-derived-backend-p backend 'latex)
>                (string-match "\\`.*ignoreheading.*\n" headline))
>       (replace-match "" nil nil headline)))
> (add-to-list 'org-export-filter-headline-functions
>              'org-latex-ignore-heading-filter-headline)
> #+end_src

Nicolas,

this is exactly what I was looking for.  It works perfectly.  Many thanks!

eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55

Re: [new exporter] ignoring a headline on export to PDF?via?latex

[Suvayu Ali]

Hi Charles,

On Wed, Mar 06, 2013 at 07:11:48AM +0000, Charles Berry wrote:
> I added to org-hacks.org at the bottom of ** Exporting org files. I tried to
> push to worg but got a permission error - its been years since I last pushed
> anything, so something on my end probably needs to be updated.
> 

You probably your keys were not moved to the new machine that hosts
Worg.  An email to Bastien and/or Jason should fix that.

> I've posted the file at:
> 
> https://raw.github.com/chasberry/orgmode-accessories/master/filter-markup.org
> 
> If you would like to put it in org-hacks, I'd appreciate it.

I had missed your email, I put your writeup with some minor formatting
changes under the new exporters directory on Worg.  Please have a look
and let me know if they are in order.

<http://orgmode.org/worg/exporters/>
<http://orgmode.org/worg/exporters/filter-markup.html>

Here are the commits:

<http://orgmode.org/cgit.cgi/worg.git/commit/?id=0ae0f97db6ac6c3ca7cc94001a442e54c2d1d3d9>
<http://orgmode.org/cgit.cgi/worg.git/commit/?id=ce62735fd8298c8924f76098d768db42b53f155b>

Thanks a lot for your contribution.

:)

-- 
Suvayu

Open source is the future. It sets us free.

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Bastien]

Hi Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> This leads me to suggest that both cases (dvipng
> and imagemagick) use the same latex code and, in fact, it may be
> possible to fold both functions org-create-formula-image-with-dvipng and
> org-create-formula-image-with-imagemagick into one...

I would welcome such a refactoring, because there is obviously some
redundancy here.  But I felt too lazy to tackle this so far, and I
guess I won't be tackling this before long.  So the door is open for
anyone to enter!

Best,

-- 
 Bastien

Re: [bug] latex fragment preview with dvipng ignores :foreground specification

[Eric S Fraga]

Bastien <bzg@gnu.org> writes:

> Hi Eric,
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> This leads me to suggest that both cases (dvipng
>> and imagemagick) use the same latex code and, in fact, it may be
>> possible to fold both functions org-create-formula-image-with-dvipng and
>> org-create-formula-image-with-imagemagick into one...
>
> I would welcome such a refactoring, because there is obviously some
> redundancy here.  But I felt too lazy to tackle this so far, and I
> guess I won't be tackling this before long.  So the door is open for
> anyone to enter!
>
> Best,

Bastien,

I will put this on my todo list and will try to find the requisite Emacs
lisp expertise from within to accomplish this task!

Thanks,
eric


-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.1-19-g9655a1