Re: [O] New exporter, beamer confusion
On Tue, Feb 5, 2013 at 3:21 PM, Nick Dokos nicholas.do...@hp.com wrote:
I added a beamer entry to org-e-latex-classes as indicated in
http://thread.gmane.org/gmane.emacs.orgmode/61497/focus=61536
(again, I
have no idea if the sectioning stuff matters or not, and whether it leads
to problems - improvements/corrections would be welcome):
Made no difference for me.
Customizing org-e-beamer-environments-extra should do the trick. I was
experimenting using the *scratch* buffer, so the following are temporary
settings, cribbed from those experiments: restart emacs and they
disappear.
Something like the following perhaps (very lightly tested - nb: I really
haven't played with the new exporter very much at all):
--8---cut here---start-8---
(setq blockenv '(block b \\begin{itemize}\\item %h \\end{itemize}))
(add-to-list 'org-e-beamer-environments-extra blockenv t)
--8---cut here---end---8---
I'm attaching an org file that illustrates a couple of the beamer
formatting options that I used a lot in the old exporter.
1. I *did* use the block environment to emphasize some text by pulling
it out of the itemize bullet lists. If I customize blockenv in org
to render as itemize, then I lose the ability to do this (or, I have
to call block something else).
2. BMCOL (column) layouts are completely ignored.
3. Strong *emphasis* now renders in red, instead of keeping the text's
original color and switching to boldface.
I've also uploaded 3 PDFs to UbuntuOne, the point being to illustrate
how much functionality is lost in the new exporter:
1. Old exporter result
http://ubuntuone.com/2ByUYyYg5wfz07aUuUVPTP
2. New exporter result, without customizing
http://ubuntuone.com/4HSQUoDlZpNHZ46OROZd54
3. New exporter result, with Nick's customization
http://ubuntuone.com/1DnRQultVtdf2OKYjaeSsu
I get the feeling here that the new beamer exporter was written
without a lot of real-world user requirements. Certainly, it's
understandable that HTML, LaTeX article-style and ODT exporters would
be more widely used and more important to get right first. For beamer,
though, I can't reconcile the announcement (Even though the internals
are completely different, the new exporter mostly behaves like its
predecessor. There are only a few noticeable changes) with the fact
that the new beamer exporter is a rather different animal that
completely breaks compatibility with org files written for the old
exporter, and may actually require a complete redo of the org markup
for each file.
I know my emacs-lisp chops are not up to the task of fixing what is
broken in the new beamer exporter. I can supply a couple dozen source
files, to help decide what level of backward compatibility is
feasible. I'm not sure how else I can help.
At least, it would be good to clarify, with respect to the
announcement, if the new beamer exporter is intended to be reasonably
backward-compatible with the old (with not-too-intrusive tweaks). If
that was the intent, then it's not ready for release. Otherwise, I'd
be happy to help draw up an upgrade path for people like myself who
have developed workflows for the old exporter that will eventually not
be supported anymore.
In the meantime, I must stick with the old exporter, though I'll keep
the discussion alive to hash out on the mailing list what needs to be
done to make the new one production-ready for me.
hjh
simple-beamer.org
Description: Binary data
Re: [O] [ANN] Merge of new export framework on Wednesday
Suvayu Ali fatkasuvayu+li...@gmail.com writes: Hi Eric, I have used the beamer export quite a few times with the new exporter, I must admit I haven't actually tried any of my big beamer talks (hundreds of slides)... I've been too intimidated to do so! I have done a short talk but one with no special blocks, columns, etc. That worked very well. The only problem I had was figuring out how to tell the new exporter what level of headlines corresponded to frames... and I can't remember how I found out (#+OPTIONS: H:2)! Maybe I should just suck it and see! [...] Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. I think that would be great. I would be happy to work on any such document if it means getting some documentation in place. If you want to send me, offline, what you've got, I'd be happy to have a look. Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-898-gcb1386
Re: [O] New exporter, beamer confusion
Nick Dokos nicholas.do...@hp.com writes: [...] Customizing org-e-beamer-environments-extra should do the trick. I was Nick, thanks for this. This hint led me to org-e-beamer-select-environment which, after binding to a key, has allowed me to play sufficiently enough with the new exporter and beamer that I am now less worried about the upcoming change in default behaviour! eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-898-gcb1386
Re: [O] viewing number of nested headlines
42 147 aeus...@gmail.com writes: Is there a way to see how many nested headlines there are within a higher-level headline (not necessarily top-level)? This is a nice feature of VimOrganizer but no, there is no way to do this with Org for now. -- Bastien
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. I think that would be great. I would be happy to work on any such document if it means getting some documentation in place. If you want to send me, offline, what you've got, I'd be happy to have a look. I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. Cheers, -- Suvayu Open source is the future. It sets us free. From d7dfb6133bcea0127d0c386334a833e8ac64323e Mon Sep 17 00:00:00 2001 From: Suvayu Ali fatkasuvayu+li...@gmail.com Date: Tue, 5 Feb 2013 10:21:23 +0100 Subject: [PATCH] Documentation for beamer export with new exporter Start an article to serve as initial documentation for beamer export using the new exporter. This is also the working document for a tutorial for the exporter. --- org-tutorials/org-beamer/org-e-beamer.org | 141 ++ 1 file changed, 141 insertions(+) create mode 100644 org-tutorials/org-beamer/org-e-beamer.org diff --git a/org-tutorials/org-beamer/org-e-beamer.org b/org-tutorials/org-beamer/org-e-beamer.org new file mode 100644 index 000..f857174 --- /dev/null +++ b/org-tutorials/org-beamer/org-e-beamer.org @@ -0,0 +1,141 @@ +#+TITLE: Beamer presentations using the new export engine +#+AUTHOR:Suvayu Ali +#+EMAIL: fatkasuvayu+linux at gmail dot com +#+DATE: 2013-02-05 +#+DESCRIPTION: +#+KEYWORDS: +#+LANGUAGE: en +#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t +#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc +#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js +#+EXPORT_SELECT_TAGS: export +#+EXPORT_EXCLUDE_TAGS: noexport +#+LINK_UP: +#+LINK_HOME: + +#+startup: folded + +* Introduction +This tutorial covers exporting org documents to LaTeX Beamer slides +using the new export engine, =org-elements= and =org-export=, written +by Nicolas Goaziou. + +_Note:_ It will not cover any of the basic features common with the +old beamer exporter; it will only focus on the improvements, new +additions and backwards incompatibilities. It is also assumed that +the reader is already acquainted with GNU Emacs and Org mode itself. +Basic understanding of LaTeX and the Beamer package is also assumed. + +* Configuring export options +Apart from the usual export options provided by the =OPTIONS= keyword, +you can put additional beamer export options in the file header. For +a minimal beamer export, you have to specify the =LaTeX_CLASS= and the +=LaTeX_CLASS_OPTIONS= keywords in the header of a file. A preset +export template can be inserted by calling the interactive function +=org-e-beamer-insert-options-template=. This can be further modified +as per your needs. You can also do a subtree export; in that case you +can provide the keywords as =PROPERTIES=. However the keyword names +should be prepended with =EXPORT_=. A list of supported +keywords are, + +#+caption: Export option keywords and corresponding subtree properties. +| File header keywords | Subtree properties | +|---+--| +| =OPTIONS= | =EXPORT_OPTIONS= | +| =LaTeX_CLASS= | =EXPORT_LaTeX_CLASS= | +| =LaTeX_CLASS_OPTIONS= | =EXPORT_LaTeX_CLASS_OPTIONS= | +| =LaTeX_HEADER=| =EXPORT_LaTeX_HEADER=| +| =BEAMER_THEME=| =EXPORT_BEAMER_THEME=| +| =BEAMER_FONT_THEME= | =EXPORT_BEAMER_FONT_THEME= | +| =BEAMER_INNER_THEME= | =EXPORT_BEAMER_INNER_THEME= | +| =BEAMER_OUTER_THEME= | =EXPORT_BEAMER_OUTER_THEME= | + +For a subtree export, a few extra keywords are supported. For example +you can specify the exported filename with the =EXPORT_FILE_NAME= +property. + +#+caption: Properties specific to subtree export +| Subtree properties | Functionality| +|+--| +| =EXPORT_TITLE= | Export title | +| =EXPORT_AUTHOR=| Export author| +| =EXPORT_DATE= | Export date | +| =EXPORT_FILE_NAME= | Export file name | + +A simple file header might look like the example below. +#+begin_example + ,#+LaTeX_CLASS: beamer + ,#+LaTeX_CLASS_OPTIONS: [smaller,presentation] + ,#+BEAMER_THEME: default +#+end_example +A corresponding subtree export should have properties as shown below. +#+begin_example + ,* Exported title +:PROPERTIES: +:EXPORT_LaTeX_CLASS: beamer +:EXPORT_LaTeX_CLASS_OPTIONS: [presentation,smaller] +:EXPORT_BEAMER_THEME: default +:EXPORT_FILE_NAME: presentation.pdf +:END: +#+end_example + +The export class is passed on to the =\documentclass= LaTeX command, +and the options
Re: [O] New exporter, beamer confusion
Nicolas Goaziou n.goaz...@gmail.com writes: [...] Here's an excerpt from ox-beamer.el documentation: ;; - Headlines become frames when their level is equal to ;; `org-beamer-frame-level' (or H value in the OPTIONS line). Nicolas, I have decided to bite the bullet and try to get all of my beamer files working with the new exporter. I have started simply with the presentation.org file that I had put on Worg for the tutorial on beamer for the old exporter. A truncated version of that file (very minimal and attached) fails completely to export. I get the following (truncated) error trace: , | Debugger entered--Lisp error: (wrong-type-argument buffer-or-string-p t) | get-text-property(0 org-props t) | org-get-text-property-any(0 org-props t) | org-beamer-sectioning(1 t) | funcall(org-beamer-sectioning 1 t) | (if (and (symbolp (nth 2 class-sectionning)) (fboundp (nth 2 class-sectionning))) (funcall (nth 2 class-sectionning) level numberedp) (nth (1+ level) class-sectionning)) | ... | org-e-latex-headline((headline (:raw-value Introduction :begin 359 :end 444 ... ` I have attached the simple test file. Where am I going wrong? If I change H:2 to H:1, it works although obviously the output is not what I want. Have I misunderstand something rather fundamental? Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-898-gcb1386 #+TITLE: Writing Beamer presentations in org-mode #+AUTHOR:Eric S Fraga #+EMAIL: e.fr...@ucl.ac.uk #+DATE: 2010-03-30 Tue #+startup: oddeven #+LaTeX_CLASS: beamer #+LaTeX_CLASS_OPTIONS: [bigger] #+BEAMER_THEME: Madrid #+OPTIONS: H:2 # +COLUMNS: %20ITEM %13BEAMER_env(Env) %6BEAMER_envargs(Args) %4BEAMER_col(Col) %7BEAMER_extra(Extra) * Introduction ** Overview - org-mode template - beamer structure - beamer settings
Re: [O] viewing number of nested headlines
Bastien b...@altern.org writes: 42 147 aeus...@gmail.com writes: Is there a way to see how many nested headlines there are within a higher-level headline (not necessarily top-level)? This is a nice feature of VimOrganizer but no, there is no way to do this with Org for now. Hi! I'm not sure the following code responds to your wish, maybe it would help enough? Surely, it is often useful to me. You might have to adapt the first few lines to your local installation or taste, however. (defvar fp-org-distribution ~/emacs/_/org-mode) (add-to-list 'load-path (concat fp-org-distribution /lisp)) (add-to-list 'load-path (concat fp-org-distribution /contrib/lisp ) t) (require 'org) (defface fp-warn-face 'class color) (background light)) (:foreground chocolate2 :weight bold)) (((class color) (background dark)) (:foreground chocolate1 :weight bold))) Face for own highlights.) (define-key org-mode-map \C-cow 'fp-org-weight-display) (defun fp-org-weight-display () Show header weights in the entire buffer. Use \\[fp-org-weight-remove-overlays] to remove the header weights. (interactive) (fp-org-weight-remove-overlays) (save-excursion (goto-char (point-min)) (outline-next-visible-heading 1) (while (not (eobp)) (save-excursion (fp-org-weight-put-overlay (fp-org-weights-at-point) (funcall outline-level))) (outline-next-visible-heading 1)) ;; Arrange to remove the overlays upon next change. (when org-remove-highlights-with-change (org-add-hook 'before-change-functions 'fp-org-weight-remove-overlays nil 'local (defvar fp-org-weight-overlays nil) (make-variable-buffer-local 'fp-org-weight-overlays) (defun fp-org-weight-put-overlay (weights optional level) Put an overlays on the current line, displaying WEIGHTS. If LEVEL is given, prefix weights with a corresponding number of stars. This creates a new overlay and stores it in `fp-org-weight-overlays', so that it will be easy to remove. (let* ((h (car weights)) (p (cdr weights)) (c 50) (l (if level (org-get-valid-level level 0) 0)) (off 0)) (org-move-to-column c) (unless (eolp) (skip-chars-backward ^ \t)) (skip-chars-backward \t) (let* ((ov (make-overlay (1- (point)) (point-at-eol))) (d (+ off (max 0 (- c (current-column) 2 (tx (concat (buffer-substring (1- (point)) (point)) (make-string d ? ) (org-add-props (format %s %3s %6s (make-string l ?*) (if (zerop p) p) (if (zerop h) (format (%s h) h))) (list 'face 'fp-warn-face)) ))) (if (not (featurep 'xemacs)) (overlay-put ov 'display tx) (overlay-put ov 'invisible t) (overlay-put ov 'end-glyph (make-glyph tx))) (push ov fp-org-weight-overlays (defun fp-org-weight-remove-overlays (optional beg end noremove) Remove the occur highlights from the buffer. BEG and END are ignored. If NOREMOVE is nil, remove this function from the `before-change-functions' in the current buffer. (interactive) (unless org-inhibit-highlight-removal (mapc 'delete-overlay fp-org-weight-overlays) (setq fp-org-weight-overlays nil) (unless noremove (remove-hook 'before-change-functions 'fp-org-weight-remove-overlays 'local ;; Compliment of Nicolas Goaziou n.goaz...@gmail.com, 2012-02-26 (defun fp-org-weights-at-point () Return cons of number of subtrees and paragraphs in the subtree at point. Paragraphs (also encompasses equivalent structures). (org-with-wide-buffer (org-narrow-to-subtree) (let ((tree (org-element-parse-buffer 'element)) (num-hl 0) (num-el 0)) (org-element-map tree 'headline (lambda (hl) (incf num-hl))) (org-element-map tree '(paragraph table verse-block quote-block src-block example-block) (lambda (el) (incf num-el))) (cons (1- num-hl) num-el
Re: [O] [ANN] Merge of new export framework on Wednesday
Suvayu Ali fatkasuvayu+li...@gmail.com writes: Hi Eric, On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. I think that would be great. I would be happy to work on any such document if it means getting some documentation in place. If you want to send me, offline, what you've got, I'd be happy to have a look. I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. Cheers, Hi Suvayu, I think it's definitely worth pushing to Worg. There's obviously much to do but having even the basics that you present in this document is very helpful. Just knowing that there is an org-e-beamer minor mode made it worth reading. If I get my original tutorial updated, the two documents together will be sufficient for many people, I think. I'm working on this now but I have run into some very strange problems to do with frame levels. Everything else seems to be fine. Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-898-gcb1386
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. I think it's definitely worth pushing to Worg. There's obviously much to do but having even the basics that you present in this document is very helpful. Just knowing that there is an org-e-beamer minor mode made it worth reading. I pushed the commit, but I see the publishing failed. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Not sure why though since I checked publishing to html before committing. Can someone take a look? -- Suvayu Open source is the future. It sets us free.
Re: [O] Opendocument problem
Hello Jambunathan and Steve,
Jambunathan K wrote:
Steve Prud'Homme sprud...@gmail.com writes:
I have emacs for cygwin and when I try to export I have a message that
emacs is unable to export a opendocument with the number 8 code(8).
Zip is intalled.
What is the problem ?
Look at *Messages* buffer for the error string that zip or unzip
prints. Make sure you have unzip as well, just in case...
If you are unable to figure out yourself, just post what all gets spewed
in to the messages buffer right from start of export to the end of
export. I believe it is some simple setup issue.
FWIW, I've the following shell script in `~/bin/gunzip':
--8---cut here---start-8---
#!/bin/sh
# gunzip -- gunzip solution on Windows
PATH=${GZIP_BINDIR-'/usr/bin'}:$PATH
exec gzip -d $@
# gunzip ends here
--8---cut here---end---8---
Best regards,
Seb
--
Sebastien Vauban
Re: [O] New exporter, beamer confusion
Hi James, James Harkins wrote: 3. Strong *emphasis* now renders in red, instead of keeping the text's original color and switching to boldface. That's because the * are exported as \alert macros in the new exporter (instead of \textbf in the old one -- for bold face). As, in the LaTeX's Beamer back-end, you have the ability to either use alert or bold face, I'd be very happy to do the same from the source Org file, using: - `*' for bold (as always), - `@' for alert (for example[1]). Though, this is not currently implemented this way, and the default has been changed between the old and the new exporters. IIRC, Nicolas' answer was to insert \textbf calls where you want such use of bold face. Or maybe overwriting one variable which would be the macro used for translation `*' characters -- but, then, you must anyway use one LaTeX macro or the other. Best regards, Seb [1] I think this is Eric Fraga's initial choice of meta-character for alert in the old exporter (using extra custom code). -- Sebastien Vauban
Re: [O] viewing number of nested headlines
Bastien, Bastien wrote: 42 147 aeus...@gmail.com writes: Is there a way to see how many nested headlines there are within a higher-level headline (not necessarily top-level)? This is a nice feature of VimOrganizer but no, there is no way to do this with Org for now. IIUC, this should (almost) answer the OP's request, by displaying the outline path in mode line: #+begin_src emacs-lisp (add-hook 'org-mode-hook (lambda() (add-to-list 'mode-line-format '(:eval (org-propertize (org-display-outline-path nil t / t) 'face 'mode-line-emphasis 'help-echo Outline path)) t))) #+end_src A variation of it could directly count the number of levels... Best regards, Seb -- Sebastien Vauban
Re: [O] New exporter, beamer confusion
James Harkins jamshar...@gmail.com wrote: ... I get the feeling here that the new beamer exporter was written without a lot of real-world user requirements. Certainly, it's understandable that HTML, LaTeX article-style and ODT exporters would be more widely used and more important to get right first. For beamer, though, I can't reconcile the announcement (Even though the internals are completely different, the new exporter mostly behaves like its predecessor. There are only a few noticeable changes) with the fact that the new beamer exporter is a rather different animal that completely breaks compatibility with org files written for the old exporter, and may actually require a complete redo of the org markup for each file. I know my emacs-lisp chops are not up to the task of fixing what is broken in the new beamer exporter. I can supply a couple dozen source files, to help decide what level of backward compatibility is feasible. I'm not sure how else I can help. At least, it would be good to clarify, with respect to the announcement, if the new beamer exporter is intended to be reasonably backward-compatible with the old (with not-too-intrusive tweaks). If that was the intent, then it's not ready for release. Otherwise, I'd be happy to help draw up an upgrade path for people like myself who have developed workflows for the old exporter that will eventually not be supported anymore. In the meantime, I must stick with the old exporter, though I'll keep the discussion alive to hash out on the mailing list what needs to be done to make the new one production-ready for me. I'm sure Nicolas is up to his ears in prep work, but eventually I'm sure he or somebody else who knows more about it than I do, will comment. Just as a general precaution, I wouldn't rush to judgement based on my fumbling attempts: these were small experiments done without knowing anything about the new exporter to begin with. I hope that they did more good than harm, but it *is* just a hope on my part. Don't mistake them for authoritative information. Nick
Re: [O] viewing number of nested headlines
Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: IIUC, this should (almost) answer the OP's request, by displaying the outline path in mode line: Oh, I completely missed the meaning of the OP request. Sorry for my noise. François
[O] [PATCH] Stop with an error if the LaTeX class is not known to the new exporter
Hello Nicolas, I've lost (a bit of) time looking at why my documents were wrong with the new exporter. The fact is I've customized: (setq org-e-latex-default-class myarticle) but hadn't added yet that private class to the list `org-e-latex-classes'. The result: a PDF, but completely undreadable, as it's missing the `documentclass' directive. Here a patch to throw an error to the user, signaling he's forgotten some pieces of the puzzle, in case he played with such vars. Better stop early, and giving hints to the user how to correct the problem, no? Feel free to adapt it to your wishes. Best regards, Seb From 3f1ef08b5accdb16495f72e27e44fbad078b87ee Mon Sep 17 00:00:00 2001 From: Sebastien Vauban wxhgmqzgw...@spammotel.com Date: Tue, 5 Feb 2013 16:36:29 +0100 Subject: [PATCH] Throw an error when class is unknown * org-e-latex.el (org-e-latex-template): Throw an error when the LaTeX class is not part of `org-e-latex-classes'. --- contrib/lisp/org-e-latex.el | 20 +++- 1 files changed, 11 insertions(+), 9 deletions(-) diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el index f115a6d..9cd0a10 100644 --- a/contrib/lisp/org-e-latex.el +++ b/contrib/lisp/org-e-latex.el @@ -1103,15 +1103,17 @@ holding export options. (replace-regexp-in-string ^[ \t]*documentclass\\(\\(\\[.*\\]\\)?\\) class-options header t nil 1) - (when document-class-string - (org-e-latex--guess-babel-language -(org-e-latex--guess-inputenc - (org-splice-latex-header - document-class-string - org-export-latex-default-packages-alist ; defined in org.el - org-export-latex-packages-alist nil ; defined in org.el - (plist-get info :latex-header-extra))) -info) + (if document-class-string + (org-e-latex--guess-babel-language + (org-e-latex--guess-inputenc + (org-splice-latex-header +document-class-string +org-export-latex-default-packages-alist ; defined in org.el +org-export-latex-packages-alist nil ; defined in org.el +(plist-get info :latex-header-extra))) + info) + (error LaTeX class `%s' is unknown; add it to `org-e-latex-classes' + class) ;; Possibly limit depth for headline numbering. (let ((sec-num (plist-get info :section-numbers))) (when (integerp sec-num) -- 1.7.9 -- Sebastien Vauban
[O] org export Taskjuggler (was: Re: [ANN] Merge of new export framework on Wednesday - )
- Messaggio originale - Da: Nicolas Goaziou n.goaz...@gmail.com Inviato: Domenica 3 Febbraio 2013 20:00 2. As a consequence, three export back-ends are not available anymore: Taskjuggler, XOXO and Docbook. Are there any plans to have a taskjuggler export compatible with the new exoprt framework? If not, is there a way I can help/contribute? By the way, I tried to use the taskjuggler export with taskjugler 3.3.0, and it worked quite well, only I have not been able to get the report part of the tjp file working. Anyway thank you, Christian an Yann for the work. cheers, Giovanni
Re: [O] tagging text, not headlines
On Mon, Feb 04, 2013 at 07:03:01PM -0500, 42 147 wrote: It would be nice to keep things in the org-style (e.g., :favorite song: is preferable to --- favorite song, just on rudimentary aesthetic grounds. I often put in my own cookies inside floawing text. For example, I label doubts in my notes with a (?). In the example below, I have a doubt about comment 2. Some statement - Comment 1 - Comment 2 (?) Then I can easily look for it with occur or grep from the commandline. If you want fontification for cookies like above, you can try something like this (untested): ;; font-lock customisations (defface my-global-tag-face '((t (:background royalblue4 :foreground thistle :weight bold))) Face for the global tags. :group 'my-faces) (add-hook 'find-file-hook (lambda () (font-lock-add-keywords nil '((\\[ (]\\([a-zA-Z0-9]\\+\\)[) ]\\ 1 'my-global-tag-face prepend) Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] org export Taskjuggler
Hello, Giovanni Ridolfi giovanni.rido...@yahoo.it writes: - Messaggio originale - Da: Nicolas Goaziou n.goaz...@gmail.com Inviato: Domenica 3 Febbraio 2013 20:00 2. As a consequence, three export back-ends are not available anymore: Taskjuggler, XOXO and Docbook. Are there any plans to have a taskjuggler export compatible with the new exoprt framework? Yes. This one has a high priority tag put on it. If not, is there a way I can help/contribute? I think, but I may be wrong, that Jambunathan has started something in the area. You may get in touch with him. If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. But, obviously, I'll appreciate if Someone beats me to it. Regards, -- Nicolas Goaziou
Re: [O] New exporter, beamer confusion
Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: I have decided to bite the bullet and try to get all of my beamer files working with the new exporter. I have started simply with the presentation.org file that I had put on Worg for the tutorial on beamer for the old exporter. A truncated version of that file (very minimal and attached) fails completely to export. I get the following (truncated) error trace: , | Debugger entered--Lisp error: (wrong-type-argument buffer-or-string-p t) | get-text-property(0 org-props t) | org-get-text-property-any(0 org-props t) | org-beamer-sectioning(1 t) | funcall(org-beamer-sectioning 1 t) | (if (and (symbolp (nth 2 class-sectionning)) (fboundp (nth 2 class-sectionning))) (funcall (nth 2 class-sectionning) level numberedp) (nth (1+ level) class-sectionning)) | ... | org-e-latex-headline((headline (:raw-value Introduction :begin 359 :end 444 ... ` I have attached the simple test file. Where am I going wrong? If I change H:2 to H:1, it works although obviously the output is not what I want. Have I misunderstand something rather fundamental? I have no problem exporting this file. Though, judging from the backtrace, you're using the old exporter since `org-beamer-sectioning' comes from it. Regards, -- Nicolas Goaziou
Re: [O] viewing number of nested headlines
Hi François, This appears to implement a mechanism for putting overlays on headlines. If so, this seems useful and would be a nice contrib or core. On 2/5/13, François Pinard pin...@iro.umontreal.ca wrote: I'm not sure the following code responds to your wish, maybe it would help enough? Surely, it is often useful to me. You might have to adapt the first few lines to your local installation or taste, however. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
[O] editing The compact Org-Mode Guide
I started reading orgguide.pdf, Release 7.9.3e and came across a couple of grammatical errors right away. I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Thank you. Best, Greg Benjamin
Re: [O] New exporter, beamer confusion
Hello,
I'm attaching an org file that illustrates a couple of the beamer
formatting options that I used a lot in the old exporter.
See below.
1. I *did* use the block environment to emphasize some text by pulling
it out of the itemize bullet lists. If I customize blockenv in org
to render as itemize, then I lose the ability to do this (or, I have
to call block something else).
2. BMCOL (column) layouts are completely ignored.
No. BMCOL are just different.
3. Strong *emphasis* now renders in red, instead of keeping the text's
original color and switching to boldface.
Indeed. Strong emphasis in Beamer's jargon is \alert{...} (see Beamer
documentation about it). Letter are so large that \textbf{...} doesn't
fill the job well enough. I'm not saying that \textbf{...} is useless
(though I think it), but alert was preferred.
I get the feeling here that the new beamer exporter was written
without a lot of real-world user requirements.
FWIW, I have used it almost daily since I wrote it.
Certainly, it's understandable that HTML, LaTeX article-style and ODT
exporters would be more widely used and more important to get right
first. For beamer, though, I can't reconcile the announcement (Even
though the internals are completely different, the new exporter mostly
behaves like its predecessor. There are only a few noticeable
changes) with the fact that the new beamer exporter is a rather
different animal that completely breaks compatibility with org files
written for the old exporter, and may actually require a complete redo
of the org markup for each file.
You are half correct. I admit: I forgot to mention that Beamer back-end
was a bit different from its predecessor. Though, it doesn't require
a complete redo, there's just some work to do at the headline level.
I know my emacs-lisp chops are not up to the task of fixing what is
broken in the new beamer exporter.
Nothing is broken in it (at least AFAIK). There are just some changes to
do.
I can supply a couple dozen source
files, to help decide what level of backward compatibility is
feasible. I'm not sure how else I can help.
Let's start slowly. I think you can get how to make the changes yourself
with a couple of examples. Since you seem to like lists (you know that
Till Tantau frowns upon the use of third level lists in presentations,
don't you?), the first rule to know is:
Headlines will never, ever, become lists in the new Beamer back-end.
If you want lists, use lists. There's a handy command to do that change:
mark the subtree you want to change, and use C-c -.
New back-end is more block friendly than lists friendly.
At least, it would be good to clarify, with respect to the
announcement, if the new beamer exporter is intended to be reasonably
backward-compatible with the old (with not-too-intrusive tweaks).
It all depends on what you mean by reasonably. You can obtain the same
output, but there are changes to make in Org files.
If that was the intent, then it's not ready for release. Otherwise,
I'd be happy to help draw up an upgrade path for people like myself
who have developed workflows for the old exporter that will eventually
not be supported anymore.
Thank you. I'll try to help you get started. You might even come to like
the new back-end in the process.
In the meantime, I must stick with the old exporter, though I'll keep
the discussion alive to hash out on the mailing list what needs to be
done to make the new one production-ready for me.
Fair enough.
I'm attaching an updated version of your simple document. Besides moving
subtree to lists, there only other change was at the columns level.
If you use a headline with only a BEAMER_col property, its title will be
ignored and can be used as a container. If you provide it an additional
environment (like block), the new environment will be put in the column
and will fill it. Moreove, the :BEAMER_col: property requires a decimal
number as value, not a length.
Oh, yes, and BEAMER_FRAME_LEVEL doesn't exist anymore. It's H:... in the
OPTIONS line.
#+begin_src org
#+LANGUAGE: en
#+OPTIONS: H:2 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_THEME: default
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col)
%8BEAMER_opt(Opt)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC
#+TITLE: Testing new beamer exporter
#+AUTHOR:H. James Harkins
#+EMAIL: jamshar...@yaddayadda.com
#+DATE: 7 November 2012
#+BEGIN_LaTeX
\AtBeginSection[] % Do nothing for \section*
{
\begin{frame}beamer
\frametitle{Outline}
\tableofcontents[currentsection]
\end{frame}
}
#+END_LaTeX
* Section A
** Slide 1
- Third-level
- Fourth-level
** Ancient history: *Music \emph{n}* languages
- Early pioneers at *Bell Labs* in New Jersey
- Max
Re: [O] editing The compact Org-Mode Guide
Aloha Greg, Gregory Benjamin gr...@laserlab.com writes: I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. The source is /path/to/org-mode/doc/orgguide.texi There is a file in that directory called Documentation_Standards.org, which contains what the file name advertises. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Assuming you are using the git version of Org mode, you should create a new branch, check it out, and edit orgguide.texi there. When you are happy with your edits, stage and commit them in the git repository. Once the edits have been committed, you can make a patch like this: git format-patch -o ~/temp/ HEAD~1 where ~/temp/ is what I use and might not be appropriate for your setup, so should be changed accordingly. You should read the instructions on formatting patches here: http://orgmode.org/worg/org-contribute.html#sec-4 It saves the developers a lot of time if you follow these instructions. Finally, if you're likely to go over the limits of a TINY CHANGE, then you will want to assign your work to FSF so that it can be included in Emacs. See the instructions here: http://orgmode.org/worg/org-contribute.html#sec-2 Hopefully, I've remembered all the steps. If this doesn't work for you, come back to the list with queries. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] editing The compact Org-Mode Guide
Hi Gregory, Gregory Benjamin gr...@laserlab.com writes: I started reading orgguide.pdf, Release 7.9.3e and came across a couple of grammatical errors right away. I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. thanks in advance for this work! Thomas gave all information you need to start -- one correction: orgguide.texi is not part of Emacs, so you don't need to assign your copyright to the FSF for them. Another caveat: most of orgguide.texi comes from org.texi, so it is very like that, if you find a typo in orgguide.texi, the typo will be in org.texi too. If you want to provide a patch for org.texi too, then you'll have to assign your copyright to the FSF -- or to let Thomas or/and I backport your changes into org.texi. All best, -- Bastien
Re: [O] [PATCH] Correctly align clock information in default time grid
Hi Bernt and Bastien, Bernt Hansen wrote: Sebastien Vauban writes: Here a tiny patch to correctly align clock info in the default time grid. For example: Day-agenda (W06): 2013-02-04 Mon __ 8:00.. Clk (1:05)9:03-10:08 TODO Organize work 10:00.. Clk (0:59) 10:08-11:07 DONE Do work for client A Clk (1:24) 11:06-12:30 TODO Do other work for client B 12:00.. Clk (-) 13:34.. TODO Send patch to org-mode ML 13:49.. now 14:00.. I'm not sure 'Clk' is more readable than 'Clocked' but it does align clock entries better. However state change logs suffer from a similar misalignment. I think a complete fix should correct the alignment for all of the items. Here is a patch which fixes both string together. Personally I don't mind the clock line misalignment - I think it's easier to read Clocked vs Clk. I think everything should be aligned or leave it as is. By respecting the rule 11-char wide string for more elements which are displayed in the time grid, I think it becomes much more easy to adapt things to our personal flavor, while still being able to keep things aligned. For example, here is how the patch looks like with the Org default settings -- well with my `leuven-theme': http://screencast.com/t/OXBjlIZgkTz The same patch with the following settings: --8---cut here---start-8--- (setq org-agenda-prefix-format '((agenda . %-11s%i %?-12t) (timeline . % s) (todo . %i %-12:c) (tags . %i %-12:c) (search . %i %-12:c))) (setq org-agenda-scheduled-leaders '(Today )) (setq org-agenda-deadline-leaders '(Deadline In %d d ;; or %d d left %d d ago)) --8---cut here---end---8--- gives a better layout (IMHO): http://screencast.com/t/KCrAHxCTJo Best regards, Seb From 513702851922a87e1d94adf862f573b7e96c1dd0 Mon Sep 17 00:00:00 2001 From: Sebastien Vauban wxhgmqzgw...@spammotel.com Date: Tue, 5 Feb 2013 20:46:16 +0100 Subject: [PATCH 2/2] Correctly align clock information and task initial status in time grid * org-agenda.el (org-agenda-get-progress): By respecting the default 11-char convention for Scheduling/Deadline information (`%s' in `org-agenda-prefix-format'), the clocked lines and the status changes are perfectly aligned in the time grid. --- lisp/org-agenda.el |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 2ce9f20..5d19a39 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -5812,8 +5812,8 @@ please use `org-class' instead. (setq txt (org-agenda-format-item (cond (closedp Closed:) - (statep (concat State: ( state ))) - (t (concat Clocked: ( clocked + (statep (concat St ( state ) )) + (t (concat Clk ( clocked ) ))) txt level category tags timestr))) (setq priority 10) (org-add-props txt props @@ -5853,7 +5853,7 @@ See also the user option `org-agenda-clock-consistency-checks'. '((:background DarkRed) (:foreground white issue face m te ts dt ov) (goto-char (point-min)) -(while (re-search-forward Clocked: +(-\\|\\([0-9]+:[0-9]+\\)) nil t) +(while (re-search-forward Clk (-\\|\\([0-9]+:[0-9]+\\)) nil t) (setq issue nil face def-face) (catch 'next (setq m (org-get-at-bol 'org-marker) -- 1.7.9 -- Sebastien Vauban
Re: [O] viewing number of nested headlines
Maybe you could point me in the right direction; somewhere in the code, org-mode must be aware of the number of nested headlines in order for show-branches and show-children to work. Or maybe it is not. In any case, I'd try and adapt the code to display a number indicating (1) position in the hierarchy; and (2) number of headlines at that / those position(s). Apologies if the original message was poorly articulated. 2013/2/5 Bastien b...@altern.org 42 147 aeus...@gmail.com writes: Is there a way to see how many nested headlines there are within a higher-level headline (not necessarily top-level)? This is a nice feature of VimOrganizer but no, there is no way to do this with Org for now. -- Bastien
Re: [O] viewing number of nested headlines
Hi 42 (what's your other name?) 42 147 aeus...@gmail.com writes: Maybe you could point me in the right direction; somewhere in the code, org-mode must be aware of the number of nested headlines in order for show-branches and show-children to work. Or maybe it is not. It is not. Long story short: folding a headline works by adding a text overlay with the invisible property, and finding the end of the overlay works by finding another headline of the same level. So there is no nothing of jumping by N subtrees. Still, you can fetch the number of invisible headline in a folded subtree *afterwards* -- I assumed this is what François' code does. In any case, I'd try and adapt the code to display a number indicating (1) position in the hierarchy; and (2) number of headlines at that / those position(s). This could end up in a minor mode or simply a feature that people could turn on and off. But beware of the efficiency: with many headlines, the folding features of Org combined with this feature could become quite slow. Apologies if the original message was poorly articulated. No problem, that's part of the game. Thanks, -- Bastien
Re: [O] editing The compact Org-Mode Guide
Thanks for the instructions on how to play nice in the sandbox. We noobs are always afraid we are going to cause more work than we fix. :-) On Tue, Feb 5, 2013 at 2:11 PM, Thomas S. Dye t...@tsdye.com wrote: Aloha Greg, Gregory Benjamin gr...@laserlab.com writes: I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. The source is /path/to/org-mode/doc/orgguide.texi There is a file in that directory called Documentation_Standards.org, which contains what the file name advertises. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Assuming you are using the git version of Org mode, you should create a new branch, check it out, and edit orgguide.texi there. When you are happy with your edits, stage and commit them in the git repository. Once the edits have been committed, you can make a patch like this: git format-patch -o ~/temp/ HEAD~1 where ~/temp/ is what I use and might not be appropriate for your setup, so should be changed accordingly. You should read the instructions on formatting patches here: http://orgmode.org/worg/org-contribute.html#sec-4 It saves the developers a lot of time if you follow these instructions. Finally, if you're likely to go over the limits of a TINY CHANGE, then you will want to assign your work to FSF so that it can be included in Emacs. See the instructions here: http://orgmode.org/worg/org-contribute.html#sec-2 Hopefully, I've remembered all the steps. If this doesn't work for you, come back to the list with queries. All the best, Tom -- Thomas S. Dye http://www.tsdye.com -- Evan Misshula Doctoral Student (Criminal Justice) CUNY John Jay Let us reform our schools, and we shall find little reform needed in our prisons. John Ruskin, Unto This Last, essay 2 (1862) English critic, essayist, reformer (1819 - 1900) Instruction does much, but encouragement does everything. Johann Wolfgang Von Goethe www.snrg-nyc.org
Re: [O] viewing number of nested headlines
Hi 42 (what's your other name?) John is my real first name. . . . As for the rest, I didn't see some of the other replies, because the org-mode mailing list moves a little two fast for my mailbox, and I prefer to read selectively from the gmane archive. That said, it is my responsibility to check that website before responding to (some) of the messages that get forwarded to my e-mail address in a thread I started. Anyway, checking out some of the other solutions, since many were provided. Thanks for the technical background on how headlines work in the code. 2013/2/5 Bastien b...@altern.org Hi 42 (what's your other name?) 42 147 aeus...@gmail.com writes: Maybe you could point me in the right direction; somewhere in the code, org-mode must be aware of the number of nested headlines in order for show-branches and show-children to work. Or maybe it is not. It is not. Long story short: folding a headline works by adding a text overlay with the invisible property, and finding the end of the overlay works by finding another headline of the same level. So there is no nothing of jumping by N subtrees. Still, you can fetch the number of invisible headline in a folded subtree *afterwards* -- I assumed this is what François' code does. In any case, I'd try and adapt the code to display a number indicating (1) position in the hierarchy; and (2) number of headlines at that / those position(s). This could end up in a minor mode or simply a feature that people could turn on and off. But beware of the efficiency: with many headlines, the folding features of Org combined with this feature could become quite slow. Apologies if the original message was poorly articulated. No problem, that's part of the game. Thanks, -- Bastien
Re: [O] New exporter, beamer confusion
Nicolas Goaziou n.goaz...@gmail.com writes:
[...]
I have attached the simple test file.
Where am I going wrong? If I change H:2 to H:1, it works although
obviously the output is not what I want. Have I misunderstand something
rather fundamental?
I have no problem exporting this file. Though, judging from the
backtrace, you're using the old exporter since `org-beamer-sectioning'
comes from it.
Which is rather strange although that thought had entered my mind. I do
not understand how I am ending up in that code when I start the exporter
off with the new dispatcher. Other files work fine but this one
doesn't.
The funny thing is that if I use the old dispatcher, and hence the old
exporter, it works!
There has to be something in my emacs/org configuration somewhere that
is causing problems.
So I try a minimal example (emacs -Q, set up paths to git org, load in
org-e-beamer) and things get even stranger. The same org file exports
(no error), but to a latex file that has no document class
definition. The first (non-comment) line of the latex file is
\usetheme{Madrid}.
I am really confused. The system is rather fragile, it would seem.
I will continue playing... although I guess I should try to do some
work as well ;-)
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org 7.9.3e-897-g787a07
Re: [O] New exporter, beamer confusion
Nicolas Goaziou n.goaz...@gmail.com writes: [...] Let's start slowly. I think you can get how to make the changes yourself with a couple of examples. Since you seem to like lists (you know that Till Tantau frowns upon the use of third level lists in presentations, don't you?), the first rule to know is: [...] Nicolas, this email has been quite helpful. I now see where you have gone with beamer and overall I like your approach. However, I *still* cannot get this to work. Taking your updated version of the example document, I cannot get the exporter to generate a latex file that will compile because it is missing a documentclass directive. Is there something else that needs to be configured to support beamer, as in maybe org-e-latex-classes? The default has no mention of beamer and although the documentation within org-e-beamer.el does allude to org-e-latex-classes, it doesn't say whether that variable needs to be adapted/updated/changed. Having looked at the code, I think I do need to add a beamer entry to that variable. Can you please suggest a default that would work? And maybe update the documentation or at least output an error message if the latex class desired is not actually found in org-e-beamer-template? That function would appear to do nothing if an appropriate entry is not found and hence explains why I get an exported file with no documentclass line! Thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-897-g787a07
Re: [O] [PATCH] Stop with an error if the LaTeX class is not known to the new exporter
Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Hello Nicolas, I've lost (a bit of) time looking at why my documents were wrong with the new exporter. The fact is I've customized: Ah ha! We've found the same problem through different routes. See my recent email re: beamer export also resulting in a latex file with no documentclass. -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org 7.9.3e-897-g787a07
[O] org-babel python :session hangs with matplotlib
Hi everyone, I am using (insert (org-version)) 7.9.3a I am using python-mode 5.2 (more modern versions do not work with :session for me) I am having a problem using matplotlib with python :session. The problem is that this hangs indefinitely. It runs fine as a standalone block. #+BEGIN_SRC python :session import matplotlib.pyplot as plt plt.plot([1,2,3,4,5]) plt.show() #+END_SRC #+RESULTS: Does anyone else have this problem (and if not, what is your python setup?). Thanks, 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
[O] python :session issues
I have been trying to use the :session feature of babel for python code blocks. I have noticed a few things that might be areas for improvement. Some issues are related to what I think might be a need for sanitizing the code blocks and the output. I am using (insert (org-version)) 7.9.3a I am using python-mode 5.2 (more modern versions do not work with :session for me) The first small detail is illustrated here: #+BEGIN_SRC python :session a = 5 b = 6 print a + b #+END_SRC #+RESULTS: : :11 In the output, there are three sets of , due to the two empty lines. Compare this to #+BEGIN_SRC python :session a = 5 b = 6 print a + b #+END_SRC #+RESULTS: : : 11 I think it would be nice to sanitize the python code block sent to the interpreter to eliminate the empty lines, and avoid the multiple in output. It would also be nice to have an option to not print those at all. The second issue is related. The following code does not work for me in :session, but it works fine as a standalone block. The issue is related to the presence of an empty line in the function definition. I like whitespace like this in functions sometimes for readability. #+BEGIN_SRC python :session def func(x): 'doc string' return x**2 print func(2) #+END_SRC #+RESULTS: : : ...File stdin, line 1 : return x**2 : ^ : IndentationError: unexpected indent : None Removing the blank line works fine, but still has some non-pretty output. #+BEGIN_SRC python :session def func(x): 'doc string' return x**2 print func(2) #+END_SRC #+RESULTS: : : ... ... 4 One of the ellipsis is due to the doc string. #+BEGIN_SRC python :session def func(x): return x**2 print func(2) #+END_SRC #+RESULTS: : : ... 4 Interestingly, this did not work, because there is no empty line after the function definition. So, sanitizing could be tricky. #+BEGIN_SRC python :session def func(x): 'doc string' return x**2 print func(2) #+END_SRC #+RESULTS: : : ... ... File stdin, line 4 : print func(2) : ^ : SyntaxError: invalid syntax I think if there was a way to strip all the empty lines from the input, it would go a long way to making the output look like what I think most people would expect and want. Anyway, those are the examples I wanted to highlight in this post. 1. Do you see similar behavior, or is this a feature of my setup? 2. Is there any interest in sanitizing the input and output of a python :session to get prettier output? if so, Any hints on where to start with that? Thanks, 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] New exporter, beamer confusion
Thanks for all this. I'll look at the new org markup later today. That
should help a lot.
On Feb 6, 2013 3:03 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
3. Strong *emphasis* now renders in red, instead of keeping the text's
original color and switching to boldface.
Indeed. Strong emphasis in Beamer's jargon is \alert{...} (see Beamer
documentation about it). Letter are so large that \textbf{...} doesn't
fill the job well enough. I'm not saying that \textbf{...} is useless
(though I think it), but alert was preferred.
Ok. There was something about customizing this on the list just recently.
I'll use that. (FWIW, I had to produce a number of *gasp cough choke*
PowerPoint shows in my previous job, and they told us not to use red for
*anything* unless it really was a four-alarm-fire you will really screw
things up if you ignore this type of point, and I retain this aversion to
red text to this day.)
Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
Never use the passive [voice] where you can use the active.)
Since you seem to like lists (you know that
Till Tantau frowns upon the use of third level lists in presentations,
don't you?)
I appreciate his contribution to LaTeX, but I'll make my own decisions
about style, thanks.
Headlines will never, ever, become lists in the new Beamer back-end.
If you want lists, use lists. There's a handy command to do that change:
mark the subtree you want to change, and use C-c -.
New back-end is more block friendly than lists friendly.
Although I'm not happy about manual intervention to convert my prior work,
this is a good step toward consistency. It was odd, in the old framework,
to use headlines for bullet lists and org's numbered lists for numbered
lists. An org list becomes an output list is an easier rule to explain.
Still, I wonder if there is a way to make the new backend less unfriendly
toward lists. It's an interesting philosophical question: In what cases is
it better for the tool to adapt to the users' wishes, versus cases where
the tool should encourage (Are blocks in the result actually better than
lists? Who says so, and why should I take his or her word for it?)
At least, it would be good to clarify, with respect to the
announcement, if the new beamer exporter is intended to be reasonably
backward-compatible with the old (with not-too-intrusive tweaks).
It all depends on what you mean by reasonably. You can obtain the same
output, but there are changes to make in Org files.
Reasonably for me would mean tweaking some configuration options and
perhaps changing a few minor details of the markup. If you have to change
the org document's structure (e.g., converting headlines to lists), it
isn't backward compatible.
For comparison: Lilypond updates frequently break some details of backward
compatibility. So, they ship a convert-ly script to handle many of those
changes automatically.
Oh, yes, and BEAMER_FRAME_LEVEL doesn't exist anymore. It's H:... in the
OPTIONS line.
Right, covered in an earlier message in this thread. I included it here so
you could compile it using the old exporter, for comparison.
I'm attaching an updated version of your simple document. Besides moving
subtree to lists, there only other change was at the columns level.
Thanks for this, and the explanation of columns. Actually, I never was
really happy with columns in the old backend. It's quite likely to be
better here!
Really appreciate the details.
hjh
Re: [O] New exporter, beamer confusion
James Harkins jamshar...@gmail.com writes:
[...]
Ok. There was something about customizing this on the list just recently.
I'll use that. (FWIW, I had to produce a number of *gasp cough choke*
PowerPoint shows in my previous job, and they told us not to use red for
*anything* unless it really was a four-alarm-fire you will really screw
things up if you ignore this type of point, and I retain this aversion to
red text to this day.)
#+BEAMER: \setbeamercolor{alerted text}{...some other colour...}
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org 7.9.3e-897-g787a07
Re: [O] org-export-as-html-and-open problem
It's odd. The value of org-file-apps-defaults-gnu is: ((remote . emacs) (system . mailcap) (t . mailcap)) And I checked my local mime file, which shows google-chrome is the default app to open html files: $ cat ~/.local/share/applications/mimeapps.list [Added Associations] application/epub+zip=FBReader.desktop; application/pdf=pdf.desktop; application/vnd.rn-realmedia=smplayer.desktop; application/x-matroska=smplayer.desktop; application/x-mimearchive=firefox.desktop; application/x-ole-storage=libreoffice-impress.desktop; audio/mpeg=audacious.desktop; text/html=google-chrome.desktop; video/mpeg=gnome-mplayer.desktop; x-scheme-handler/mailto=google-chrome.desktop;KMail2.desktop; [Default Applications] text/html=google-chrome.desktop x-scheme-handler/mailto=google-chrome.desktop Any idea? On Mon, Feb 4, 2013 at 4:29 PM, Bastien b...@altern.org wrote: zhenjiang xu zhenjiang...@gmail.com writes: Thanks, Bastien. It's the default value - I've not changed it: org-file-apps is a variable defined in `org.el'. Its value is ((auto-mode . emacs) (\\.mm\\' . default) (\\.x?html?\\' . default) (\\.pdf\\' . default)) So you need to check the relevant variable: org-file-apps-defaults-gnu org-file-apps-defaults-macosx org-file-apps-defaults-windowsnt If the relevant variable uses the defaults (as I guess), you need to configure the mailcap file for your system See http://en.wikipedia.org/wiki/Mailcap HTH, -- Bastien
