Re: [O] [patch] Typo in org-e-texinfo.el

2012-11-11 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 Patch attached.

Applied. Thank you.


Regards,

-- 
Nicolas Goaziou



Re: [O] [New exporter][texinfo] noexport tag ignored

2012-11-11 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 #+TITLE: export-test.org
 #+AUTHOR:Thomas Dye
 #+EMAIL: t...@tsdye.com
 #+DATE:  2012-11-10 Sat
 #+DESCRIPTION: #+KEYWORDS:
 #+LANGUAGE:  en
 #+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
 #+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 
 path:http://orgmode.org/org-info.js
 #+SELECT_TAGS: export
 #+EXCLUDE_TAGS: noexport
 #+LINK_UP:   
 #+LINK_HOME: 
 #+XSLT:

 * Export

 * Do not export:noexport:

 Exports:

 ...

 @menu
 * Export::   
 * Do not export::

 @end menu

 ...

This should be fixed now. Thank you for reporting it.


Regards,

-- 
Nicolas Goaziou



Re: [O] Suggestions for progress tracking

2012-11-11 Thread Ian Barton

On 11/11/12 03:48, Eric Abrahamsen wrote:

David Rogers davidandrewrog...@gmail.com writes:


Eric Abrahamsen e...@ericabrahamsen.net writes:


I'm starting another novel translation, and want to keep track of
progress in org (I've blown too many deadlines in the past). I've been
looking at the habits functionality, but it doesn't quite match what I
want, and I'm looking for a little advice here. I'd like to:

1. Set myself a minimum of pages translated per day, on weekdays.
2. Record how many pages I do each day.
3. View some habit-style report of how I'm doing relative to my goal.
4. Project when I will be done with the novel at the current rate of
progress.



I am assuming that the novel is available in plain text. Why not turn it 
into an org file. Divide it up into units, with each unit being a day's 
worth of translation. Make each unit a separate TODO with either a 
SCHEDULED or DEADLINE. The you can use the Agenda to see how far in 
front, or behind, you are.


Ian.





[O] (no subject)

2012-11-11 Thread Fabrice Popineau
I just updated a few hours ago with the git current version and I now get:

Debugger entered--Lisp error: (invalid-read-syntax #)
  eval-buffer(#buffer  *load* nil c:/Home/.org-timestamps/CQP-org.cache
nil t)  ; Reading at buffer position 621
  load-with-code-conversion(c:/Home/.org-timestamps/CQP-org.cache
c:/Home/.org-timestamps/CQP-org.cache nil nil)
  load(c:/Home/.org-timestamps/CQP-org.cache nil nil t)
  load-file(c:/Home/.org-timestamps/CQP-org.cache)

Actually, the .cache file reads :

...
(puthash c:/Home/Cours/CQP-ArTech/org/CQP-Artech-slides.org '(:title
#(CQP-ArTech Slides 0 17 (:parent (#(CQP-ArTech Slides 0 17 (:parent
#3)) org-e-publish-cache)
...

I guess the #3 is the culprit. Any idea what went wrong?

Fabrice


[O] org-entities for texinfo

2012-11-11 Thread Thomas S. Dye
Aloha all,

With the new exporter's texinfo back-end, I think org-entities and
org-entities-user might usefully be augmented with the entities listed
in Chapter 14 of the texinfo manual, Special Insertions.

Or, is there some other Org mechanism that might be preferable?  

All the best,
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



Re: [O] org-entities for texinfo

2012-11-11 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 With the new exporter's texinfo back-end, I think org-entities and
 org-entities-user might usefully be augmented with the entities listed
 in Chapter 14 of the texinfo manual, Special Insertions.

 Or, is there some other Org mechanism that might be preferable?

AFAIU, texinfo can handle UTF-8 characters with:

  @documentencoding UTF-8

(see section 18.2 from texinfo manual). So I guess it's safe to rely
on :utf-8 entities.

However, special characters like @dots{} are usually handled with
special strings mechanism, directly at the plain text transcoded (see
`org-e-latex-plain-text' for example).


Regards,

-- 
Nicolas Goaziou



[O] [new exporter][texinfo] Macro definition section

2012-11-11 Thread Thomas S. Dye
Aloha all,

The texinfo source for the Org manual has a number of macro definitions
for commands and keys between the end of the header (@finalout) and the
beginning of the Copying section.

The texinfo back-end for the new exporter doesn't have a slot here and
I'm wondering if it needs one?  

All the best,
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



Re: [O] orgmode html export - cygwin - browser

2012-11-11 Thread Manish
On Tue, Nov 6, 2012 at 10:50 PM, Jan-Mark Batke bad...@gmx.net wrote:

 Dear all,
 when exporting to html and starting a browser, I encounter the problem my
 browser cannot find the file. I am using win xp and run emacs inside
 cygwin. Therefore the exported path send to the browser is:

 file:///cygdrive/c/path/file.html

 Since the browser is running natively (outside cygwin), it expects

 file:///c:/path/file.html

 Is it possible to adapt the export path?



 Or is a cygwin browser mandatory anyway (I would like to avoid that)?


can you please help understand/rephrase this last line?

cheers!
--manish


Re: [O] [ANN] e-icalendar back-end

2012-11-11 Thread Simon Thum

Hi,

just tested and it seems to work fine.

A glitch: Unlike the other functions, I could not get 
org-e-icalendar-export-current-agenda to auto-complete in M-x and it 
also did not produce meaningful results (empty icalendar).


What I'm missing is the ability to influence the amount of information 
diclosed for a public calendar. But 'll hack on this myself and come 
back eventually.


Thanks for this nice exporter!

Cheers,

Simon


On 11/03/2012 12:48 AM, Nicolas Goaziou wrote:

Hello,

I've just pushed a new (and probably very buggy) iCalendar back-end for
org-export.el.

To install it:

 (require 'org-e-icalendar)

It should then be available under `org-export-dispatch' menu.

There's also a function to write current agenda view to a calendar, but
it isn't hooked into `org-agenda-write' yet. For now, you can test it,
from an agenda buffer, with:

 M-: (org-e-icalendar-export-current-agenda)


Feedback is welcome.


Regards,






Re: [O] [ANN] e-icalendar back-end

2012-11-11 Thread Nicolas Goaziou
Hello,

Simon Thum simon.t...@gmx.de writes:

 just tested and it seems to work fine.

Thanks for testing it.

 A glitch: Unlike the other functions, I could not get
 org-e-icalendar-export-current-agenda to auto-complete in M-x

That's correct. `org-e-icalendar-export-current-agenda' isn't meant to
be a command. It will be called internally by `org-agenda-write' (C-x
C-w from an agenda buffer). Though, for now, it isn't since
org-icalendar.el is still current icalendar back-end.

 and it also did not produce meaningful results (empty icalendar).

Make sure to call it from an agenda buffer. Also, you may want to check
`org-e-icalendar-include-todo' variable if your agenda view only
contains TODO entries.

 What I'm missing is the ability to influence the amount of information
 diclosed for a public calendar. But 'll hack on this myself and come
 back eventually.

You can tweak `org-e-icalendar-include-body' (i.e. set it to nil).


Regards,

-- 
Nicolas Goaziou



Re: [O] [ANN] e-icalendar back-end

2012-11-11 Thread Simon Thum

On 11/11/2012 10:12 PM, Nicolas Goaziou wrote:

Hello,

Simon Thumsimon.t...@gmx.de  writes:


just tested and it seems to work fine.


Thanks for testing it.


A glitch: Unlike the other functions, I could not get
org-e-icalendar-export-current-agenda to auto-complete in M-x


That's correct. `org-e-icalendar-export-current-agenda' isn't meant to
be a command. It will be called internally by `org-agenda-write' (C-x
C-w from an agenda buffer). Though, for now, it isn't since
org-icalendar.el is still current icalendar back-end.


and it also did not produce meaningful results (empty icalendar).


Make sure to call it from an agenda buffer. Also, you may want to check
`org-e-icalendar-include-todo' variable if your agenda view only
contains TODO entries.


What I'm missing is the ability to influence the amount of information
diclosed for a public calendar. But 'll hack on this myself and come
back eventually.


You can tweak `org-e-icalendar-include-body' (i.e. set it to nil).
I saw there are some knobs but I'm looking for more felixble soultions, 
e.g. sth like org-icalendar-verify-function. Also body suggests the 
headline is kept, which is too much for simply indicating availability.


But for now I'm content to get my phone to grasp the ical...

Thanks,

Simon






Regards,






Re: [O] [ANN] e-icalendar back-end

2012-11-11 Thread Nicolas Goaziou
Simon Thum simon.t...@gmx.de writes:

 I saw there are some knobs but I'm looking for more felixble
 soultions, e.g. sth like org-icalendar-verify-function.

I removed this variable since I didn't need it in the new back-end.
Nevertheless, hooks and filters from org-export.el provide the same
functionality, so you shouldn't be missing anything.


Regards,

-- 
Nicolas Goaziou



Re: [O] orgmode html export - cygwin - browser

2012-11-11 Thread Jan-Mark Batke
2012/11/11 Manish mailtomanish.sha...@gmail.com

 On Tue, Nov 6, 2012 at 10:50 PM, Jan-Mark Batke bad...@gmx.net wrote:

 Dear all,
 when exporting to html and starting a browser, I encounter the problem my
 browser cannot find the file. I am using win xp and run emacs inside
 cygwin. Therefore the exported path send to the browser is:

 file:///cygdrive/c/path/file.html

 Since the browser is running natively (outside cygwin), it expects

 file:///c:/path/file.html

 Is it possible to adapt the export path?



 Or is a cygwin browser mandatory anyway (I would like to avoid that)?


 can you please help understand/rephrase this last line?


Well, a cygwin browser would expect (and understand) a file locator like
file:///cygdrive/c/file.html (I guess), whereas chrome wants to see the
same but c: instead of cygdrive/c

I am wondering if anybody here is using cygwin ...

Best

Jan-Mark



 cheers!
 --manish





-- 
Jan-Mark Batke  bad...@gmx.net
FON +49 511 33 64 800
FAX +49 511 22 09 521


Re: [O] (no subject)

2012-11-11 Thread Nicolas Goaziou
Hello,

Fabrice Popineau fabrice.popin...@gmail.com writes:

 I just updated a few hours ago with the git current version and I now get:

 Debugger entered--Lisp error: (invalid-read-syntax #)
   eval-buffer(#buffer  *load* nil c:/Home/.org-timestamps/CQP-org.cache
 nil t)  ; Reading at buffer position 621
   load-with-code-conversion(c:/Home/.org-timestamps/CQP-org.cache
 c:/Home/.org-timestamps/CQP-org.cache nil nil)
   load(c:/Home/.org-timestamps/CQP-org.cache nil nil t)
   load-file(c:/Home/.org-timestamps/CQP-org.cache)

 Actually, the .cache file reads :

 ...
 (puthash c:/Home/Cours/CQP-ArTech/org/CQP-Artech-slides.org '(:title
 #(CQP-ArTech Slides 0 17 (:parent (#(CQP-ArTech Slides 0 17 (:parent
 #3)) org-e-publish-cache)
 ...

 I guess the #3 is the culprit. Any idea what went wrong?

To sum it up, I added :parent property to each string but org-e-publish
tries to store them in the cache, which is impossible since cache is
eventually written to a file.

I have pushed a fix for that problem. Is it correct now?

Thanks for submitting this.


Regards,

-- 
Nicolas Goaziou



[O] Bug: Exporting table with footnote to LaTeX [7.9.2]

2012-11-11 Thread Bill Jackson
When exporting to LaTeX, any footnotes inside a table are missing the
closing curly brace.

For example, a footnote such as:

   | Field 1[fn:: A footnote.] | Field 2 |

is exported to LaTeX as:

\begin{center}
\begin{tabular}{l}
 Field 1\footnote{A footnote.  \\
\end{tabular}
\end{center}

Note that the closing curly brace is missing from the footnote.

The code for generating the LaTeX appears to be in org-latex.el at line
2,463, and looks correct to me.  Perhaps the closing brace is removed later?


Re: [O] How to customize the heading definition in org-mode

2012-11-11 Thread Darlan Cavalcante Moreira
At Sat, 10 Nov 2012 07:58:40 -0800,
David Rogers wrote:

But for this specific need (organizing the Emacs configuration with
org-mode), there is really no need for changing the headline
definition. You instead change your Emacs configuration to 'real' org-mode
files with the actual configuration inside Emacs-lisp src blocks. This is
much more powerful. As Memnon Anon mentioned, you only need a minimal
configuration in your init.el file and the rest can go all in one or more
org files that you load with org-babel-load-file.

I have converted my configuration to an org-mode file a good time ago and I
can tell you it is VERY worth the time invested. You can benefit from all
org-mode features. What org-babel-load-file does is tangling all of the
Emacs-lisp src blocks (only emacs-lisp blocks) to an Emacs lisp file and
then load that file. The org-babel-load-file function is smart enough to
only tangle the org file if something has changed. Therefore the delay
caused by the tangle process only happens when you change something.

A bonus side effect of this tangling process is that you can disable a
whole part of your Emacs configuration easily simple by setting the
'TANGLE' property of a headline containing the source blocks you want to
disable to 'no'.

--
Darlan

 
 On Sat, 10 Nov 2012 10:38:41 + (UTC)
 Memnon Anon gegendosenflei...@googlemail.com wrote:
 
  Avner Moshkovitz avnermoshkov...@lighthausvci.com writes:
 
   I looked for an equivalent to this in org-mode but couldn't find a
   way to customize the heading definition.
  
   Is there a way to do so?
  
  AFAIK, the * is a fixed part of the org syntax and is not
  customizable.
 
 Yes, there was a discussion here not so long ago - the result of the
 discussion was (and I'm only paraphrasing) It's true there is no way to
 change it, and we're intentionally keeping it that way to prevent
 needless complexity in org-mode.
 
 -- 
 David
 



[O] Indenting into lists

2012-11-11 Thread William Léchelle
Hi list,

I often structure notes into (multi-level) lists, and copy-paste multi-line
text into them, some of which gets pasted on column zero. For it to be part of
the list item, it needs to be indented as such, which I'd like tab to do.

  ┏[ tab runs the command org-cycle ]
  ┃ When point is not at the beginning of a headline, execute the global binding
  ┃ for TAB, which is re-indenting the line.
  ┗

Problem is tab only indents to the first possible level, that is, until the
bullets, like so:

* heading
  - list item on
many lines
  HERE is not enough to be in the list.

So in order to achieve the desired behaviour, I have to press space and tab
alternatively until the line reaches where it belongs (for that combination
makes it be indented more and more), which becomes tedious when indenting a few
lines across nested lists.

Is there a better way to indent to the maximum point ?

(Could tab cycle between all indenting points, like is automagical in python ?
That would be truly awesome.)

Thanks in advance



Re: [O] (no subject)

2012-11-11 Thread Fabrice Popineau
Seems to be ok on my side.

I wonder if my problem could have been triggered by the fact I had a
spurious file in the way of the (new) exporter: I had a foo.org file
exported to some other directory, but also a foo.html in the source
directory that had to be copied to the target directory by another
dependency of the project.

Thanks anyway for taking care of this.

Fabrice


2012/11/12 Nicolas Goaziou n.goaz...@gmail.com

 Hello,

 Fabrice Popineau fabrice.popin...@gmail.com writes:

  I just updated a few hours ago with the git current version and I now
 get:
 
  Debugger entered--Lisp error: (invalid-read-syntax #)
eval-buffer(#buffer  *load* nil
 c:/Home/.org-timestamps/CQP-org.cache
  nil t)  ; Reading at buffer position 621
load-with-code-conversion(c:/Home/.org-timestamps/CQP-org.cache
  c:/Home/.org-timestamps/CQP-org.cache nil nil)
load(c:/Home/.org-timestamps/CQP-org.cache nil nil t)
load-file(c:/Home/.org-timestamps/CQP-org.cache)
 
  Actually, the .cache file reads :
 
  ...
  (puthash c:/Home/Cours/CQP-ArTech/org/CQP-Artech-slides.org '(:title
  #(CQP-ArTech Slides 0 17 (:parent (#(CQP-ArTech Slides 0 17 (:parent
  #3)) org-e-publish-cache)
  ...
 
  I guess the #3 is the culprit. Any idea what went wrong?

 To sum it up, I added :parent property to each string but org-e-publish
 tries to store them in the cache, which is impossible since cache is
 eventually written to a file.

 I have pushed a fix for that problem. Is it correct now?

 Thanks for submitting this.


 Regards,

 --
 Nicolas Goaziou