Re: [O] [ANN] Edit emails in Org-mode
HI Thorsten, Thorsten Jolitz wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Thorsten Jolitz wrote: 2.3 Usage ~ There are only two commands involved: Command Keybinding Comment --- M-x outorg-edit-as-org M-# M-# or M-# # outline-prefix M-# C-c ' outline-prefix C-c M-x outorg-copy-edits-and-exit M-#--- When I have message code blocks, and when I edit them in an indirect buffer (for refilling them, for example), then I have a draft message that stays in my Gnus/Message emails. Any idea how to get rid of that? its a nice idea to be able to replace the source-blocks by their results when composing messages (if I understood your feature request right). No, this may be a good idea, but not what I was talking about. I now have the following capture command: #+begin_src emacs-lisp (add-to-list 'org-capture-templates `(m Mail to task entry (file+headline ,org-default-notes-file Tasks) * TODO %:subject%? (from %:fromname) :mail: %:date-timestamp-inactive #+begin_src message %i #+end_src From %a :immediate-finish t) t) #+end_src But, sometimes, I want to refill the contents of the captured email. To do so, I go onto the email message code block, edit it in an indirect buffer (through C-c '), refill, and quit the indirect buffer (another C-c '). Though, after having done that, I now have the above email saved as a draft in Gnus. Not what I was expecting. So, my question was: how to avoid the email to be saved as a draft? Opens a lot of possiblilities for (semi-)automatic email creation. Here is the doc-string: #+begin_src emacs-lisp (defun outorg-replace-source-blocks-with-results (optional arg rest languages) Replace source-blocks with their results. Only source-blocks with ':export results' in their header arguments will be mapped. If LANGUAGES is non-nil, only those source-blocks with a language found in the list are mapped. If LANGUAGES is nil but a prefix-argument ARG is given, only the languages read from the mini-buffer (separated by blanks) are mapped. Otherwise, all languages found in `org-babel-load-languages' are mapped. ...) #+end_src it basically says: - only blocks with ':export results' will be mapped - blocks for all languages found in `org-babel-load-languages' will be mapped, except the function ist called (from a program) with a list of language names (as strings) or the user calls the command with prefix arg (e.g. C-u) and enters language names (like this: R emacs-lisp sh org). let me know if the function does what you wanted. Do we need a keybinding for that, or should it rather be a bit oscure (only accessible by M-x) to avoid confusing accidents? Best regards, Seb -- Sebastien Vauban
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Hello Nicolas, Nicolas Goaziou wrote: Any objection to applying the following patch to master? Not at all. Basically, #+HTML_INCLUDE_STYLE: nil becomes #+OPTIONS: html-style:nil and #+HTML_HTML5_FANCY: t becomes #+OPTIONS: html5-fancy:t Though, I'd also even prefer the form #+OPTIONS: :html-style nil which would clone the way we pass options in the publishing project. Whatever you decide, you proposed solution is better than the current one. Best regards, Seb -- Sebastien Vauban
[O] Upgrade to org 8.0
Dear list, I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. Here is the first confusion: *Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded?* * * Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. 2. About org-export I read through the upgrading notes from worg, but still haven't got a working configuration file, maybe that's the issue of my org installation. But is there's *working conf on org-export that I can start with*? I attached my lch-org-export.el, could somebody have a look how to improve them to get 8.0.3 working. Thanks in advance for the help. Chris lch-org-export.el Description: Binary data
[O] [PATCH] * lisp/org.el (org-scan-tags): do not impose a value of case-fold-search on the user
Hello, when using org-contacts, (let ((filename (make-temp-file contacts nil .org))) (with-temp-file filename (insert * Eva Luator\n:PROPERTIES:\n:EMAIL: e...@gmail.com.invalid\n:END:\n)) (let ((org-contacts-files (list filename))) (org-contacts eva luator))) doesn't list Eva Luator in the Contacts buffer, although case-fold-search is set to t for me. I think it's an org-mode bug in fact ; I suggest the following : From: Nicolas Richard theonewiththeevill...@yahoo.fr Date: Wed, 5 Jun 2013 15:02:37 +0200 --- lisp/org.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 97773a0..da3e2f0 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -13807,7 +13807,6 @@ headlines matching this string. (abbreviate-file-name (or (buffer-file-name (buffer-base-buffer)) (buffer-name (buffer-base-buffer))) -(case-fold-search nil) (org-map-continue-from nil) lspos tags tags-list (tags-alist (list (cons 0 org-file-tags))) @@ -13820,7 +13819,8 @@ headlines matching this string. (when (eq action 'sparse-tree) (org-overview) (org-remove-occur-highlights)) - (while (re-search-forward re nil t) + (while (let (case-fold-search) + (re-search-forward re nil t)) (setq org-map-continue-from nil) (catch :skip (setq todo (if (match-end 1) (org-match-string-no-properties 2)) -- 1.8.1.5
Re: [O] [ANN] Convert Org-mode file to Source-code file
Charles Berry ccbe...@ucsd.edu writes: Thorsten Jolitz tjolitz at gmail.com writes: Hi List, it is now possible to convert existing Org-mode files with source-blocks into machine-executable source-code files, using the following function from `outorg.el': #+begin_src emacs-lisp (defun outorg-convert-org-file-to-source-code (optional mode infile outfile BATCH) With this buffer , | | | * head1 | | abc | | | #+NAME: test-src | #+BEGIN_SRC R | ls() | #+END_SRC ` it fails with Debugger entered--Lisp error: (void-variable outorg-code-buffer-beg-of-subtree-marker) (set-marker outorg-code-buffer-beg-of-subtree-marker nil) outorg-reset-global-vars() outorg-copy-edits-and-exit() ... in the backtrace. This should be fixed now, thanks for reporting. The tmp buffer looks right, though , | | | ## * head1 | | ## abc | | | ## #+NAME: test-src | ls() ` Please note that I renamed ,--- | outorg-convert-org-file-to-source-code `--- to ,--- | outorg-convert-org-to-outshine `--- because that better reflects its purpose. This ,-- | ## * head1 `-- is actually the decisive part of the output, since the converted source-code file will have (if outshine is activated) the lookfeel of the original Org-mode file, only that now the text parts are 'caged' behind comments while in the Org file the source code was 'caged' in special blocks. -- cheers, Thorsten
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Any objection to applying the following patch to master? Basically, #+HTML_INCLUDE_STYLE: nil becomes #+OPTIONS: html-style:nil and #+HTML_HTML5_FANCY: t becomes #+OPTIONS: html5-fancy:t Regards, Looks good! +1 for merging :foo nil syntax from babel...
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Hi Nicolas, This is a good change - I am also for merging it. - Carsten On Jun 20, 2013, at 9:20 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Any objection to applying the following patch to master? Basically, #+HTML_INCLUDE_STYLE: nil becomes #+OPTIONS: html-style:nil and #+HTML_HTML5_FANCY: t becomes #+OPTIONS: html5-fancy:t Regards, -- Nicolas Goaziou 0001-ox-html-Use-OPTIONS-items-instead-of-keywords-for-bo.patch
Re: [O] [ANN] Convert Org-mode file to Source-code file
Eric Schulte schulte.e...@gmail.com writes: How does this differ from :tangle yes :comments org? I wasn't actually aware (or forgot about) the :comments argument in Babel when I wrote the conversion function (that is renamed to 'outorg-convert-org-to-outshine' now to better reflect its purpose). e.g., #+Property: tangle yes #+Property: comments org * This is the top #+begin_src sh :shebang #!/bin/bash echo ##this file will cat itself echo #+end_src Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nulla posuere. Donec vitae dolor. Nullam tristique diam non turpis. Cras placerat accumsan nulla. Nullam rutrum. Nam vestibulum accumsan nisl. | a | table | | in | the | | tangled | file | #+begin_src sh cat $0 #+end_src tangles to #!/bin/bash # This is the top echo ##this file will cat itself echo # Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec # hendrerit tempor tellus. Donec pretium posuere tellus. Proin quam # nisl, tincidunt et, mattis eget, convallis nec, purus. Cum sociis # natoque penatibus et magnis dis parturient montes, nascetur ridiculus # mus. Nulla posuere. Donec vitae dolor. Nullam tristique diam non # turpis. Cras placerat accumsan nulla. Nullam rutrum. Nam vestibulum # accumsan nisl. # | a | table | # | in | the | # | tangled | file | cat $0 in your example file the main difference is that , | * This is the top ` becomes , | # This is the top ` which is not an outshine header, thus the outline structure is lost in the tangled file. But it would really be nice if the conversion from Org to Outshine could be done with the existing 'Babel Toolkit'. On the other hand, since my conversion function seems to work alright now (bugreports welcome!), it would not make much sense to invest time into make Babel do the same thing. I see the following problems with Babel: 1. (from your example I deduce that) outline structure is not conserved in the comment sections, thus the tangles files won't work with outshine. 2. the overriding of header args cause problems with files that set (e.g. code block specific) :tangle or :comment args themnselves, that then override buffer wide args. 3. an outshine file is a file in a certain programming language major-mode. 'outorg-convert-org-to-outshine' outcomments everything else, including property-drawers, org comments, or souce-blocks from other languages, so that the whole Org-file is preserved. I'm not sure how this works when tangling with :comments org? Maybe just check if it works with a real world .org file? The best one I can think of is ,-- | http://doc.norang.ca/org-mode.org `-- since it covers so many aspects of Org-mode. So I downloaded it and added this at the front ,--- | [...] | #+EXPORT_EXCLUDE_TAGS: noexport | | #+PROPERTY: tangle yes | #+PROPERTY: comments org | | Org-mode is a fabulous organizational tool originally built by Carsten | Dominik that operates on plain text files. Org-mode is part of Emacs. | [...] `--- and then did 1. ,-- | C-c C-v t `-- The tangled file org-mode.el does not at all look as expected, it rather seems the added properties have been completely ignored. Is it possible to squeeze Org-Babel such that the tangled file looks like the result of 2. ,-- | M-: (outorg-convert-org-to-outshine emacs-lisp-mode |~/junk/org-mode.org ~/junk/org-mode-outorg.el) `-- This seems to convert the full Org file to Outshine, and when I do M-# M-# then on the Outshine file, I see the same Org-file as before in the *outorg-edit-buffer*, as intended. (almost, see the PS). PS One thing on my list for outorg is better handling of src-block header args for the code-sections. Until now, I viewed it from the perspective of a source-code file (e.g. emacs-lisp), and it was no problem to surround the code parts simply with #+begin_src emacs-lisp code #+end_src and assume that the users use Org-mode properties for persistantly specifying export options. So when going back from Org to Outshine, I simply deleted the ,- |#+begin_src emacs-lisp |#+end_src `- lines. But now, from the perspective of converting existing Org-files to Outshine, this does not look like such a good idea anymore, since I delete important header info from the original file
Re: [O] Unexpected behaviour with gnuplot source blocks
On 20 June 2013 18:12, Eric Schulte schulte.e...@gmail.com wrote: Why not do the following instead which would be equivalent and simpler. The output will be automatically set from the value of your :file header argument. #+begin_src gnuplot :file fig/transInc.eps reset set encoding utf8 . #+end_src That kinda works, but I think you still need to set the terminal type within the source block. Using the above the command set terminal eps gets sent to gnuplot, but you actually need set terminal postscript eps. The following works #+BEGIN_SRC gnuplot :file test.eps reset set terminal postscript eps . #+END_SRC Thanks for the help! Chris.
Re: [O] [ANN] Edit emails in Org-mode
Sebastien Vauban sva-n...@mygooglest.com writes: Hi Sebastien, Thorsten Jolitz wrote: Sebastien Vauban sva-n...@mygooglest.com writes: Thorsten Jolitz wrote: 2.3 Usage ~ There are only two commands involved: Command Keybinding Comment --- M-x outorg-edit-as-org M-# M-# or M-# # outline-prefix M-# C-c ' outline-prefix C-c M-x outorg-copy-edits-and-exit M-#--- When I have message code blocks, and when I edit them in an indirect buffer (for refilling them, for example), then I have a draft message that stays in my Gnus/Message emails. Any idea how to get rid of that? its a nice idea to be able to replace the source-blocks by their results when composing messages (if I understood your feature request right). No, this may be a good idea, but not what I was talking about. anyway, I really like it for myself ... I now have the following capture command: #+begin_src emacs-lisp (add-to-list 'org-capture-templates `(m Mail to task entry (file+headline ,org-default-notes-file Tasks) * TODO %:subject%? (from %:fromname) :mail: %:date-timestamp-inactive #+begin_src message %i #+end_src From %a :immediate-finish t) t) #+end_src But, sometimes, I want to refill the contents of the captured email. To do so, I go onto the email message code block, edit it in an indirect buffer (through C-c '), refill, and quit the indirect buffer (another C-c '). Though, after having done that, I now have the above email saved as a draft in Gnus. Not what I was expecting. So, my question was: how to avoid the email to be saved as a draft? Thats quite a complicated set-up, not sure if I really can say something about that. Maybe you noticed, that in my original post I exported my mail written in the *outorg-edit-buffer* to ASCII with this code block: #+begin_src emacs-lisp :results output replace (org-export-to-buffer 'ascii email-transcode-buffer) (print (with-current-buffer email-transcode-buffer (let ((mail-as-ascii (buffer-substring-no-properties (point-min) (point-max (set-buffer-modified-p nil) (kill-buffer) mail-as-ascii))) #+end_src and the result looked like this (I did not fiddle with the export options, just used the settings I have): #+results: ,-- |_ | | 134 | | Thorsten Jolitz |_ | | | Table of Contents | _ | | 1 --text follows this line-- | 2 Documentation `-- I think this 134 in the headline comes from Gnus too, and is a draft number or so. I'm not really sure whats happening there, it seems to be something between Org and Gnus. I do use C-c ' in the *outorg-edit-buffer* too for editing source-blocks, not sure if Org-mode automatically saves the original buffer when returning from the temporal (source-code) edit buffer and updating the original buffer - but that would then be the *outorg-edit-buffer*, not the message-buffer. I checked outorg.el - there is only one explicit use of 'save-buffer' not related to this, so I don't seem to save the original-buffer when returning from *outorg-edit-buffer* buffer (and I remember that I decided to better leave that to the user). Opens a lot of possiblilities for (semi-)automatic email creation. Here is the doc-string: #+begin_src emacs-lisp (defun outorg-replace-source-blocks-with-results (optional arg rest languages) Replace source-blocks with their results. Only source-blocks with ':export results' in their header arguments will be mapped. If LANGUAGES is non-nil, only those source-blocks with a language found in the list are mapped. If LANGUAGES is nil but a prefix-argument ARG is given, only the languages read from the mini-buffer (separated by blanks) are mapped. Otherwise, all languages found in `org-babel-load-languages' are mapped. ...) #+end_src it basically says: - only blocks with ':export results' will be mapped - blocks for all languages found in `org-babel-load-languages' will be mapped, except the function ist called (from a program) with a list of language names (as strings) or the user calls the command with prefix arg (e.g. C-u) and enters language names (like this: R emacs-lisp sh org). let me know if the function does what you wanted. Do we need a keybinding for that, or should it rather be a bit oscure (only accessible by M-x) to avoid confusing accidents? Best regards, Seb -- cheers, Thorsten
Re: [O] Starting emacs followed directly by org-agenda search and visiting file removes color formatting
Am 12.06.2013 23:08, schrieb Bastien: Hi John, John Hendy jw.he...@gmail.com writes: Just wanted to follow up on this. I haven't been using =C-a s= a ton so it drifted off my radar, but recently needed to use it a lot and noticed this was still persisting. ... it's still on my radar too, I've just been overwhelmed by work and other stuff. I should have more time next week, sorry for the delay. Bastien, I pulled today and as expected am without colors. Any chance to get this solved any time soon? I wonder if there are not a many more users having the issue .. Thanks, Rainer
Re: [O] Upgrade to org 8.0
On Fri, Jun 21, 2013 at 03:43:33AM -0400, Chao Lu wrote: Dear list, I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. You should read this: http://orgmode.org/worg/org-8.0.html Here is the first confusion: *Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded?* This has been obsolete for quite a while now; all you need is `(require 'org)' * * Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. You should read this: http://orgmode.org/worg/org-faq.html#mixed-install Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] Upgrade to org 8.0
Nicolas Richard writes: IIUC, when nothing bad happens, org has autoloads installed in emacs which will load org as soon as needed. So you are right, (require 'org) is unneeded. This relies heavily on luck with both the original and the new version of Org. You should at least do a `(require org-install)´ (but not when you are trying to use the Org version that comes with Emacs). In rare cases, though (such as major update of org not yet reflected in emacs), I guess it might be required to load the right set of autoloads, i.e. say (load org-loaddefs). I'm have no idea why org-install got removed, because I think it used to serve the same purpose. Maybe I simply don't understand correctly. FWIW, I carry a local patch that re-introduces org-install for this very reason. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Bug: broken agenda view? [8.0.2 (8.0.2-dist @ /usr/share/emacs/site-lisp/org-mode/)]
On Thu, Jun 20, 2013 at 10:16:11PM -0400, Nick Dokos wrote: Did you see this: http://thread.gmane.org/gmane.emacs.orgmode/73666/focus=73667 Strange, I didn't receive your earlier email either! This one arrived just fine though. -- Suvayu Open source is the future. It sets us free.
Re: [O] Unexpected behaviour with gnuplot source blocks
Suvayu Ali fatkasuvayu+li...@gmail.com writes: On Fri, Jun 21, 2013 at 09:02:28AM -0600, Eric Schulte wrote: I've added a customization variable to ob-gnuplot which may be used to map file extensions to terminals. Currently it just holds the mapping from eps to postscript eps ;; -*- emacs-lisp -*- (defcustom *org-babel-gnuplot-terms* '((eps . postscript eps)) List of file extensions and the associated gnuplot terminal. :group 'org-babel :type '(repeat (cons (symbol :tag File extension) (string :tag Gnuplot terminal Great idea! Thanks, I hope it is useful. If anyone knows of other good default mapping to add please let me know. I personally use pdfcairo color for pdf output. This is already the default behavior for term pdf on my system, so I don't think we need to add it to the list. I did just add some logic to ensure that output terminals are closed at the end of code blocks, which was required for a simple pdf example to work for me. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte
[O] [PATCH][ox-latex] support for latexmk
This patch allows latexmk as an option to `org-latex-pdf-process'. I've added the -g option, as I sometimes have experienced that latexmk otherwise doesn't run often enough. –Rasmus -- May contains speling mistakeFrom e03411adaf5c45dfb60d84016f77e75739f9c642 Mon Sep 17 00:00:00 2001 From: rasmus ras...@gmx.us Date: Fri, 21 Jun 2013 17:57:32 +0200 Subject: [PATCH] Let =`latexmk'= be an option to =`org-latex-pdf-process'=. * ox-latex.el (org-latex-pdf-process): let =`latexmk'= be a preconfigured choice and change the wording of the docstring. TINYCHANGE --- lisp/ox-latex.el | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index 9172cd7..25b80fb 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -784,8 +784,12 @@ the infamous egrep/locale bug: http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html -then `texi2dvi' is the superior choice. Org does offer it as one -of the customize options. +then `texi2dvi' is the superior choice as it automates the LaTeX +build process by calling the \correct\ combinations of +auxiliary programs. Org does offer `texi2dvi' as one of the +customize options. Alternatively, `rubber' and `latexmk' also +provide similar functionality. The latter supports `biber' out +of the box. Alternatively, this may be a Lisp function that does the processing, so you could use this to apply the machinery of @@ -823,6 +827,8 @@ file name as its single argument. (texi2dvi -p -b -c -V %f)) (const :tag rubber (rubber -d --into %o %f)) + (const :tag latexmk + (latexmk -g -pdf %f)) (function))) (defcustom org-latex-logfiles-extensions -- 1.8.3.1
Re: [O] [ANN] Convert Org-mode file to Source-code file
Thorsten Jolitz tjolitz at gmail.com writes: Charles Berry ccberry at ucsd.edu writes: Thorsten Jolitz tjolitz at gmail.com writes: Hi List, it is now possible to convert existing Org-mode files with source-blocks into machine-executable source-code files, using the following function from `outorg.el': [bug description deleted] This should be fixed now, thanks for reporting. Now I get Debugger entered--Lisp error: (void-function region-or-buffer-limits) [...] outorg-convert-org-to-outshine() eval((outorg-convert-org-to-outshine) nil) eval-expression((outorg-convert-org-to-outshine) nil) call-interactively(eval-expression nil nil) and nothing visible in the tmp buffer.
Re: [O] Unexpected behaviour with gnuplot source blocks
On Fri, Jun 21, 2013 at 10:07:39AM -0600, Eric Schulte wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I personally use pdfcairo color for pdf output. This is already the default behavior for term pdf on my system, so I don't think we need to add it to the list. I did just add some logic to ensure that output terminals are closed at the end of code blocks, which was required for a simple pdf example to work for me. Closing the terminal is crucial indeed! I scratched my head quite a bit when I first started using pdf output. -- Suvayu Open source is the future. It sets us free.
[O] Setting a parametric org-agenda-skip-function?
Hello, I'm trying to have a custom agenda where I say I want to skip some tags. I wrote a function that does what I want (it takes two arguments: the list of tags to keep, and a boolean that says whether entries with no tags should be kept). The function works well, but for some reason it is not called. Here is how I try to call it: (w Work Agenda ((agenda ((org-agenda-skip-function '(org-agenda-skip-entry-unless-tags my-work-tags t I make org-agenda-skip-entry-unless-tags as debugged, and when I call this agenda view, I don't go in the debugger, so I guess it is not called. I tried adding a lambda () at the beginning, or getting rid of the quote, but it does not work. Any suggestion as to what I'm doing wrong? Thanks, Alan PS: here are the functions this depends on (defun as/has-tag (tags-to-test taglist optional trueifempty) return true if a tag in TAGS-TO-TEST is in TAGLIST. If TRUEIFEMPTY is non-nil, then returns true if TAGS-TO-TEST is empty. (or (and trueifempty (not tags-to-test)) (catch 'match (mapc (lambda (tag) (when (member tag taglist) (throw 'match t))) tags-to-test) nil)) ) (defun org-agenda-skip-entry-unless-tags (tags optional keepempty) Skip entries that do not contain specified tags. TAGS is a list specifying which tags should be displayed. Inherited tags will be considered. If keepempty is non-nil, entries with no tags will be kept. (let ((next-headline (save-excursion (or (outline-next-heading) (point-max (current-headline (or (and (org-at-heading-p) (point)) (save-excursion (org-back-to-heading) (let ((atags (org-get-tags-at current-headline))) (if (as/has-tag atags tags keepempty) nil next-headline
Re: [O] [ANN] Convert Org-mode file to Source-code file
Charles Berry ccbe...@ucsd.edu writes: Thorsten Jolitz tjolitz at gmail.com writes: Charles Berry ccberry at ucsd.edu writes: Thorsten Jolitz tjolitz at gmail.com writes: Hi List, it is now possible to convert existing Org-mode files with source-blocks into machine-executable source-code files, using the following function from `outorg.el': [bug description deleted] This should be fixed now, thanks for reporting. Now I get Debugger entered--Lisp error: (void-function region-or-buffer-limits) [...] outorg-convert-org-to-outshine() eval((outorg-convert-org-to-outshine) nil) eval-expression((outorg-convert-org-to-outshine) nil) call-interactively(eval-expression nil nil) and nothing visible in the tmp buffer. ups, sorry, another function from the 'basic-edit-toolkit' I have installed and take for granted (i.e. think its part of core Emacs). I just pushed a fix, should work now. -- cheers, Thorsten
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Hello, Carsten Dominik carsten.domi...@gmail.com writes: This is a good change - I am also for merging it. Applied on master, since it introduces a syntax change. Tell me if you want it on maint anyway (or just cherry-pick it yourself). As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value, I can provide a patch, but it will break export in many documents. A workaround would be to support both versions and document only the newest one. Regards, -- Nicolas Goaziou
Re: [O] Bug: Setting HTML_INCLUDE_STYLE: nil doesn't work [8.0.3 (8.0.3-32-g0c789f-elpa @ /home/aj/.emacs.d/elpa/org-20130617/)]
Hello, Anders Johansson mejlaande...@gmail.com writes: I put: #+HTML_INCLUDE_STYLE: nil at the top of my org-file and expect the exported html file to not include the standard styles in it's header (documentation section 12.6.9 CSS support). This does not work and the styles are included as usual. A quick debugging with edebug reveals that nil is interpreted as a string, nil, in the info-plist and therefore evaluates as true in the check in org-html--build-head: (when (plist-get info :html-head-include-default-style) (org-element-normalize-string org-html-style-default)) (from: ox-html.el:1448) Thank you for the report. This should be fixed on master branch: use #+OPTIONS: html-style:nil Regards, -- Nicolas Goaziou
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
On 2013-06-21 13:28, Nicolas Goaziou wrote: Hello, Carsten Dominik carsten.domi...@gmail.com writes: This is a good change - I am also for merging it. Applied on master, since it introduces a syntax change. Tell me if you want it on maint anyway (or just cherry-pick it yourself). As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value, I can provide a patch, but it will break export in many documents. A workaround would be to support both versions and document only the newest one. +1 for supporting both versions (with a deprecation on the old syntax) until the next major release. rick
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Nicolas Goaziou writes: As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value, I can provide a patch, but it will break export in many documents. A workaround would be to support both versions and document only the newest one. I didn't know supporting both styles was in the cards. If it isn't overly complicated, that would be welcome of course. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] [PATCH][ox-latex] support for latexmk
Hello, Rasmus ras...@gmx.us writes: This patch allows latexmk as an option to `org-latex-pdf-process'. I've added the -g option, as I sometimes have experienced that latexmk otherwise doesn't run often enough. Thank you for your patch. Though, I cannot apply it on master. Would you mind re-sending it? Regards, -- Nicolas Goaziou
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Hello,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value,
I can provide a patch, but it will break export in many documents.
A workaround would be to support both versions and document only the
newest one.
I didn't know supporting both styles was in the cards. If it isn't
overly complicated, that would be welcome of course.
Here is a preliminary patch. It doesn't update org.texi yet.
I find the new syntax weird for one character keys:
#+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t
Maybe we should expand them in order to make them less cryptic.
Regards,
--
Nicolas Goaziou
From df3934522fc922d4c1b1a88c4cfa9a6d06370720 Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou n.goaz...@gmail.com
Date: Fri, 21 Jun 2013 20:49:05 +0200
Subject: [PATCH] ox: Change OPTIONS syntax from key:value to :key value
* lisp/ox.el (org-export--parse-option-keyword): Change OPTIONS syntax
from key:value to :key value. Still recognize old syntax for
compatibility.
(org-export-insert-default-template): Use new syntax.
* testing/lisp/test-ox.el: Update tests.
---
lisp/ox.el | 26 +-
testing/lisp/test-ox.el | 24
2 files changed, 29 insertions(+), 21 deletions(-)
diff --git a/lisp/ox.el b/lisp/ox.el
index e49de22..8a29908 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -1524,20 +1524,29 @@ specific items to read, if any.
(append (and backend (org-export-backend-options backend))
org-export-options-alist))
plist)
-(dolist (option all)
+(dolist (option all plist)
(let ((property (car option))
(item (nth 2 option)))
(when (and item
(not (plist-member plist property))
- (string-match (concat \\(\\`\\|[ \t]\\)
- (regexp-quote item)
- :\\(([^)\n]+)\\|[^ \t\n\r;,.]*\\))
- options))
+ (let ((item (regexp-quote item)))
+ (or (string-match
+ (concat \\(?:\\`\\|[ \t]\\):
+ item
+ [ \t]+\\(([^)\n]+)\\|[^ \t\n\r;,.]*\\))
+ options)
+ ;; Compatibility code for deprecated
+ ;; item:value syntax. It can be removed in
+ ;; Org 9.0+.
+ (string-match
+ (concat \\(?:\\`\\|[ \t]\\)
+ item
+ :\\(([^)\n]+)\\|[^ \t\n\r;,.]*\\))
+ options
(setq plist (plist-put plist
property
(car (read-from-string
- (match-string 2 options
-plist))
+ (match-string 1 options))
(defun org-export--get-subtree-options (optional backend)
Get export options in subtree at point.
@@ -3171,8 +3180,7 @@ locally for the subtree through node properties.
(when options
(let ((items
(mapcar
- (lambda (opt)
- (format %s:%s (car opt) (format %s (cdr opt
+ (lambda (opt) (format :%s %s (car opt) (cdr opt)))
(sort options (lambda (k1 k2) (string (car k1) (car k2)))
(if subtreep
(org-entry-put
diff --git a/testing/lisp/test-ox.el b/testing/lisp/test-ox.el
index cbae08a..1a9c241 100644
--- a/testing/lisp/test-ox.el
+++ b/testing/lisp/test-ox.el
@@ -120,9 +120,9 @@ already filled in `info'.
(should
(equal
(org-export--parse-option-keyword
- H:1 num:t \\n:t timestamp:t arch:t author:t creator:t d:t email:t
- *:t e:t ::t f:t pri:t -:t ^:t toc:t |:t tags:t tasks:t :t todo:t inline:nil
- stat:t)
+ :H 1 :num t :\\n t :timestamp t :arch t :author t :creator t :d t :email t
+ :* t :e t :: t :f t :pri t :- t :^ t :toc t :| t :tags t :tasks t : t :todo t
+ :inline nil :stat t)
'(:headline-levels
1 :preserve-breaks t :section-numbers t :time-stamp-file t
:with-archived-trees t :with-author t :with-creator t :with-drawers t
@@ -135,13 +135,13 @@ already filled in `info'.
(should
(equal
(org-export--parse-option-keyword
- arch:headline creator:comment d:(\TEST\)
- ^:{} toc:1 tags:not-in-toc tasks:todo num:2 :active)
-'( :section-numbers
- 2
- :with-archived-trees headline :with-creator comment
- :with-drawers (TEST) :with-sub-superscript {} :with-toc 1
- :with-tags not-in-toc :with-tasks todo :with-timestamps active
+ :arch headline :creator comment :d (\TEST\) :^ {} :toc 1
+ :tags not-in-toc :tasks todo :num 2 : active)
+'(:section-numbers
+ 2
+ :with-archived-trees headline :with-creator comment
+ :with-drawers (TEST) :with-sub-superscript {} :with-toc 1
+ :with-tags not-in-toc :with-tasks todo :with-timestamps active
(ert-deftest test-org-export/get-inbuffer-options ()
Test reading all standard export keywords.
@@ -208,10 +208,10 @@ Paragraph
:title
'(subtree-title)
;; EXPORT_OPTIONS.
- (org-test-with-temp-text #+OPTIONS: H:1
+ (org-test-with-temp-text #+OPTIONS: :H 1
* Headline
:PROPERTIES:
- :EXPORT_OPTIONS: H:2
+ :EXPORT_OPTIONS: :H 2
:END:
Paragraph
(forward-line)
--
1.8.3.1
Re: [O] Upgrade to org 8.0
Thanks a lot for those replies, which are quite helpful. 1. lch-org.el and lch-org-export.el together completes my conf about org, which works before 8.0 2. The version I installed is 8.0.3 tar ball instead of git, usually I do not prefer living at cutting edge. - M-x org-version -- Org-mode version 8.0.3 (8.0.3-dist @ /Users/LooChao/Dropbox/.emacs.d/lisp/org/) - Which reveals the org loaded is the one I installed, which is in my lisp dir. - I agree with John's advice -- keep the new version separate and some where in the load-path, which is ~/Dropbox/.emacs.d/lisp/org/ 3. M-x locate org-publish gives: '/Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.elc', indicating my installation has something wrong... still working on it. Thanks, Chao On Fri, Jun 21, 2013 at 8:45 AM, John Hendy jw.he...@gmail.com wrote: On Jun 21, 2013 2:43 AM, Chao Lu loochao.l...@gmail.com wrote: Dear list, I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. Here is the first confusion: Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded? Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. 2. About org-export I read through the upgrading notes from worg, but still haven't got a working configuration file, maybe that's the issue of my org installation. But is there's working conf on org-export that I can start with? I attached my lch-org-export.el, could somebody have a look how to improve them to get 8.0.3 working. Thanks in advance for the help. Hi, Where exactly are the new org files installed? I don't see any load paths defined. I think the easiest/simplest/cleanest is to keep the hit version separate and just add the lisp dir to your load path vs mixing default org with installed git org files. I didn't catch any defined ox-* backends loaded either. For every backed you need to add it to org-export-backends or do: (require 'ox-backend) Lastly, you have old variable names in there... org-export-backend-* vars are now org-backend-*. I'd suggest reading the worg doc again! John Chris lch-org.el Description: Binary data lch-org-export.el Description: Binary data
Re: [O] Upgrade to org 8.0
On Fri, Jun 21, 2013 at 3:27 PM, Chao Lu loochao.l...@gmail.com wrote: Thanks a lot for those replies, which are quite helpful. 1. lch-org.el and lch-org-export.el together completes my conf about org, which works before 8.0 2. The version I installed is 8.0.3 tar ball instead of git, usually I do not prefer living at cutting edge. - M-x org-version -- Org-mode version 8.0.3 (8.0.3-dist @ /Users/LooChao/Dropbox/.emacs.d/lisp/org/) - Which reveals the org loaded is the one I installed, which is in my lisp dir. - I agree with John's advice -- keep the new version separate and some where in the load-path, which is ~/Dropbox/.emacs.d/lisp/org/ *3. M-x locate org-publish gives: '/Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.elc', indicating my installation has something wrong... * * still working on it.* * I just tried list-load-path-shadows, got outputs like:* /Users/LooChao/Dropbox/.emacs.d/lisp/org/org hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org /Users/LooChao/Dropbox/.emacs.d/lisp/org/contrib/lisp/org-wl hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-wl /Users/LooChao/Dropbox/.emacs.d/lisp/org/org-w3m hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-w3m *...* * * *which shows my installation is OK, I guess just the new version don't have org-publish so the one bundled with emacs is not shadowed?* = Thanks, Chao On Fri, Jun 21, 2013 at 8:45 AM, John Hendy jw.he...@gmail.com wrote: On Jun 21, 2013 2:43 AM, Chao Lu loochao.l...@gmail.com wrote: Dear list, I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. Here is the first confusion: Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded? Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. 2. About org-export I read through the upgrading notes from worg, but still haven't got a working configuration file, maybe that's the issue of my org installation. But is there's working conf on org-export that I can start with? I attached my lch-org-export.el, could somebody have a look how to improve them to get 8.0.3 working. Thanks in advance for the help. Hi, Where exactly are the new org files installed? I don't see any load paths defined. I think the easiest/simplest/cleanest is to keep the hit version separate and just add the lisp dir to your load path vs mixing default org with installed git org files. I didn't catch any defined ox-* backends loaded either. For every backed you need to add it to org-export-backends or do: (require 'ox-backend) Lastly, you have old variable names in there... org-export-backend-* vars are now org-backend-*. I'd suggest reading the worg doc again! John Chris
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
On 6/21/13, Nicolas Goaziou n.goaz...@gmail.com wrote: #+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t Maybe we should expand them in order to make them less cryptic. To me, that would be ideal. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Nicolas Goaziou n.goaz...@gmail.com writes: I find the new syntax weird for one character keys: #+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t Maybe we should expand them in order to make them less cryptic. +1 for making this #+OPTIONS lines human readable ... -- cheers, Thorsten
Re: [O] Upgrade to org 8.0
This is so confusing... M-x org-version Org-mode version 8.0.3 (8.0.3-dist @ /Users/LooChao/Dropbox/.emacs.d/lisp/org/) M-x list-load-path-shadows: /Users/LooChao/Dropbox/.emacs.d/lisp/org/org hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org /Users/LooChao/Dropbox/.emacs.d/lisp/org/contrib/lisp/org-wl hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-wl /Users/LooChao/Dropbox/.emacs.d/lisp/org/org-w3m hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-w3m *M-x describe-function org-export* * * org-export is an interactive autoloaded compiled Lisp function in*`org-exp.el'. * * |* * This one is in /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/* * * This explains why I got the error when org-export-as-latex on test.org: * org-export-as-latex: Symbol's value as variable is void: org-export-latex-default-packages-alist * * * Totally lost why this is happening... On Fri, Jun 21, 2013 at 3:34 PM, Chao Lu loochao.l...@gmail.com wrote: On Fri, Jun 21, 2013 at 3:27 PM, Chao Lu loochao.l...@gmail.com wrote: Thanks a lot for those replies, which are quite helpful. 1. lch-org.el and lch-org-export.el together completes my conf about org, which works before 8.0 2. The version I installed is 8.0.3 tar ball instead of git, usually I do not prefer living at cutting edge. - M-x org-version -- Org-mode version 8.0.3 (8.0.3-dist @ /Users/LooChao/Dropbox/.emacs.d/lisp/org/) - Which reveals the org loaded is the one I installed, which is in my lisp dir. - I agree with John's advice -- keep the new version separate and some where in the load-path, which is ~/Dropbox/.emacs.d/lisp/org/ *3. M-x locate org-publish gives: '/Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.elc', indicating my installation has something wrong... * * still working on it.* * I just tried list-load-path-shadows, got outputs like:* /Users/LooChao/Dropbox/.emacs.d/lisp/org/org hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org /Users/LooChao/Dropbox/.emacs.d/lisp/org/contrib/lisp/org-wl hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-wl /Users/LooChao/Dropbox/.emacs.d/lisp/org/org-w3m hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-w3m *...* * * *which shows my installation is OK, I guess just the new version don't have org-publish so the one bundled with emacs is not shadowed?* = Thanks, Chao On Fri, Jun 21, 2013 at 8:45 AM, John Hendy jw.he...@gmail.com wrote: On Jun 21, 2013 2:43 AM, Chao Lu loochao.l...@gmail.com wrote: Dear list, I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. Here is the first confusion: Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded? Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. 2. About org-export I read through the upgrading notes from worg, but still haven't got a working configuration file, maybe that's the issue of my org installation. But is there's working conf on org-export that I can start with? I attached my lch-org-export.el, could somebody have a look how to improve them to get 8.0.3 working. Thanks in advance for the help. Hi, Where exactly are the new org files installed? I don't see any load paths defined. I think the easiest/simplest/cleanest is to keep the hit version separate and just add the lisp dir to your load path vs mixing default org with installed git org files. I didn't catch any defined ox-* backends loaded either. For every backed you need to add it to org-export-backends or do: (require 'ox-backend) Lastly, you have old variable names in there... org-export-backend-* vars are now org-backend-*. I'd suggest reading the worg doc again! John Chris
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
As for the move from #+OPTIONS: key:value to #+OPTIONS: :key value, I can provide a patch, but it will break export in many documents. A workaround would be to support both versions and document only the newest one. I didn't know supporting both styles was in the cards. If it isn't overly complicated, that would be welcome of course. Here is a preliminary patch. It doesn't update org.texi yet. I find the new syntax weird for one character keys: #+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t I'm not sure how to weight aesthetics against consistency, but personally I much prefer the previous #+OPTIONS: *:t e:t ::t f:t -:t ^:t |:t to the new possibility posted above. In my opinion it is not as important to be consistent with code block header arguments here as it is to be legible. All header arguments are full words and typically have longer values, so they don't run into the same readability issues. Just my 2¢ -- Eric Schulte http://cs.unm.edu/~eschulte
[O] Exporting timestamps in html
I have the following options line in my file header: #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t Sample file: #+begin_src org #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t * Task list ** todo task 1 DEADLINE: 2013-06-21 Fri ** todo task 2 SCHEDULED: 2013-06-24 Mon #+end_src I'm not getting any time stamps in my output file, though. Any suggestions on where to start looking for the issue? Thanks, John
Re: [O] [RFC] Replace some HTML related keywords with OPTIONS items
Nicolas Goaziou writes: Here is a preliminary patch. It doesn't update org.texi yet. I find the new syntax weird for one character keys: #+OPTIONS: :* t :e t :: t :f t :- t :^ t :| t Maybe we should expand them in order to make them less cryptic. Indeed, too much punctuation. How about something along these lines? #+OPTIONS: :enable *e: :disable ^| Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Exporting timestamps in html
On Fri, Jun 21, 2013 at 3:41 PM, John Hendy jw.he...@gmail.com wrote: I have the following options line in my file header: #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t Sample file: #+begin_src org #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t * Task list ** todo task 1 DEADLINE: 2013-06-21 Fri ** todo task 2 SCHEDULED: 2013-06-24 Mon #+end_src I'm not getting any time stamps in my output file, though. Any suggestions on where to start looking for the issue? Just wanted to look at =org-export-date-timestamp-format= and noted this: #+begin_src help org-export-date-timestamp-format is a variable defined in `org-exp.el'. Its value is nil Original value was %Y-%m-%d Documentation: Time string format for Org timestamps in the #+DATE option. You can customize this variable. This variable was introduced, or its default value was changed, in version 24.1 of Emacs. #+end_src I'm on emacs 24.3.1... is this variable having a setting of nil preventing export of timestamps? Since I didn't do this myself, does the above mean that Emacs might have introduced something that affects this Org export option? Thanks, John Thanks, John
[O] [PATCH] do not use mapcar* for transposing tables
I've recently stumbled over a mapcar* compiled into Org for transposing tables. This is a function from cl / cl-lib and should not be used at runtime. Since we can make some simplifying assumptions about the data we'll have to deal with, re-implmenting the two uses with plain mapcar was (relatively) painless. From 8941eb1f7ed2a7f1164a92a957a53560127cc26f Mon Sep 17 00:00:00 2001 From: Achim Gratz strom...@stromeko.de Date: Fri, 21 Jun 2013 22:37:51 +0200 Subject: [PATCH] do not use mapcar* for transposing tables * lisp/ob-core.el (org-babel-get-rownames), lisp/org-table.el (org-table-transpose-table-at-point): Replace the inadvertent use of mapcar* (from cl) by plain mapcar and direct cons manipulation. The error was not caught at compilation time since both source files require cl during compilation for using cl macros. These were the only uses of mapcar* in Org, but I didn't check for other cl _functions_ (as opposed to macros, which would need to be checked if their implementation uses cl functions). --- lisp/ob-core.el | 28 lisp/org-table.el | 15 ++- 2 files changed, 22 insertions(+), 21 deletions(-) diff --git a/lisp/ob-core.el b/lisp/ob-core.el index e2cb03b..a22a696 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -1502,22 +1502,18 @@ (defun org-babel-get-colnames (table) (defun org-babel-get-rownames (table) Return the row names of TABLE. Return a cons cell, the `car' of which contains the TABLE less -colnames, and the `cdr' of which contains a list of the column -names. Note: this function removes any hlines in TABLE. - (let* ((trans (lambda (table) (apply #'mapcar* #'list table))) - (width (apply 'max - (mapcar (lambda (el) (if (listp el) (length el) 0)) table))) - (table (funcall trans (mapcar (lambda (row) - (if (not (equal row 'hline)) - row - (setq row '()) - (dotimes (n width) - (setq row (cons 'hline row))) - row)) - table -(cons (mapcar (lambda (row) (if (equal (car row) 'hline) 'hline row)) - (funcall trans (cdr table))) - (remove 'hline (car table) +rownames, and the `cdr' of which contains a list of the rownames. +Note: this function removes any hlines in TABLE. + (let* ((table (org-babel-del-hlines table)) + (rownames (funcall (lambda () + (let ((tp table)) +(mapcar + (lambda (row) + (prog1 + (pop (car tp)) + (setq tp (cdr tp + table)) +(cons table rownames))) (defun org-babel-put-colnames (table colnames) Add COLNAMES to TABLE if they exist. diff --git a/lisp/org-table.el b/lisp/org-table.el index 9468b2b..243449f 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -1870,11 +1870,16 @@ (defun org-table-transpose-table-at-point () Note that horizontal lines disappeared. (interactive) - (let ((contents - (apply #'mapcar* #'list -;; remove 'hline from list - (delq nil (mapcar (lambda (x) (when (listp x) x)) - (org-table-to-lisp)) + (let* ((table (delete 'hline (org-table-to-lisp))) + (contents (mapcar (lambda (p) + (let ((tp table)) + (mapcar +(lambda (rown) + (prog1 + (pop (car tp)) +(setq tp (cdr tp +table))) + (car table (delete-region (org-table-begin) (org-table-end)) (insert (mapconcat (lambda(x) (concat | (mapconcat 'identity x | ) |\n )) contents )) -- 1.8.3 Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Exporting timestamps in html
On Fri, Jun 21, 2013 at 3:47 PM, John Hendy jw.he...@gmail.com wrote: On Fri, Jun 21, 2013 at 3:41 PM, John Hendy jw.he...@gmail.com wrote: I have the following options line in my file header: #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t Sample file: #+begin_src org #+options: :t num:t author:t tags:t toc:nil tasks:t todo:t * Task list ** todo task 1 DEADLINE: 2013-06-21 Fri ** todo task 2 SCHEDULED: 2013-06-24 Mon #+end_src I'm not getting any time stamps in my output file, though. Any suggestions on where to start looking for the issue? Just wanted to look at =org-export-date-timestamp-format= and noted this: #+begin_src help org-export-date-timestamp-format is a variable defined in `org-exp.el'. Its value is nil Original value was %Y-%m-%d Documentation: Time string format for Org timestamps in the #+DATE option. You can customize this variable. This variable was introduced, or its default value was changed, in version 24.1 of Emacs. #+end_src I'm on emacs 24.3.1... is this variable having a setting of nil preventing export of timestamps? Since I didn't do this myself, does the above mean that Emacs might have introduced something that affects this Org export option? One more update... I had the idea to try a regular timestamp, and those export, even though SCHEDULED and DEADLINE do not. Lastly, I used a minimal config and emacs -Q and get the same behavior: #+begin_src min-config (add-to-list 'load-path ~/.elisp/org.git/contrib/lisp) (add-to-list 'load-path ~/.elisp/org.git/lisp/) #+end_src Same file as above, and not getting deadline/scheduled timestamps exported. John Thanks, John Thanks, John
Re: [O] Upgrade to org 8.0
hi, Chao Lu Chris, do you have the git version or did you download the tar.gz archive? Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded? in my .emacs I have: (setq load-path (cons ... /my/path then (require 'org) ; but I don't know if it is necessary Please, let's fix the installation then the exporter. cheers, Giovanni Da: Chao Lu loochao.l...@gmail.com A: emacs-orgmode@gnu.org Inviato: Venerdì 21 Giugno 2013 9:43 Oggetto: [O] Upgrade to org 8.0 I'm trying to upgrade to org 8.0.3 and met some difficulty that could not solve. Please help. 1. About installation Currently I'm using Emacs 24.3 under MacOSX mountain lion. The org mode shipped with this version of emacs is 7.9 I followed the instruction, successfully compiled org 8.0.3 and put all the *.elc file into my load-path. Here is the first confusion: Before I was using (require 'org-install) to get org code evaluated. Seems org-install is obsolete now, then what should I put in my .emacs to get org loaded? Although I do know why, but seems my old settings get org(8.0.3) loaded, i.e. M-x org-version gives 8.0.3. But when I try ffap on (require 'org-publish) seems emacs wants to jump to /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.el.gz, which is the old org version shipped with Emacs itself. 2. About org-export I read through the upgrading notes from worg, but still haven't got a working configuration file, maybe that's the issue of my org installation. But is there's working conf on org-export that I can start with? I attached my lch-org-export.el, could somebody have a look how to improve them to get 8.0.3 working.
Re: [O] Upgrade to org 8.0
On Fri, Jun 21, 2013 at 04:15:41PM -0400, Chao Lu wrote: *3. M-x locate org-publish gives: '/Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-publish.elc', indicating my installation has something wrong... org-publish has been replaced by ox-publish. M-x org-version Org-mode version 8.0.3 (8.0.3-dist @ /Users/LooChao/Dropbox/.emacs.d/lisp/org/) M-x list-load-path-shadows: /Users/LooChao/Dropbox/.emacs.d/lisp/org/org hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org /Users/LooChao/Dropbox/.emacs.d/lisp/org/contrib/lisp/org-wl hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-wl /Users/LooChao/Dropbox/.emacs.d/lisp/org/org-w3m hides /Applications/Documents/Emacs.app/Contents/Resources/lisp/org/org-w3m *M-x describe-function org-export* * * org-export is an interactive autoloaded compiled Lisp function in*`org-exp.el'. The new export menu is: org-export-dispatch. That said, I think you are still missing the point. What is suggested in the FAQs and I think was repeated by John, was to ensure you load lch-org.el *after* you change your load path. The order matters! If you still have problems, why not use ELPA? -- Suvayu Open source is the future. It sets us free.
[O] Copying/pasting org html export into IBM Community Wiki
Greetings, My company uses a few different social media platforms, including IBM Communities, Wiki Enterprise, and Sharepoint. IBM Communities are what I'm using to manage a project, and would like to use the Wiki feature to keep a dashboard on tasks and a timeline. I've been able to export taskjuggler to html, print as a PDF, and then use pdf2svg to generate a nice scalable timeline. Now I'd like to take my Org-mode task list and make a copy/pastable export that will be compatible with the wiki. Unfortunately, I don't know that it accepts stylecss/style input or respects anything like head/head... When I try, it appears to just remove that stuff upon saving. (i.e. I can paste it in there when editing html manually, but when switching back to rich text or preview mode, the appearance isn't changed, and going back into html mode shows all of my pasted text as removed.) Is there some recommended way to paste in standalone org html code that will work without the ability to specify stylesheets? I think it would require removing div's css-specified alignment and directly applying text coloring or spacing. At present, I end up coloring/spacing things manually, which sort of defeats the purpose. Not a big deal for getting up and running, but as the project continues and I want to update things, this will be a major time saver. Any suggestions? Thanks! John
Re: [O] Exporting timestamps in html
Hello, John Hendy jw.he...@gmail.com writes: One more update... I had the idea to try a regular timestamp, and those export, even though SCHEDULED and DEADLINE do not. Lastly, I used a minimal config and emacs -Q and get the same behavior: #+begin_src min-config (add-to-list 'load-path ~/.elisp/org.git/contrib/lisp) (add-to-list 'load-path ~/.elisp/org.git/lisp/) #+end_src Same file as above, and not getting deadline/scheduled timestamps exported. See `org-export-with-planning'. Regards, -- Nicolas Goaziou
Re: [O] Copying/pasting org html export into IBM Community Wiki
John Hendy jw.hendy at gmail.com writes: Greetings, My company uses a few different social media platforms, including IBM Communities, Wiki Enterprise, and Sharepoint. IBM Communities are what I'm using to manage a project, and would like to use the Wiki feature to keep a dashboard on tasks and a timeline. John, I don't know if there is a generic exporter in Org 8.0. In versions prior to Org 8.0, there was a generic exporter which could be tailored for your flavor of wiki output. Will the wiki export format work for you? The down side is the styles will be inherited from IBM Communities and not your own style. - Srinivas
[O] org-indent-region and org-indent-block do nothing
Hi List, what might be the reason for the behaviour described in the subject? When I come back from a temporary source-code edit buffer, there is indentation introduced automatically into the source-block (2 spaces), but when I call the above functions with point in a source-block, nothing happens. -- cheers, Thorsten
Re: [O] org-indent-region and org-indent-block do nothing
Thorsten Jolitz writes: When I come back from a temporary source-code edit buffer, there is indentation introduced automatically into the source-block (2 spaces), but when I call the above functions with point in a source-block, nothing happens. M-x load-library org-src C-h v org-edit-src-content-indentation C-h v org-src-preserve-indentation Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
