Re: [O] Classification of Org mode elements

2013-06-18 Thread Thomas S. Dye
Aloha Thorsten,

Thorsten Jolitz tjol...@gmail.com writes:

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

 Hi Thomas,

 The attached Org mode document contains some notes on the classification
 of Org mode elements that might be a useful addition to Nicolas
 Goaziou's draft Org syntax document
 (http://orgmode.org/worg/dev/org-syntax.org).

 It distinguishes nine classes of element and proposes names for them.  

 I really like the idea to make Nicolas decisions when modelling Org
 syntax more explicit and write them down as a quick reference overview.

Well, I'm just summarizing Nicolas' draft Org Syntax document.  I don't
think I've made anything more explicit than he does in that fine
document.  I'm glad you like the table. 

 I compressed your table a bit to make it fit on a screen/page

Much better, a real improvement.  Thanks!

 , and added
 a subtree for each element to the file that could contain a short
 (man-page like) descripton of syntax and semantics of that element (see
 my attempts for 'Property drawer' as an example). This should not
 compete with the manual or the cheat sheet, but rather serve as a
 minimal overview of the Org 8+ syntax elements.

My idea is to add the table to Nicolas' draft Org Syntax document, and
use the classes as the basis for editing and restructuring the document
a bit. Perhaps your subtrees would fit in, too?


 Right now I don't have the time to fill the other subtrees, but I might
 add to this the next days, maybe others can add to it too and then this
 file can be uploaded to Worg?

Yes, perhaps we could do that if Nicolas doesn't like the changes I have
in mind for the draft Org Syntax document.

Also, I'd like to see the Org Syntax document become an appendix to the
manual. I know some think that it is too developer-ish to be a part of
the manual, but it has helped me see Org Mode documents more clearly and
I think it might benefit others, as well.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com



[O] Bug: HTML export adds trailing junk characters for each line in source code block [8.0.3 (release_8.0.3-243-g0e3543 @ /Users/yuezhu/.emacs.d/el-get/org-mode/lisp/)]

2013-06-18 Thread Yue Zhu

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

 http://orgmode.org/manual/Feedback.html#Feedback

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


I am sending a bug report because in my machine the HTML export cannot
work correctly for code block (tested under C and Java). The problem is
that it adds several trailing junk characters for each line like
`#57344;#57345;#57345;', which are displayed as squares in the
Firefox 21.

Emacs  : GNU Emacs 24.3.1 (x86_64-apple-darwin12.3.0, NS apple-appkit-1187.37)
 of 2013-03-31 on teneight-slave.macports.org
Package: Org-mode version 8.0.3 (release_8.0.3-243-g0e3543 @ 
/Users/yuezhu/.emacs.d/el-get/org-mode/lisp/)

current state:
==
(setq
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-log-done 'time
 org-confirm-shell-link-function 'yes-or-no-p
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-from-is-user-regexp \\Yue Zhu\\
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[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)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-src-fontify-natively t
 org-publish-project-alist '((org-site :base-directory ~/Dropbox/Notes/org/ 
:base-extension
  org :publishing-directory 
~/Dropbox/Notes/html/ :recursive t
  :publishing-function org-html-publish-to-html 
:headline-levels 4
  :section-numbers nil :auto-preamble t 
:auto-postamble t :exclude
  private*)
 (org-static :base-directory 
~/Dropbox/Notes/org/
  :base-extension
  
css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf
  :publishing-directory ~/Dropbox/Notes/html/ 
:recursive t
  :publishing-function org-publish-attachment)
 (site :components (org-site org-static)))
 )



[O] [PATCH] minor patch to org-babel-load-file

2013-06-18 Thread Levin Du
Hi, all

I find org-babel-load-file not work for my emacs-starter-kit  org file.
After some traces, I find that

   (org-babel-merge-params nil nil nil)

returns:

   ((:comments . ) (:shebang . ) (:cache . ) (:padline . ) (:noweb
. ) (:tangle . ) (:exports . ) (:results . ))

which will override my default (:tangle yes) value in
org-babel-default-header-args
and org-babel-load-file simply don't tangle source blocks without :tangle
yes.

Below is the patch that solves this problem.

diff  a/lisp/ob-core.el b/lisp/ob-core.el
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2337,7 +2337,8 @@ parameters when merging lists.
  (lambda (hd)
(let ((key (intern (concat : (symbol-name hd
  (val (eval hd)))
- (setf params (cons (cons key (mapconcat 'identity val  )) params
+ (when val
+ (setf params (cons (cons key (mapconcat 'identity val  )) params)
  '(results exports tangle noweb padline cache shebang comments))
 params))

--
Best Regards,
Levin


Re: [O] [PATCH] minor patch to org-babel-load-file

2013-06-18 Thread Michael Brand
Hi Levin

On Tue, Jun 18, 2013 at 9:44 AM, Levin Du zsle...@gmail.com wrote:
 Below is the patch that solves this problem.

Recently I also noticed a regression of org-babel-load-file that is
resolved with your patch. Thank you for saving me of one of my TODOs.

Michael



Re: [O] Classification of Org mode elements

2013-06-18 Thread Suvayu Ali
On Mon, Jun 17, 2013 at 09:08:38PM -1000, Thomas S. Dye wrote:
 
 Also, I'd like to see the Org Syntax document become an appendix to the
 manual. I know some think that it is too developer-ish to be a part of
 the manual, but it has helped me see Org Mode documents more clearly and
 I think it might benefit others, as well.

Not to mention having access to it as an info page!  At the moment I
have an info version exported with the texinfo exporter (I think
Jambunathan posted this sometime back); I installed it manually.

-- 
Suvayu

Open source is the future. It sets us free.



Re: [O] org-caldav will continue to work with Google Calendar

2013-06-18 Thread Eric S Fraga
David Engster d...@randomsample.de writes:

[...]

 PS: I know that there are problems with org-caldav and the new
 exporter. I'll switch to Org 8 soon and will then merge the pending pull
 requests.

David,

What is the status on this?  I'm asking because my phone suffered a
mishap yesterday and so I'm needing to use your caldav-sync again to
keep my calendar synchronised instead of MobileOrg.  However, the sync
operation fails for me.  I'm using org v8; is this the cause?  The
failure is to do with UIDs not being found.  I can send a debug trace if
necessary.

Thanks,
eric
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.3-193-g334581




[O] org-element: property now always uppercase?

2013-06-18 Thread Peter Münster
Hi,

After updating org-mode from git, I noticed, that
org-element-parse-buffer uppercases the properties now. Is this a
feature or a bug?

Example:

* TODO test
  DEADLINE: 2013-06-18 Tue 12:00
  :PROPERTIES:
  :notify:   test
  :END:

Result of (org-element-parse-buffer 'headline):

(headline (:raw-value test  :NOTIFY test ... ))

-- 
   Peter




[O] PDF documentation for new exporter

2013-06-18 Thread Thorsten Jolitz

Hi List, 

I extracted the documentation parts of the core exporter libraries and
converted them to pdf, so they might serve as an detailled reference for
the new exporter, much more detailled than any tutorial could be (the pdf's
are still impressive in size, some 50 and 80 pages). 

,
| DISCLAIMER:
| 
| I did not go out of my way to produce these docs accurately and
| complete, I just used 'outorg' to export to LaTeX and then ran some
| replace commands and keyboard-macros on the .tex files. Things might
| have gone wrong in some places, the resulting documents might be
| incomplete or otherwise defective. But they might still be useful, so I
| offer them here. When in doubt always refer to `ox.el' and
| `org-elements.el' as reference.
`

PS

I tried to send the PDF's attached to a post to this mailing list, but
they don't seem to get through. So what shall I do with them? Can I send
them to somebody who uploads them to Worg if he thinks they are worth to
be made available to the public? Or shall I upload them on
'mediafire.com' and post a download link here?

-- 
cheers,
Thorsten





Re: [O] PDF documentation for new exporter

2013-06-18 Thread Rasmus
Thorsten Jolitz tjol...@gmail.com writes:

 Hi List, 

 I extracted the documentation parts of the core exporter libraries and
 converted them to pdf, so they might serve as an detailled reference for
 the new exporter, much more detailled than any tutorial could be (the pdf's
 are still impressive in size, some 50 and 80 pages). 

Sounds nice. 

 ,
 | DISCLAIMER:
 | 
 | I did not go out of my way to produce these docs accurately and
 | complete, I just used 'outorg' to export to LaTeX and then ran some
 | replace commands and keyboard-macros on the .tex files. Things might
 | have gone wrong in some places, the resulting documents might be
 | incomplete or otherwise defective. But they might still be useful, so I
 | offer them here. When in doubt always refer to `ox.el' and
 | `org-elements.el' as reference.
 `

 PS

 I tried to send the PDF's attached to a post to this mailing list, but
 they don't seem to get through. So what shall I do with them? Can I send
 them to somebody who uploads them to Worg if he thinks they are worth to
 be made available to the public? Or shall I upload them on
 'mediafire.com' and post a download link here?

Please add it to Worg, I'd say, preferably as html, if possible.


-- 
When in doubt, do it!




Re: [O] org-caldav will continue to work with Google Calendar

2013-06-18 Thread Eric S Fraga
David,

just to follow up on my own email.  With the attached draft,
org-caldav-sync works for me now.

Thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.3-193-g334581
diff --git a/org-caldav.el b/org-caldav.el
index 0383366..cd5b273 100644
--- a/org-caldav.el
+++ b/org-caldav.el
@@ -786,7 +786,7 @@ is no UID to rewrite. Returns the UID.
  ((re-search-forward ^UID:\\(orgsexp-[0-9]+\\) nil t)
   ;; This is a sexp entry, so do nothing.
   (match-string 1))
- ((re-search-forward ^UID:\\(\\s-*\\)\\([A-Z][A-Z]-\\)?\\(.+\\)\\s-*$
+ ((re-search-forward ^UID:\\(\\s-*\\)\\([A-Z][A-Z][0-9]-\\)?\\(.+\\)\\s-*$
 			 nil t)
   (when (match-string 1)
 	(replace-match  nil nil nil 1))


Re: [O] PDF documentation for new exporter

2013-06-18 Thread Thorsten Jolitz
Rasmus ras...@gmx.us writes:

 Please add it to Worg, I'd say, preferably as html, if possible.

I cloned the word repo again (because my existing clone had turned into
a mess somehow) and added the exporter doc-files (as .org files), and
pushed, but got an error:

,-
| $ git --no-pager push -v origin master:refs/heads/master
| send to git://orgmode.org/worg.git
| fatal: Could not read from remote repository.
| 
| Please make sure you have the correct access rights
| and the repository exists.
| git exited abnormally with code 128.
`-

Seems I lost my access rights in the process - what do i have to do to
regain them?

-- 
cheers,
Thorsten




[O] [help] How to ignore a head but don't ignore it's subhead when export

2013-06-18 Thread Feng Shu

#+begin_org

* headA
** headB

#+end_org

When export to latex, how to ignore headA and don't ignore headB?


Thanks


-- 



[O] [Help] How to insert a latex command in table environment when export

2013-06-18 Thread Feng Shu

---input---

#+CAPTION: test
| a | b |
| c | d |


output-
\begin{table}[htb]
\caption{test}

% How can I insert a command in this place? for example:
% \bitablecaption{你好}{Hello}

\centering
\begin{tabular}{ll}
a  b\\
c  d\\
\end{tabular}
\end{table}


Thanks
-- 



Re: [O] PDF documentation for new exporter

2013-06-18 Thread Bastien
Hi Thorsten,

Thorsten Jolitz tjol...@gmail.com writes:

 Seems I lost my access rights in the process - what do i have to do to
 regain them?

You lost your public key?  Either recover it or create a new one that
you send to me.

Thanks,

-- 
 Bastien



Re: [O] [help] How to ignore a head but don't ignore it's subhead when export

2013-06-18 Thread Bastien
Hi Feng,

Feng Shu tuma...@gmail.com writes:

 #+begin_org

 * headA
 ** headB

 #+end_org

 When export to latex, how to ignore headA and don't ignore headB?

You can't, sorry.

-- 
 Bastien



Re: [O] [help] How to ignore a head but don't ignore it's subhead when export

2013-06-18 Thread Marcin Borkowski
Dnia 2013-06-18, o godz. 15:38:27
Bastien b...@gnu.org napisał(a):

 Hi Feng,
 
 Feng Shu tuma...@gmail.com writes:
 
  #+begin_org
 
  * headA
  ** headB
 
  #+end_org
 
  When export to latex, how to ignore headA and don't ignore headB?
 
 You can't, sorry.
 

You can (probably), but on the LaTeX side, by redefining \section,
\subsection etc.

Hth,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University



Re: [O] [help] How to ignore a head but don't ignore it's subhead when export

2013-06-18 Thread Feng Shu
Bastien b...@gnu.org writes:

 Hi Feng,

 Feng Shu tuma...@gmail.com writes:

 #+begin_org

 * headA
 ** headB

 #+end_org

 When export to latex, how to ignore headA and don't ignore headB?

 You can't, sorry.

Thanks for the information

-- 



Re: [O] Bug: HTML export adds trailing junk characters for each line in source code block [8.0.3 (release_8.0.3-243-g0e3543 @ /Users/yuezhu/.emacs.d/el-get/org-mode/lisp/)]

2013-06-18 Thread Nick Dokos
Yue Zhu yuez...@gmail.com writes:

 I am sending a bug report because in my machine the HTML export cannot
 work correctly for code block (tested under C and Java). The problem is
 that it adds several trailing junk characters for each line like
 `#57344;#57345;#57345;', which are displayed as squares in the
 Firefox 21.

 Emacs  : GNU Emacs 24.3.1 (x86_64-apple-darwin12.3.0, NS apple-appkit-1187.37)
  of 2013-03-31 on teneight-slave.macports.org
 Package: Org-mode version 8.0.3 (release_8.0.3-243-g0e3543 @ 
 /Users/yuezhu/.emacs.d/el-get/org-mode/lisp/)


I suggest you post a minimal org file and the corresponding html
output exhibiting the problem.

-- 
Nick




[O] One more question on bibliographies in Org

2013-06-18 Thread Vincent Beffara

Hi,

Following the recent trend on the list, although this is not a question
about BibTeX as such, nor about the syntax to use for references within
the text, but rather about how to integrate references in an Org file to
be easily exportable. For now, a central database is not part of the
question, copy-and-paste is ok. The target would be mainly HTML and TeX
export. Here is a sketch:

For HTML: \cite{ABC09} would be mapped to a link to the bibliography,
something like a href=#ABC09[ABC09]/a (regardless of whether there
is such a reference). The bibliography itself would be part of the HTML
page, typically like footnotes right at the end, with some structure
kept (but styling would be done by ad-hoc CSS so nothing much needed
here).

For TeX: AMSRefs sounds good because it makes the .tex file
self-contained. \cite{ABC09} kept as it is, and the bibliography would
be a \begin{bibdiv}/\end{bibdiv} generated from the .org file.


The main question is: what would be a convenient way to store the
references in the .org file, to allow for easy editing and exporting ?

Idea 1: A new block type #+begin_biblio containing the data in whatever
form (but amsrefs makes sense, easily parsable for html export and
nothing to be done for tex export). While we're at it, maybe also
#+begin_bibentry if it helps cross-backend support.

Idea 2: #+begin_src amsrefs, and leverage babel for the output. But I'm
not sure if babel can act differently according to the export backend
being used?

Idea 3: A heading with tag :biblio:, which would be treated as a special
case at some point in the export, and containing one sub-heading per bib
entry, with properties storing the database like in org-bibtex (and
possibly unexported contents for notes). This gives access to structure
manipulation, refile, column view ... which would be awesome, but I'm
not sure how it would fit the export framework.


Which one would be best? Which one would be easiest to implement?

I'm willing to try a bit of coding, but the first step is the hardest
...

Cheers,

/vincent

-- 
Vincent Beffara




[O] Unexpected behaviour with gnuplot source blocks

2013-06-18 Thread Christopher Witte
Hi all,

I had some wierd behaviour with gnuplot source blocks and I'm not sure of
the best way to fix it.

I have gnuplot source blocks that write output files that I insert into the
document using links, as such:

#+begin_src gnuplot :file transInc.eps
reset
set encoding utf8
set output ./fig/transInc.eps
.
#+end_src
[[fig/transInc.eps]]

and I have two documents in different directories, say 'a' and 'b' that do
this.
If I go to the first document in folder 'a' and export it to latex and then
go to the second document in folder 'b' and also export it to latex, all
the generated plots end up in 'a'.  It took me a while to work it out, but
this is because only one gnuplot session is started and 'reset' doesn't
reset output.  Killing the gnuplot buffer fixes this, but that is annoying
if I frequently switch back and forth between the documents.

I could use full paths, but that seams like a pain, any other suggestions?

Thanks for the help,
Chris.


Re: [O] [help] How to ignore a head but don't ignore it's subhead when export

2013-06-18 Thread Charles Berry
Feng Shu tumashu at gmail.com writes:

 
 
 #+begin_org
 
 * headA
 ** headB
 
 #+end_org
 
 When export to latex, how to ignore headA and don't ignore headB?
 

With a tag. See this:

http://article.gmane.org/gmane.emacs.orgmode/67692

HTH,

Chuck






Re: [O] PDF documentation for new exporter

2013-06-18 Thread Suvayu Ali
On Tue, Jun 18, 2013 at 01:32:10PM +0200, Thorsten Jolitz wrote:
 Rasmus ras...@gmx.us writes:
 
  Please add it to Worg, I'd say, preferably as html, if possible.
 
 I cloned the word repo again (because my existing clone had turned into
 a mess somehow) and added the exporter doc-files (as .org files), and
 pushed, but got an error:
 
 ,-
 | $ git --no-pager push -v origin master:refs/heads/master
 | send to git://orgmode.org/worg.git
 | fatal: Could not read from remote repository.
 | 
 | Please make sure you have the correct access rights
 | and the repository exists.
 | git exited abnormally with code 128.
 `-
 
 Seems I lost my access rights in the process - what do i have to do to
 regain them?

Did you clone the public url?  If so, you cannot push with the same url.
You need the ssh+git url.  Here is my config:

  [remote origin]
  fetch = +refs/heads/*:refs/remotes/origin/*
  url = git+ssh://w...@orgmode.org/~/worg.git

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.



[O] how to refile without refiling in order to cache a restricted refile?

2013-06-18 Thread Samuel Wales
I use the refile cache, but there is one operation that is not
performed by the caching.

The first call to refile after rebuilding the cache takes seconds to
run.  Subsequent calls are much faster.

How can I do a refile without refiling in the following defun?

(defun hoka-org-refile-rebuild-cache ()
  (org-refile-cache-clear)
  (org-refile-get-targets))

What I want is to know what to do after the last form in that defun.

The slowdown seems to occur when the first refile is not the full set
of headlines.  I do that like this:

(defun hoka-org-refile-restricted ()
  (interactive)
  (let ((org-refile-targets alpha-org-refile-targets-restricted))
(call-interactively 'org-refile)))

Thanks.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.



Re: [O] org-element: property now always uppercase?

2013-06-18 Thread Nicolas Goaziou
Hello,

Peter Münster pmli...@free.fr writes:

 After updating org-mode from git, I noticed, that
 org-element-parse-buffer uppercases the properties now. Is this a
 feature or a bug?

 Example:

 * TODO test
   DEADLINE: 2013-06-18 Tue 12:00
   :PROPERTIES:
   :notify:   test
   :END:

 Result of (org-element-parse-buffer 'headline):

 (headline (:raw-value test  :NOTIFY test ... ))

This is a feature. Otherwise, something like

 * Headline
   :PROPERTIES:
   :contents-begin: text
   :END:

would put the parser into trouble.


Regards,

-- 
Nicolas Goaziou



Re: [O] PDF documentation for new exporter

2013-06-18 Thread Achim Gratz
Achim Gratz writes:
 Thorsten Jolitz writes:
 ,-
 | $ git --no-pager push -v origin master:refs/heads/master
 | send to git://orgmode.org/worg.git
 | fatal: Could not read from remote repository.

 Try this in your ~/.gitconfig:

 [url orgm...@orgmode.org:org-mode.git]
 pushInsteadOf = git://orgmode.org/org-mode.git

For Worg of course that'd be:

--8---cut here---start-8---
[url git+ssh://w...@orgmode.org/~/worg.git]
pushInsteadOf = git://orgmode.org/worg.git
--8---cut here---end---8---


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

DIY Stuff:
http://Synth.Stromeko.net/DIY.html




Re: [O] PDF documentation for new exporter

2013-06-18 Thread Achim Gratz
Thorsten Jolitz writes:
 ,-
 | $ git --no-pager push -v origin master:refs/heads/master
 | send to git://orgmode.org/worg.git
 | fatal: Could not read from remote repository.

Try this in your ~/.gitconfig:

--8---cut here---start-8---
[url orgm...@orgmode.org:org-mode.git]
pushInsteadOf = git://orgmode.org/org-mode.git
--8---cut here---end---8---


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: [O] PDF documentation for new exporter

2013-06-18 Thread Thorsten Jolitz
Achim Gratz strom...@nexgo.de writes:

 Achim Gratz writes:
 Thorsten Jolitz writes:
 ,-
 | $ git --no-pager push -v origin master:refs/heads/master
 | send to git://orgmode.org/worg.git
 | fatal: Could not read from remote repository.

 Try this in your ~/.gitconfig:

 [url orgm...@orgmode.org:org-mode.git]
 pushInsteadOf = git://orgmode.org/org-mode.git

 For Worg of course that'd be:

 [url git+ssh://w...@orgmode.org/~/worg.git]
 pushInsteadOf = git://orgmode.org/worg.git


ok, thanks, it worked and now the pages are online:

,--
| http://orgmode.org/worg/exporters/ox-docstrings.html
| http://orgmode.org/worg/exporters/org-element-docstrings.html
`--

PS
I linked to them from this page:

,---
| http://orgmode.org/worg/exporters/ox-overview.html
`---

but its a bit hard to find itself ...

-- 
cheers,
Thorsten




Re: [O] Classification of Org mode elements

2013-06-18 Thread Nicolas Goaziou
Hello,

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

 My idea is to add the table to Nicolas' draft Org Syntax document, and
 use the classes as the basis for editing and restructuring the document
 a bit.

Please go ahead, as long as the document stays faithful to the
implementation.


[...]

 Also, I'd like to see the Org Syntax document become an appendix to the
 manual. I know some think that it is too developer-ish to be a part of
 the manual, but it has helped me see Org Mode documents more clearly and
 I think it might benefit others, as well.

I also think that, once it is finalized (i.e. readable), it deserves to
be added to appendix.

Though, some parts of Org do not rely on org-element and may slightly
differ in their interpretation of the Org syntax.


Regards,

-- 
Nicolas Goaziou



Re: [O] Classification of Org mode elements

2013-06-18 Thread Thomas S. Dye
Aloha Nicolas,

Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

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

 My idea is to add the table to Nicolas' draft Org Syntax document, and
 use the classes as the basis for editing and restructuring the document
 a bit.

 Please go ahead, as long as the document stays faithful to the
 implementation.

Yes, this is the editor's challenge.  The author need's to keep a sharp
eye, too.



 [...]

 Also, I'd like to see the Org Syntax document become an appendix to the
 manual. I know some think that it is too developer-ish to be a part of
 the manual, but it has helped me see Org Mode documents more clearly and
 I think it might benefit others, as well.

 I also think that, once it is finalized (i.e. readable), it deserves to
 be added to appendix.

Great.  Unless others object let's set this as a goal.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com



Re: [O] [PATCH] Override the default class name with a new one.

2013-06-18 Thread Nicolas Goaziou
Hello,

Feng Shu tuma...@gmail.com writes:

 Not all the org-mode users are expert of lisp and  not all of the org-mode
 users are well in English, so finding the variable `org-latex-classes can
 customize latex class and adding  a lisp block to it  may be not a easy
 things for many users.

I understand, and I agree we should make this very important variable
understandable to any user.

 1. we can add a function `(defun org-latex-add-deriverd-class (class 
 exist-class) ...)  to menupulate `org-latex-classes
 2. My patch's approach.
 3. others.

We can modify `org-latex-classes' docstring (e.g. by adding examples) so
it is easier to understand. I'd rather have a patch in that direction
than to add yet another variable and keyword.


Regards,

-- 
Nicolas Goaziou



Re: [O] Bug in export orgtbl / LaTeX

2013-06-18 Thread Nicolas Goaziou
Hello,

AW alexander.will...@t-online.de writes:

 isn't that quite a contradiction: according to org-syntax tables can not 
 contain lists, but orgtbl-to-latex treats 1. inside a table as if it were a 
 beginning of a list?

Of course it is a contradiction. As, I wrote it, orgtbl-to-latex
interprets Org syntax differently, since it doesn't rely on Elements.

 Besides that, thank you for your code, but as my MEW showed, I use things 
 like 
 :splice t . In fact, I do splice nearly every orgtbl into a frame on the 
 LaTeX-side.

Take 2. We can implement back :splice property. The others are much less
useful.

  (defun orgtbl-to-latex (table params)
Convert the orgtbl-mode TABLE to LaTeX.
  TABLE is a list, each entry either the symbol `hline' for
  a horizontal separator line, or a list of fields for that line.
  PARAMS is a property list of parameters that can influence the
  conversion.  Currently this function recognizes the following
  parameters:

  :spliceWhen set to t, return only table body lines, don't wrap
 them into a \tabular\ environment.  Default is nil.
(require 'ox-latex)
(let ((table-string (orgtbl-to-orgtbl table nil)))
  (if (not (plist-get params :splice))
  (org-export-string-as table-string 'latex t '(:with-tables t))
;; If :splice is non-nil, we create a temporary back-end,
;; `latex-tmp', derived from `latex', but with a transparent
;; table translator.
(let ((org-export-registered-backends org-export-registered-backends))
  (org-export-define-derived-backend 'latex-tmp 'latex
:translate-alist (list (cons 'table (lambda (e c i) c
  (org-export-string-as table-string 'latex-tmp t '(:with-tables t))

WDYT?


Regards,

-- 
Nicolas Goaziou



Re: [O] :session question -- and changes to #+Property: syntax

2013-06-18 Thread Achim Gratz
Hi Eric,

while starting to write up a test document I've found some behaviour
when executing LOB calls that warrant discussion, I think:

1. The properties are evaluated at the site of the definition rather
than the site of the call.  This is simply how org-babel-process-params
works, it jumps to the definition and then executes the source block
there (this may be in another file even).

2. The evaluation of header arguments assumes emacs-lisp as a language.


These two combined make it somewhat difficult to use properties to
control the behaviour of LOB calls and understand what is happening and
why.  A workaround is to beam the source to the place of call via noweb
syntax.  The first point could perhaps be addressed in a cleaner way by
using org-babel-current-src-block-location when calling org-entry-get,
but I'm not sure yet if it is always correctly set.  Another thorny
question is how to deal with another layer of calls that might evaluate
properties again.  A last option would be to introduce another header
argument that can be used to inject the properties into the argument
list of the call and, if set, would suppress any property evaluation in
downstream calls.

For the second, I think that lob should be treated as a language for
the purpose of anything *-default-header-args* so these settings can be
independently controlled.


Thoughts, comments?


Regards,
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: [O] [BUG][PATCH] latex export of links in description lists

2013-06-18 Thread Nicolas Goaziou
Hello,

Rick Frankel r...@rickster.com writes:

 There is a bug in the processing of description list.

 Given the list:

 ,
 | - not a link :: not a link
 | - [[http://link.com][http link]] :: baz
 | - [[#href-test][custom_id link]] :: bar
 | - [[def list][search link]] :: foo
 `

 The latex exporter generates the following output, which fails
 latex processing on the `hyperref's.

 ,
 | \begin{description}
 | \item[not a link] not a link
 | \item[\href{http://link.com}{http link}] baz
 | \item[\hyperref[sec-1]{custom\_id link}] bar
 | \item[\hyperref[sec-1]{search link}] foo
 | \end{description}
 `

 I believe the simplest patch to solve is to wrap the item argument in
 braces as follows:

Applied. Thank you.


Regards,

-- 
Nicolas Goaziou



[O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

2013-06-18 Thread Peter Münster
* contrib/lisp/org-notify.el (org-notify-make-todo)
(org-notify-process, org-notify-on-action-button)
(org-notify-action-email, org-notify-action-window): Replace `flet'
and `macrolet' by `cl-flet' and `cl-macrolet'.
---
 contrib/lisp/org-notify.el | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el
index 4047448..3019852 100644
--- a/contrib/lisp/org-notify.el
+++ b/contrib/lisp/org-notify.el
@@ -118,7 +118,7 @@ simple timestamp string.
 
 (defun org-notify-make-todo (heading rest ignored)
   Create one todo item.
-  (macrolet ((get (k) `(plist-get list ,k))
+  (cl-macrolet ((get (k) `(plist-get list ,k))
  (pr (k v) `(setq result (plist-put result ,k ,v
 (let* ((list (nth 1 heading))  (notify (or (get :notify) default))
(deadline (org-notify-convert-deadline (get :deadline)))
@@ -157,7 +157,7 @@ PERIOD.
 (defun org-notify-process ()
   Process the todo-list, and possibly notify user about upcoming or
 forgotten tasks.
-  (macrolet ((prm (k) `(plist-get prms ,k))  (td (k) `(plist-get todo ,k)))
+  (cl-macrolet ((prm (k) `(plist-get prms ,k))  (td (k) `(plist-get todo ,k)))
 (dolist (todo (org-notify-todo-list))
   (let* ((deadline (td :deadline))  (heading (td :heading))
  (uid (td :uid))(last-run-sym
@@ -268,7 +268,7 @@ seconds.  The default value for SECS is 20.
 
 (defun org-notify-on-action-button (button)
   User wants to see action after button activation.
-  (macrolet ((get (k) `(button-get button ,k)))
+  (cl-macrolet ((get (k) `(button-get button ,k)))
 (org-notify-on-action (get 'plist) (get 'key))
 (org-notify-delete-window (get 'buffer))
 (cancel-timer (get 'timer
@@ -311,7 +311,7 @@ seconds.  The default value for SECS is 20.
   (compose-mail user-mail-address (concat TODO:  (plist-get plist :heading)))
   (insert (org-notify-body-text plist))
   (funcall send-mail-function)
-  (flet ((yes-or-no-p (prompt) t))
+  (cl-flet ((yes-or-no-p (prompt) t))
 (kill-buffer)))
 
 (defun org-notify-select-highest-window ()
@@ -334,7 +334,7 @@ org-notify window.  Mostly copied from 
`appt-select-lowest-window'.
 (defun org-notify-action-window (plist)
   Pop up a window, mostly copied from `appt-disp-window'.
   (save-excursion
-(macrolet ((get (k) `(plist-get plist ,k)))
+(cl-macrolet ((get (k) `(plist-get plist ,k)))
   (let ((this-window (selected-window))
 (buf (get-buffer-create
   (format org-notify-window-buffer-name (get :uid)
-- 
1.8.1.4




[O] [PATCH 2/2] org-notify: Fix compatibility with latest org-element (uppercase properties)

2013-06-18 Thread Peter Münster
* contrib/lisp/org-notify.el (org-notify-make-todo): Properties from
org-element are all uppercase now.
---
 contrib/lisp/org-notify.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/lisp/org-notify.el b/contrib/lisp/org-notify.el
index 3019852..dd4100d 100644
--- a/contrib/lisp/org-notify.el
+++ b/contrib/lisp/org-notify.el
@@ -120,7 +120,7 @@ simple timestamp string.
   Create one todo item.
   (cl-macrolet ((get (k) `(plist-get list ,k))
  (pr (k v) `(setq result (plist-put result ,k ,v
-(let* ((list (nth 1 heading))  (notify (or (get :notify) default))
+(let* ((list (nth 1 heading))  (notify (or (get :NOTIFY) default))
(deadline (org-notify-convert-deadline (get :deadline)))
   (heading (get :raw-value))
result)
-- 
1.8.1.4




Re: [O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

2013-06-18 Thread David Engster
Peter Münster writes:
 * contrib/lisp/org-notify.el (org-notify-make-todo)
 (org-notify-process, org-notify-on-action-button)
 (org-notify-action-email, org-notify-action-window): Replace `flet'
 and `macrolet' by `cl-flet' and `cl-macrolet'.

cl-lib was just introduced in Emacs 24.3.

-David



Re: [O] [PATCH 1/2] org-notify: Don't use obsolete flet and macrolet

2013-06-18 Thread Peter Münster
On Tue, Jun 18 2013, David Engster wrote:

 Peter Münster writes:
 * contrib/lisp/org-notify.el (org-notify-make-todo)
 (org-notify-process, org-notify-on-action-button)
 (org-notify-action-email, org-notify-action-window): Replace `flet'
 and `macrolet' by `cl-flet' and `cl-macrolet'.

 cl-lib was just introduced in Emacs 24.3.

Does that mean, that the trunk should be modified later?

I've submitted the patch only because of this message:
http://article.gmane.org/gmane.emacs.orgmode/71560

-- 
   Peter