Re: [O] [Orgmode] Re: [Feature Request] Cross headings in tables
Hi Achim, On 30.5.2011, at 23:02, Achim Gratz wrote: Hi Carsten, Carsten Dominik carsten.domi...@gmail.com writes: this looks pretty good. One thing I found missing is that header lines should be exempted from column formulas being applied. This works for the headlines at the top of the table, but not in the middle. thank you for having a look. You are right, but this looks like something that goes a bit deeper than my current understanding, I'm afraid. Header lines don't appear to be marked in any way, but simply skipped over before starting the formula calculation. Consequently, the column formula is evaluated for any header line when doing a C-c * directly in the header, which might be considered a bug. I won't touched this aspect of the code since it will probably have farther reaching consequences if changed. I quickly hacked in some extra stuff that looks for cross headers and skips them while the full table is updated — but I'm not sure this is the right thing to do and the way the program logic works requires me to check certain pathological cases twice, which is a bit ugly. I've just rebased against current master and pushed everything back to the repo. I think a better strategy would be to find these additional header lines right before this section of the recalculate function: ;; Now evaluate the column formulas, but skip fields covered by ;; field formulas and mark those extra header lines with the org-untouchable text property. Then you can let the column formulas do their game, and fields marked by this property will automatically exempted.. Also documentation in the manual is missing - one or two sentences in the right place should be enough. Sure, but I'd like to get it working correctly first. :-) Fair enough. I'm using this code at work and things have gone smoothly, but I only use the HTML backend and certainly don't exercise the full breadth of the table functionality (obviously no column formulas were used by me, for instance). Another part which might need a look to support this would be `orgtbl-to-generic'. While testing I stumbled upon this: if a buffer has no undo information associated, org-self-insert-command produces an error while trying to edit the formula. This code path may need to be protected against this (admittedly rare) case, I've been triggering it while testing your example directly in the gnus article buffer. This issue is fixed, thanks for the report. Finally: this patch goes clearly beyond the TINYCHANGE limits. What is yours, and Lawrence's copyright status with the FSF? - Carsten Debugger entered--Lisp error: (wrong-type-argument listp t) cadr(t) (not (cadr buffer-undo-list)) (and ( org-self-insert-command-undo-counter 0) buffer-undo-list (not (cadr buffer-undo-list)) (setcdr buffer-undo-list (cddr buffer-undo-list))) (if (= org-self-insert-command-undo-counter 20) (setq org-self-insert-command-undo-counter 1) (and ( org-self-insert-command-undo-counter 0) buffer-undo-list (not ...) (setcdr buffer-undo-list ...)) (setq org-self-insert-command-undo-counter (1+ org-self-insert-command-undo-counter))) (if (not (eq last-command ...)) (setq org-self-insert-command-undo-counter 1) (if (= org-self-insert-command-undo-counter 20) (setq org-self-insert-command-undo-counter 1) (and ... buffer-undo-list ... ...) (setq org-self-insert-command-undo-counter ...))) (if org-self-insert-cluster-for-undo (if (not ...) (setq org-self-insert-command-undo-counter 1) (if ... ... ... ...))) (cond ((and org-use-speed-commands ...) (cond ... ... ... ...)) ((and ... ... ... ...) (let ... ... ... ... ...)) (t (setq org-table-may-need-update t) (self-insert-command N) (org-fix-tags-on-the-fly) (if org-self-insert-cluster-for-undo ...))) org-self-insert-command(1) Regards Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [Orgmode] Re: [Feature Request] Cross headings in tables
On 31/05/2011 08:21, Carsten Dominik wrote: [...] Finally: this patch goes clearly beyond the TINYCHANGE limits. What is yours, and Lawrence's copyright status with the FSF? I have papers with the FSF for past and future changes to Emacs, so I believe my contributions are covered. Lawrence
Re: [O] Beamer and non-frames
Rasmus Pank Roulund rasmus.p...@gmail.com writes:
I am sorry I have no solution for you just now.
This behavior you're seeking is something I long for as well, to
insert a this frame only custom background, to be precise.
So many great things can be put in-between
\end{frame}
...
\begin{frame}
in Beamer
The issue lies in the org-beamer.el way of divvying up the file into
frames (if memory servers me, it's the org-beamer-sectioning function,
but I can be mistaken), it's a big function that handles most of
org-beamers functionality. For the behavior that we seek we need to
implement a function that can encapsulate the \begin{frame}
... \end{frame} code. However, this is not trivial.
Yeah, I gussed it was something like that..
However, maybe something like to the following could be implemented.
I note the following in my file:
** Frame
...
#+latex_beamer_outside_frame: \againframe2{overview.fig} %(1)
** Next frame
[...]
Depending on whether you use beamer for both presentation and for
handouts, I can give you a kludge that should work for presentation
only:
--8---cut here---start-8---
** Previous frame
text here
#+begin_latex
\end{frame}
\againframe2{overview.fig}
\begin{frame}handout
#+end_latex
** Following frame
--8---cut here---end---8---
Very fragile... and untested! This won't work if the previous frame has
blocks or unterminated lists unfortunately.
An alternative, and likely more workable, solution would be to do some
post-processing using one of org's hooks (org-export-latex-final-hook
maybe with a check for org-beamer-export-is-beamer-p?) to catch some
special tags you put in and insert the appropriate latex code yourself.
This would require some elisp...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.323.gd1f33)
[O] Fatal error occurred, no output PDF file produced
Hi!
Trying to export a subtree to pdf I run into this error:
(c:/texlive/2009/texmf-dist/tex/latex/base/t1cmtt.fd) [1{c:/texlive/2009/texmf-
var/fonts/map/pdftex/updmap/pdftex.map}
! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd
fstartlink.
\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.69 \end{itemize}
! == Fatal error occurred, no output PDF file produced!
Org-mode version 7.5 (release_7.5.365.g929b6)
GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) from trunk 2011-02-16 on
LENNART-69DE564 (patched)
HTML Export of the subtree works perfectly.
How can I find the reason/workaround?
OK - 5 minutes later: I deleted the result/contents of this clocktable
#+BEGIN: clocktable :maxlevel 4 :scope tree2 :timestamp t :link t
#+END:
Now it works.
As far as I read the *Org PDF latex output the reason are the links in the
clocktable output.
This maybe is a bug in the exporter.
I do not like to publish the org file here so
if necessary I could send the contents of the org subtree privately.
-- Rainer
Re: [O] Fatal error occurred, no output PDF file produced
Am 31.05.2011 11:54, schrieb Rainer Stengele:
Hi!
Trying to export a subtree to pdf I run into this error:
(c:/texlive/2009/texmf-dist/tex/latex/base/t1cmtt.fd)
[1{c:/texlive/2009/texmf-
var/fonts/map/pdftex/updmap/pdftex.map}
! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than
\pd
fstartlink.
\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.69 \end{itemize}
! == Fatal error occurred, no output PDF file produced!
Org-mode version 7.5 (release_7.5.365.g929b6)
GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) from trunk 2011-02-16 on
LENNART-69DE564 (patched)
HTML Export of the subtree works perfectly.
How can I find the reason/workaround?
OK - 5 minutes later: I deleted the result/contents of this clocktable
#+BEGIN: clocktable :maxlevel 4 :scope tree2 :timestamp t :link t
#+END:
Now it works.
As far as I read the *Org PDF latex output the reason are the links in the
clocktable output.
This maybe is a bug in the exporter.
I do not like to publish the org file here so
if necessary I could send the contents of the org subtree privately.
-- Rainer
This works: (set :link to nil)
#+BEGIN: clocktable :maxlevel 4 :scope tree2 :timestamp t :link nil
#+END:
-- Rainer
Re: [O] [Patch] For the Manual: using org-crypt
Applied, thanks. - Carsten On May 30, 2011, at 8:23 PM, Ian Barton wrote: Here is the patch. Thanks to Christian for his help. I have edited the text to take into account Jambunathans comments. Ian. On 27/05/11 11:47, Carsten Dominik wrote: Actually, please just make the section in texi formatting, I or someone else will link it in into the manual structure. This is difficult to get right with a patch. Please take Jambunathans comments int account. Thanks - Carsten On May 27, 2011, at 12:38 PM, Ian Barton wrote: On 27/05/11 10:15, Christian Egli wrote: Carsten Dominikcarsten.domi...@gmail.com writes: Is anyone working on making this a complete patch? Sorry, no. I'll have a go and try to make a proper patch against the current manual. Don't blame me if the manual breaks:) Ian. org-crypt.patch - Carsten
Re: [O] [PATCH] Makefile robustness tweak
Applied, thanks. This was not coucht by the patchwork server - please make sure your next patch is formatted properly and attached to the mail, that should do it... - Carsten On May 30, 2011, at 10:25 AM, Barak A. Pearlmutter wrote: From 7c79ea0a21ad6d2646958d25c298a1ac9624e9f6 Mon Sep 17 00:00:00 2001 From: Barak A. Pearlmutter barak+...@cs.nuim.ie Date: Sun, 29 May 2011 22:20:31 +0100 Subject: [PATCH] fail to rm or build incorrect files when doc directory nonexistent --- Makefile | 24 1 files changed, 12 insertions(+), 12 deletions(-) diff --git a/Makefile b/Makefile index 9693fd3..239ab2e 100644 --- a/Makefile +++ b/Makefile @@ -238,30 +238,30 @@ lisp/org-install.el: $(LISPFILES0) Makefile mv org-install.el lisp doc/org: doc/org.texi - (cd doc; $(MAKEINFO) --no-split org.texi -o org) + (cd doc $(MAKEINFO) --no-split org.texi -o org) doc/org.pdf: doc/org.texi - (cd doc; $(TEXI2PDF) org.texi) + (cd doc $(TEXI2PDF) org.texi) doc/orgguide.pdf: doc/orgguide.texi - (cd doc; $(TEXI2PDF) orgguide.texi) + (cd doc $(TEXI2PDF) orgguide.texi) doc/org.html: doc/org.texi - (cd doc; $(TEXI2HTML) --no-split -o org.html org.texi) + (cd doc $(TEXI2HTML) --no-split -o org.html org.texi) UTILITIES/manfull.pl doc/org.html doc/orgcard.pdf: doc/orgcard.tex - (cd doc; pdftex orgcard.tex) + (cd doc pdftex orgcard.tex) doc/orgcard.txt: doc/orgcard.tex - (cd doc; perl ../UTILITIES/orgcard2txt.pl orgcard.tex orgcard.txt) + (cd doc perl ../UTILITIES/orgcard2txt.pl orgcard.tex orgcard.txt) doc/orgcard_letter.tex: doc/orgcard.tex perl -pe 's/\\pdflayout=\(0l\)/\\pdflayout=(1l)/' \ doc/orgcard.tex doc/orgcard_letter.tex doc/orgcard_letter.pdf: doc/orgcard_letter.tex - (cd doc; pdftex orgcard_letter.tex) + (cd doc pdftex orgcard_letter.tex) # Below here are special targets for maintenance only @@ -427,11 +427,11 @@ cleancontrib: cleanelc: rm -f $(ELCFILES) cleandoc: - (cd doc; rm -f org.pdf org org.html orgcard.pdf orgguide.pdf) - (cd doc; rm -f *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs) - (cd doc; rm -f *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps) - (cd doc; rm -f orgcard_letter.tex orgcard_letter.pdf) - (cd doc; rm -rf manual) + -(cd doc rm -f org.pdf org org.html orgcard.pdf orgguide.pdf) + -(cd doc rm -f *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs) + -(cd doc rm -f *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps) + -(cd doc rm -f orgcard_letter.tex orgcard_letter.pdf) + -(cd doc rm -rf manual) cleanrel: rm -rf RELEASEDIR -- 1.7.2.5 - Carsten
Re: [O] [patch] Do not run flyspell checks on org keywords
No one interested in this one ? :)
Cheers,
--Seb
On 2011-05-24, Sébastien Delafond sdelaf...@gmail.com wrote:
Here is a small patch that prevents flyspelle from checking all the Org
keywords. This is especially useful when using a dictionary other than
english.
Cheers,
--Seb
From 0a6493331f1d84a4c44533bdea1c3c9b41c997eb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Delafond?= sdelaf...@gmail.com
Date: Mon, 23 May 2011 18:16:57 +0200
Subject: [PATCH] [flyspell] Do not run flyspell-checks on
{todo,all-time,additional-option-like}-keywords
* this is useful when using flyspell with a non-English dictionary,
or if some of your keywords are in another language
---
lisp/org.el | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index 9f8fa92..676f08f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -20135,9 +20135,15 @@ To get rid of the restriction, use
\\[org-agenda-remove-restriction-lock].
;; Make flyspell not check words in links, to not mess up our keymap
(defun org-mode-flyspell-verify ()
- Don't let flyspell put overlays at active buttons.
- (and (not (get-text-property (max (1- (point)) (point-min)) 'keymap))
- (not (get-text-property (max (1- (point)) (point-min))
'org-no-flyspell
+ Don't let flyspell put overlays at active buttons, or on
+ {todo,all-time,additional-option-like}-keywords.
+ (let ((pos (max (1- (point)) (point-min)))
+ (word (thing-at-point 'word)))
+(and (not (get-text-property pos 'keymap))
+ (not (get-text-property pos 'org-no-flyspell))
+ (not (member word org-todo-keywords-1))
+ (not (member word org-all-time-keywords))
+ (not (member word org-additional-option-like-keywords)
(defun org-remove-flyspell-overlays-in (beg end)
Remove flyspell overlays in region.
Re: [O] [patch] Do not run flyspell checks on org keywords
I would be interested, if I could could get ispell.el to work with
hunspell in a UTF-8 environment (it's the 21st century), or even in
Emacs' Slovenian language environment (Latin-2), without breaking
words for every non-ascii character it encounters...
This is off-topic (sorry), but if anyone has a working setup for
something like the above, I'd be grateful if you'd share it with me
off-list.
I'm using GNU Emacs 23 and hunspell under Mac OS X. Hunspell seems to
work perfectly well from the command line with a UTF-8 text file, even
when I'm using it with a Latin-2-encoded dictionary.
Yours,
Christian
On 5/31/11 3:14 PM, Sébastien Delafond wrote:
No one interested in this one ? :)
Cheers,
--Seb
On 2011-05-24, Sébastien Delafondsdelaf...@gmail.com wrote:
Here is a small patch that prevents flyspelle from checking all the Org
keywords. This is especially useful when using a dictionary other than
english.
Cheers,
--Seb
From 0a6493331f1d84a4c44533bdea1c3c9b41c997eb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Delafond?=sdelaf...@gmail.com
Date: Mon, 23 May 2011 18:16:57 +0200
Subject: [PATCH] [flyspell] Do not run flyspell-checks on
{todo,all-time,additional-option-like}-keywords
* this is useful when using flyspell with a non-English dictionary,
or if some of your keywords are in another language
---
lisp/org.el | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index 9f8fa92..676f08f 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -20135,9 +20135,15 @@ To get rid of the restriction, use
\\[org-agenda-remove-restriction-lock].
;; Make flyspell not check words in links, to not mess up our keymap
(defun org-mode-flyspell-verify ()
- Don't let flyspell put overlays at active buttons.
- (and (not (get-text-property (max (1- (point)) (point-min)) 'keymap))
- (not (get-text-property (max (1- (point)) (point-min))
'org-no-flyspell
+ Don't let flyspell put overlays at active buttons, or on
+ {todo,all-time,additional-option-like}-keywords.
+ (let ((pos (max (1- (point)) (point-min)))
+ (word (thing-at-point 'word)))
+(and (not (get-text-property pos 'keymap))
+(not (get-text-property pos 'org-no-flyspell))
+(not (member word org-todo-keywords-1))
+(not (member word org-all-time-keywords))
+(not (member word org-additional-option-like-keywords)
(defun org-remove-flyspell-overlays-in (beg end)
Remove flyspell overlays in region.
[O] How to allow for no-date when prompting for a DEADLINE?
Hello,
I would like my TODO capture template to prompt me for a due date, as this is
often an intrinsic property of the task (fill your tax report, answer for
presence at birthday party, etc.).
However, some tasks don't have or don't need a due date. But the prompt does
not allow me to answer none:
#+begin_src emacs-lisp
(setq org-capture-templates
`((t Task entry
(file+headline ,org-default-notes-file Tasks)
* NEW %^{Task Name}%? %^g
DEADLINE: %^{Due Date?|}t
:PROPERTIES:
:Effort: %^{Time Estimate|0|10|30|60|120}
:END:
%i
:empty-lines 1)))
#+end_src
You can see, here above, that I tried to change the prompt label, and to
include an empty default value, but that does not make it...
In fact, it is a bit worse than that: I'd like no DEADLINE line to be inserted
in this case.
Maybe the way I try to solve my problem is getting too complex. Any idea?
Best regards,
Seb
--
Sebastien Vauban
[O] Problem with org-export to LaTeX and babel
Hello, I tried to use org-mode the first time with LaTeX export and embedded babel block. But it doesn't do the right thing. Following test: -- snip * gnuplot example Just a test. #+begin_src gnuplot :session none :file out.png set terminal png set xlabel gx;set ylabel gy;set zlabel gz set grid xtics ytics set view 0,0 plot cos(x) #+end_src -- snip This in an org-mode file and than exporting to LaTeX I always get following error message from babel: snip from *Messages*: Export buffer: Exporting to LaTeX... org-babel-exp processing... executing Gnuplot code block... gnuplot-mode 0.6.0 (gnuplot 4.4) -- report bugs with C-c C-u split-string: Wrong type argument: stringp, nil snip I'm using GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-12-11 on brahms, modified by Debian and org-mode commit cec8711a44a9a1ac6552546c05ec0623a2bf9e45 I tried to trace this down till org-babel-execute:gnuplot (body params) where params is nil. which ist called by org-babel-execute-src-block (optional arg info params) where params is nil which is called by org-babel-exp-results (info type optional silent hash) in this function (nth 2 info) does contain the scanned parameters, but org-babel-execute-src-block is called just with with two not three parameters. After trying the patch: diff --git a/.emacs-lisp/org-mode/ob-exp.el b/.emacs-lisp/org-mode/ob-exp.el index 09e85ca..baccba5 100644 --- a/.emacs-lisp/org-mode/ob-exp.el +++ b/.emacs-lisp/org-mode/ob-exp.el @@ -262,7 +262,8 @@ inhibit insertion of results into the buffer. (equal hash (org-babel-exp-in-export-file (nth 0 info) (org-babel-result-hash info)) (let ((lang (nth 0 info)) - (body (nth 1 info))) + (body (nth 1 info)) + (params (nth 2 info))) ;; skip code blocks which we can't evaluate (when (fboundp (intern (concat org-babel-execute: lang))) (org-babel-eval-wipe-error-buffer) @@ -275,11 +276,11 @@ inhibit insertion of results into the buffer. `((:results . ,(if silent silent replace))) (cond ((or (equal type 'block) (equal type 'inline)) - (org-babel-execute-src-block nil info)) + (org-babel-execute-src-block nil info params)) ((equal type 'lob) (save-excursion (re-search-backward org-babel-lob-one-liner-regexp nil t) - (org-babel-execute-src-block nil info) + (org-babel-execute-src-block nil info params) (provide 'ob-exp) it worked. But I'm not sure if my using of babel is correct and if yes, wheter the patch will do the right thing in all usings babel. (I'm just learning to understand lisp programming.) Any suggestions? Stefan -- Stefan-W. Hahn It is easy to make things. It is hard to make things simple.
Re: [O] [Orgmode] Re: [Feature Request] Cross headings in tables
Hi Carsten, Carsten Dominik carsten.domi...@gmail.com writes: I think a better strategy would be to find these additional header lines right before this section of the recalculate function: [...] I'll have a look (probably not today), but I'd rather tag them with an org-header property and arrange it so that this can be used in other places as well. Another part which might need a look to support this would be `orgtbl-to-generic'. Noted. Finally: this patch goes clearly beyond the TINYCHANGE limits. What is yours, and Lawrence's copyright status with the FSF? My status with the FSF is succinctly and fully characterized as non-existing. I've sent that mail form to the FSF and I'll see what happens next — it seems I'll get snail mail in a few weeks? Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] [PATCH] extend doc strings of priority defcustoms
My most recent patch has been applied. Unfortunately it broke the wrap around when cycling through priorities. Now I have rewritten the if that I obviously did not understand enough, have corrected the error message, have tested much better and suggest this additional patch that should definitely improve the situation. Michael 0001-Priorities-Fix-error-handling-and-improve-docstring.patch Description: Binary data
Re: [O] Bug in latex description list export
Hello, Robert Goldman rpgold...@sift.info writes: I stumbled across a /very/ weird bug in latex export. The bug arises when there is 1. A footnote in a description list 2. The word description appears in the footnote and 3. The word description is flush to the left margin. It will happen anytime contents of a footnote are at column 0. Anyway, I've pushed a fix for that issue. Thank you for the report ! Regards, -- Nicolas Goaziou
Re: [O] [Orgmode] Re: [Feature Request] Cross headings in tables
My status with the FSF is succinctly and fully characterized as non-existing. I've sent that mail form to the FSF and I'll see what happens next ― it seems I'll get snail mail in a few weeks? In my case the process took close to 4 months. Jambunathan K. --
[O] Broken LaTeX export of tables
Hi,
I think LaTeX export of tables broke sometime between these two commits
Works:
commit 2a8fbc4b464d10dda3ceebf70e4f99825f179dd5
Author: Carsten Dominik carsten.domi...@gmail.com
Date: Mon May 16 08:36:56 2011 +0200
Bury calendar buffer
* lisp/org.el (org-read-date): Bury Calendar buffer after
using it for selecting a date.
Patch by Ben North
TINYCHANGE
Stopped working:
commit bc161ded3693f752616dcd247fc9d638789025ee
Author: Carsten Dominik carsten.domi...@gmail.com
Date: Fri May 27 20:50:09 2011 +0200
Capture: Store time from prompt in file+datetree+prompt target
* lisp/org-capture.el (org-capture-current-plist): Improve docstring.
(org-capture-put): Add docstring.
(org-capture-get): Add docstring.
(org-capture-member): Add LOCAL argument. Add docstring.
(org-capture-set-target-location): Store the time received from a date
prompt into the :prompt-time property.
When using the file+datetree+prompt target for capture, the time set
by the prompt is now stored in the :prompt-time property.
I have attached a minimal org file reproducing the problem. The problem
is subscripts and superscripts inside a table are not put inside math
environments when exporting to LaTeX.
--
Suvayu
Open source is the future. It sets us free.
* Some heading
some text with parameters: /S_p/ /S_0/ /S_1/ /S_2/
GeV/c^2
#+CAPTION: Some parameters.
|---+---|
| Parameter | Value (GeV/c^2) |
|---+---|
| (/S_p/) | 1.0001 \pm 0.0012 |
| (/S_0/) | 0.000\p{0} \pm 0.071\p{0} |
| (/S_1/) | 0.022\p{0} \pm 0.003\p{0} |
| (/S_2/) | 0.18\p{00} \pm 0.04\p{00} |
|---+---|
test.tex
Description: TeX document
Re: [O] HTML Postamble is inside Content DIV
Hi, Sébastien Vauban wrote: Jonathan BISSON wrote: Sébastien Vauban wxhgmqzgwmuf@... writes: After a couple of tests, I've observed that the postamble is forced to be included *inside* the div content. Proof on Line 1764... These are the ending tags of every HTML page: #+begin_src emacs-lisp (unless body-only (insert \n/div\n/body\n/html\n)) #+end_src ... the closing /div referring to the opening of content. Shouldn't it make sense to be able to insert something *out of* the content div? I think so (and the same for preamble)! I rewrote org-export-as-html and did a custom org-publish-org-to-html to call it, in order to get them out off the content div (you can look at a first test on my webpage http://www.bjonnh.net). It's easy to do it I can send you my file if you are interested. I think sharing the code here is always a good idea. However, I'd favor an approach commonly shared by others, ie by either: - moving the postamble out of the content DIV - adding an extra environment next to the content DIV, if the postamble must stay where it currently is -- for historical or compliance reasons? (same applies for preamble) I'm hijacking my own thread, as it received little support, and as the new question is quite related to that: - if we customize the preamble, our string will be inserted as is; - if we customize the postamble, our string will be inserted as is... between a wrapping div called postamble. Shouldn't it be normal to apply the same reasoning for both cases: either impose a wrapper, either not? Any comment for others? Best regards, Seb -- Sebastien Vauban
[O] Column view odd behaviour on emptying field
I am trying to learn the org-taskjuggler mode and following the tutorial on http://orgmode.org/worg/org-tutorials/org-taskjuggler.html. Another great feature of org-mode! Anyhow, this uses Column View extensive, and I noticed a strange behaviour if setting a column field and subsequently emptying it. It seems the property remains, but is blanked and thus disabled, and when setting the property again to an allowed value, a new property field is created. The propery is not displayed in column view, presumably because of the remaining broken (empty) property from the previous erase. 1) Property set *** Database coupling :PROPERTIES: :Effort: 20.0 :allocate: doc :END: 2) Property cleared *** Database coupling :PROPERTIES: :Effort: 20.0 :allocate: :END: 3) Property set again *** Database coupling :PROPERTIES: :Effort: 20.0 :allocate: :allocate: test :END: Regards, -- Johnny
[O] org-preview-latex-fragment + Emacs Themes + tikz
Hello list, One of the many features I regularly enjoy with org-mode is org-preview-latex-fragment, but after I started using a dark theme with white text it haven't work so great. org-preview-latex-fragment is smart and it tries to get my background color and default text color so that the generated images for the latex fragments can have the same appearance as rest of the text (this is REALLY nice). However, while the background changes accordingly the text in the generated images does not. That is, the text is still black as in the default theme, while the background is dark following my theme (the Naquadah theme by Julien Danjou). After investigating this I found out the problem was my org-export-latex-default-packages-alist variable. Particularly, if I include the tikz package the problem occurs, but if tikz is not included (at least not for preview latex) then org-preview-latex-fragment works as it should. Does this problems occur with anyone else? The code I use to set org-export-latex-default-packages-alist is shown below #+begin_src emacs-lisp (setq org-export-latex-default-packages-alist '((AUTO inputenc t) (T1 fontenc t) ( fixltx2e nil) ( graphicx t) ( longtable nil) ( float nil) ( wrapfig nil) ( soul t) ( textcomp t) ( marvosym t) ;;( wasysym t) ; Conflicts with amsmath ( latexsym t) ( amssymb t) ( amsmath t) ;; ( tikz t) ; uncomment to see the bug ( hyperref nil) ( MathDefinitions t) \\tolerance=1000)) #+end_src -- Darlan Cavalcante
[O] Some remarks on org-contacts
Hi to all After some days of using org-contacts with Gnus, I would like to make some comments. I know that this is an early stage of the development, but I think some views and suggestions by users could help Julien or other developers to decide what could be done in the next steps of their work. There seems to be no roadmap on the homepage of the project. - The buffers displaying the contacts file(s) get the changed mark whenever something is done with org-contacts. Even if only a name was searched and no changes have happened at all. Is it a bug or some feature that I don't understand? - The last-read-mail property is a good idea, but it has the disadvantage of changing the file. People using Dropbox or other synchronization tools have a problem here, because they have to remember to manually save the file before they start to work on another computer. There should be an auto-save-hook or something similar. - What I deem most important: For quite a few contacts most people will use to have more than one email address. Org-contacts stores all addresses under the same property with no preference on one of them (unlike BBDB which uses the first entry as a default for completion). It is annoying to hit tab 3 to 4 times before the To-header is complete. It would perhaps be best to have only one address in the EMAIL property and to store alternate addresses in another property (SECONDARY_EMAIL). The SECONDARY_EMAIL could be called by a special function that could be set to a key different from TAB (maybe C-u TAB). Maybe it is even possible to expand to the default address by hitting TAB once, and to give a list of the other addresses by hitting TAB once again. - What can you do with ICONS? Arte they only for chatting? It would be nice to have a small window automatically opening below an Article buffer in Gnus that displays information about the author including his/her image. - Email, phone numbers and postal address should be displayed in the Agenda buffer when a name is searched by org-contacts. Maybe it would be possible to display different information by hitting certain keys: m: mobile-phone, e: email, b: birthday, a: all etc. At the moment one has to switch on follow-mode to display the information. I deem this not very beautiful. For my taste, the look-and-feel of an org-file with lots of property lines is not an aesthetic pleasure. A tabular output (including a picture of the person) would be much nicer. - There should be a function to sort the entries of the same level in contacts files alphabetically. Thank you very much for org-contacts. Best, Sven
Re: [O] Problem with org-export to LaTeX and babel
Stefan-W. Hahn i...@s-hahn.de writes: Hello, I tried to use org-mode the first time with LaTeX export and embedded babel block. But it doesn't do the right thing. Following test: -- snip * gnuplot example Just a test. #+begin_src gnuplot :session none :file out.png set terminal png set xlabel gx;set ylabel gy;set zlabel gz set grid xtics ytics set view 0,0 plot cos(x) #+end_src -- snip [...] I'm using GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.20.1) of 2010-12-11 on brahms, modified by Debian and org-mode commit cec8711a44a9a1ac6552546c05ec0623a2bf9e45 Works fine for me but I'm using a more recent version of org (see signature) *and* I'm using emacs 24.0.x so a couple of differences... although the former is likely more relevant than the latter? -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.331.g2422.dirty)
Re: [O] Unwanted (progn ) when Tangling Lisp Code
Hi Mark, Thanks for the suggestion, I've applied a modified version of your patch which moves the progn wrapping out of the expand-body function and into the evaluation function. Progn wrapping is required for blocks like the following. #+begin_src lisp :results value (format t ~eric) (+ 1 2) #+end_src #+results: : 3 Thanks -- Eric Mark Cox markco...@gmail.com writes: Hi, When tangling lisp source code blocks, the tangled code is wrapped in a `(progn ,@body). For example, the block #+begin_src lisp :tangle example.lisp (defun mischief () (/ 1 0)) #+end_src produces : (progn (defun mischief () : (/ 1 0)) : ) With the attached patch, the tangling process now produces : : (defun mischief () : (/ 1 0)) Thanks Mark Here is the patch. diff --git a/lisp/ob-lisp.el b/lisp/ob-lisp.el index a810d86..3382418 100644 --- a/lisp/ob-lisp.el +++ b/lisp/ob-lisp.el @@ -54,7 +54,7 @@ (format (%S (quote %S)) (car var) (cdr var))) vars \n ) )\n body )) - (format (progn %s) body) + body (if (or (member code result-params) (member pp result-params)) (format (pprint %s) body) @@ -65,7 +65,7 @@ (require 'slime) (org-babel-reassemble-table (with-temp-buffer - (insert (org-babel-expand-body:lisp body params)) + (insert (format (progn\n %s) (org-babel-expand-body:lisp body params))) ((lambda (result) (if (member output (cdr (assoc :result-params params))) (car result) -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] getting org-mode to display its version
Is this possible? I think when I export a web page, I'd like to have a line like: Exported by org-mode version x.y.z ondate ... in that way org-mode can get well deserved credit.
Re: [O] getting org-mode to display its version
Jude DaShiell jdash...@shellworld.net writes: Is this possible? I think when I export a web page, I'd like to have a line like: Exported by org-mode version x.y.z ondate ... in that way org-mode can get well deserved credit. Isn't it already? You are talking of creator info down below. , | org-export-html-postamble is a variable defined in `org-html.el'. | Its value is auto | | Documentation: | Non-nil means insert a postamble in HTML export. | | When `t', insert a string as defined by the formatting string in | `org-export-html-postamble-format'. When set to a string, this | string overrides `org-export-html-postamble-format'. When set to | 'auto, discard `org-export-html-postamble-format' and honor | `org-export-author/email/creator-info' variables. When set to a | function, apply this function and insert the returned string. | The function takes the property list of export options as its | only argument. | | Setting :html-postamble in publishing projects will take | precedence over this variable. | | You can customize this variable. | | [back] ` --
Re: [O] A simpler way to write literal examples?
On Wed, May 25, 2011 at 10:25 PM, Nick Dokos nicholas.do...@hp.com wrote: Steven Haryanto stevenharya...@gmail.com wrote: I plan to document some parts of Perl source code (more specifically, description in subroutine Sub::Spec specification, http://search.cpan.org/dist/Sub-Spec) using Org format instead of the canonical POD, hoping to have better table support, more customizable links, and overall markups that are nicer to look at (IMO). However, one of the nice things of POD (and Wiki, Markdown, etc) for documenting source code is the relative simplicity of writing literal examples: an indented paragraph. In Org we either have to use the colon+space prefix syntax: : this is an example : another line : another line or the example block: #+BEGIN_EXAMPLE this is an example another line another line #+END_EXAMPLE Is there an alternative syntax? If there isn't, would people consider an alternative syntax (e.g. say a setting which toggles parsing an indented paragraph as a literal example)? What is the problem with #+BEGIN_EXAMPLE/#+END_EXAMPLE? IOW, why do you need an alternative syntax? If your answer is too much typing, check out section 15.2, Easy templates, in the Org manual. The problem is visual clutter (yes, I guess Emacs can be told to hide the markup, but I'm talking about when text is displayed as-is and/or outside Emacs) and copy-pasteability (especially with the colon syntax). I know Org format is not optimized for fixed width section, but perhaps there is a way? -- sh
[O] Google Analytics tracking code for org-export-as-html
Hi. I would like to add a Google Analytics tracking code to the exported html file from an org-file. According to the instruction of GAnalytics, the tracking code must be right before /head tag. And I assume it's OK as long as the code is between head and /head. The tracking code needs to be in the html file every time I export it as html. So, I need to somehow add the code segment in the org-file. #+BEGIN_HTML ... #+END_HTML This seems to add whatever between to a location after body tag. Is there anyway to achieve this? soichi
[O] [PATCH] Common Lisp source blocks are now wrapped in a LET form which binds the symbol *default-pathname-defaults* to the directory in which the org file resides.
Hi, This may be contentious and break backward compatibility for some people. Currently, relative pathnames in Common Lisp source blocks are meaningless as the *default-pathname-defaults* symbol is set to whatever the value is when SLIME was invoked. This behaviour is contrary to the shell source block processor (I haven't checked the others). This is in /tmp/example1/test.org #+begin_src sh pwd #+end_src #+results: : #P/tmp/example1/ This is in /tmp/example2/test.org #+begin_src sh pwd #+end_src #+results: : #P/tmp/example2/ The attached patch brings this expected behaviour (well from my point of view) to lisp source blocks. Given the behaviour of Emacs commands like DIRED and COMPILE, I think the patch makes things more consistent. I couldn't figure out how the sh block processor determines the path to the org file so I hacked together something that works using some of the Org hooks. Thanks Mark lisp/ob-lisp.el: Added new variable ORG-BABEL-LISP-CURRENT-BUFFER which is used to store a reference to the currently being processed org file. This variable is setq'd in the hooks for ORG-BABEL-PRE-TANGLE-HOOK, ORG-CTRL-C-CTRL-C-HOOK and ORG-EXPORT-FIRST-HOOK. lisp/ob-lisp.el (org-babel-expand-body:lisp): The code sent to SLIME is now wrapped in a LET block which binds COMMON-LISP:*DEFAULT-PATHNAME-DEFAULTS* to the directory where the currently being processed org file resides. diff --git a/lisp/ob-lisp.el b/lisp/ob-lisp.el index a875d55..db06182 100644 --- a/lisp/ob-lisp.el +++ b/lisp/ob-lisp.el @@ -40,6 +40,14 @@ (defvar org-babel-default-header-args:lisp '()) (defvar org-babel-header-arg-names:lisp '(package)) +(defvar org-babel-lisp-current-buffer nil) + +(let ((fn (lambda () + (setq org-babel-lisp-current-buffer (current-buffer)) + nil))) + (dolist (hook '(org-babel-pre-tangle-hook org-ctrl-c-ctrl-c-hook org-export-first-hook)) +(add-hook hook fn))) + (defun org-babel-expand-body:lisp (body params) Expand BODY according to PARAMS, return the expanded body. @@ -73,8 +81,10 @@ (read (org-bable-lisp-vector-to-list (cadr result))) (error (cadr result) (slime-eval `(swank:eval-and-grab-output - ,(format (progn %s) (buffer-substring-no-properties - (point-min) (point-max + ,(format (let ((common-lisp:*default-pathname-defaults* #P%S)) %s) +(file-name-directory (buffer-file-name org-babel-lisp-current-buffer)) +(buffer-substring-no-properties + (point-min) (point-max (cdr (assoc :package params) (org-babel-pick-name (cdr (assoc :colname-names params)) (cdr (assoc :colnames params)))
Re: [O] Google Analytics tracking code for org-export-as-html
Hi soichi, Hi. I would like to add a Google Analytics tracking code to the exported html file from an org-file. ah, please don't do that. code is between head and /head. You could sneak it in using #+STYLE or org-publish-project-alist :style. Cheers, Tomas
