[O] #+END_SRC and recent pull
Hello all, I pulled in latest changes from master and the following snippet is not getting tangled. #+begin_src emacs-lisp (message This is a test) #+end_src emacs-lisp Yes, the documentation has plain #+end_src, but somehow the above snippet was working earlier. Sending this mail out, just in case this is useful to someone else. Does the parser should really care about what is next to #+end_src ? Thanks and Regards Noorul
[O] org-html-publish-to-html fails to recognize BEGIN_EXAMPLE/END_EXAMPLE blocks when exporting an example containing org-mode heading
Hello, when trying to export as html an example which contains org-mode headings, the example is not quoted in mono-space as it should be. Example: *1. Failing example: * This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. *2. Workaround: * This works as expected, but only because the * headline is indented by 1 character: This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. I used (meta-x) org-html-export-to-html to do the export. Same happens with org-publish. I am running following emacs version: GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2013-03-13 on bob.porkrind.org on MacOS X 10.8.5 with org-mode version: Org-mode version 8.0.7 (8.0.7-6-g13cb28-elpa @ /Users/iani2/.emacs.d/elpa/org-20130812/) Is this a bug? Any suggestions? Iannis Zannos
Re: [O] Org mode issue tracker
Hi Suvayu, What a nice work you've done... Some comments... Suvayu Ali wrote: This is the general structure I'm proposing: * TODO Subject timestamp :emacs_ver:org_ver:org_module: :PROPERTIES: :DEBGUGS_ID: bug number :REPORTER:Reporter Name :CC_EMAIL:list of emails of interested parties :END: I elaborate the ideas below. On Wed, Sep 25, 2013 at 08:56:50PM +0200, Michael Albinus wrote: Let's check it with an example. For bug 15081, debbugs-gnu returns the following list: ((source . unknown) (found_versions 24.3) Emacs version ends up as a tag: * TODO . :24.3: (done) (blocks) (date . 1376383861) * TODO . :24.3: 2013-08-13 Tue I'd use the inactive version of the timestamp, that is (for Michael) [2013-08-13 Tue]. (fixed) (fixed_versions) (mergedwith) (found (item (key . 24.3) (value))) (unarchived) (blockedby) (keywords) (summary) (msgid . 877gfqkm9t@gmail.com) An added bonus idea: Gmane has this amazing feature where you can link to a message using it's message id. So a property like: GMANE_URL would be awesome. * TODO . :24.3: :PROPERTIES: :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 2013-08-13 Tue (id . 15081) * TODO . :24.3: :PROPERTIES: :DEBGUGS_ID: 15081 :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 2013-08-13 Tue It would be cool if you could provide a function that uses browse-url to direct you to the webpage using DEBGUGS_ID: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15081 We could get it by adding a new link type, don't we? (forwarded) (severity . normal) (owner) (log_modified . 1376383862) (location . db-h) (subject . 24.3; org-crypt: Making epg-context local to *epg* while let-bound!) * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 2013-08-13 Tue As you see above, it would be great if we could simplify the suject and tag the org-module involved (note hyphens are not allowed, they need to be transformed to underscore). (originator . Thierry Volpiatto thierry.volpia...@gmail.com) * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpia...@gmail.com I'd maybe use Creator or CreatedBy (with or without hyphens or underscore) to make that framework less bug-specific. That way, I guess it could stay as well as general for common tasks in any project. BTW, is there a convention for using ALLCAPS or First-letter-cap? I mean: the time estimate property is written Effort, not EFFORT; is there a convention to distinguish between Org official built-in properties, and user-defined ones? Or is there another rule? (This question may sound stupid, but I live conventions, so that all files look the same). :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 2013-08-13 Tue (last_modified . 1376408720) Maybe this should go into a property called: LAST_MODIFIED. (pending . pending) And this should finally decide the TODO state. For the moment a reasonable mapping would be pending - TODO. But would be good to have support for DONE, WIP, or similar (I'm not familiar with all the debbug states :-p) (affects) (archived) (tags) (package emacs org-mode) I guess this is how you filter out org-mode bugs from the rest. (fixed_date) (found_date) (bug_num . 15081)) The keys shall be self-explaining. How would a TODO item look like? Note, that these metadata do not contain the corresponding messages yet. debbugs-gnu could retrieve them in a second run; the TODO item shall offer a link to them, inline. So finally I propose the following for this particular bug. * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpia...@gmail.com :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 152 2013-08-13 Tue What's this 152? A typo? However in this example there were no interested parties. If you take this (non org-mode) bug as an example: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15282, the CC_EMAIL property would be: Eli Zaretskii e...@gnu.org, Gregor Zattler telegr...@gmx.net, hyper...@debian.org, Paul Eggert egg...@cs.ucla.edu, and all the contributors to bug 15222 (that would be me :-p, Suvayu Ali fatkasuvayu+li...@gmail.com). What do others think? Is it a good start? I like your work a lot! Overall this looks very promising, I am excited :). So do I. Best
Re: [O] build errors on os x
skip.coll...@gmail.com writes: The problem persists. Can anyone else confirm? Perhaps this should be added to the bug tracker file. For the record, my local.mk file is: EMACS = /Applications/Emacs.app/Contents/MacOS/Emacs prefix = /usr/local/share On Tue, Sep 24, 2013 at 11:11 AM, Skip Collins skip.coll...@gmail.com wrote: For the last few days, building org with make up2 results in the following failed tests with Emacs for Mac OS X 24.3.1: Ran 456 tests, 448 results as expected, 8 unexpected (2013-09-24 10:59:21-0400) 5 expected failures 8 unexpected results: FAILED test-ob/org-babel-remove-result--results-code FAILED test-ob/org-babel-remove-result--results-default FAILED test-ob/org-babel-remove-result--results-html FAILED test-ob/org-babel-remove-result--results-latex FAILED test-ob/org-babel-remove-result--results-list FAILED test-ob/org-babel-remove-result--results-org FAILED test-ob/org-babel-remove-result--results-pp FAILED test-ob/org-babel-remove-result--results-wrap I'm seeing the same errors here, using the emacs from https://github.com/railwaycat/emacs-mac-port Alan
Re: [O] [PATCH] Display a count of items next to each list (or block)
Am 25.09.2013 22:09, schrieb Sebastien Vauban: In order to make Org much nicer to use, I felt we missed a count of items next to the lists (or blocks, for multi-block agenda views). Here is a patch to add this, depending on the new variable `org-agenda-display-count-of-items' (enabled by default). Minor nit: to my ears item count sounds better than count of items. Achim.
Re: [O] Elpa color-theme with emacs24
Hi Rene, Rene wrote: I just tried out color-theme with emacs24. It seems the code on http://orgmode.org/worg/org-color-themes.html is not quite compatible with elpa packages. Here is what I used instead ... For the sake of completion, I think that, starting with Emacs 24, it's better to use their new custom theme mechanism, which is more general than the `color-theme' package (and offers the same services regarding color themes). Best regards, Seb -- Sebastien Vauban
Re: [O] #+END_SRC and recent pull
Noorul Islam Kamal Malmiyoda wrote: I pulled in latest changes from master and the following snippet is not getting tangled. #+begin_src emacs-lisp (message This is a test) #+end_src emacs-lisp Yes, the documentation has plain #+end_src, but somehow the above snippet was working earlier. Sending this mail out, just in case this is useful to someone else. Does the parser should really care about what is next to #+end_src ? I think so. You really should NOT put the language name at the end of the code block. Note that it shouldn't occur, would you use C-c C-v C-d to automatically convert a region in a code block. Neither with the easy templates, nor with custom YASnippets... Now, your code block alone, given above, can't be tangled, as there is no tangle directive. If it still does not work, please provide us with an ECM (Example Complete... and Minimal). Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] Display a count of items next to each list (or block)
Hi Achim, Achim Gratz wrote: Am 25.09.2013 22:09, schrieb Sebastien Vauban: In order to make Org much nicer to use, I felt we missed a count of items next to the lists (or blocks, for multi-block agenda views). Here is a patch to add this, depending on the new variable `org-agenda-display-count-of-items' (enabled by default). Minor nit: to my ears item count sounds better than count of items. No problem (I'm no English native speaker, and I'm glad when I'm corrected, for improving myself). You then mean you'd rename the variable (and potentially other comments or names in the code)? To `org-agenda-display-item-count' or `org-agenda-display-items-count'? Best regards, Seb -- Sebastien Vauban
Re: [O] org-html-publish-to-html fails to recognize BEGIN_EXAMPLE/END_EXAMPLE blocks when exporting an example containing org-mode heading
Iannis Zannos, Iannis Zannos wrote: Hello, when trying to export as html an example which contains org-mode headings, the example is not quoted in mono-space as it should be. Example: *1. Failing example: * This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. *2. Workaround: * This works as expected, but only because the * headline is indented by 1 character: This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. The official solution (normally automatic[1] for Org code blocks) is to have a , inserted before the *; it is removed automatically when exporting. Best regards, Seb [1] Sometimes, the , is not automatically inserted for me, though, when TAB'ing. -- Sebastien Vauban
Re: [O] A tutorial on using ox-rss.el to publish an Emacs-made blog
On Wed, 25 Sep 2013 17:58:51 +0200 Carsten Dominik carsten.domi...@gmail.com wrote: +1. Tis is the post that might put me over the edge and try it. +1. Same status here. Detlef - Carsten
Re: [O] [BUG] in Release 8.2 - editing code in indirect buffer
Andreas Leha andreas.l...@med.uni-goettingen.de writes: On the ess list (emacs.ess.general) there has been the announcement [fn:2] of polymode [fn:1] recently, which is going in this direction. True - sounds very much like what Eric mentioned. I poster a question there [1]to see if Vitalie could implement support for org mode. Since my elisp knowledge is limited to the least, this comment might be irrelevant here, in which case please ignore it. Not at all - don't worry. Your comment is spot on. Cheers, Rainer Regards, Andreas Footnotes: [fn:1] https://github.com/vitoshka/polymode [fn:2] http://comments.gmane.org/gmane.emacs.ess.general/6994 #secure method=pgpmime mode=sign Footnotes: [1] https://github.com/vitoshka/polymode/issues/9 -- Rainer M. Krug email: RMKrugatgmaildotcom
Re: [O] [PATCH] babel support for ABC notation music files
On Wed, 25 Sep 2013 09:15:45 -0600, Eric Schulte schulte.e...@gmail.com said:
Hi William, I've added your ABC notation support to Org-mode.
Thank you Eric!
If you have time to add ob-ABC documentation to [1] that would
be much appreciated but is not required.
Patch for the web site attached.
Cheers,
-w
From e82589c7a964e895b04047823621ae6725bf262f Mon Sep 17 00:00:00 2001
From: William Waites wwai...@tardis.ed.ac.uk
Date: Thu, 26 Sep 2013 09:09:55 +0100
Subject: [PATCH] add ABC docs to web site
---
org-contrib/babel/languages.org|1 +
org-contrib/babel/languages/ob-doc-abc.org | 97
2 files changed, 98 insertions(+)
create mode 100644 org-contrib/babel/languages/ob-doc-abc.org
diff --git a/org-contrib/babel/languages.org b/org-contrib/babel/languages.org
index 71f6925..51f349b 100644
--- a/org-contrib/babel/languages.org
+++ b/org-contrib/babel/languages.org
@@ -24,6 +24,7 @@ language documentation.
#+Caption: Babel has support for the following languages.
| Language | Identifier | Documentation| Requirements|
|+-+--+-|
+| ABC| abc | [[file:languages/ob-doc-abc.org][ob-doc-abc]] | [[http://moinejf.free.fr/][abcm2ps]], [[https://github.com/mkjunker/abc-mode][abc-mode]] |
| Asymptote | asymptote | [[file:languages/ob-doc-asymptote.org][ob-doc-asymptote]] | [[http://asymptote.sourceforge.net/][asymptote]], [[http://asymptote.sourceforge.net/doc/Editing-modes.html][asy-mode]] |
| Awk| awk | [[file:languages/ob-doc-awk.org][ob-doc-awk]] | awk |
| C | C | [[file:languages/ob-doc-C.org][ob-doc-C]] | none|
diff --git a/org-contrib/babel/languages/ob-doc-abc.org b/org-contrib/babel/languages/ob-doc-abc.org
new file mode 100644
index 000..09ab8c9
--- /dev/null
+++ b/org-contrib/babel/languages/ob-doc-abc.org
@@ -0,0 +1,97 @@
+#+OPTIONS:H:3 num:nil toc:2 \n:nil ::t |:t ^:{} -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
+#+STARTUP:align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO: TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS: Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE: Org-babel-abc
+#+AUTHOR: William Waites
+#+LANGUAGE: en
+#+HTML_HEAD: style type=text/css#outline-container-introduction{ clear:both; }/style
+#+LINK_UP:../languages.html
+#+LINK_HOME: http://orgmode.org/worg/
+
+#+begin_html
+ div id=subtitle style=float: center; text-align: center;
+ p
+ Org Babel support for
+ a href=http://abcnotation.com/;ABC Notation/a
+ /p
+ /div
+#+end_html
+
+* Introduction
+
+An /Emacs Org Babel language/ - provided to allow [[http://abcnotation.com/][ABC Notation]] Music
+Score generation.
+
+* Usage
+ Generating output in various formats (PostScript, Encapsulated
+ PostScript, PDF, SVG) is done by naming the `:file` parameter
+ correctly and passing the command-line options to /abcm2ps/ using
+ the `:cmdline` parameter.
+
+* Examples
+** PDF generation
+: #+begin_src abc :file congress.pdf
+: T: The Congress
+: R: reel
+: M: 4/4
+: L: 1/8
+: K: Ador
+: eAAG A2 (3Bcd | eaaf gedg | eA ~A2 eAcA | BdGB dG (3Bcd |
+: eAAG A2 (3Bcd | eaaf gedB | ~c3 d (3efg ed | cdBc A2(3Bcd |
+: eA ~A2 EAcd | eAaf gafg | ea ~a2 AecA | BG ~G2 B,DGB |
+: AE ~E2 cA (3Bcd | eaaf gedB | ~c3 d eged | cdBc A2Bd |
+: eaa^g ~a3 =g | eaaf gedg | (3efg dg (3efg dg | eaaf gabg |
+: eaa^g aba=g | eaaf gedB | ~c3 d (3efg ed | cdBc A2(3Bcd |
+: eaa^g ~a3 =g | eaaf gedg | (3efg dg cgBg | eaaf gabg |
+: eaa^g ab=ga | eaaf gedB | ~c3 d eged | cd (3efg agfg |
+: #+end_src
+
+** SVG generation for inclusion in web pages
+: #+begin_src abc :file john_maccol_kilbowie.svg :cmdline -g
+: T: John MacColl's March To Kilbowie Cottage
+: R: March
+: M: 4/4
+: L: 1/8
+: K: Amix
+: AB|: c4 cB Ac | e4 fe ce | AB cf ec AB | cf ec B2 AB |
+: c4 cB Ac | e4 fe ce | fe fc eA Bc |1 A2 A2 A2 AB :|2 A2 A2 A2 f=g ||
+: a2-af ec Bc | Ac e=g fc ec | af ef ~A2-AB | cf ec B2 f=g |
+: a2-af ec Bc | Ac e=g fc ec | fa ce eA Bc | A2 A2 A2 f=g |
+: a2-af ec Bc | Ac e=g fc ec | af ef ~A2-AB | cf ec B2 AB |
+: c4 cB Ac | e4 fe ce | fe fc eA Bc | A2 A2 A2 cB |
+: | : Ac Bc Af ef | ae fa ef ce | Ac Bc Af ef | af ec B2 cB |
+: Ac Bc Af ef | ae fa ef ce | fe fc eA Bc |1 A2 A2 A2 cB :|2 A2 A2 A2 ed ||
+: ce Bc Ac eA | ce ae fe cd | ec Bc A2 AB | cf ec B2 ed|
+: ce Bc Ac eA | ce ae fe cd | ef ce eA Bc | A2 A2 A2 ed |
+: ce Bc Ac eA | ce ae fe cd | ec Bc A2 AB | cf ec B2 AB |
+: c4 cB Ac | e4 fe ce | fe fc eA Bc | A2 A2 A4 |
+: #+end_src
+
+* Compiling ABC Blocks
Re: [O] org mode R remote code evaluation
Alexander Vorobiev alexander.vorob...@gmail.com writes: Michael, Hi Alex, * this doesn't work #+BEGIN_SRC sql :engine postgresql :dir /grid: :results output select 1+2 as three; #+END_SRC /plinkx:grid:/tmp/sql-in-7928arv...done psql -A -F -f c:/tmp/sql-in-7928arv -o c:/tmp/sql-out-7928Z_E -f c:/tmp/sql-in-7928arv -o c:/tmp/sql-out-7928Z_E No such file or directory 'c:/tmp/sql-in-7928arv' Try this extended patch: --8---cut here---start-8--- diff --git a/lisp/ob-core.el b/lisp/ob-core.el index 5a032a1..2789f47 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -2680,11 +2680,7 @@ Fixes a bug in `tramp-handle-call-process-region'. (defun org-babel-local-file-name (file) Return the local name component of FILE. - (if (file-remote-p file) - (let (localname) - (with-parsed-tramp-file-name file nil -localname)) -file)) + (or (file-remote-p file 'localname) file)) (defun org-babel-process-file-name (name optional no-quote-p) Prepare NAME to be used in an external process. @@ -2694,7 +2690,10 @@ remotely. The file name is then processed by `expand-file-name'. Unless second argument NO-QUOTE-P is non-nil, the file name is additionally processed by `shell-quote-argument' ((lambda (f) (if no-quote-p f (shell-quote-argument f))) - (expand-file-name (org-babel-local-file-name name + ;; We must apply `expand-file-name' on the whole filename. If we + ;; would apply it on the local filename only, undesired effects + ;; like prepending a drive letter on MS Windows could happen. + (org-babel-local-file-name (expand-file-name name (defvar org-babel-temporary-directory) (unless (or noninteractive (boundp 'org-babel-temporary-directory)) @@ -2736,7 +2735,7 @@ of `org-babel-temporary-directory'. (if (file-remote-p default-directory) (let ((prefix (concat (file-remote-p default-directory) - (expand-file-name prefix temporary-file-directory + (expand-file-name prefix /tmp/ (make-temp-file prefix nil suffix)) (let ((temporary-file-directory (or (and (boundp 'org-babel-temporary-directory) --8---cut here---end---8--- Thanks Alex Best regards, Michael. PS: the analysis of your cygwin problem is delayed. I don't run MS Windows on my machines, I need to hijack a machine from my wife or somebody else for analysis.
Re: [O] Org mode issue tracker
Hi Seb and others, On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote: (date . 1376383861) * TODO . :24.3: 2013-08-13 Tue I'd use the inactive version of the timestamp, that is (for Michael) [2013-08-13 Tue]. Doesn't the agenda show active timestamps only? Developers working on bugs might want to add the file as their agenda file. It would be cool if you could provide a function that uses browse-url to direct you to the webpage using DEBGUGS_ID: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15081 We could get it by adding a new link type, don't we? Indeed! I usually dislike bare links in documents. I think it breaks the flow of text. Your suggestion sounds perfect! (originator . Thierry Volpiatto thierry.volpia...@gmail.com) * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpia...@gmail.com I'd maybe use Creator or CreatedBy (with or without hyphens or underscore) to make that framework less bug-specific. That way, I guess it could stay as well as general for common tasks in any project. Indeed a great suggestion! BTW, is there a convention for using ALLCAPS or First-letter-cap? I mean: the time estimate property is written Effort, not EFFORT; is there a convention to distinguish between Org official built-in properties, and user-defined ones? Or is there another rule? (This question may sound stupid, but I live conventions, so that all files look the same). I'm not sure if there is any convention. So finally I propose the following for this particular bug. * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpia...@gmail.com :GMANE_URL:http://mid.gmane.org/877gfqkm9t@gmail.com :END: 152 2013-08-13 Tue What's this 152? A typo? It's a typo. :-p What do others think? Is it a good start? I like your work a lot! Thank you :). -- Suvayu Open source is the future. It sets us free.
Re: [O] org-html-publish-to-html fails to recognize BEGIN_EXAMPLE/END_EXAMPLE blocks when exporting an example containing org-mode heading
Hi Iannis, Iannis Zannos wrote: On Thu, Sep 26, 2013 at 10:36 AM, Sebastien Vauban wrote: Iannis Zannos wrote: when trying to export as html an example which contains org-mode headings, the example is not quoted in mono-space as it should be. Example: *1. Failing example: * This is a test of publishing an example which contains org mode code in html: #+BEGIN_EXAMPLE * test #+END_EXAMPLE End of test. The official solution (normally automatic for Org code blocks) is to have a , inserted before the *; it is removed automatically when exporting. Thank you for the answer. It is clear now. Glad it helped! Perhaps the info manual of org-mode should be updated to indicate this? I would propose to do this in the following places in the manual: 11.3 Literal examples and perhaps also: 15.2 Easy Templates Would you mind providing a patch? Best regards, Seb -- Sebastien Vauban
Re: [O] example filter for code blocks?
John Kitchin wrote:
Hi everyone,
I have an idea for putting links in a pdf that would open python code
blocks in an editor. To do that, I need to modify what happens when an
org-file is published to latex.
Hello John,
Few days ago, I did some research on the general problem:
- not python specific (code agnostic)
- not latex specific (export back-end agnostic)
Unfortunately I ended up only for specific parts, but hope that can be
useful starting points.
I think that the ability to attach code blocks in a easy and general
way can be a nice improvement.
Essentially I want it to do exactly what it already does in terms of
running pygments, and making nicely formatted and syntax highlighted
code blocks and output.
After that though, I want to tangle the code block to a file in a
directory, and insert a new link after the rendered code block. I
would prefer not to have to put :tangle headings in each code block
because there are many (e.g. hundreds) of them in course notes.
sufficient if they were just sequentially numbered as dir/1.py,
dir/2.py, etc... and it is fine if these get overwritten on each
export.
If can live with a different file per section instead of per code
block you can group the common setting, eg:
:PROPERTIES:
:header-args: octave :session *octave-sess* :exports both :results output
:tangle lab1-ex1.m
:END:
the link that would go after the code block in the latex export would
be something like: \LaunchPython{dir/1.py}{Open code}
Then clicking on it would open dir/1.py in whatever editor your
system is configured for. \LaunchPython is a newcommand I have
defined that works already.
My hack with limited use to latex and html (and probably will not copy
the tangled file with html publish) is:
#+LATEX_HEADER: \usepackage{attachfile}
#+MACRO: embed-matlab @@latex:\textattachfile[mimetype=text/x-matlab,color=0 0 0.5]{$1}{$1}@@
@@html:a href=$1$1/a@@
#+NAME: code:2
#+BEGIN_SRC octave
x = 1:10
#+END_SRC
Snippets of octave source code for this exercise
{{{embed-matlab(lab1-ex1.m)}}}
It seems like the new export engine should make this easy to do, but
I am not sure where to start. Could anyone point me to a starting
place? Thanks!
I only have limited lisp knowledge, but I am interested as well in
pointers for a general solution.
Regards,
Daniele
Re: [O] Org mode issue tracker
On Thu, Sep 26, 2013 at 10:22 AM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote: On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote: BTW, is there a convention for using ALLCAPS or First-letter-cap? I mean: the time estimate property is written Effort, not EFFORT; is there a convention to distinguish between Org official built-in properties, and user-defined ones? Or is there another rule? (This question may sound stupid, but I live conventions, so that all files look the same). I'm not sure if there is any convention. There is: User-defined properties are capitalized, see http://orgmode.org/manual/Conventions.html Although for user-defined properties and at least for my private Org files I don't follow this convention and prefer all lower case. It helps me e. g. when sorting properties with locale C: Built-in properties first, User-defined last. Michael
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
Dnia 2013-09-25, o godz. 12:53:18 Thorsten Jolitz tjol...@gmail.com napisał(a): One possible remaining option would be to introduce user variables org-BACKEND-format-property-drawer-function in analogy org-BACKEND-format-drawer-function. This would provide an easy way to configure export of the property drawer as a whole, in a way that could be file-local. I would like to have this option +1 property drawers are just too useful to restrict them to Org-mode's internal meta-data, and anything that makes it easier to export them when used for 'use case' related meta-data or as simple DB is welcome. I hardly ever use export, but: AFAIR, properties can be used to provide data for the spreadsheet. Exporting with them would be very useful for educational material (my use case: loan payment table with data like interest rate etc. in properties). Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] [export] Should sidewaystable option automatically add rotating package?
Dnia 2013-09-25, o godz. 11:09:43 Rasmus ras...@gmx.us napisał(a): Nicolas Girard girard.nico...@gmail.com writes: 2013/9/25 Carsten Dominik carsten.domi...@gmail.com: I came to think that, having a piece of code that brings cross-compatibility between the 3 engines would be of interest to people outside of the Org community. But this is not trivial, especially if the code has to work with older TeX distributions (a reasonable expectation would be that it works with, say, TeXlive 2011 and TeXlive 2012). Why 2011? We also require a recent Emacs with recent Org, or? My 3cents: TeX distros have been notoriously outdated in e.g. Ubuntu. Things got much better recently, but think of Ubuntu LTS users. (And people tend not to update TeXlive for *several years* on Windows. Given the stability of LaTeX, there is some method in this madness, though.) Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] Spurious exporting of text before first header
Dnia 2013-09-25, o godz. 19:25:53 Nicolas Goaziou n.goaz...@gmail.com napisał(a): I agree, this is a misfeature. This should be fixed in master. ^^ I love this word!!! -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] Rackspace is sponsoring orgmode.org hosting
Dnia 2013-09-25, o godz. 16:49:20 Carsten Dominik carsten.domi...@gmail.com napisał(a): Hi everyone, I guess it is appropriate to give a little shout-out to rackspace.com here, because a few month back they have decided to sponsor the webhosting for orgmode.org. Jason Dunsmore set us up with a rackspace account a few years ago (2010 IIRC) and has done a great service to our community by running the server for us and giving us many additional capabilities beyond what we used to have. Orgmode.org is hosting its own git repositories which we all use to get our updates and to push patches. It also runs the orgmode.org website and the worg pages, which are automatically created from the basic Org files whenever we push a change. I don't know if any of you has ever experience downtime of orgmode.org in the last few year - I do not. Over all these years Jason has put up with the hosting costs. Now Rackspace is stepping in, letting us do all of this for free, and without any ads we would have to display (except this one, maybe :) ) The server works great, just a virtual Linux machine where we (Jason, Bastien and myself) can log in and do all the configuration we want. A few minutes ago I tried creating a new VM, then resizing it, a lot of fun. As far as I know, we have a carte blanche from Rackspace, so if we can think of an additional interesting service we want to provide, we could. Let me know if you come up with an idea. Kodos to Jason for all his (continuing!) great work, and Kodos for Rackspace for the sponsorship! - Carsten Great, thanks to them! What about a feed aggregator, bringing together org-related posts from various blogs? Something similar to http://texample.net/community/ in TeX world. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
Re: [O] Rackspace is sponsoring orgmode.org hosting
Marcin Borkowski mb...@wmi.amu.edu.pl writes: What about a feed aggregator, bringing together org-related posts from various blogs? Something similar to http://texample.net/community/ in TeX world. Great idea! -- Bastien
Re: [O] example filter for code blocks?
Dnia 2013-09-25, o godz. 20:03:10
John Kitchin jkitc...@andrew.cmu.edu napisał(a):
Hi everyone,
I have an idea for putting links in a pdf that would open python code
blocks in an editor. To do that, I need to modify what happens when an
org-file is published to latex.
Essentially I want it to do exactly what it already does in terms of
running pygments, and making nicely formatted and syntax highlighted
code blocks and output.
After that though, I want to tangle the code block to a file in a
directory, and insert a new link after the rendered code block. I
would prefer not to have to put :tangle headings in each code block
because there are many (e.g. hundreds) of them in course notes. It
would be sufficient if they were just sequentially numbered as
dir/1.py, dir/2.py, etc... and it is fine if these get overwritten on
each export.
the link that would go after the code block in the latex export would
be something like:
\LaunchPython{dir/1.py}{Open code}
Then clicking on it would open dir/1.py in whatever editor your
system is configured for. \LaunchPython is a newcommand I have
defined that works already.
It seems like the new export engine should make this easy to do, but
I am not sure where to start. Could anyone point me to a starting
place? Thanks!
I'm not 100% sure, but I think you can do this (maybe more easily,
maybe not) on the LaTeX side. Check out the etoolbox package, look at
the patching commands and remember that \begin{foo} ... \end{foo}
translate (more or less) into something like \begingroup\foo ...
\endfoo\endgroup, so patching \endfoo might be the way to go.
John
hth
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
[O] Convention for tags and properties
Hello, According to the manual [1]: - User-defined tags are written in lowercase; built-in tags with special meaning (such as ARCHIVE) are written with all capitals. - User-defined properties are capitalized; built-in properties with special meaning (such as PRIORITY) are written with all capitals. Following those conventions, I guess that: - The `crypt' tag should be renamed `CRYPT' - The `Effort' property should be renamed `EFFORT' Right? Best regards, Seb [1] http://orgmode.org/manual/Conventions.html -- Sebastien Vauban
Re: [O] org-caldav for Google or Zimbra?
Jason Riedy ja...@lovesgoodfood.com writes: Does anyone have org-caldav working with the new Google endpoint Can you expand on this? I am not sure what you mean by endpoint. I use org-caldav-sync several times a day and it generally works very well with Google's calendar service. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.1.1-7-gaecdf5
Re: [O] Org mode issue tracker
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Hi Sebastien and Suvayu, Thanks a lot for your comments. That's pretty good for starting a proof-of-concept. Will do. Some comments from my side: ((source . unknown) (found_versions 24.3) Emacs version ends up as a tag: * TODO . :24.3: found_versions is optional. So we cannot assume it is always set. Furthermore, it is a *list* of strings (although I haven't seen ever more than one entry). What to do in this case? (msgid . 877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org) An added bonus idea: Gmane has this amazing feature where you can link to a message using it's message id. So a property like: GMANE_URL would be awesome. * TODO . :24.3: :PROPERTIES: :GMANE_URL: http://mid.gmane.org/877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org :END: 2013-08-13 Tue Agreed. However, debbugs.el is also capable to retrieve all messages from the server, as we do in debbugs-gnu. I'll show below. (severity . normal) I would really appreciate, if we could make the severity visible. In the org manual, I've read something about A B C priorities. On debbugs, we have the severities serious, important, normal, minor, wishlist, and tagged. How could we map them on the TODO items? In debbugs-gnu we use different faces (colors) for the entries. (subject . 24.3; org-crypt: Making epg-context local to *epg* while let-bound!) * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :GMANE_URL: http://mid.gmane.org/877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org :END: 2013-08-13 Tue As you see above, it would be great if we could simplify the suject and tag the org-module involved (note hyphens are not allowed, they need to be transformed to underscore). OK. However, we cannot assume a given syntax on the subject. An error can be reported by a simple mail to @debbugs.gnu.org, with free subject. A preformatted subject can be assumed only, if the error has been reported by `report-emacs-bug' or `org-submit-bug-report'. (pending . pending) And this should finally decide the TODO state. For the moment a reasonable mapping would be pending - TODO. But would be good to have support for DONE, WIP, or similar (I'm not familiar with all the debbug states :-p) The pending field could have the values pending, forwarded or done. forwarded does not seem to be used on debbugs.gnu.org. (tags) Tags are useful for more information on the status. They are a list of strings like fixed, notabug, wontfix, unreproducible, moreinfo or patch. In the given example, this list is empty. (package emacs org-mode) I guess this is how you filter out org-mode bugs from the rest. Yep. In the org-mode case, it is sufficient to filter for the package org-mode. But why not create a todo list for another debbugs project, like emacs or gnus or whatever? And btw, one could filter also for other attributes but just package. Even full text search is possible. * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpiatto-re5jqeeqqe8avxtiumw...@public.gmane.org :GMANE_URL: http://mid.gmane.org/877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org :END: Yep. Now it comes to the attached emails. In a second (!) step, debbugs-gnu is able to retrieve the corresponding emails. In the given example, it would call (debbugs-get-bug-log 15081) This returns a list like (((body . The body of the message) (msg_num . 5) (attachments) (header . All header lines of the message))) I have just shown one message, of course all messages will be retrieved. Alternative, one could retrieve the messages in MBOX format. Wouldn't it be nice, if we could include the messages as well? Likely not by default (it would be expensive to download all messages for, let's say, 500 bugs at once). But we could add a kind of link which, when followed, could show the messages as well in org-mode. Somehow. Best regards, Seb Best regards, Michael.
Re: [O] build errors on os x
On Thu, Sep 26, 2013 at 3:32 PM, Alan Schmitt alan.schm...@polytechnique.org wrote: skip.coll...@gmail.com writes: The problem persists. Can anyone else confirm? Perhaps this should be added to the bug tracker file. For the record, my local.mk file is: EMACS = /Applications/Emacs.app/Contents/MacOS/Emacs prefix = /usr/local/share On Tue, Sep 24, 2013 at 11:11 AM, Skip Collins skip.coll...@gmail.com wrote: For the last few days, building org with make up2 results in the following failed tests with Emacs for Mac OS X 24.3.1: Ran 456 tests, 448 results as expected, 8 unexpected (2013-09-24 10:59:21-0400) 5 expected failures 8 unexpected results: FAILED test-ob/org-babel-remove-result--results-code FAILED test-ob/org-babel-remove-result--results-default FAILED test-ob/org-babel-remove-result--results-html FAILED test-ob/org-babel-remove-result--results-latex FAILED test-ob/org-babel-remove-result--results-list FAILED test-ob/org-babel-remove-result--results-org FAILED test-ob/org-babel-remove-result--results-pp FAILED test-ob/org-babel-remove-result--results-wrap I'm seeing the same errors here, using the emacs from https://github.com/railwaycat/emacs-mac-port Alan Same errors here both on os x and gentoo. Longmin -- Longmin Wang (http://math.nankai.edu.cn/~wanglm/) Nankai University, 94 Weijin Road, Tianjin 300071, P. R. China http://math.nankai.edu.cn/~wanglm/
Re: [O] build errors on os x
same on Ubuntu 13.04, with Emacs 24.3.1 2013/9/26 Longmin WANG longminw...@gmail.com On Thu, Sep 26, 2013 at 3:32 PM, Alan Schmitt alan.schm...@polytechnique.org wrote: skip.coll...@gmail.com writes: The problem persists. Can anyone else confirm? Perhaps this should be added to the bug tracker file. For the record, my local.mk file is: EMACS = /Applications/Emacs.app/Contents/MacOS/Emacs prefix = /usr/local/share On Tue, Sep 24, 2013 at 11:11 AM, Skip Collins skip.coll...@gmail.com wrote: For the last few days, building org with make up2 results in the following failed tests with Emacs for Mac OS X 24.3.1: Ran 456 tests, 448 results as expected, 8 unexpected (2013-09-24 10:59:21-0400) 5 expected failures 8 unexpected results: FAILED test-ob/org-babel-remove-result--results-code FAILED test-ob/org-babel-remove-result--results-default FAILED test-ob/org-babel-remove-result--results-html FAILED test-ob/org-babel-remove-result--results-latex FAILED test-ob/org-babel-remove-result--results-list FAILED test-ob/org-babel-remove-result--results-org FAILED test-ob/org-babel-remove-result--results-pp FAILED test-ob/org-babel-remove-result--results-wrap I'm seeing the same errors here, using the emacs from https://github.com/railwaycat/emacs-mac-port Alan Same errors here both on os x and gentoo. Longmin -- Longmin Wang (http://math.nankai.edu.cn/~wanglm/) Nankai University, 94 Weijin Road, Tianjin 300071, P. R. China http://math.nankai.edu.cn/~wanglm/
Re: [O] Org mode issue tracker
Hi Suvayu, Suvayu Ali wrote: On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote: (date . 1376383861) * TODO . :24.3: 2013-08-13 Tue I'd use the inactive version of the timestamp, that is (for Michael) [2013-08-13 Tue]. Doesn't the agenda show active timestamps only? Yes, but then I don't expect an event timestamp. Developers working on bugs might want to add the file as their agenda file. Absolutely, but the question comes down to: do they want to have their today's agenda filled with Org bugs? If they add `org-issues.org' to their `org-agenda-files', that's clear they wanna have the pendings bugs, etc. in *some* custom agenda views, but do they want that always in the default agenda? Adding the bug as an event timestamp will show it only on that day. Then, you don't see it anymore... If you want to see them, I'd propose to put a SCHEDULED type of timestamp, or a DEADLINE one, no? If you don't need the bugs in your default agenda view, then you can still put the date as an inactive timestamp to keep track of when the bug was submitted. Another way (to what you show) would be to add it under a property `Created' or `CreatedOn'... Best regards, Seb -- Sebastien Vauban
Re: [O] A tutorial on using ox-rss.el to publish an Emacs-made blog
Hi all, Since I use ox-rss to generate my rss feed, I would like to make some clarification: * EMACS You need to have an Emacs version greater than 24.2.1. The function 'url-encode-url' must be present to generate successfully the RSS feed. Since I'm using Xubuntu 13.4. I had to add the PAA of Damien CASSOU to my apt config. Then I installed Emacs 24.3.1. The command 'url-encode-url' was listed in. * ORG Files You should take care about the PROPERTIES section you use in your org_files or section used to generate the RSS feeed. the CATEGORY might be usefull to manage multiple feeds. Personnaly I don't try it but with Liferea RSS reader this option is visible. Personnaly, I put the same date for the DATE and PUBDATE options. The date are correctly displayed in my RSS reader. E.G: 8X-cut here-- * HEADER ON :PROPERTIES: :DATE: 2012-10-12 Fri :PUBDATE: 2012-10-12 Fri :CATEGORY: Blog :END: BLABLABLA BLABLABLA BLABLABLA 8X-cut here-- Regards, Basile 2013/9/26 Detlef Steuer detlef.ste...@gmx.de On Wed, 25 Sep 2013 17:58:51 +0200 Carsten Dominik carsten.domi...@gmail.com wrote: +1. Tis is the post that might put me over the edge and try it. +1. Same status here. Detlef - Carsten
Re: [O] [PATCH] babel support for ABC notation music files
William Waites wwai...@tardis.ed.ac.uk writes: On Wed, 25 Sep 2013 09:15:45 -0600, Eric Schulte schulte.e...@gmail.com said: Hi William, I've added your ABC notation support to Org-mode. Thank you Eric! If you have time to add ob-ABC documentation to [1] that would be much appreciated but is not required. Patch for the web site attached. Applied, Thanks! -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
[O] different toc levels per headline?
Hi all, If I have something like: #+OPTIONS: toc:1 * h1 no options *** h2 * h3 * h1 toc:2 :PROPERTIES: :EXPORT_OPTIONS: toc:2 :END: *** h2 * h3 * h1 toc:3 :PROPERTIES: :EXPORT_OPTIONS: toc:3 :END: *** h2 * h3 I would expect a ToC which looks like: Table of Contents _ 1 h1 no options 2 h1 toc:1 .. 2.1 h2 3 h1 toc:2 .. 3.1 h2 . 3.1.1 h3 In otherwise, I would expect the EXPORT_OPTIONS in the subtrees to override the file-wide setting for `toc'. This expectation is based on what the manual says: Export options can be set: globally with variables; for an individual file by making variables buffer-local with in-buffer settings (*note In-buffer settings::), by setting individual keywords, or by specifying them in a compact form with the `#+OPTIONS' keyword; or for a tree by setting properties (*note Properties and Columns::). Options set at a specific level override options set at a more general level. However instead I get: Table of Contents _ 1 h1 no options 2 h1 toc:1 3 h1 toc:2 What am I missing, and is there another way to vary the toc level per subtree? Thanks! Adam
Re: [O] different toc levels per headline?
Hi Adam, EXPORT_OPTIONS are for the special case that you only export that specific subtree, by restricting the export to a tree using C-s in the dispatcher. They do not modify the behavior of a tree in a larger export of the document, and they also should not do so IMO. Generating a single document should follow one set of rules, not many. - Carsten On 26.9.2013, at 13:01, Adam Spiers orgm...@adamspiers.org wrote: Hi all, If I have something like: #+OPTIONS: toc:1 * h1 no options *** h2 * h3 * h1 toc:2 :PROPERTIES: :EXPORT_OPTIONS: toc:2 :END: *** h2 * h3 * h1 toc:3 :PROPERTIES: :EXPORT_OPTIONS: toc:3 :END: *** h2 * h3 I would expect a ToC which looks like: Table of Contents _ 1 h1 no options 2 h1 toc:1 .. 2.1 h2 3 h1 toc:2 .. 3.1 h2 . 3.1.1 h3 In otherwise, I would expect the EXPORT_OPTIONS in the subtrees to override the file-wide setting for `toc'. This expectation is based on what the manual says: Export options can be set: globally with variables; for an individual file by making variables buffer-local with in-buffer settings (*note In-buffer settings::), by setting individual keywords, or by specifying them in a compact form with the `#+OPTIONS' keyword; or for a tree by setting properties (*note Properties and Columns::). Options set at a specific level override options set at a more general level. However instead I get: Table of Contents _ 1 h1 no options 2 h1 toc:1 3 h1 toc:2 What am I missing, and is there another way to vary the toc level per subtree? Thanks! Adam signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Spurious exporting of text before first header
Hello, François Pinard pin...@iro.umontreal.ca writes: Nicolas Goaziou n.goaz...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: The spirit behind :export: is [...] I agree, this is a misfeature. This should be fixed in master. Thank you for bringing it out. Thanks as well. :-) OTOH, this fix introduces another problem. What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. IOW, it is easier to make that text disappear than to make it appear. IOW, even though the new behaviour is more logical, in the end, I'm not sure it is desirable. It's the old good versus best story. WDYT? Regards, -- Nicolas Goaziou
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
Hi, this does look good to me, except that the customize type of org-export-with-properties needs to be extended to allow for the list of strings. Please just go ahead and apply it to master, then I and hopefully others will test it further. - Carsten On 25.9.2013, at 22:57, Nicolas Goaziou n.goaz...@gmail.com wrote: Carsten Dominik carsten.domi...@gmail.com writes: Not really. It would simplify processing to have the list instead of a string, but indeed, a filter can accomplish all of it. Here is a first patch. It doesn't handle export back-ends in contrib. Regards, -- Nicolas Goaziou From c48974d10e0d57b6332fcfed384a49ee530ea04a Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou n.goaz...@gmail.com Date: Wed, 25 Sep 2013 21:27:29 +0200 Subject: [PATCH] ox: Add a defcustom to export properties drawers * lisp/ox.el (org-export-with-drawers): Improve docstring. (org-export-with-properties): New variable (org-export--skip-p): Handle new variable. (org-export-options-alist): Install new variable. * lisp/ox-ascii.el (org-ascii-node-property, org-ascii-property-drawer): New functions. * lisp/ox-html.el (org-html-node-property): New function. (org-html-property-drawer): Export property drawers as pre blocks. * lisp/ox-latex.el (org-latex-property-drawer, org-latex-node-property): New functions. * lisp/ox-man.el (org-man-node-property, org-man-property-drawer): New functions. * lisp/ox-md.el (org-md-node-property, org-md-property-drawer): New functions. * lisp/ox-odt.el (org-odt-node-property): New function. (org-odt-property-drawer): Export property drawers as fixed width blocks. * lisp/ox-texinfo.el (org-texinfo-node-property): New function. (org-texinfo-property-drawer): Export property drawers as verbatim blocks. * testing/lisp/test-ox.el: Add tests. --- lisp/ox-ascii.el| 23 +++ lisp/ox-html.el | 21 - lisp/ox-latex.el| 25 - lisp/ox-man.el | 19 ++- lisp/ox-md.el | 24 lisp/ox-odt.el | 23 ++- lisp/ox-texinfo.el | 21 - lisp/ox.el | 28 +--- testing/lisp/test-ox.el | 19 +++ 9 files changed, 183 insertions(+), 20 deletions(-) diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el index 74a7c64..e0a3fa9 100644 --- a/lisp/ox-ascii.el +++ b/lisp/ox-ascii.el @@ -81,10 +81,12 @@ (latex-fragment . org-ascii-latex-fragment) (line-break . org-ascii-line-break) (link . org-ascii-link) +(node-property . org-ascii-node-property) (paragraph . org-ascii-paragraph) (plain-list . org-ascii-plain-list) (plain-text . org-ascii-plain-text) (planning . org-ascii-planning) +(property-drawer . org-ascii-property-drawer) (quote-block . org-ascii-quote-block) (quote-section . org-ascii-quote-section) (radio-target . org-ascii-radio-target) @@ -1440,6 +1442,18 @@ INFO is a plist holding contextual information. (unless org-ascii-links-to-notes (format (%s) raw-link + Node Properties + +(defun org-ascii-node-property (node-property contents info) + Transcode a NODE-PROPERTY element from Org to ASCII. +CONTENTS is nil. INFO is a plist holding contextual +information. + (format %s:%s + (org-element-property :key node-property) + (let ((value (org-element-property :value node-property))) +(if value (concat value) + + Paragraph (defun org-ascii-paragraph (paragraph contents info) @@ -1509,6 +1523,15 @@ channel. )) + Property Drawer + +(defun org-ascii-property-drawer (property-drawer contents info) + Transcode a PROPERTY-DRAWER element from Org to ASCII. +CONTENTS holds the contents of the drawer. INFO is a plist +holding contextual information. + (org-string-nw-p contents)) + + Quote Block (defun org-ascii-quote-block (quote-block contents info) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index 14b31b2..66862bc 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -76,6 +76,7 @@ (latex-fragment . org-html-latex-fragment) (line-break . org-html-line-break) (link . org-html-link) +(node-property . org-html-node-property) (paragraph . org-html-paragraph) (plain-list . org-html-plain-list) (plain-text . org-html-plain-text) @@ -2782,6 +2783,17 @@ INFO is a plist holding contextual information. See ;; No path, only description. Try to do something useful. (t (format i%s/i desc) + Node Property + +(defun org-html-node-property (node-property contents info) + Transcode a NODE-PROPERTY element from Org to HTML. +CONTENTS is nil. INFO is a plist holding contextual +information. + (format %s:%s + (org-element-property :key node-property) + (let ((value
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: François Pinard pin...@iro.umontreal.ca writes: Nicolas Goaziou n.goaz...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: The spirit behind :export: is [...] I agree, this is a misfeature. This should be fixed in master. Thank you for bringing it out. Thanks as well. :-) OTOH, this fix introduces another problem. What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. He would have to add as well the tag :ignoreheading:, right, and would have no problem in the output? Though, he would see the headline in his Org buffer, what he'd dislike anyway (like François). IOW, it is easier to make that text disappear than to make it appear. IOW, even though the new behaviour is more logical, in the end, I'm not sure it is desirable. It's the old good versus best story. WDYT? At this stage, I don't have any preference for one over the other. Best regards, Seb -- Sebastien Vauban
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
Hello, Carsten Dominik carsten.domi...@gmail.com writes: this does look good to me, except that the customize type of org-export-with-properties needs to be extended to allow for the list of strings. Please just go ahead and apply it to master, then I and hopefully others will test it further. Fixed and done. I added an entry in the manual. Regards, -- Nicolas Goaziou
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
Excellent, thank you for the fast solution to this issue. Will you also work on exporters in contrib, or should I ping the respective authors to do this? - Carsten On 26.9.2013, at 13:48, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Carsten Dominik carsten.domi...@gmail.com writes: this does look good to me, except that the customize type of org-export-with-properties needs to be extended to allow for the list of strings. Please just go ahead and apply it to master, then I and hopefully others will test it further. Fixed and done. I added an entry in the manual. Regards, -- Nicolas Goaziou signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Org mode issue tracker
Hello Michael, On Thu, Sep 26, 2013 at 11:34:31AM +0200, Michael Albinus wrote: Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: ((source . unknown) (found_versions 24.3) Emacs version ends up as a tag: * TODO . :24.3: found_versions is optional. So we cannot assume it is always set. Furthermore, it is a *list* of strings (although I haven't seen ever more than one entry). What to do in this case? Indeed, I guess this is quite common. I would think handling this as an optional tag should suffice. (severity . normal) I would really appreciate, if we could make the severity visible. In the org manual, I've read something about A B C priorities. On debbugs, we have the severities serious, important, normal, minor, wishlist, and tagged. How could we map them on the TODO items? In debbugs-gnu we use different faces (colors) for the entries. You are right! The default set of priorities are: A, B, and C. But it can be extended; see (info (org) Priorities). (subject . 24.3; org-crypt: Making epg-context local to *epg* while let-bound!) * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :GMANE_URL: http://mid.gmane.org/877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org :END: 2013-08-13 Tue As you see above, it would be great if we could simplify the suject and tag the org-module involved (note hyphens are not allowed, they need to be transformed to underscore). OK. However, we cannot assume a given syntax on the subject. An error can be reported by a simple mail to @debbugs.gnu.org, with free subject. A preformatted subject can be assumed only, if the error has been reported by `report-emacs-bug' or `org-submit-bug-report'. Would it be possible to have some heuristics? If reported by report-emacs-bug or org-submit-bug-report, try to extract those tags from the subject, otherwise ignore them. (pending . pending) And this should finally decide the TODO state. For the moment a reasonable mapping would be pending - TODO. But would be good to have support for DONE, WIP, or similar (I'm not familiar with all the debbug states :-p) The pending field could have the values pending, forwarded or done. forwarded does not seem to be used on debbugs.gnu.org. (tags) Tags are useful for more information on the status. They are a list of strings like fixed, notabug, wontfix, unreproducible, moreinfo or patch. In the given example, this list is empty. I have a suggestion to combine the above two. Assuming we can't have multiple tags from debbugs, something like below should work. - pending with no tags - TODO - done with no tags - DONE - I can see the use of unreproducible, moreinfo, or patch tags with pending - UNREPRODUCIBLE, MOREINFO, or PATCH - Whereas the other tags, fixed, notabug, wontfix, goes with done. We can map them to: DONE, NOTABUG, WONTFIX. As you see, I treat fixed the same as done with no tags. This can be implemented by type TODO keywords. You basically have 2 states, TODO and DONE. But there are different kinds of them. (setq org-todo-keywords '((type TODO(t) UNREPRODUCIBLE(u) MOREINFO(m) PATCH(p) | DONE(d) NOTABUG(n) WONTFIX(w Here I'm a bit uncertain about the syntax. Are multiple DONE type keywords allowed? If not we could split this into sets as follows: (setq org-todo-keywords '((type TODO(t) UNREPRODUCIBLE(u) MOREINFO(m) PATCH(p) | DONE(d)) (sequence | NOTABUG(n)) (sequence | WONTFIX(w WDYT? (package emacs org-mode) I guess this is how you filter out org-mode bugs from the rest. Yep. In the org-mode case, it is sufficient to filter for the package org-mode. But why not create a todo list for another debbugs project, like emacs or gnus or whatever? And btw, one could filter also for other attributes but just package. Even full text search is possible. Great idea, there could be a defcustom where you assign different org files for different package tags! * TODO Making epg-context local to *epg* while let-bound! :24.3:org_crypt: :PROPERTIES: :DEBGUGS_ID: 15081 :REPORTER: Thierry Volpiatto thierry.volpiatto-re5jqeeqqe8avxtiumw...@public.gmane.org :GMANE_URL: http://mid.gmane.org/877gfqkm9t.fsf-re5jqeeqqe8avxtiumw...@public.gmane.org :END: Yep. Now it comes to the attached emails. In a second (!) step, debbugs-gnu is able to retrieve the corresponding emails. In the given example, it would call (debbugs-get-bug-log 15081) This returns a list like (((body . The body of the message) (msg_num . 5) (attachments) (header . All header lines of the message))) I have just shown one message, of course all messages will be retrieved. Alternative, one could retrieve the messages in MBOX format. Wouldn't it be
Re: [O] different toc levels per headline?
Hi Carsten, On Thu, Sep 26, 2013 at 01:15:56PM +0200, Carsten Dominik wrote: Hi Adam, EXPORT_OPTIONS are for the special case that you only export that specific subtree, by restricting the export to a tree using C-s in the dispatcher. They do not modify the behavior of a tree in a larger export of the document, and they also should not do so IMO. Thanks a lot for the reply. However, what you say seems to directly contradict this sentence in the manual: Options set at a specific level override options set at a more general level. which is why this confused me. I guess that sentence was intended to refer only to subtree exports, not whole document exports, but that meaning was not clear to me. Perhaps it can be clarified via a small tweak? Generating a single document should follow one set of rules, not many. I agree that KISS is valuable when designing the rules. However, it also seems a perfectly reasonable requirement to be able to control the toc: level per subtree during a whole document export, since in an arbitrary document there's no guarantee that every headline has the same depth. E.g. one chapter may have a few deep subsections, whereas another may contain lots of shallow subsections. In these scenarios it is clearly beneficial to allow the author to choose which subsections appear in the ToC. So is there a way of achieving this? If not, please consider this a feature request ;-) Thanks! Adam
Re: [O] example filter for code blocks?
Check out `org-export-filter-src-block-functions'. It shouldn't be too hard to add a custom filter to that list which may be used to process all code block bodies during latex export. Best, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] Org mode issue tracker
On Thu, Sep 26, 2013 at 02:13:19PM +0200, Suvayu Ali wrote: Now it comes to the attached emails. In a second (!) step, debbugs-gnu is able to retrieve the corresponding emails. In the given example, it would call (debbugs-get-bug-log 15081) This returns a list like (((body . The body of the message) (msg_num . 5) (attachments) (header . All header lines of the message))) I have just shown one message, of course all messages will be retrieved. Alternative, one could retrieve the messages in MBOX format. Wouldn't it be nice, if we could include the messages as well? Likely not by default (it would be expensive to download all messages for, let's say, 500 bugs at once). But we could add a kind of link which, when followed, could show the messages as well in org-mode. Somehow. Since this is possibile, I think my suggestion about GMANE_URL is redundant. Dealing with this much more detailed information is a matter of taste I think. For example, some like their TODOs to be clean and simple, with all the details in headline attachments. Others might like all the information easily available under the headline formatted as Org text (text as plain text, email attachments as links). I think this requires input from the community. For now as a safe default you could have each message as a sub-heading of the TODO. I forgot to add; regarding your comment about retrieving several messages might be expensive, there could be an elisp link or a babel source block that does this on demand. -- Suvayu Open source is the future. It sets us free.
[O] Invalid function: org-with-silent-modifications
Hello, Trying to provide batch Emacs/Org scripts to colleagues, I must ensure that they have Org 8. I wrote the following code so that users which have a default (Cygwin) Emacs 24.3.1 (with the default Org 7.9.3f) are proposed an upgrade through the `package' manager: --8---cut here---start-8--- (require 'package) (add-to-list 'package-archives '(org . http://orgmode.org/elpa/;)) (package-initialize) ;; version info (let ((org-dir (file-name-directory (locate-library org (message Org mode version %s (org @ %s) (org-version) org-dir)) (unless (string-match ^8 (org-version)) (message This version of Org mode is no longer supported) (if (yes-or-no-p (format Install package `%s'? 'org)) (ignore-errors (package-install 'org)) (setq debug-on-error nil) (error Please upgrade to 8 or later))) --8---cut here---end---8--- Problem experienced by colleagues: Invalid function: org-with-silent-modifications. Looking on the web, I find a post [1] where Bastien tells: When installing from ELPA, please do so from a fresh Emacs session where no Org function has been called. That wasn't the case in the above code, as I first had to call `org-version' to check for their current version, then install from ELPA if they don't have an Org 8... So, - Is there a way to unload Org before installing from ELPA? (= workaround) or better: - Is there a way to fix the problem? (= solution) Best regards, Seb [1] http://comments.gmane.org/gmane.emacs.orgmode/70880 -- Sebastien Vauban
Re: [O] different toc levels per headline?
On 26.9.2013, at 14:16, Adam Spiers orgm...@adamspiers.org wrote: Hi Carsten, On Thu, Sep 26, 2013 at 01:15:56PM +0200, Carsten Dominik wrote: Hi Adam, EXPORT_OPTIONS are for the special case that you only export that specific subtree, by restricting the export to a tree using C-s in the dispatcher. They do not modify the behavior of a tree in a larger export of the document, and they also should not do so IMO. Thanks a lot for the reply. However, what you say seems to directly contradict this sentence in the manual: Options set at a specific level override options set at a more general level. which is why this confused me. I guess that sentence was intended to refer only to subtree exports, not whole document exports, but that meaning was not clear to me. I think it means this in general, but I also think that toc creation is done at a global level, and not recursive in the tree. Maybe Nicolas has an authoritative answer on this one. - Carsten Perhaps it can be clarified via a small tweak? Generating a single document should follow one set of rules, not many. I agree that KISS is valuable when designing the rules. However, it also seems a perfectly reasonable requirement to be able to control the toc: level per subtree during a whole document export, since in an arbitrary document there's no guarantee that every headline has the same depth. E.g. one chapter may have a few deep subsections, whereas another may contain lots of shallow subsections. In these scenarios it is clearly beneficial to allow the author to choose which subsections appear in the ToC. So is there a way of achieving this? If not, please consider this a feature request ;-) Thanks! Adam signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Org mode issue tracker
Suvayu Ali fatkasuvayu+li...@gmail.com writes: I forgot to add; regarding your comment about retrieving several messages might be expensive, there could be an elisp link or a babel source block that does this on demand. Elisp link is the beast I was looking for, thanks. Likely, there is no need for a babel source block. Best regards, Michael.
[O] Using Variable Width Fonts for org-mode and Fixed Width for Tables
I am struggling to get this to work. In my init files I have:
(set-default-font DejaVu Serif Italic)
I have followed the advice on StackOverflow
http://stackoverflow.com/questions/3758139/variable-pitch-for-org-mode-fixed-pitch-for-tables
and customized my Init file to include:
(set-face-attribute 'org-table nil :inherit 'fixed-pitch)
However, table formatting is still screwed up. C-u C-x = shows
xft:-unknown-IM FELL DW
Pica-normal-italic-normal-*-15-*-*-*-*-0-iso10646-1 (#x29)
Character code properties: customize what to show
name: LATIN CAPITAL LETTER F
general-category: Lu (Letter, Uppercase)
decomposition: (70) ('F')
There are text properties here:
face org-table
fontifiedt
line-prefix [Show]
wrap-prefix [Show]
I have tried setting the font for org-table using Emacs Customize
Interface, but without any success. Ideally I want tables to use a
monospace font like Inconsolata or DejaVu mono. Can anyone provide an
example of how to set org-table to use a specified fixed width font.
Ian.
Re: [O] org-caldav for Google or Zimbra?
And Eric S. Fraga writes: Can you expand on this? I am not sure what you mean by endpoint. I use org-caldav-sync several times a day and it generally works very well with Google's calendar service. Google has deprecated the URL in org-caldav, and that old URL does not work for me. The new one is documented at https://developers.google.com/google-apps/calendar/caldav/v2/guide#new_endpoint Fiddling with the regexp in org-caldav-events-url triggers an error apparently in the authentication code: Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil) url-http-handle-authentication(nil) url-http-parse-headers() url-http-chunked-encoding-after-change-function(415 440 25) url-http-wait-for-headers-change-function(1 453 452) url-http-generic-filter(#process apidata.googleusercontent.com HTTP/1.1 401 Unauthorized\nWWW-Authenticate: Bearer realm=\https://www.google.com/accounts/AuthSubRequest\\nContent-Type: text/html; charset=UTF-8\nDate: Thu, 26 Sep 2013 13:48:37 GMT\nExpires: Thu, 26 Sep 2013 13:48:37 GMT\nCache-Control: private, max-age=0\nX-Content-Type-Options: nosniff\nX-Frame-Options: SAMEORIGIN\nX-XSS-Protection: 1; mode=block\nServer: GSE\nAlternate-Protocol: 443:quic\nTransfer-Encoding: chunked\n\ne\nLogin Required\n0\n\n) accept-process-output(#process apidata.googleusercontent.com) #[0 \302\303\300@!)\207 [(#process apidata.googleusercontent.com) inhibit-quit nil accept-process-output] 2 \n\n(fn)]() funcall(#[0 \302\303\300@!)\207 [(#process apidata.googleusercontent.com) inhibit-quit nil accept-process-output] 2 \n\n(fn)]) url-retrieve-synchronously(https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/;) url-http-options(https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/;) url-dav-supported-p(https://apidata.googleusercontent.com/caldav/v2/jason.riedy/events/;) (if (url-dav-supported-p (org-caldav-events-url)) nil (error The URL %s does not seem to accept DAV requests (org-caldav-events-url))) org-caldav-sync() eval((org-caldav-sync) nil) eval-last-sexp-1(nil) eval-last-sexp(nil) call-interactively(eval-last-sexp nil nil) Someone on github reported the same issue. -- Jason
Re: [O] Org mode issue tracker
Hi, Suvayu Ali fatkasuvayu+li...@gmail.com writes: * TODO Subject timestamp :emacs_ver:org_ver:org_module: ... Emacs version ends up as a tag: * TODO . :24.3: Or, if I add an Org version: * TODO . :24.3:8.0.3: These bare numbers seem a bit too anonymous to me. I think it's unlikely that Org will reach versions in the 20's anytime soon so collision won't happen for a while but eventually (hackers willing!) it will. So, I suggest simply qualifying the versions like: * TODO . :emacs_24.3:org_8.0.3: I can also see a desire to list other software and their versions that might be implicated in the bug being reported. Listing their bare versions as tags is, I think, obviously no good. They could just include this info in an ad-hoc manner in the body of their report, but maybe it would be good to define a property to explicitly list them following the same package_version pattern of the tags. * TODO . :emacs_24.3:org_8.0.3: :PROPERTIES: :IMPLICATED_SOFTWARE: texlive_2012.20120611-5 beamer_3.10-2 BTW, I think an issue tracker in Org is very interesting. I look forward to seeing how it evolves. -Brett. pgp6kwuMSCpiV.pgp Description: PGP signature
Re: [O] different toc levels per headline?
Carsten Dominik carsten.domi...@gmail.com writes: On 26.9.2013, at 14:16, Adam Spiers orgm...@adamspiers.org wrote: Thanks a lot for the reply. However, what you say seems to directly contradict this sentence in the manual: Options set at a specific level override options set at a more general level. which is why this confused me. I guess that sentence was intended to refer only to subtree exports, not whole document exports, but that meaning was not clear to me. I think it means this in general, but I also think that toc creation is done at a global level, and not recursive in the tree. Maybe Nicolas has an authoritative answer on this one. Not really. For the record, the full paragraph is: Export options can be set: globally with variables; for an individual file by making variables buffer-local with in-buffer settings, by setting individual keywords, or by specifying them in a compact form with the '#+OPTIONS' keyword; or for a tree by setting properties. Options set at a specific level override options set at a more general level. There are three ways (four if you use a subtree export) to tweak export settings. The last sentence means that more specific ways have precedence over more general ones. IOW: #+OPTIONS or #+KEYWORDS variables and in the case of a subtree export: Properties #+OPTIONS or #+KEYWORDS variables Regards, -- Nicolas Goaziou
Re: [O] Convention for tags and properties
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Following those conventions, I guess that: - The `crypt' tag should be renamed `CRYPT' - The `Effort' property should be renamed `EFFORT' Right? FWIW, I think you're correct. Regards, -- Nicolas Goaziou
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
Carsten Dominik carsten.domi...@gmail.com writes: Will you also work on exporters in contrib, or should I ping the respective authors to do this? This is a grunt job. Also, only ox-confluence and ox-groff have to be updated. I will commit the changes in a little while. Regards, -- Nicolas Goaziou
Re: [O] Spurious exporting of text before first header
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Nicolas Goaziou wrote: What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. He would have to add as well the tag :ignoreheading:, right, and would have no problem in the output? AFAIK, there is no such thing as a :ignoreheading: tag, at least not in the general case (Beamer export back-end has this feature, but it's a kludge). You may be referring to a personal export filter. Regards, -- Nicolas Goaziou
Re: [O] build errors on os x
On 2013-09-25 20:44, Skip Collins wrote: The problem persists. Can anyone else confirm? Perhaps this should be added to the bug tracker file. For the record, my local.mk file is: FWIW, on solaris i get the following on th latest master branch, commit ec28c33062b3468abc2fa2458118df11165b096d: Ran 453 tests, 443 results as expected, 10 unexpected (2013-09-26 10:36:04-0400) 6 expected failures 10 unexpected results: FAILED ob-exp/use-case-of-reading-entry-properties FAILED test-ob/org-babel-remove-result--results-code FAILED test-ob/org-babel-remove-result--results-default FAILED test-ob/org-babel-remove-result--results-html FAILED test-ob/org-babel-remove-result--results-latex FAILED test-ob/org-babel-remove-result--results-list FAILED test-ob/org-babel-remove-result--results-org FAILED test-ob/org-babel-remove-result--results-pp FAILED test-ob/org-babel-remove-result--results-wrap FAILED test-ob/specific-colnames So, this is not a mac specific problem. rick
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Nicolas Goaziou wrote: What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. He would have to add as well the tag :ignoreheading:, right, and would have no problem in the output? AFAIK, there is no such thing as a :ignoreheading: tag, at least not in the general case (Beamer export back-end has this feature, but it's a kludge). You may be referring to a personal export filter. Entirely possible: I've seen that while reading posts of this ML. Wouldn't it be worth to make such a filter officially present in Org, not only for Beamer? Best regards, Seb -- Sebastien Vauban
Re: [O] Spurious exporting of text before first header
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Wouldn't it be worth to make such a filter officially present in Org, not only for Beamer? Here we are. No it wouldn't. As I said, it's a kludge used as a workaround in Beamer-specific syntax because headlines, which are not blocks, can only be ended with another headline or the end of buffer. It's a specific solution for a local problem. These do not usually generalize very well. For example, visibility cycling isn't related anymore to sections in export output: * H1 Section 1 * Ignore me! :ignoreheading: Section 1 (continued) * H2 Section 2 You can achieve the same (and, apparently, you already do) with a simple hook, without extending Org syntax. I _really_ think that's better. Regards, -- Nicolas Goaziou
[O] Wrong captialisation from a latex src block
Dear (),
when I'm trying to asign a variable in the following way:
#+BEGIN_SRC latex :var Idir = (concat (org-attach-dir) /PostImage)
\animategraphics[autoplay,loop,width=10cm]
{5}{Idir}{716}{728}
#+END_SRC
I'm getting a wrong capitalisation of Idir:
#+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/Uidg1626/Development/Report/Tz/Haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
instead of the following corrected output
# #+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/uidg1626/development/report/tz/haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
Am I doing something wrong?
Thanks
Dieter
--
Best wishes
H. Dieter Wilhelm
Darmstadt
Germany
Re: [O] Wrong captialisation from a latex src block
Sorry, I forgot to say that I'm using org-8.2.
2013/9/26 Dieter Wilhelm, H. die...@duenenhof-wilhelm.de:
Dear (),
when I'm trying to asign a variable in the following way:
#+BEGIN_SRC latex :var Idir = (concat (org-attach-dir) /PostImage)
\animategraphics[autoplay,loop,width=10cm]
{5}{Idir}{716}{728}
#+END_SRC
I'm getting a wrong capitalisation of Idir:
#+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/Uidg1626/Development/Report/Tz/Haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
instead of the following corrected output
# #+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/uidg1626/development/report/tz/haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
Am I doing something wrong?
Thanks
Dieter
--
Best wishes
H. Dieter Wilhelm
Darmstadt
Germany
Re: [O] different toc levels per headline?
On Thu, Sep 26, 2013 at 04:24:57PM +0200, Nicolas Goaziou wrote: Carsten Dominik carsten.domi...@gmail.com writes: On 26.9.2013, at 14:16, Adam Spiers orgm...@adamspiers.org wrote: Thanks a lot for the reply. However, what you say seems to directly contradict this sentence in the manual: Options set at a specific level override options set at a more general level. which is why this confused me. I guess that sentence was intended to refer only to subtree exports, not whole document exports, but that meaning was not clear to me. I think it means this in general, but I also think that toc creation is done at a global level, and not recursive in the tree. Maybe Nicolas has an authoritative answer on this one. Not really. For the record, the full paragraph is: Export options can be set: globally with variables; for an individual file by making variables buffer-local with in-buffer settings, by setting individual keywords, or by specifying them in a compact form with the '#+OPTIONS' keyword; or for a tree by setting properties. Options set at a specific level override options set at a more general level. Right, I quoted that in my original post :-) There are three ways (four if you use a subtree export) to tweak export settings. The last sentence means that more specific ways have precedence over more general ones. IOW: #+OPTIONS or #+KEYWORDS variables and in the case of a subtree export: Properties #+OPTIONS or #+KEYWORDS variables Sure, I understood that. But AFAICS it doesn't provide a way of controlling the depth of headings within the ToC _per_heading_, which as I suggested in my previous email shouldn't be a particularly rare use case. Cheers, Adam
[O] Export of inline source blocks
Hi,
When exporting an org file containing the line
,
| Here is some source code: src_c++[:exports code]{int a;} It is inline.
`
the following HTML is generated
,
| Here is some source code: #+BEGINsubSRC/sub c++
| int a;
| #+ENDsubSRC/sub It is inline.
`
which looks approximately like this
,
| Here is some source code: #+BEGINSRC c++ int a; #+ENDSRC It is inline.
`
When rendered, as opposed to the desired
,
| Here is some source code: int a; It is inline.
`
where the 'int a;' would be syntax highlighted, use a proportional font,
etc.
Switching automitic subscripting off with
,
| #+OPTIONS: ^:{}
`
doesn't improve the situation. The generated HTML is now
,
| Here is some source code: #+BEGIN_SRC c++
| int a;
| #+END_SRC It is inline.
`
which has the equally unsatisfactory visual appearance
,
| Here is some source code: #+BEGIN_SRC c++ int a; #+END_SRC It is inline.
`
when rendered.
The experiments were performed with org mode 8.2 on Emacs 24.3.50.1
Could you point out my mistake, please?
Thank you.
Re: [O] SUMMARY: [Feature Request] Make property-drawers exportable
On 26.9.2013, at 16:33, Nicolas Goaziou n.goaz...@gmail.com wrote: Carsten Dominik carsten.domi...@gmail.com writes: Will you also work on exporters in contrib, or should I ping the respective authors to do this? This is a grunt job. Also, only ox-confluence and ox-groff have to be updated. I will commit the changes in a little while. Thank you again. - Carsten signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] Export of inline source blocks
Inline code blocks are meant for exporting results, not code. I don't
believe Org-mode supports inline source-code export. I'd use simple
verbatim markers instead.
Cheers,
Jacek Generowicz jacek.generow...@cern.ch writes:
Hi,
When exporting an org file containing the line
,
| Here is some source code: src_c++[:exports code]{int a;} It is inline.
`
the following HTML is generated
,
| Here is some source code: #+BEGINsubSRC/sub c++
| int a;
| #+ENDsubSRC/sub It is inline.
`
which looks approximately like this
,
| Here is some source code: #+BEGINSRC c++ int a; #+ENDSRC It is inline.
`
When rendered, as opposed to the desired
,
| Here is some source code: int a; It is inline.
`
where the 'int a;' would be syntax highlighted, use a proportional font,
etc.
Switching automitic subscripting off with
,
| #+OPTIONS: ^:{}
`
doesn't improve the situation. The generated HTML is now
,
| Here is some source code: #+BEGIN_SRC c++
| int a;
| #+END_SRC It is inline.
`
which has the equally unsatisfactory visual appearance
,
| Here is some source code: #+BEGIN_SRC c++ int a; #+END_SRC It is inline.
`
when rendered.
The experiments were performed with org mode 8.2 on Emacs 24.3.50.1
Could you point out my mistake, please?
Thank you.
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
Re: [O] org mode R remote code evaluation
#+BEGIN_SRC sql :engine postgresql :dir /grid: :results output :colnames yes select 2+2 as four, 1+1 as one; #+END_SRC #+RESULTS: | 4\t2 | It works! As you see there are still some problems with ob-sql (no column names and \t is not parsed correctly) but the remote execution seems to be fixed. Thanks, Alex On Thu, Sep 26, 2013 at 11:53 AM, Michael Albinus michael.albi...@gmx.dewrote: Alexander Vorobiev alexander.vorob...@gmail.com writes: Hi Michael, Hi Alex, I can't apply the patch for some reason. Strange. Could you send it and/or new ob-core.el as a attachment? It's appended. Thanks, Alex Best regards, Michael.
Re: [O] org mode R remote code evaluation
Alexander Vorobiev alexander.vorob...@gmail.com writes: #+BEGIN_SRC sql :engine postgresql :dir /grid: :results output : colnames yes select 2+2 as four, 1+1 as one; #+END_SRC #+RESULTS: | 4\t2 | It works! As you see there are still some problems with ob-sql (no column names and \t is not parsed correctly) but the remote execution seems to be fixed. Great! I will prepare the patch tomorrow, as instructed by Eric. Thanks, Alex Best regards, Michael.
Re: [O] example filter for code blocks?
Hi everyone,
Thanks for the tips in using export filters for code blocks. I thought I
would share my current solution. The goal was to export all the code blocks
in an org-file to files systematically named part1/script-%d.py where %d is
a number. I didnot want to tangle exactly, because I wanted to avoid naming
the code block tangle files.
Then, I wanted to insert a pdf link that would open the file, after the
syntax highlighted code.
I wanted this because it is not convenient to copy and paste the
syntax-highlighted code into an editor. I teach from the pdf that is
generated, and it would be convenient to just open the code, edit and rerun
to explore solutions.
So, here is the solution:
At the top of my orgfile, I have this definition which creates a pdf link.
#+LATEX_HEADER: \newcommand{\LaunchBinary}[2]{%
#+LATEX_HEADER: % #1: layer name,
#+LATEX_HEADER: % #2: link text
#+LATEX_HEADER: \leavevmode%
#+LATEX_HEADER: \pdfstartlink attr{/C [0.9 0 0] /Border [0 0 2]} user {
#+LATEX_HEADER: /Subtype /Link
#+LATEX_HEADER: /A
#+LATEX_HEADER: /F
#+LATEX_HEADER: /DOS (#1)
#+LATEX_HEADER:
#+LATEX_HEADER: /S /Launch
#+LATEX_HEADER:
#+LATEX_HEADER: } #2%
#+LATEX_HEADER: \pdfendlink%
#+LATEX_HEADER: }
Then, I use the code snippet below to export the file to latex. It is
stored in a noexport section at the end of the document. basically I set a
counter, and wrote a filter function for src blocks. the function captures
the lines between the first and last (first is \begin{minted}... and last
is \end{minted} in this case. I write those lines to a file named according
to the counter, and finally insert \LaunchBinary... into the string
returned by the filter. everything else in this let block is just
fine-tuning the latex packages, and export behavior.
(let (
;; these packages are loaded in the latex file
(org-latex-default-packages-alist
'((utf8 inputenc nil)
(T1 fontenc nil)
( fixltx2e nil)
( natbib t)
( url t)
( graphicx t)
( textcomp t)
( underscore t)
( amsmath t)
(version=3 mhchem t)
(tight,pdftex web nil)
( exerquiz nil)
(ImplMulti dljslib nil)
))
(async nil)
(subtreep nil)
(visible-only nil)
(body-only nil))
(setq counter 0)
(defun ox-mrkup-filter-src-block (text back-end info)
(setq counter (+ counter 1))
(let ((filename (format part1-scripts/script-%d.py counter)))
(with-temp-buffer
(insert (mapconcat 'identity (butlast (cdr (split-string text \n
t))) \n))
(write-region (point-min) (point-max) filename))
(format %s
\\LaunchBinary{%s}{Open the python script (%s).}
text filename filename)))
(let ((org-export-filter-src-block-functions '(ox-mrkup-filter-src-block)))
(org-latex-export-to-latex async subtreep visible-only body-only
'(:with-author t
:with-date t
:with-title t
:with-timestamps t
:with-todo-keywords t
:with-toc nil
After building the pdf with pdflatex, I get a link with a red box around it
that I can click on, and on my system it opens the python file in the
python editor I have configured to open the file!
Thanks again!
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
Re: [O] Spurious exporting of text before first header
Hello Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Wouldn't it be worth to make such a filter officially present in Org, not only for Beamer? Here we are. No it wouldn't. As I said, it's a kludge used as a workaround in Beamer-specific syntax because headlines, which are not blocks, can only be ended with another headline or the end of buffer. It's a specific solution for a local problem. I understand it *is* needed for Beamer. These do not usually generalize very well. For example, visibility cycling isn't related anymore to sections in export output: * H1 Section 1 * Ignore me! :ignoreheading: Section 1 (continued) * H2 Section 2 For me, visibility in the original Org buffer and sections in export output are orthogonal things. They don't impact each other. You can achieve the same (and, apparently, you already do) with a simple hook, without extending Org syntax. I _really_ think that's better. Yes, but that would solve the problem of having preliminary notes well or not exported in the output, depending on the fact you tag the section or not. That was what you said: there is no good solution between saying that preliminary notes will always be exported (as François wished) or never, if we can't customize that. And that would be not only for me: by putting a hook locally, my file won't produce the same output for all the other users. That was the point of having it in Org, as it seems it is a common request. That said, that's not something I need; so I don't mind that much. Best regards, Seb -- Sebastien Vauban
Re: [O] org-caldav for Google or Zimbra?
Jason Riedy writes: Google has deprecated the URL in org-caldav, and that old URL does not work for me. The new one is documented at https://developers.google.com/google-apps/calendar/caldav/v2/guide#new_endpoint Fiddling with the regexp in org-caldav-events-url triggers an error apparently in the authentication code: Google has changed authentication on the new endpoint to OAuth. Julien has written an OAuth2 client implementation, which is in GNU ELPA, but I didn't have time to look at it yet. Not sure when I get to it; I hope someone beats me to it. -David
Re: [O] Export of inline source blocks
Eric Schulte writes: Inline code blocks are meant for exporting results, not code. I don't believe Org-mode supports inline source-code export. I see. Thanks. I'd use simple verbatim markers instead. How would I persuade those not to collapse whitespace? Both ~stuff~ and =stuff= get exported as codestuff/code, while #+BEGIN_SRC lang stuff #+end_SRC gets exported as pre class=src src-lang ... /pre
Re: [O] example filter for code blocks?
Check out `org-export-filter-src-block-functions'. It shouldn't be too hard to add a custom filter to that list which may be used to process all code block bodies during latex export. Somewhat off-topic, but, thanks for pointing out this variable Eric I've been wanting an approach that would wrap all exported code in some kind of folded mode (maybe a jquery accordion). Initially the html document by default would display only exported 'results'. The user could choose to display the code behind any result with a single click (keyboard interactivity would be even better). Do you think that this is the right 'hook' to apply such? Have you seen this already done better somewhere? ~ Malcolm Cook Best, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] org-caldav for Google or Zimbra?
And David Engster writes: Google has changed authentication on the new endpoint to OAuth. Julien has written an OAuth2 client implementation, which is in GNU ELPA, but I didn't have time to look at it yet. Not sure when I get to it; I hope someone beats me to it. Ok, well understood. Thank you! -- Jason
Re: [O] example filter for code blocks?
I think the approach I sent earlier would potentially work. essentially you
would get the html code and wrap it with whatever text is required for
the folding mode. you would return something like (format code to
fold%s/end code to fold text) where text is the html code from the src
block. In latex I had to parse that text a little bit because the first
line was \begin{minted}... and the last line was \end{minted}, which I did
not want.
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Thu, Sep 26, 2013 at 2:31 PM, Cook, Malcolm m...@stowers.org wrote:
Check out `org-export-filter-src-block-functions'. It shouldn't be too
hard to add a custom filter to that list which may be used to process
all code block bodies during latex export.
Somewhat off-topic, but, thanks for pointing out this variable Eric
I've been wanting an approach that would wrap all exported code in some
kind of folded mode (maybe a jquery accordion). Initially the html
document by default would display only exported 'results'. The user could
choose to display the code behind any result with a single click (keyboard
interactivity would be even better). Do you think that this is the right
'hook' to apply such? Have you seen this already done better somewhere?
~ Malcolm Cook
Best,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
Re: [O] example filter for code blocks?
Hi John, John Kitchin jkitc...@andrew.cmu.edu writes: Hi everyone, Thanks for the tips in using export filters for code blocks. I thought I would share my current solution. The goal was to export all the code blocks in an org-file to files systematically named part1/script-%d.py where %d is a number. I didnot want to tangle exactly, because I wanted to avoid naming the code block tangle files. Then, I wanted to insert a pdf link that would open the file, after the syntax highlighted code. I wanted this because it is not convenient to copy and paste the syntax-highlighted code into an editor. I teach from the pdf that is generated, and it would be convenient to just open the code, edit and rerun to explore solutions. This seems like it might be an elegant way to distribute a piece of reproducible research. I suspect most readers would prefer to have a pdf entry point into a compendium over an Org-mode entry point. Instead of distributing the Org-mode file that is configured to make a pdf file, carry out calculations, draw figures, etc., one could distribute a ready-made pdf file with an appendix of Supplementary Material that has all the code for calculations, figures, etc. What do you think? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] example filter for code blocks?
I think it is so interesting, we have actually tried a variation of it! I set up an org-file that exported a supplementary information file, using attachfile to embed data files and scripts in the pdf. Unfortunately, the journal processed the pdf file, and stripped those files out ;( We haven't tried to see if we can get our original supplemental pdf accepted. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, Sep 26, 2013 at 3:43 PM, Thomas S. Dye t...@tsdye.com wrote: Hi John, John Kitchin jkitc...@andrew.cmu.edu writes: Hi everyone, Thanks for the tips in using export filters for code blocks. I thought I would share my current solution. The goal was to export all the code blocks in an org-file to files systematically named part1/script-%d.py where %d is a number. I didnot want to tangle exactly, because I wanted to avoid naming the code block tangle files. Then, I wanted to insert a pdf link that would open the file, after the syntax highlighted code. I wanted this because it is not convenient to copy and paste the syntax-highlighted code into an editor. I teach from the pdf that is generated, and it would be convenient to just open the code, edit and rerun to explore solutions. This seems like it might be an elegant way to distribute a piece of reproducible research. I suspect most readers would prefer to have a pdf entry point into a compendium over an Org-mode entry point. Instead of distributing the Org-mode file that is configured to make a pdf file, carry out calculations, draw figures, etc., one could distribute a ready-made pdf file with an appendix of Supplementary Material that has all the code for calculations, figures, etc. What do you think? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Lots of \n in ox-html output
Hi List, although I did not update recently, html-export of this test org-file suddenly includes lots of \n in the html output. ,--- | * Org-mode Markup Syntax | | Org-mode Markup has a relatively simple syntax. Some of its most basic | elements are listed below, for an in-debt coverage please consult the | manuals. | | These and quite a lot other markup types are supported: | | # Levels 1 .. 8 are allowed | ** Heading# Heading (level 3) | | Some /italic/ words mixed with *bold* words look nice, while | _underlined_ text is a bit overkill sometimes. An unordered list like | | # Unordered list | - List item 1# List items | - List item 2 | | or an ordered list like | | # Ordered list | 1. List item 1# List items | 2. List item 2 | | look nice too. | | There is much more information available at the | [[http://orgmode.org/][Orgmode]] website. `--- here is an excerpt ,- | div id=\table-of-contents\\nh2Table of Contents/h2\ndiv | id=\text-table-of-contents\\nul\nlia href=\#sec-1\1. Org-mode | Markup Syntax/a\nul\nlia href=\#sec-1-1\1.1. Heading # Heading | (level 3)/a/li\n/ul\n/li\n/ul\n/div\n/div\ndiv | id=\outline-container-sec-1\ class=\outline-2\\nh2 | [...] | too.\n/p\n\np\nThere is much more information available at the a | href=\http://orgmode.org/\;Orgmode/a website.\n/p\n\np\nWhat | happens to export - where do all the \\n come | from?/p\n/div\n/div\n/div\n br/br/ `- an it look ugly in the browser too: , | | \n\n | \nThese and quite a lot other markup types are supported:\n | | \n | \n | \n | 1.1 Heading # Heading (level 3) | | \n | \n | | \nSome italic words mixed with bold words look nice, while | underlined\ntext is a bit overkill sometimes. An unordered list like\n | | \n\n | \n | List item 1 # List items\n | \n | List item 2\n | \n | \n\n ` I actually do the export with emacs -Q and load only the necessary files like ox-html.el. Is this related to ox-html? Has somebody seen something like this before? Any hints would be appreciated. -- cheers, Thorsten
Re: [O] Spurious exporting of text before first header
On 26.9.2013, at 13:26, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, François Pinard pin...@iro.umontreal.ca writes: Nicolas Goaziou n.goaz...@gmail.com writes: François Pinard pin...@iro.umontreal.ca writes: The spirit behind :export: is [...] I agree, this is a misfeature. This should be fixed in master. Thank you for bringing it out. Thanks as well. :-) OTOH, this fix introduces another problem. What if a user wants to both use :export: tag and export text before first headline? An almost equivalent solution for him would be to add a headline before that text and append it an :export: tag. But in that case, he will get the additional headline in the output, which isn't desirable. IOW, it is easier to make that text disappear than to make it appear. IOW, even though the new behaviour is more logical, in the end, I'm not sure it is desirable. It's the old good versus best story. The new behavior is the correct one. :export: selects stuff to be exported. A way to have initial text and some trees would be to add :noexport: to the ones that should not be exported. If there is string desire to be able to export initial text with :export: tags, the only solutions I see would be an additional variable with an #+OPTIONS equivalent, like org-export-force-initial-content. Default obviously off, setting the variable to t with list or customize not recommended, but possible to set it on a per file basis with #+OPTIONS - Carsten WDYT? Regards, -- Nicolas Goaziou signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [O] example filter for code blocks?
Hi John, Terrific! There go my plans for the weekend ... :) Good luck with the heavy-handed journal processor. It seems worth pursuing to me. All the best, Tom John Kitchin jkitc...@andrew.cmu.edu writes: I think it is so interesting, we have actually tried a variation of it! I set up an org-file that exported a supplementary information file, using attachfile to embed data files and scripts in the pdf. Unfortunately, the journal processed the pdf file, and stripped those files out ;( We haven't tried to see if we can get our original supplemental pdf accepted. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, Sep 26, 2013 at 3:43 PM, Thomas S. Dye t...@tsdye.com wrote: Hi John, John Kitchin jkitc...@andrew.cmu.edu writes: Hi everyone, Thanks for the tips in using export filters for code blocks. I thought I would share my current solution. The goal was to export all the code blocks in an org-file to files systematically named part1/script-%d.py where %d is a number. I didnot want to tangle exactly, because I wanted to avoid naming the code block tangle files. Then, I wanted to insert a pdf link that would open the file, after the syntax highlighted code. I wanted this because it is not convenient to copy and paste the syntax-highlighted code into an editor. I teach from the pdf that is generated, and it would be convenient to just open the code, edit and rerun to explore solutions. This seems like it might be an elegant way to distribute a piece of reproducible research. I suspect most readers would prefer to have a pdf entry point into a compendium over an Org-mode entry point. Instead of distributing the Org-mode file that is configured to make a pdf file, carry out calculations, draw figures, etc., one could distribute a ready-made pdf file with an appendix of Supplementary Material that has all the code for calculations, figures, etc. What do you think? All the best, Tom -- Thomas S. Dye http://www.tsdye.com I think it is so interesting, we have actually tried a variation of it! I set up an org-file that exported a supplementary information file, using attachfile to embed data files and scripts in the pdf. Unfortunately, the journal processed the pdf file, and stripped those files out ;( We haven't tried to see if we can get our original supplemental pdf accepted. John --- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu On Thu, Sep 26, 2013 at 3:43 PM, Thomas S. Dye t...@tsdye.com wrote: Hi John, John Kitchin jkitc...@andrew.cmu.edu writes: Hi everyone, Thanks for the tips in using export filters for code blocks. I thought I would share my current solution. The goal was to export all the code blocks in an org-file to files systematically named part1/script-%d.py where %d is a number. I didnot want to tangle exactly, because I wanted to avoid naming the code block tangle files. Then, I wanted to insert a pdf link that would open the file, after the syntax highlighted code. I wanted this because it is not convenient to copy and paste the syntax-highlighted code into an editor. I teach from the pdf that is generated, and it would be convenient to just open the code, edit and rerun to explore solutions. This seems like it might be an elegant way to distribute a piece of reproducible research. I suspect most readers would prefer to have a pdf entry point into a compendium over an Org-mode entry point. Instead of distributing the Org-mode file that is configured to make a pdf file, carry out calculations, draw figures, etc., one could distribute a ready-made pdf file with an appendix of Supplementary Material that has all the code for calculations, figures, etc. What do you think? All the best, Tom -- Thomas S. Dye http://www.tsdye.com -- 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
[O] epresent issue
Hi I am trying to use epresent for presentation. Start epresent with M-x epresent-run I seem to need to press one more q to get out of epresenting and then that q gets into the file. Thanks Rusi
Re: [O] epresent issue
On Fri, Sep 27, 2013 at 7:20 AM, Rustom Mody rustompm...@gmail.com wrote: Hi I am trying to use epresent for presentation. Start epresent with M-x epresent-run I seem to need to press one more q to get out of epresenting and then that q gets into the file. Thanks Rusi Sorry for the half-complete line: Start epresent with M-x epresent-run Was meaning to write a scenario but then decided that the one line was enough :-) Did not include usual version stuff (I assumed that I am doing something wrong) so here it is Org-mode version 8.2 (release_8.2-34-g33aded Emacs 23.4.1 epresent downloaded yesterday Rusi -- http://www.the-magus.in http://blog.languager.org
Re: [O] Elpa color-theme with emacs24
Sebastien Vauban sva-news@... writes: For the sake of completion, I think that, starting with Emacs 24, it's better to use their new custom theme mechanism, which is more general than the `color-theme' package (and offers the same services regarding color themes). You're right. DefTheme is the way to go and should be advised on the worg page: http://orgmode.org/worg/org-color-themes.html Thanks. -- Rene
Re: [O] Wrong captialisation from a latex src block
Dieter Wilhelm, H. die...@duenenhof-wilhelm.de writes:
Sorry, I forgot to say that I'm using org-8.2.
2013/9/26 Dieter Wilhelm, H. die...@duenenhof-wilhelm.de:
Dear (),
when I'm trying to asign a variable in the following way:
#+BEGIN_SRC latex :var Idir = (concat (org-attach-dir) /PostImage)
\animategraphics[autoplay,loop,width=10cm]
{5}{Idir}{716}{728}
#+END_SRC
I'm getting a wrong capitalisation of Idir:
#+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/Uidg1626/Development/Report/Tz/Haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
instead of the following corrected output
# #+RESULTS:
#+BEGIN_LaTeX
\animategraphics[autoplay,loop,width=10cm]
{5}{/HOME/uidg1626/development/report/tz/haeug0x8g0/PostImage}{716}{728}
#+END_LaTeX
Am I doing something wrong?
I don't think so: I can reproduce it. It seems to be caused by the
mixed-case variable name. If I change Idir to idir, it does not
happen. Not sure how the replacement happens, but it seems suspiciously
similar to the behavior of replace-match when the FIXEDCASE argument is
nil (or absent perhaps?)
--
Nick
Re: [O] Elpa color-theme with emacs24
Hi Rene, would you like to prepare a patch for the site? - Carsten On 27.9.2013, at 04:08, Rene jl...@yahoo.com wrote: Sebastien Vauban sva-news@... writes: For the sake of completion, I think that, starting with Emacs 24, it's better to use their new custom theme mechanism, which is more general than the `color-theme' package (and offers the same services regarding color themes). You're right. DefTheme is the way to go and should be advised on the worg page: http://orgmode.org/worg/org-color-themes.html Thanks. -- Rene signature.asc Description: Message signed with OpenPGP using GPGMail
