[O] extra whitespace on first page of LaTeX PDF
I'm using xelatex org-latex-to-pdf-process to convert org-mode to PDF.
I wanted a page break after the Table of Contents so I modified my
org-export-latex-classes and added:
\\makeatletter
\\g@addto@macro\\@cfttocfinish{\\clearpage}
\\makeatother
But now I have lots of extra whitespace on the page after the Table of
Contents, before the first text appears.
Has anyone run into this before?
Thanks,
Peter
Re: [O] bug with org-mode-hook and text-scale-set
text-mode-hook and c-mode-hook do NOT have this bug. and the org-mode-hook of orgmode shipped within emacs 23.3 does NOT have this bug. On Wed, Mar 14, 2012 at 1:41 PM, David Maus dm...@ictsoc.de wrote: Hi, At Tue, 13 Mar 2012 14:49:41 +0800, Du Yanning wrote: org-mode 7.8.03 emacs 23.3, 23.4, 24.0.94 steps to recreate: emacs -q copy the following code and paste it into the *scratch* buffer: (add-to-list 'auto-mode-alist '(\\.txt\\' . org-mode)) (add-hook 'org-mode-hook '(lambda () (text-scale-set 4))) M-x eval-buffer then C-x C-f to open a .txt file, and then C-x C-f to open another .txt file. Every time a .txt is opened, the font size become larger and larger. However, the indicator in the mode line remains +4. I can confirm this behaviour but I don't think this is an error. The description of `text-scale-set' reads: C-h f text-scale-set RET , | text-scale-set is an interactive autoloaded Lisp function in | `face-remap.el'. | | (text-scale-set LEVEL) | | Set the scale factor of the default face in the current buffer to LEVEL. | If LEVEL is non-zero, `text-scale-mode' is enabled, otherwise it is disabled. | | LEVEL is a number of steps, with 0 representing the default size. | Each step scales the height of the default face by the variable | ^ | `text-scale-mode-step' (a negative number decreases the height by | the same amount). ` The first time `org-mode-hook' is run the height of default font is scaled by 4 levels, i.e. the height of default font is set to a new value. The second time `org-mode-hook' is run the height is scaled again, this time based on the new value. And so on. If you want to set the face height you might use: (set-face-attribute 'default nil :height 100) Here `100' means 100% of the font size in pt (afaik). Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de
Re: [O] Problem with choosing mode while editing blocks with C-c '
Hey Nick, On Wed, Mar 14, 2012 at 04:11, Nick Dokos nicholas.do...@hp.com wrote: suvayu ali fatkasuv...@gmail.com wrote: There was a discussion of this topic recently, I had and still have my q= uote source blocks in artists (picture) mode and thought this was strange behaviour. BTW, artist-mode is *not* the same as picture-mode. Actually I keep confusing between the two and I'm not sure which I was seeing. Well, they *are* different, but it turns out that if artist-picture-compatibility is true (which it is by default), then artist-mode turns on picture-mode, so they are difficult to tell apart just looking at the modeline. Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! Nick Thanks a lot. :) -- Suvayu Open source is the future. It sets us free.
[O] Bug: Falsely identify Table formula as INVISIBLE target
I use a formula like this in my org table: #+TBLFM: $=vmean($..$);%.3f However, when I export the org table to a latex file, there appears a line in the tex file like this: ..\$(INVISIBLE) If I use #+TBLFM: $=vmean($2..$);%.3f, the problem will disappear. I think this is caused by the functions in org-exp.el falsely identifies the formula as INVISIBLE target. By: Muchenxuan Tong
Re: [O] Problem with choosing mode while editing blocks with C-c '
Sorry the quoting was all wrong! Gmail was behaving weirdly. I wanted to quote the other message. On Wed, Mar 14, 2012 at 03:59, Nick Dokos nicholas.do...@hp.com wrote: The case-fold-search problem is in org-src.el:org-edit-src-code. case-fold-search is let-bound to t, but the let form evaluates all the VARLIST forms before evaluating the body, so the very next varlist (case-fold-search t) (info (org-edit-src-find-region-and-lang)) ... fails because in its evaluation, case-fold-search is still nil. The solution is to use a let* form instead: just change the let on line 216 to a let*. On Wed, Mar 14, 2012 at 09:41, suvayu ali fatkasuv...@gmail.com wrote: Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! I am attaching the changes as a patch. Let me know if it is okay. Thanks, -- Suvayu Open source is the future. It sets us free. From 48eb85df419c38a57d35808ca3a3bc9d86e05c33 Mon Sep 17 00:00:00 2001 From: Suvayu Ali fatkasuvayu+li...@gmail.com Date: Wed, 14 Mar 2012 09:49:40 +0100 Subject: [PATCH] Change let bind to a let* in org-edit-src-code * org-src.el (org-edit-src-code): Change let bind to let*, e.g. if case-fold-search is bound to nil globally, the (case-fold-search t) doesn't work until we get to the body. The fix and analysis was provided by Nick Dokos on this email message thread: http://thread.gmane.org/gmane.emacs.orgmode/53335/focus=53342 TINY CHANGE --- lisp/org-src.el | 20 ++-- 1 files changed, 10 insertions(+), 10 deletions(-) diff --git a/lisp/org-src.el b/lisp/org-src.el index 9cd56d2..dfaa72d 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -213,16 +213,16 @@ (defun org-edit-src-code (optional context code edit-buffer-name) (interactive) (unless (eq context 'save) (setq org-edit-src-saved-temp-window-config (current-window-configuration))) - (let ((mark (and (org-region-active-p) (mark))) - (case-fold-search t) - (info (org-edit-src-find-region-and-lang)) - (full-info (org-babel-get-src-block-info 'light)) - (org-mode-p (derived-mode-p 'org-mode)) ;; derived-mode-p is reflexive - (beg (make-marker)) - (end (make-marker)) - (allow-write-back-p (null code)) - block-nindent total-nindent ovl lang lang-f single lfmt buffer msg - begline markline markcol line col transmitted-variables) + (let* ((mark (and (org-region-active-p) (mark))) + (case-fold-search t) + (info (org-edit-src-find-region-and-lang)) + (full-info (org-babel-get-src-block-info 'light)) + (org-mode-p (derived-mode-p 'org-mode)) ;; derived-mode-p is reflexive + (beg (make-marker)) + (end (make-marker)) + (allow-write-back-p (null code)) + block-nindent total-nindent ovl lang lang-f single lfmt buffer msg + begline markline markcol line col transmitted-variables) (if (not info) nil (setq beg (move-marker beg (nth 0 info)) -- 1.7.7.6
Re: [O] Syntax highlighting of code blocks in beamer slides
Dear Alan,
dear Nick,
many thanks for your help. Installing minted and pygments and then putting the
emacs-lisp snippet from
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
into my .emacs file did work. Now my code snippets are syntax-highlighted! Do
you have any suggestions on which pygments color styles work well in
presentations?
Many thanks in advance,
Stefan
On 13.03.2012, at 14:58, Nick Dokos wrote:
Alan Schmitt alan.schm...@polytechnique.org wrote:
On 13 mars 2012, at 14:41, Stefan Vollmar wrote:
Hello, we want to create slides via beamer. This works fine except
for source code listings (#begin_src python...#end_src) - if
exported as HTML they have syntax-highlighting as expected, however,
when exported as LaTeX the syntax-highlighting is lost. Is there a
way to create beamer slides with source code snippets that have
syntax-highlighting?
I'm following this tutorial for this:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
Yup, I followed the tutorial and set up minted some time ago and I have
not looked back: I just tried the following
--8---cut here---start-8---
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_FRAME_LEVEL: 1
#+BEAMER_HEADER_EXTRA: \usetheme{default}\usecolortheme{default}
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_envargs(Env Args)
%4BEAMER_col(Col) %8BEAMER_extra(Extra)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 :ETC
* foo
#+BEGIN_SRC python :exports code
for x in range(100):
print x=%d , x^2=%d % (x, x*x)
#+END_SRC
--8---cut here---end---8---
and I get a caleidoscope of colors.
The TeX FAQ has some details about where to get minted and its dependencies
(it requires an external Python script, called Pygments):
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist
Nick
--
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213 FAX +49-221-4726-298
Tel.: +49-221-478-5713 Mobile: 0160-93874279
Email: voll...@nf.mpg.de http://www.nf.mpg.de
smime.p7s
Description: S/MIME cryptographic signature
Re: [O] extra whitespace on first page of LaTeX PDF
Hi! I wanted a page break after the Table of Contents so I modified my org- export-latex-classes and added: Have you tried using \newpage instead of \clearpage? When I want a page break after the TOC, I'll usually just drop a \newpage in just before the first heading like this: #+ORG_EXPORT_SETTINGS... \newpage * First Heading ** A Subhead This seems to work satisfactorily. My understanding is that \newpage is what you use for regular pagebreaks, while \clearpage is for ending a chapter because it flushes out floating elements. This discussion on tex.stackexchange.com /may/ be helpful: http://tex.stackexchange.com/questions/45609/is-it-wrong-to-use-clearpage-instead-of-newpage Hope this helps! (Disclaimer: This advice is worth what you paid for it... ; - ) Jos'h
[O] Bug: Bug reporting doesn't work [7.8.03 (release_7.8.03.583.gd7943.dirty)]
Attempting to send a bug report using org-submit-bug-report results in the following backtrace: (expand-file-name scripts (file-name-as-directory (expand-file-name ../contrib ...))) (file-name-as-directory (expand-file-name scripts (file-name-as-directory ...))) (expand-file-name ditaa.jar (file-name-as-directory (expand-file-name scripts ...))) eval((expand-file-name ditaa.jar (file-name-as-directory (expand-file-name scripts ... (equal (symbol-value v) (eval (car ...))) (not (equal (symbol-value v) (eval ...))) (and (get v (quote custom-type)) (get v (quote standard-value)) (not (equal ... ...))) (or (and (symbol-value v) (string-match \\(-hook\\|-function\\)\\' ...)) (and (get v ...) (get v ...) (not ...))) (and (boundp v) (string-match \\`\\(org-\\|outline-\\) (symbol-name v)) (or (and ... ...) (and ... ... ...)) (push v list)) (lambda (v) (and (boundp v) (string-match \\`\\(org-\\|outline-\\) ...) (or ... ...) (push v list)))(org-ditaa-jar-path) mapatoms((lambda (v) (and (boundp v) (string-match \\`\\(org-\\|outline-\\) ...) (or ... ...) (push v list (progn (mapatoms (lambda ... ...))) (if (yes-or-no-p Include your Org-mode configuration ) (progn (mapatoms ...))) (when (yes-or-no-p Include your Org-mode configuration ) (mapatoms (lambda ... ...))) (save-window-excursion (org-pop-to-buffer-same-window (get-buffer-create *Warn about privacy*)) (delete-other-windows) (erase-buffer) (insert You are about to submit a bug report to the Org-mode mailing list.\n\nWe would like to add your full Org-mode and Outline configuration to the\nbug report. This greatly simplifies the work of the maintainer and\nother experts on the mailing list.\n\nHOWEVER, some variables you have customized may contain private\ninformation. The names of customers, colleagues, or friends, might\nappear in the form of file names, tags, todo states, or search strings.\nIf you answer yes to the prompt, you might want to check and remove\nsuch private information before sending the email.) (add-text-properties (point-min) (point-max) (quote ...)) (when (yes-or-no-p Include your Org-mode configuration ) (mapatoms ...)) (kill-buffer (get-buffer *Warn about privacy*)) list) (let (list) (save-window-excursion (org-pop-to-buffer-same-window ...) (delete-other-windows) (erase-buffer) (insert You are about to submit a bug report to the Org-mode mailing list.\n\nWe would like to add your full Org-mode and Outline configuration to the\nbug report. This greatly simplifies the work of the maintainer and\nother experts on the mailing list.\n\nHOWEVER, some variables you have customized may contain private\ninformation. The names of customers, colleagues, or friends, might\nappear in the form of file names, tags, todo states, or search strings.\nIf you answer yes to the prompt, you might want to check and remove\nsuch private information before sending the email.) (add-text-properties ... ... ...) (when ... ...) (kill-buffer ...) list)) (reporter-submit-bug-report emacs-orgmode@gnu.org (org-version) (let (list) (save-window-excursion ... ... ... ... ... ... ... list)) nil nil Remember to cover the basics, that is, what you expected to happen and\nwhat in fact did happen. You don't know how to make a good report? See\n\n http://orgmode.org/manual/Feedback.html#Feedback\n\nYour bug report will be posted to the Org-mode mailing list.\n) (let ((reporter-prompt-for-summary-p Bug report subject: )) (reporter-submit-bug-report emacs-orgmode@gnu.org (org-version) (let ... ...) nil nil Remember to cover the basics, that is, what you expected to happen and\nwhat in fact did happen. You don't know how to make a good report? See\n\n http://orgmode.org/manual/Feedback.html#Feedback\n\nYour bug report will be posted to the Org-mode mailing list.\n) (save-excursion (if ... ...))) org-submit-bug-report() call-interactively(org-submit-bug-report nil nil) This can be traced to evaluating the standard-value property of org-ditaa-jar-path. The relevant defcustom (in org-exp-blocks) is: (defcustom org-ditaa-jar-path (expand-file-name ditaa.jar (file-name-as-directory (expand-file-name scripts (file-name-as-directory (expand-file-name ../contrib (file-name-directory (or load-file-name buffer-file-name))) Path to the ditaa jar executable. :group 'org-babel :type 'string) The second argument (specifying the standard value) can not be evaluated in other contexts where load-file-name and buffer-file-name are undefined. I think this can be traced to changing the original defvar to a defcustom. The following patch seems to fix the
Re: [O] Problem with choosing mode while editing blocks with C-c '
Suvayu Ali fatkasuvayu+li...@gmail.com wrote: On Wed, Mar 14, 2012 at 09:41, suvayu ali fatkasuv...@gmail.com wrote: Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! I am attaching the changes as a patch. Let me know if it is okay. Perfect. Thanks! Nick
[O] [ANN] org-e-html
I am opening up org-e-html for wider usage. This is an alpha release. Start with M-x org-export-dispatch RET etc etc. I will *NOT* be prompt with resolving open issues. I can integrate patches much faster though. --
Re: [O] [PATCH] org-store-link: Fixed a bug where source block edit buffers were not recognized
On 08/03/2012 22:33, Ilya Shlyakhter wrote: attached. Having just run into this same problem (being unable to create and store a code reference link using C-l in a source block edit buffer) I would like to second the inclusion of this or an equivalent patch. Ilya's patch can be seen on the patchwork server at: http://patchwork.newartisans.com/patch/1209/ I am currently using the following patch to work around this problem: diff --git a/lisp/org.el b/lisp/org.el index ad63213..4a97cc9 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -8684,7 +8684,7 @@ For file links, arg negates `org-context-in-file-links'. (setq link (plist-get org-store-link-plist :link) desc (or (plist-get org-store-link-plist :description) link))) - ((equal (buffer-name) *Org Edit Src Example*) + ((org-bound-and-true-p org-edit-src-from-org-mode) (let (label gc) (while (or (not label) (save-excursion Shaun Johnson.
Re: [O] Sticky Agenda buffer: Announcement and request for testing
Hi, Thanks for the new possibility! It works as described. I have a few functions based on the org-agenda-buffer-name, which now is no more available, as all the agenda buffers are named differently: .. (if (get-buffer org-agenda-buffer-name) .. will no more work. I hope that the current agenda buffer names pattern will stay as it is. I will have to hardcode the changed buffer names. Thanks, Rainer Am 11.03.2012 13:48, schrieb Dominik, Carsten: Hi everyone, already in Januar, Max Mikhanosha had published the first version of his code to implement multiple agenda buffers. I have worked with him over the last few weeks, and we think that it is now quite stable. Sticky agenda buffers (this is how Max calls it now) means the ability to keep multiple agenda buffer around. So while this does not cut down on the time it takes to create an agenda view, it has massive impact in a situation where you would like to switch between different agenda views frequently. The code it available in the git repository, in the branch max-sticky-agenda. And it would be great if a few people could go ahead and do some testing before we merge it. Testing should be done both with sticky buffers turned off and turned on. We have made it now very simple to test it: git pull origin git checkout max-sticky-agenda Then, in Emacs, use the `*' key in the agenda dispatcher to turn sticky buffers on and off. Since sticky buffers are not made new each time you look at them, you need to update them when you think it is needed, by pressing `g' or `r' in the buffer. To make sure all buffer are rebuilt, use `C-c a * *', so press the star twice to toggle sticky buffer off and back on. This will remove all existing agenda buffers, so that they will be made again when you dispatch to them. Regards - Carsten and Max
[O] Tangling without clutter?
Hi! I was writing some documentation about how to use a Python function, so I decided to try the tangling feature. However, the result, when exported to PDF, is unsatisfactory because the referenced code block is included twice -- first in the original location, then again where I referenced it with function-definition. This is, of course, exactly what it needs to do to be able to execute the code properly and show the result. But it doesn't look nice. Is there any way to suppress the second printing inside the function-demo block? If this isn't clear from the example below, I can provide examples of the duplication in action as well as what I'd like the output to look like. Thanks very much! Example file: #+TITLE: Tangle Test #+LANGUAGE: en #+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc * Tangled Code I want to show the definition of a function first: #+name: function-definition #+begin_src python :tangle yes :exports code def entable(data): if not data: return /No data./ columns = len(data[0]) sizes = [0,]*columns for row in data: sizes = [max(x) for x in zip(sizes, [len(str(t)) for t in row])] format = | + | .join([%%%ds % x for x in sizes])+ | return \n.join([format % tuple(row) for row in data]) #+end_src Now I want to show a demonstration of how the function might be called. I need the function to be included so that demonstration code can be executed, but I don't want to include the function definition twice: #+name: function-demo #+begin_src python :tangle yes :exports both :noweb yes :results output function-definition print entable([[One, 2, 3],[Four, 5, 6], [Seven, 8, 9]]) #+end_src Which gives us this result: #+results: function-demo : | One | 2 | 3 | : | Four | 5 | 6 | : | Seven | 8 | 9 |
Re: [O] Sticky Agenda buffer: Announcement and request for testing
At Wed, 14 Mar 2012 16:54:17 +0100, Rainer Stengele wrote: I have a few functions based on the org-agenda-buffer-name, which now is no more available, as all the agenda buffers are named differently: .. (if (get-buffer org-agenda-buffer-name) .. will no more work. If you don't turn sticky on, then the name of the agenda will stay the same as before, it only generates unique names if sticky is enabled. I hope that the current agenda buffer names pattern will stay as it is. I will have to hardcode the changed buffer names. The method of generating default sticky agenda buffer names by adding keys used to invoke it will not change. You can also override it by using `org-agenda-custom-commands', if you specify `org-agenda-buffer-name' as one of the variables being overridden for a specific command, that name will take precedence over the automatic method. Regards, Max
Re: [O] Percent justification in Beamer tables
Nick Dokos nicholas.do...@hp.com writes: François Pinard pin...@iro.umontreal.ca wrote: [...] in an Org table, a column is made up of numbers, each of which is immediately followed by a percent sign [...] It's of course possible (even probable) that the latex exporter behaves differently from the html exporter in this case (and probably many other cases.) [...] The new exporters based on Nicolas's org-element parser will presumably behave a lot more consistently. Hello, Nick. OK, so light comes from the future :-). In the meantime [...] #+ATTR_LaTeX: align=|r|r|l|r|l|r| Let me thank you for your advice. It worked very nicely. François
Re: [O] Tangling without clutter?
Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! I was writing some documentation about how to use a Python function, so I decided to try the tangling feature. However, the result, when exported to PDF, is unsatisfactory because the referenced code block is included twice -- first in the original location, then again where I referenced it with function-definition. This is, of course, exactly what it needs to do to be able to execute the code properly and show the result. But it doesn't look nice. Is there any way to suppress the second printing inside the function-demo block? If this isn't clear from the example below, I can provide examples of the duplication in action as well as what I'd like the output to look like. Thanks very much! Example file: #+TITLE: Tangle Test #+LANGUAGE: en #+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc * Tangled Code I want to show the definition of a function first: #+name: function-definition #+begin_src python :tangle yes :exports code def entable(data): if not data: return /No data./ columns = len(data[0]) sizes = [0,]*columns for row in data: sizes = [max(x) for x in zip(sizes, [len(str(t)) for t in row])] format = | + | .join([%%%ds % x for x in sizes])+ | return \n.join([format % tuple(row) for row in data]) #+end_src Now I want to show a demonstration of how the function might be called. I need the function to be included so that demonstration code can be executed, but I don't want to include the function definition twice: #+name: function-demo #+begin_src python :tangle yes :exports both :noweb yes :results output function-definition print entable([[One, 2, 3],[Four, 5, 6], [Seven, 8, 9]]) #+end_src Which gives us this result: #+results: function-demo : | One | 2 | 3 | : | Four | 5 | 6 | : | Seven | 8 | 9 | Aloha! Does the :no-expand header argument do what you want? See http://orgmode.org/manual/no_002dexpand.html#no_002dexpand. hth, Tom -- Thomas S. Dye http://www.tsdye.com
[O] I'm tripping over #+BABEL: vs. #+PROPERTY:
1) I see from http://orgmode.org/Changes.html, section Incompatible changes,
that I have to change my #+BABEL: lines to something else, in order to upgrade
from 7.7 to 7.8.03. But I can't figure out to what.
I previously had:
#+BABEL: :session *R* :results output :exports both
#+begin_src R :exports none :results silent
setwd('c:/Users/ken/wdir')
source(src/main/R/mylib.R)
#+end_src
What does that translate to, using #+PROPERTY: syntax? I tried the following,
but then when I execute a #+begin_src R block, it doesn't evaluate in a
session called *R*, it just evaluates in-process. No *R* buffer is created.
#+PROPERTY: session *R*
#+PROPERTY: results output
#+PROPERTY: exports both
A pointer to some transition doc would also be great, if such a thing exists.
2) In the same list of Incompatible changes, it says code blocks are named
with - results are named with code block may still be labeled with named with
#+tblname: will be considered to be named results. What on earth does that
mean?? I would offer a doc patch but I can't figure it out. =)
--
Ken Williams, Senior Research Scientist
WindLogics
http://windlogics.com
CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution of any kind is strictly
prohibited. If you are not the intended recipient, please contact the sender
via reply e-mail and destroy all copies of the original message. Thank you.
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
Hi Ken,
Did you press C-c C-c on each property line after it was written?
Property lines only take effect either with C-c C-c, or when the file is
first opened.
Best,
Ken Williams ken.willi...@windlogics.com writes:
1) I see from http://orgmode.org/Changes.html, section Incompatible
changes, that I have to change my #+BABEL: lines to something else,
in order to upgrade from 7.7 to 7.8.03. But I can't figure out to
what.
I previously had:
#+BABEL: :session *R* :results output :exports both
#+begin_src R :exports none :results silent
setwd('c:/Users/ken/wdir')
source(src/main/R/mylib.R)
#+end_src
What does that translate to, using #+PROPERTY: syntax? I tried the
following, but then when I execute a #+begin_src R block, it doesn't
evaluate in a session called *R*, it just evaluates in-process. No
*R* buffer is created.
#+PROPERTY: session *R*
#+PROPERTY: results output
#+PROPERTY: exports both
A pointer to some transition doc would also be great, if such a thing exists.
2) In the same list of Incompatible changes, it says code blocks
are named with - results are named with code block may still be
labeled with named with #+tblname: will be considered to be named
results. What on earth does that mean?? I would offer a doc patch
but I can't figure it out. =)
--
Ken Williams, Senior Research Scientist
WindLogics
http://windlogics.com
CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution of any
kind is strictly prohibited. If you are not the intended recipient, please
contact the sender via reply e-mail and destroy all copies of the original
message. Thank you.
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
Aha! That was the trick, thanks. How about a translation of the text for question 2)? -Ken -Original Message- From: Eric Schulte [mailto:eric.schu...@gmx.com] Sent: Wednesday, March 14, 2012 1:29 PM To: Ken Williams Cc: emacs-orgmode@gnu.org Subject: Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY: Hi Ken, Did you press C-c C-c on each property line after it was written? Property lines only take effect either with C-c C-c, or when the file is first opened. [...] 2) In the same list of Incompatible changes, it says code blocks are named with - results are named with code block may still be labeled with named with #+tblname: will be considered to be named results. What on earth does that mean?? I would offer a doc patch but I can't figure it out. =) CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
How about a translation of the text for question 2)? [...] 2) In the same list of Incompatible changes, it says code blocks are named with - results are named with code block may still be labeled with named with #+tblname: will be considered to be named results. What on earth does that mean?? I would offer a doc patch but I can't figure it out. =) Name code blocks with #+name: and their results will be named with #+results:, e.g., #+name: foo #+begin_src emacs-lisp :foo #+end_src #+RESULTS: foo : :foo If you want to include literal data you should also use #+name: to name the data, e.g., #+name: bar : bar For backwards compatibility and inter-operation with existing table functionality, you can use #+tblname: instead of #+name: when naming a table. #+tblname: baz | foo | bar | | baz | quz | Hope that clarifies. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Tangling without clutter?
Hi! Does the :no-expand header argument do what you want? See http://orgmode.org/manual/no_002dexpand.html#no_002dexpand. I tried using it like this: #+name: function-demo #+begin_src python :exports both :noweb yes :results output :no-expand function-definition print entable([[One, 2, 59],[Four, 5, 27], [Seven, 8, 9]]) #+end_src But it didn't seem to affect the results at all. I may be using it wrong, the documentation is a bit sparse, without any examples... It seems like I almost need some variant of the tangle argument to :noweb where syntax references are expanded for evaluation, but not for anything else. Thanks for taking a look! Jos'h -Original Message- From: Thomas S. Dye [mailto:t...@tsdye.com] Sent: Wednesday, March 14, 2012 2:23 PM To: Jos'h Fuller Cc: emacs-orgmode@gnu.org Subject: Re: Tangling without clutter? Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! I was writing some documentation about how to use a Python function, so I decided to try the tangling feature. However, the result, when exported to PDF, is unsatisfactory because the referenced code block is included twice -- first in the original location, then again where I referenced it with function-definition. This is, of course, exactly what it needs to do to be able to execute the code properly and show the result. But it doesn't look nice. Is there any way to suppress the second printing inside the function-demo block? If this isn't clear from the example below, I can provide examples of the duplication in action as well as what I'd like the output to look like. Thanks very much! Example file: #+TITLE: Tangle Test #+LANGUAGE: en #+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in- toc * Tangled Code I want to show the definition of a function first: #+name: function-definition #+begin_src python :tangle yes :exports code def entable(data): if not data: return /No data./ columns = len(data[0]) sizes = [0,]*columns for row in data: sizes = [max(x) for x in zip(sizes, [len(str(t)) for t in row])] format = | + | .join([%%%ds % x for x in sizes])+ | return \n.join([format % tuple(row) for row in data]) #+end_src Now I want to show a demonstration of how the function might be called. I need the function to be included so that demonstration code can be executed, but I don't want to include the function definition twice: #+name: function-demo #+begin_src python :tangle yes :exports both :noweb yes :results output function-definition print entable([[One, 2, 3],[Four, 5, 6], [Seven, 8, 9]]) #+end_src Which gives us this result: #+results: function-demo : | One | 2 | 3 | : | Four | 5 | 6 | : | Seven | 8 | 9 | Aloha! Does the :no-expand header argument do what you want? See http://orgmode.org/manual/no_002dexpand.html#no_002dexpand. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
-Original Message- From: Eric Schulte [mailto:eric.schu...@gmx.com] Sent: Wednesday, March 14, 2012 1:40 PM To: Ken Williams Cc: emacs-orgmode@gnu.org Subject: Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY: How about a translation of the text for question 2)? [...] Hope that clarifies. Cheers, Thanks. I think I see what happened - the following text (in the commit message for 7e93b90f8816346a16ad49cee22870b17c05b211) : - call lines are specified with #+call: - code blocks are named with #+name: - results are named with #+name:, however results generated by a code block may still be labeled with #+results:, and tables named with #+tblname: will be considered to be named results got mangled by the HTML builder into this: call lines are specified with #+call: code blocks are named with - results are named with code block may still be labeled with named with #+tblname: will be considered to be named results So some '#' characters probably need to be escaped. -Ken CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.
Re: [O] Tangling without clutter?
Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! Does the :no-expand header argument do what you want? See http://orgmode.org/manual/no_002dexpand.html#no_002dexpand. I tried using it like this: #+name: function-demo #+begin_src python :exports both :noweb yes :results output :no-expand function-definition print entable([[One, 2, 59],[Four, 5, 27], [Seven, 8, 9]]) #+end_src But it didn't seem to affect the results at all. I may be using it wrong, the documentation is a bit sparse, without any examples... It seems like I almost need some variant of the tangle argument to :noweb where syntax references are expanded for evaluation, but not for anything else. Why would you want to tangle out a python src file with an un-expanded noweb reference? Either way, who am I to judge. I've just added a new eval option to the noweb header argument which will expand noweb references *only* during interactive evaluation. Best, Thanks for taking a look! Jos'h -Original Message- From: Thomas S. Dye [mailto:t...@tsdye.com] Sent: Wednesday, March 14, 2012 2:23 PM To: Jos'h Fuller Cc: emacs-orgmode@gnu.org Subject: Re: Tangling without clutter? Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! I was writing some documentation about how to use a Python function, so I decided to try the tangling feature. However, the result, when exported to PDF, is unsatisfactory because the referenced code block is included twice -- first in the original location, then again where I referenced it with function-definition. This is, of course, exactly what it needs to do to be able to execute the code properly and show the result. But it doesn't look nice. Is there any way to suppress the second printing inside the function-demo block? If this isn't clear from the example below, I can provide examples of the duplication in action as well as what I'd like the output to look like. Thanks very much! Example file: #+TITLE: Tangle Test #+LANGUAGE: en #+OPTIONS: H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in- toc * Tangled Code I want to show the definition of a function first: #+name: function-definition #+begin_src python :tangle yes :exports code def entable(data): if not data: return /No data./ columns = len(data[0]) sizes = [0,]*columns for row in data: sizes = [max(x) for x in zip(sizes, [len(str(t)) for t in row])] format = | + | .join([%%%ds % x for x in sizes])+ | return \n.join([format % tuple(row) for row in data]) #+end_src Now I want to show a demonstration of how the function might be called. I need the function to be included so that demonstration code can be executed, but I don't want to include the function definition twice: #+name: function-demo #+begin_src python :tangle yes :exports both :noweb yes :results output function-definition print entable([[One, 2, 3],[Four, 5, 6], [Seven, 8, 9]]) #+end_src Which gives us this result: #+results: function-demo : | One | 2 | 3 | : | Four | 5 | 6 | : | Seven | 8 | 9 | Aloha! Does the :no-expand header argument do what you want? See http://orgmode.org/manual/no_002dexpand.html#no_002dexpand. hth, Tom -- Thomas S. Dye http://www.tsdye.com -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Tangling without clutter?
Hi! It seems like I almost need some variant of the tangle argument to :noweb where syntax references are expanded for evaluation, but not for anything else. Why would you want to tangle out a python src file with an un-expanded noweb reference? Either way, who am I to judge. I've just added a new eval option to the noweb header argument which will expand noweb references *only* during interactive evaluation. Please allow me to explain, I think it's a legitimate use case... I would like to provide a listing of a Python function, then later in the document show a demonstration of how it's used. I just did this when preparing some documentation for another programmer who is porting an application between languages. So I listed the function, then after a discussion, I had a demonstration of how to use the function. I wanted the output from the demonstration to be live, generated from the demonstration code. Therefore, I needed to reference the function defined above. Unfortunately, the reference was expanded during export so that the same block of code appeared /twice/, presenting the reader with something like this: : Here's a function: : def gorking(): : return gork : : Here's how to use the function: : def gorking(): : return gork : : print gorking() : : Which gives us: : gork As you can see, it's rather clumsy to have the function in the output twice. It's not too bad for this example, but anything more than a few lines becomes quite a distraction! This would have been preferable: : Here's a function: : def gorking(): : return gork : : Here's how to use the function: : function-gorking : : print gorking() : : Which gives us: : gork The original %.org file would look like this: : Here's a function: : #+name: function-gorking : #+begin_src python :tangle yes : def gorking(): : return gork : #+end_src : : Here's how to use the function: : #+name: function-gorking-demo : #+begin_src python :tangle yes : function-gorking : : print gorking() : #+end_src : : Which gives us: : #+results: function-gorking-demo : gork Does that explain it better? Thanks! Jos'h
[O] Org-mode and icicles - tags
I find Icicles useful in most areas of emacs, but it gets in the way when I'm trying to complete tags. This is probably as much of an Icicles question as an Org one. I do C-c C-q and see the existing tag for a heading e.g. :boring:. I type comp and press TAB, hoping for completion to :boring:computer:. Instead the existing tag boring is entirely replaced by the completed one computer. If I turn off icy mode, the behaviour is as expected. Does anyone else use Icicles and Org-mode, and if so have they found a way around this? Only relevant bit from custom-set-variables: '(icicle-TAB-completion-methods (quote (vanilla basic))) Thanks Nick
[O] Org-mode and icicles - tags
I find Icicles useful in most areas of emacs, but it gets in the way when I'm trying to complete tags. This is probably as much of an Icicles question as an Org one. I do C-c C-q and see the existing tag for a heading e.g. :boring:. I type comp and press TAB, hoping for completion to :boring:computer:. Instead the existing tag boring is entirely replaced by the completed one computer. If I turn off icy mode, the behaviour is as expected. Does anyone else use Icicles and Org-mode, and if so have they found a way around this? Only relevant bit from custom-set-variables: '(icicle-TAB-completion-methods (quote (vanilla basic))) Thanks Nick
Re: [O] Problem with choosing mode while editing blocks with C-c '
Nick Dokos nicholas.do...@hp.com writes:
Thorsten quintf...@googlemail.com wrote:
suvayu ali fatkasuvayu+li...@gmail.com writes:
Hi,
I am having problems editing blocks with C-c '. If the blocks are
marked
with upper case letters Emacs brings up the temporary buffer in
picture-mode.
#+BEGIN_SRC latex
#+END_SRC
However the buffer mode is chosen correctly if lower case letters are
used.
#+begin_src latex
#+end_src
Any ideas what could be wrong?
There was a discussion of this topic recently, I had and still have
my quote source
blocks in artists (picture) mode and thought this was strange behaviour.
Some stated that this is a feature, while Eric (Schulte) confirmed the
behaviour and agreed that it appears more like a bug than a feature.
I'm not sure how to link to email threads, I hope the following link
works for you:
[[gnus:nntp%2Bnews.gmane.org:gmane.emacs.orgmode#87d3964cpp@googlemail.com][Email
from Thorsten: {babel} Editing 'quote' source]]
My system:
GNU Emacs 24.0.93.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10)
of 2012-02-07 on arch
Org-mode version 7.8.03
Ma Gnus v0.2
Wandering aroung org-src.el, I stumbled on the following variable which you
(Thorsten) may find useful in your case:
,
| org-edit-fixed-width-region-mode is a variable defined in `org-src.el'.
| Its value is artist-mode
|
| Documentation:
| The mode that should be used to edit fixed-width regions.
| These are the regions where each line starts with a colon.
|
| You can customize this variable.
`
Thanks, I chose fundamental mode instead of artist mode, since it seems
more natural for quotes. I don't know which other types of fixed-width
regions there are, but for me quotes seem to be the most frequently used
regions of this type. If thats generally the case, wouldn't fundamental
mode be a smarter choice as a default mode in this case (principle
of least surprise)?
--
cheers,
Thorsten
Re: [O] Tangling without clutter?
Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! It seems like I almost need some variant of the tangle argument to :noweb where syntax references are expanded for evaluation, but not for anything else. Why would you want to tangle out a python src file with an un-expanded noweb reference? Either way, who am I to judge. I've just added a new eval option to the noweb header argument which will expand noweb references *only* during interactive evaluation. Please allow me to explain, I think it's a legitimate use case... I would like to provide a listing of a Python function, then later in the document show a demonstration of how it's used. I just did this when preparing some documentation for another programmer who is porting an application between languages. So I listed the function, then after a discussion, I had a demonstration of how to use the function. I wanted the output from the demonstration to be live, generated from the demonstration code. Therefore, I needed to reference the function defined above. Unfortunately, the reference was expanded during export so that the same block of code appeared /twice/, presenting the reader with something like this: : Here's a function: : def gorking(): : return gork : : Here's how to use the function: : def gorking(): : return gork : : print gorking() : : Which gives us: : gork As you can see, it's rather clumsy to have the function in the output twice. It's not too bad for this example, but anything more than a few lines becomes quite a distraction! This would have been preferable: : Here's a function: : def gorking(): : return gork : : Here's how to use the function: : function-gorking : : print gorking() : : Which gives us: : gork The original %.org file would look like this: : Here's a function: : #+name: function-gorking : #+begin_src python :tangle yes : def gorking(): : return gork : #+end_src : : Here's how to use the function: : #+name: function-gorking-demo : #+begin_src python :tangle yes : function-gorking : : print gorking() : #+end_src : : Which gives us: : #+results: function-gorking-demo : gork Does that explain it better? Yes, although it seems that the existing no-export or strip-export options to the :noweb header argument may better suit your purposes. These are described in the Org-mode manual, however, they are not mentioned in the online version of the manual which is out of date. Cheers, Thanks! Jos'h -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
Eric Schulte eric.schu...@gmx.com wrote: Did you press C-c C-c on each property line after it was written? Just to clarify: do I really have to C-c C-c on each line? If I add a bunch of them and then do C-c C-c on one of them, shouldn't that be enough to refresh the setup? Thanks, Nick
Re: [O] Tangling without clutter?
Hi! Yes, although it seems that the existing no-export or strip-export options to the :noweb header argument may better suit your purposes. These are described in the Org-mode manual, however, they are not mentioned in the online version of the manual which is out of date. I thought I had the latest at 7.8.03... Are you referring to a development version? I don't see a reference to those in the documentation that came with that version. Thanks! Jos'h
Re: [O] Tangling without clutter?
Jos'h Fuller Jos'h.ful...@arcproductions.com writes: Hi! Yes, although it seems that the existing no-export or strip-export options to the :noweb header argument may better suit your purposes. These are described in the Org-mode manual, however, they are not mentioned in the online version of the manual which is out of date. I thought I had the latest at 7.8.03... Are you referring to a development version? I don't see a reference to those in the documentation that came with that version. I was referring to the head of the git repository, which can be installed following the instructions from the main org-mode page. Best, -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] How to sort table in blocks.
Sorry for the confusing title. Here is what I would like to do:- 1. I have a multiple column table, one of which has time stamp and another one has an entry in multiple lines, because of better visibility. Therefore the table looks something like this:- |+| | DATE 1 | line 1 | || line 2 | || line 3 | |+| | Date 2 | line 1 | || line 2 | || line 3 | || line 4 | |+| 2. I would like to sort the table based on date, but instead of sorting each line is it possible to sort by block (defined by the horizontal lines.)? I must say I did not find time to do an extensive search to find a solution- therefore a pointer to another post or some URL will be very welcome. Thanks Deb
Re: [O] How to sort table in blocks.
Hi Debaditya, On Thu, Mar 15, 2012 at 01:47, Debaditya Mukhopadhyay debadi...@gmail.com wrote: 2. I would like to sort the table based on date, but instead of sorting each line is it possible to sort by block (defined by the horizontal lines.)? What you are asking about is a table.el table. You can use those with org, but the support is spotty at best. You will loose the ability use table formulae, sorting or even nice export to multiple backends. In short, the answer is no you can't. That said, I believe you can put the multiple lines in one long line and specify how wide the column can be so it appears to be small and neatly folded in buffer. While editing you can call org-edit-special and edit the long line conveniently. You also retain all the other awesome org table features. Hope this helps. -- Suvayu Open source is the future. It sets us free.
Re: [O] setting default pdf viewer
Nick Dokos nicholas.do...@hp.com writes: Part of my frustration with these things (gnome things in particular) is the sparse-to-non-existent documentation, But Nick, the GUI is everything now. Who needs documentation! ? :-( Anecdote. A big, complex translation system was demonstrated to a few governmental possible buyers, who were taking it a bit from above. At the end of the demo, the technician decided to leave printed copies of the documentation. One of the receiving guy said: What? You mean that your users actually have to *learn* how to use your system? Sorry! But am i? I did not even want to resist :-). that's a fight that's been fought and lost many times - many more times than it's been won. On the Linux system, I seem just unable to find everything that needs to be changed to prevent Nautilus from ever getting started. In particular, xdg-open DIRECTORY required that I patch the program rather setting parameters. It is very possible that I might have done it all wrong, but for me at least, it *is* frustrating. Enough venting: I've veered off-topic quite a bit here. [...] But I hope that the discussion, however tangential, is useful. Well, you allowed me to release some steam. Thanks! :-) François
[O] org-odt, org-e-html, org-e-odt needs new maintainers
org-odt, org-e-html, org-e-odt needs new maintainers. Wrt, org-odt the only thing that has remained uncleard for a long time is this feature: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9914. There has been some progress on this the last few days. I believe org-odt is stable enough to hit Emacs-24.1. If you would like to bring specific issue to my attention, mail me directly. I am signing off from the list and I will not be keeping track of the issues - specifically org-odt/ELPA ones - posted in this list. Jambunathan K. --
