[O] Bug: [testing] Need note to (setq org-confirm-babel-evaluate nil) [7.7 (release_7.7.340.ga342)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. The interactive testing described in testing/README.org is pretty tiresome otherwise. Or you could use a (let ((org-confirm-babel-evaluate nil)) ... ) in the testing recipe. Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.8.0, Carbon Version 1.6.0 AppKit 1038.36) of 2011-09-12 on pluto.luannocracy.com Package: Org-mode version 7.7 (release_7.7.340.ga342) -- Dave Abrahams BoostPro Computing http://www.boostpro.com
[O] Bug: [testing] missing dependency [7.7 (release_7.7.340.ga342)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. testing/README.org mentions the dependency on jump.el, but not on the ESS package, which appears to be required for `(org-test-load)' to work Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.8.0, Carbon Version 1.6.0 AppKit 1038.36) of 2011-09-12 on pluto.luannocracy.com Package: Org-mode version 7.7 (release_7.7.340.ga342) -- Dave Abrahams BoostPro Computing http://www.boostpro.com
[O] Bug: `org-test-for-executable' should use `executable-find'... [7.7 (release_7.7.320.gc8c8.dirty)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. ...shouldn't it? Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.8.0, Carbon Version 1.6.0 AppKit 1038.36) of 2011-09-12 on pluto.luannocracy.com Package: Org-mode version 7.7 (release_7.7.320.gc8c8.dirty) -- Dave Abrahams BoostPro Computing http://www.boostpro.com
[O] Face color for LaTeX preview
Since my last pull from git master, the preview images of my LaTeX fragments have been black. I've tried customizing org-format-latex-options, but while the :scale property works, changing the :foreground property has no effect. I would like to have it use my default foreground color. Any help would be appreciated, Derek
Re: [O] [babel] BUG in :session
Hi Martyn and Eric, Martyn Jago wrote: > Eric Schulte writes: >> Martyn Jago writes: >>> Eric Schulte writes: I've just pushed up what will hopefully be a more general solution. Basically, language-specific test files can now signal errors if they have unmet dependencies. These are then intercepted by `org-test-load' and the file is not added to the test suite. Hopefully this will allow language-specific tests to be written without breaking the config-less test suite. See the top of test-ob-R.el for an example usage. Cheers -- Eric >>> >>> Unfortunately this is still broken for me. Given the exe exists but the >>> feature doesn't (ie no personal config), the following line causes the >>> error `peculiar error' ! >>> >>>(signal 'org-test-lib-not-found "ess")) FYI, same for me, with the "batch tests", on a git update'd copy done 2 mins ago. #+begin_src sh emacs -Q --batch -l "/cygdrive/c/Program Files/Emacs-24.0/lisp/emacs-lisp/ert.el" -l "/cygdrive/c/Program Files/Emacs-24.0/lisp/emacs-lisp/ert-x.el" -l ~/src/org-mode/testing/org-test.el --eval "(setq org-confirm-babel-evaluate nil)" -f org-test-run-batch-tests #+end_src #+results: OVERVIEW Loading vc-git... OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW OVERVIEW Loading /cygdrive/c/home/sva/src/org-mode/testing/lisp/test-ob-R.el (source)... peculiar error This is on Windows XP SP3, with a Cygwin Emacs (when run from terminal; otherwise, it is a Win32 binary from the FSF). Best regards, Seb -- Sebastien Vauban
[O] [feature request] More flexible repeats
I have habits that I need to perform, e.g., every weekday, or four times a week. I don't see a way to express that. If I could schedule a task for +1.4d or +1.75d (respectively), I'd be happy. Even better would be a more human-readable way to express repetition, because in addition to being frustrated by its limitations, I forget the meaning of Org's fiddly repeat syntax. For example, words like "weekdays" or codes like "4x:w" (meaning four times per week) would be really nice to work with. I'd rather use "/" for "per" but that is already taken. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] [babel] Multiple results blocks for the same source code
"Sebastien Vauban" writes: > Hi Eric, > > Eric Schulte wrote: >> I could not reproduce the error you describe, and your test case passes >> for me. I have added your test case to testing/test-ob.el however so it >> should protect from this error in the future. > > I can't reproduce it anymore right now. But the goal was to have a fuse > against that for the future, yes. > >> You could try running the test suite in batch mode (which will not load >> your configuration) and see if the test still fails for you. If not >> then the problem is probably due to either something in your config. > > When I get back in a "broken" config such as the one described here, I'll do > it. > >> Thanks for the test case! -- Eric >> >> ps. the only comments I have on the test itself are >> 1. The initial placement of the point is described in the >>documentation string for the `org-test-with-temp-text' function > > That's very clear, yes, but for the case where we don't have the string > "" in the initial text. Is point at the end of the string, then? I > guess so. > Oh, I see I didn't address that in the function documentation. In the case of no explicit "" marker the point is placed at the beginning of the inserted text (which also happens to be the very beginning of the buffer). > > But my question was more about... > >>> (org-babel-execute-src-block) ;; second code block execution >>> ;; where is point (supposed to be)? > > ... the position of point after `org-babel-execute-src-block'. > The point should remain wherever it was before executing the code block. > >> 2. In the future if you could share new test cases as patches to the >>relevant test file (i.e., using git format-patch) that would be >>ideal > > That was my intention, after receiving a "nihil obstat" from you, or some > suggestions for changes. > > Anyway, next time, I'll directly send a properly formatted patch. > Wonderful. Thanks again -- Eric > > Thanks. > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] Multiple results blocks for the same source code
Hi Eric, Eric Schulte wrote: > I could not reproduce the error you describe, and your test case passes > for me. I have added your test case to testing/test-ob.el however so it > should protect from this error in the future. I can't reproduce it anymore right now. But the goal was to have a fuse against that for the future, yes. > You could try running the test suite in batch mode (which will not load > your configuration) and see if the test still fails for you. If not > then the problem is probably due to either something in your config. When I get back in a "broken" config such as the one described here, I'll do it. > Thanks for the test case! -- Eric > > ps. the only comments I have on the test itself are > 1. The initial placement of the point is described in the >documentation string for the `org-test-with-temp-text' function That's very clear, yes, but for the case where we don't have the string "" in the initial text. Is point at the end of the string, then? I guess so. But my question was more about... >> (org-babel-execute-src-block) ;; second code block execution >> ;; where is point (supposed to be)? ... the position of point after `org-babel-execute-src-block'. > 2. In the future if you could share new test cases as patches to the >relevant test file (i.e., using git format-patch) that would be >ideal That was my intention, after receiving a "nihil obstat" from you, or some suggestions for changes. Anyway, next time, I'll directly send a properly formatted patch. Thanks. Best regards, Seb -- Sebastien Vauban
[O] [babel] bug in ob-latex - :exports argument is not honored when it is set as a header property
Dear list I believe I have found a bug in the export of latex source blocks (to HTML, ascii, etc) when ob-latex.el has been loaded. In summary, setting the :exports argument as a header property fails to override the default value in org-babel-default-header-args:latex Please see the attached org file for a demonstration. Cheers Will -- Dr William Henney, Centro de Radioastronomía y Astrofísica, Universidad Nacional Autónoma de México, Campus Morelia test-export-latex-src-block.org Description: Binary data
Re: [O] bug: org-mouse broken
Hi Nicolas On Fri, Sep 23, 2011 at 18:45, Nicolas Goaziou wrote: > Michael Brand writes: >> There is an issue with org-feed. The backtrace is attached. I hope >> this is enough to reproduce. > > Fixed. Here comes the new patch. > > Thanks again. I can confirm that the issue is resolved. Thank you. Michael
[O] "Edward N. Lewis": RE: Bug: File Links [6.33x]
[posted at Edward's request] --- Forwarded Message Date:Thu, 22 Sep 2011 22:36:29 -0400 From:"Edward N. Lewis" To: Subject: RE: [O] Bug: File Links [6.33x] Please disregard my earlier e-mail earlier this evening. I found a solution for the display issue. change the line in /etc/mailcap that reads 'application/pdf; /usr/bin/xdg-open %s' to read 'application/pdf; /usr/bin/evince %s' Please post this thread in the event that it helps someone else. Needless to say, I use GNU/Linux (Fedora 15) Thanks so much for your help. Edward N. Lewis, PE PO Box 611 Worthington, MA 01098-0611 USA +1 413-238-0109 ed.le...@enlewis.com - -Original Message- From: n...@dokosmarshall.org [mailto:n...@dokosmarshall.org] On Behalf Of Nick Dokos Sent: Thursday, September 22, 2011 6:07 PM To: Edward N. Lewis Cc: emacs-orgmode@gnu.org; nicholas.do...@hp.com Subject: Re: [O] Bug: File Links [6.33x] Edward N. Lewis wrote: > Links to external pdf files do not work in org-mode. Links do not > export properly into PDF files. Links to web addresses and other file > types such as text files work fine, however. > > To reproduce: create a link in your org file in any form, e.g. > [[file:/full_path/whatever.pdf]], > [[file:/full_path/whatever.pdf][Label for file]], file:whatever.pdf. > > 1) The link will not work from within org-mode. > 2) The link will not be properly formatted when viewed in a PDF viewer > such as Adobe Acrobat Professional. To make the link work, the link's > properties have to be manually edited from within Adobe Acrobat/ > > Emacs : GNU Emacs 23.2.1 (i386-redhat-linux-gnu, GTK+ Version 2.24.4) > of 2011-05-23 on x86-05.phx2.fedoraproject.org > Package: Org-mode version 6.33x > I cannot reproduce this with Org-mode version 7.7 (release_7.7.311.g0c099), so I'd suspect your 6.33 (which is quite old, but unfortunately still ships with older versions of emacs). If you are at all serious about using org-mode, you probably need to install the 7.7 release (or if you are willing to live on the edge, clone the git repository and enjoy all the up-to-date features - and some breakages, but ime, breakages get fixed quickly). Nick --- End of Forwarded Message
Re: [O] bug: org-mouse broken
Hello, Michael Brand writes: > There is an issue with org-feed. The backtrace is attached. I hope > this is enough to reproduce. Fixed. Here comes the new patch. Thanks again. Regards, -- Nicolas Goaziou >From 1f8df0573427f02f0e0553bcfa8bec10ac097188 Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou Date: Thu, 25 Aug 2011 01:58:29 +0200 Subject: [PATCH] Provide more consistent regexps for headlines * lisp/org-agenda.el (org-search-view): Simplify regexp. (org-agenda-get-todos): Use new format string. * lisp/org-archive.el (org-archive-all-done): Simplify regexp. * lisp/org-ascii.el (org-export-as-ascii): More accurate regexp. * lisp/org-colview-xemacs.el (org-columns-capture-view): Use new format string and new string. * lisp/org-colview.el (org-columns-capture-view): Use new format string and new string. * lisp/org-docbook.el (org-export-as-docbook): More accurate regexp. Also use new regexp to match generic headlines. * lisp/org-exp.el (org-export-protect-quoted-subtrees): More accurate regexp. Also use new regexp to match generic headlines. * lisp/org-html.el (org-export-as-html): More accurate regexp. Also use new regexp to match generic headlines. * lisp/org-mouse.el (org-mouse-match-todo-keyword): Removed unused and now erroneous function. * lisp/org.el (org-heading-regexp, org-heading-keyword-regexp-format): New variables. (org-set-regexps-and-options): Create regexps according to the following rule: use spaces only to separate elements from an headline, while allowing mixed tabs and spaces for any indentation job. (org-nl-done-regexp, org-looking-at-done-regexp): Removed variables. (org-set-font-lock-defaults): Fontify again headlines with a keyword and no other text. Use new format strings. (org-get-heading, org-toggle-comment, org-prepare-agenda-buffers, org-toggle-fixed-width-section): Use new format string. (org-todo): More accurate regexps. (org-point-at-end-of-empty-headline): Simplify regexp. (org-insert-heading): Headline can sometimes be nil. This patch attempts to reduce the number of hard-coded headlines, by providing two format strings and one generic string to cover most of the cases of headline construction. --- lisp/org-agenda.el | 35 + lisp/org-archive.el|2 +- lisp/org-ascii.el |4 +- lisp/org-colview-xemacs.el |5 +- lisp/org-colview.el|5 +- lisp/org-docbook.el|7 +- lisp/org-exp.el|6 +- lisp/org-html.el |7 +- lisp/org-mouse.el |7 -- lisp/org.el| 189 +--- 10 files changed, 147 insertions(+), 120 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index b1fa5f5..28c5d44 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -3868,7 +3868,7 @@ in `org-agenda-text-search-extra-files'." (if (not regexps+) (setq regexp org-outline-regexp-bol) (setq regexp (pop regexps+)) - (if hdl-only (setq regexp (concat "^" org-outline-regexp ".*?" + (if hdl-only (setq regexp (concat org-outline-regexp-bol " .*?" regexp (setq files (org-agenda-files nil 'ifmode)) (when (eq (car org-agenda-text-search-extra-files) 'agenda-archives) @@ -4574,18 +4574,21 @@ the documentation of `org-diary'." 'help-echo (format "mouse-2 or RET jump to org file %s" (abbreviate-file-name buffer-file-name - (regexp (concat "^\\*+[ \t]+\\(" - (if org-select-this-todo-keyword - (if (equal org-select-this-todo-keyword "*") - org-todo-regexp - (concat "\\<\\(" - (mapconcat 'identity - (org-split-string - org-select-this-todo-keyword "|") "\\|") - "\\)\\>")) - org-not-done-regexp) - "[^\n\r]*\\)")) - marker priority category category-pos tags todo-state ee txt beg end) + (regexp (format org-heading-keyword-regexp-format + (cond + ((and org-select-this-todo-keyword +(equal org-select-this-todo-keyword "*")) + org-todo-regexp) + (org-select-this-todo-keyword + (concat "\\(" + (mapconcat 'identity + (org-split-string + org-select-this-todo-keyword + "|") + "\\|") "\\)")) + (t org-not-done-regexp + marker priority category tags todo-state + ee txt beg end) (goto-char (point-min)) (while (re-search-forward regexp nil t) (catch :skip @@ -4597,11 +4600,11 @@ the documentation of `org-diary'." (goto-char (1+ beg)) (or org-agenda-todo-list-sublevels (org-end-of-subtree 'invisible)) (throw :skip nil))) - (goto-char (match-beginning 1)) + (goto-char (match-beginning 2)) (setq marker (org-agenda-new-marker (match-beginning 0)) category (org-get-category) category-pos (get-text-property (point) 'org-category-position) - txt (match-string 1) + txt (match-string 2) tags (org-get-tags-at (point)) txt (org-format-agenda-ite
Re: [O] [babel] BUG in :session
Hi Eric Eric Schulte writes: > Martyn Jago writes: > >> Hi Eric >> >> Eric Schulte writes: >> >>> Hi Martyn, >>> >>> I've just pushed up what will hopefully be a more general solution. >>> Basically, language-specific test files can now signal errors if they >>> have unmet dependencies. These are then intercepted by `org-test-load' >>> and the file is not added to the test suite. Hopefully this will allow >>> language-specific tests to be written without breaking the config-less >>> test suite. >>> >>> See the top of test-ob-R.el for an example usage. >>> >>> Cheers -- Eric >> >> Unfortunately this is still broken for me. Given the exe exists but the >> feature doesn't (ie no personal config), the following line causes the >> error `peculiar error' ! >> >>(signal 'org-test-lib-not-found "ess")) >> > > Oh, > > I forgot to update the types of errors that I am catching after adding a > new error type for missing libraries (e.g., ess). This should now be > fixed. > There still seems to be a problem with test-ob-R - same error "peculiar error". >> >> I've published the output of my test server so you can see the >> backtrace. It is at http://martynjago.com: >> > > Very cool, > > Does this page refresh after every git commit? Yes - the repository is polled once per minute and a git pull + make clean / install etc + run tests is performed, so the test server now reflects your latest commit. > > Is there a way to see the output of the test run, all I can find is the > command which is executed. Yes - just click on the org-mode_Emacs_24 (title) link and then on the build log link. There isn't much of a log on the failing tests since the entire test run is broken by the signal. You can checkout the build log for my-org-mode-dev to see what you should get. Best, Martyn > > Cheers -- Eric > >> >> Best, Martyn >> >> >> [...] >> >> >>
Re: [O] [babel] Multiple results blocks for the same source code
Hi Seb, I could not reproduce the error you describe, and your test case passes for me. I have added your test case to testing/test-ob.el however so it should protect from this error in the future. You could try running the test suite in batch mode (which will not load your configuration) and see if the test still fails for you. If not then the problem is probably due to either something in your config. Thanks for the test case! -- Eric ps. the only comments I have on the test itself are 1. The initial placement of the point is described in the documentation string for the `org-test-with-temp-text' function 2. In the future if you could share new test cases as patches to the relevant test file (i.e., using git format-patch) that would be ideal "Sebastien Vauban" writes: > #+TITLE: Multiple results blocks for the same source code > #+AUTHOR:Seb Vauban > #+DATE: 2011-09-23 > #+LANGUAGE: en > > * Bug > > When evaluating multiple times the following code, we get multiple =results= > blocks. > > #+begin_src sh > echo Hello > #+end_src > > #+results: > : Hello > > #+results: > : Hello > > * ERT Test Case > > #+begin_src emacs-lisp > (ert-deftest test-org-babel/just-one-results-block () > "Test that evaluating two times the same code block does not result in a > duplicate results block." > (org-test-with-temp-text "#+begin_src sh\necho Hello\n#+end_src\n" > (org-babel-execute-src-block) > (org-babel-execute-src-block) ;; second code block execution > ;; where is point (supposed to be)? > (goto-char (point-min)) > (should (search-forward "Hello")) ;; the string inside the source code > block > (should (search-forward "Hello")) ;; the same string in the (first?) > results block > (should-error (search-forward "Hello" > #+end_src > > * Extra context > > This problem appeared after having executed sh code blocks (calling Ledger) > which failed -- for some reason still to be studied. > > After an Emacs restart, I can't reproduce this anymore. So, not really fixed, > but not there systematically either... > > Status is unreproducible right now, but I guess the above test case can > already be added. Please comment on it, for me to progress... > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] BUG in :session
Martyn Jago writes: > Hi Eric > > Eric Schulte writes: > >> Hi Martyn, >> >> I've just pushed up what will hopefully be a more general solution. >> Basically, language-specific test files can now signal errors if they >> have unmet dependencies. These are then intercepted by `org-test-load' >> and the file is not added to the test suite. Hopefully this will allow >> language-specific tests to be written without breaking the config-less >> test suite. >> >> See the top of test-ob-R.el for an example usage. >> >> Cheers -- Eric > > Unfortunately this is still broken for me. Given the exe exists but the > feature doesn't (ie no personal config), the following line causes the > error `peculiar error' ! > >(signal 'org-test-lib-not-found "ess")) > Oh, I forgot to update the types of errors that I am catching after adding a new error type for missing libraries (e.g., ess). This should now be fixed. > > I've published the output of my test server so you can see the > backtrace. It is at http://martynjago.com: > Very cool, Does this page refresh after every git commit? Is there a way to see the output of the test run, all I can find is the command which is executed. Cheers -- Eric > > Best, Martyn > > > [...] > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] [babel] Multiple results blocks for the same source code
#+TITLE: Multiple results blocks for the same source code #+AUTHOR:Seb Vauban #+DATE: 2011-09-23 #+LANGUAGE: en * Bug When evaluating multiple times the following code, we get multiple =results= blocks. #+begin_src sh echo Hello #+end_src #+results: : Hello #+results: : Hello * ERT Test Case #+begin_src emacs-lisp (ert-deftest test-org-babel/just-one-results-block () "Test that evaluating two times the same code block does not result in a duplicate results block." (org-test-with-temp-text "#+begin_src sh\necho Hello\n#+end_src\n" (org-babel-execute-src-block) (org-babel-execute-src-block) ;; second code block execution ;; where is point (supposed to be)? (goto-char (point-min)) (should (search-forward "Hello")) ;; the string inside the source code block (should (search-forward "Hello")) ;; the same string in the (first?) results block (should-error (search-forward "Hello" #+end_src * Extra context This problem appeared after having executed sh code blocks (calling Ledger) which failed -- for some reason still to be studied. After an Emacs restart, I can't reproduce this anymore. So, not really fixed, but not there systematically either... Status is unreproducible right now, but I guess the above test case can already be added. Please comment on it, for me to progress... Best regards, Seb -- Sebastien Vauban
Re: [O] [babel] BUG in :session
Hi Eric Eric Schulte writes: > Hi Martyn, > > I've just pushed up what will hopefully be a more general solution. > Basically, language-specific test files can now signal errors if they > have unmet dependencies. These are then intercepted by `org-test-load' > and the file is not added to the test suite. Hopefully this will allow > language-specific tests to be written without breaking the config-less > test suite. > > See the top of test-ob-R.el for an example usage. > > Cheers -- Eric Unfortunately this is still broken for me. Given the exe exists but the feature doesn't (ie no personal config), the following line causes the error `peculiar error' ! --8<---cut here---start->8--- (signal 'org-test-lib-not-found "ess")) --8<---cut here---end--->8--- I've published the output of my test server so you can see the backtrace. It is at http://martynjago.com: Best, Martyn [...]
Re: [O] how to both :body-only t and :table-of-contents t
Dear Jan On Fri, Sep 23, 2011 at 3:51 AM, Jan Böcker wrote: > > Hi Jay, > > I faced the same problem about a year ago. > See this thread in the mailing list archive: > > http://thread.gmane.org/gmane.emacs.orgmode/24227 > > The HTML exporter will refuse to include a TOC if body-only is t; the > atom exporter and a "send HTML messages with Wanderlust" hack relied on > that behaviour, which is why this was not changed in the official Org > repository. > > You can either apply the one-line patch I included in the linked thread > or ask Ian Barton about his solution using jQuery he mentioned at the > end of that thread. > > HTH, > Jan > Thanks; I was afraid it was going to be something like that, and am appreciative that I don't need to reinvent this particular wheel. My previous workaround was to export once with TOC, copy-paste the TOC bit to the org-file in a #+BEGIN_HTML block, then export again with :body-only t. But each run takes a couple of hours (another question for another day), which is a pain, and not convenient should the document structure change. I noticed in the thread that Carsten mentioned writing a "hook" that strips the other stuff. Don't have much experience writing hooks, but there should be a way to write a custom publishing function just like the current one which strips everything but the TOC. I'll use your patch while I continue thinking about it. Thanks again. Jay
Re: [O] bug: org-mouse broken
Hi Nicolas There is an issue with org-feed. The backtrace is attached. I hope this is enough to reproduce: 1) /tmp/feed.org: #+begin_src org ,-*- coding: utf-8-unix -*- ,#+DRAWERS: FEEDSTATUS ,* podcast , :FEEDSTATUS: , :END: #+end_src 2) (setq org-feed-alist '(("podcast" "http://pod.drs.ch/sounds_mpx.xml"; "/tmp/feed.org" "podcast"))) 3) (org-feed-update-all) 4) hit SPC once to workaround some non-related org-feed bug (?) that I ignore Michael On Thu, Sep 22, 2011 at 20:25, Nicolas Goaziou wrote: > Michael Brand writes: > >> The file name 0001-Provide-more-consistent-regexps-for-headlines.patch >> made me curious and I take the opportunity to support such an effort >> by testing this patch on release_7.7-316-gdecd722. > > Great! Thank you for testing it. > >> I found the issue that "* TODO task" setting to done with "C-c C-t d" >> leads to "* DONE TODO task". > > Indeed. This is fixed in the following patch. Please disregard the > previous one. Debugger entered--Lisp error: (error "Wrong position") signal(error ("Wrong position")) error("Wrong position") (if (looking-at org-complex-heading-regexp) nil (error "Wrong position")) (unless (looking-at org-complex-heading-regexp) (error "Wrong position")) (save-excursion (goto-char pos) (unless (looking-at org-complex-heading-regexp) (error "Wrong position")) (setq level (org-get-valid-level ... 1)) (org-end-of-subtree t t) (skip-chars-backward " \n") (beginning-of-line 2) (setq pos (point)) (while (setq entry ...) (org-paste-subtree level entry ...)) (org-mark-ring-push pos)) (let (entry level) (save-excursion (goto-char pos) (unless ... ...) (setq level ...) (org-end-of-subtree t t) (skip-chars-backward " \n") (beginning-of-line 2) (setq pos ...) (while ... ...) (org-mark-ring-push pos))) org-feed-add-items(1 ("* Sounds!-Podcast - Vintage-Elektronik: das Apparat Organ Quartet aus Island\n [2011-09-15 Thu 23:55]\n Vier Keyboarder und ein Schlagzeuger bilden zusammen das Apparat Organ Quartet. Die Band aus Island verzichtet auf moderne Computer und Sequencer, verwendet dafür analoge Synthesizer, Farfisa-Orgeln und Casio-Keyboards. Ihr neues Album «Polyfonia» tönt ein wenig nach Kraftwerk, Game-Soundtracks aus den 80er und Prog-Rock aus den 90er-Jahren.\n [[http://pod.drs.ch/mp3/sounds/sounds_201109152355_10193717.mp3]]\n"; "* Die belgischen Indie-Rock-Urgesteine mit neuer CD\n [2011-09-19 Mon 23:55]\n dEUS, die belgische Indie-Rock-Institution, feiern in diesem Jahr ihr 20-jähriges Jubiläum. Mit den Alben \"Worst Case Scenario (1994) „In A Bar, Under The Sea\"(1996) und „The Ideal Crash\" (1999) wurden sie auch international zu einer festen Grösse. Übriggeblieben Tom Barman und der Keyboarder Klaas Janzoons. Waren die Vielschichtig und trotzdem geradlinig präsentiert sich die neue, 6.CD „Keep You Close „. Verzichtet wurde auf elektronische Spielereien („Vintage Point\"), Dancefloor-orientierte Beatlastigkeit („The Architect\") oder Zerfahrenheit (\"Pocket Revolution\"). Angesagt ist entspannter Pop-Rock mit Klavier, Gitarre Streicher und Bläser. von der Urbesetzung sind allerdings nur noch der Sänger und Gitarrist Tom Barman und der Keyboarder Klaas Janzoons.\n [[http://pod.drs.ch/mp3/sounds/sounds_201109192355_10194329.mp3]]\n"; "* Sounds!-Podcast - Mit Düsi durch die Plattenläden Londons\n [2011-09-20 Tue 23:55]\n Unser Mann in London, Hanspeter Düsi Künzler , stöberte einmal mehr in den Regalen der Plattenläden in der englischen Hauptstadt. Gefunden hat er ein paar heisse, bei uns noch nicht veröffentlichten Herbstneuheiten auf CD und Vinyl. Zu hören sind u.a. Duke Spirit, Veronica Falls, Real Tuesday Weld oder Peggy Sue.\n [[http://pod.drs.ch/mp3/sounds/sounds_201109202355_10194271.mp3]]\n"; "* Podcast: Charmanter Folk-Pop vom Duo Slow Club aus Sheffield\n [2011-09-21 Wed 23:55]\n Kennengelernt haben sich Rebeccca Taylor und Charles Watson während der Schulzeit in Sheffield. Seit 2006 machen sie unter dem Name Slow Club gemeinsam Musik. Ihr Debut-Album «Yeah So» war geprägt von einer charmanten Mischung aus Folk und Pop , beschränkt auf Gesang und Gitarre. Auf der neuen CD «Paradise» kommen noch Geige, Piano und E-Gitarre hinzu. Herzschmerz, Liebe und Tod sind die zentralen Themen. \n [[http://pod.drs.ch/mp3/sounds/sounds_201109212355_10194350.mp3]]\n"; "* Sounds!-Podcast - Interview mit St. Vincent\n [2011-09-22 Thu 23:55]\n Hinter dem Namen St. Vincent steckt die texanische Singer/Songwriterin und Multiinstrumentalistin Annie Clark. Im Sounds!-Interview spricht sie u.a. über ihre Affinität zu Jazz (John Coltrane, Charlie Mingus), die Bedeutung von Tom Waits oder ihre ersten musikalischen Gehversuche auf dem Computer. Ausserdem verrät sie uns ihre literarischen Vorlieben und gibt Auskunft über die neue CD «Strange Mercy».\n [[http://pod.drs.ch/mp3/sounds/sounds_201109222355_10194051.mp3]]\n";)) (progn (if new-han
Re: [O] how to both :body-only t and :table-of-contents t
On 09/21/2011 09:40 PM, G. Jay Kerns wrote: > In other words, it looks like I am obliged to :body-only t which cuts > out header/footer/TOC or I can NOT do :body-only t which will give me > the TOC plus a bunch of extra stuff. > > My question: is it possible to do what I want? Is there some sort of > YAML {{ page.toc }} that I'm missing somewhere, or is there some > combination of publishing options that I've missed that will export an > org file to an HTML file that looks like this: Hi Jay, I faced the same problem about a year ago. See this thread in the mailing list archive: http://thread.gmane.org/gmane.emacs.orgmode/24227 The HTML exporter will refuse to include a TOC if body-only is t; the atom exporter and a "send HTML messages with Wanderlust" hack relied on that behaviour, which is why this was not changed in the official Org repository. You can either apply the one-line patch I included in the linked thread or ask Ian Barton about his solution using jQuery he mentioned at the end of that thread. HTH, Jan