[O] Mac OS Alias file links
I use links to files quite often in Org Mode. Either by C-l file: or drag-and-drop (with smart-dnd). But when files move, the links break. BibDesk solves this by storing Mac OS Aliases to files. Then if files move, the alias still works. BibDesk actually stores more: The Bdsk-File entries store Mac OS aliases, which contain a file ID and absolute path. Bdsk-File entries also store a relative path, which is used if the alias is broken. Is there a way to add this feature to Org Mode? Yes, obviously, since this is emacs and Org Mode. But has anyone already done this? Any advice where to start? Thanks, -k.
Re: [O] Maintainer change on May 1st
Carsten Dominik carsten.domi...@gmail.com writes: Hi everyone, per May 1st, I would like to swing the official maintainership back to Bastien, who has agreed to this change. This really only means putting facts onto websites, because Bastien has in effect been doing this job all the time - I have unfortunately been unable to make time free to contribute here in any meaningful way, for which I apologise. I trust that an overwhelming majority of you will have not objections to this step To make this overwhelming majority not to silent, I have no objections at all. Thanks for all the hard work you and Bastien have put into org. Rainer Regards - Carsten -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 pgpzj7aXb9Yih.pgp Description: PGP signature
Re: [O] sending emails from org
Thorsten Jolitz tjol...@gmail.com writes: Sharon Kimble boudic...@talktalk.net writes: Rainer M Krug rai...@krugs.de writes: Hi I have two questions concerning sending subtrees as emails. 1) Which properties are supported by org-mime - I could not find a list or an example of an email from org. 2) I am using gnus and have the following hooks to add automatic signing of emails: , | #+begin_src emacs-lisp | (add-hook 'gnus-message-setup-hook 'mml-secure-message-sign-pgpmime) | (add-hook 'message-s'etup-hook 'mml-secure-message-sign-pgpmime) | #+end_src ` These hooks are not called when composing emails in org. Is this on purpose, or to gnus specific? I've found that I have to have some commands both in '.emacs' and in .gnus', and I use the same code to sign my emails in gnus. I've never tried writing an email in org-mode, but if I was I'd tend to use a snippet from YASnippet', or write my own for it. I've always believed in writing emails in gnus, and using org-mode for TODOs, documents, etc. You probably could have the best of both worlds using outorg.el, which works out of the box with message-mode (although I never tried these signing functions). 1. get outshine.el and outorg.el (github or melpa) 2. before loading outline-mode: define outline-minor-mode prefix in .emacs: #+begin_src emacs-lisp ;; must be set before outline is loaded (defvar outline-minor-mode-prefix \M-#) #+end_src or maybe \C-c. 3. put this in your .emacs: #+begin_src emacs-lisp (require 'outshine) ; has soft dependency to 'outorg (add-hook 'outline-minor-mode-hook 'outshine-hook-function) (add-hook 'message-mode-hook 'outline-minor-mode) #+end_src 4. write your emails/posts in message-mode, and switch to full Org-mode with e.g. M-# M-# (M-x outorg-edit-as-org). When there are already Org-mode headlines in the message mode buffer, use C-u M-# M-# to edit the whole buffer in Org-mode, and M-# M-# to edit the subtree at point. Use M-# (outorg-copy-edits-and-exit) when you are done in the \*outorg-edit-buffer\*. There are several prefix args that allow you to (temporarilly or persistently) insert a template for export options: #+begin_quote outorg-edit-as-org is an interactive Lisp function in `outorg.el'. (outorg-edit-as-org optional ARG) Convert and copy to temporary Org buffer With ARG, act conditional on the raw value of ARG: | prefix | raw | action 1 | action 2 | |+-+---+--| | C-u| (4) | edit-whole-buffer | --- | | C-1| 1 | edit-whole-buffer | insert default export-template | | C-2| 2 | edit-whole-buffer | ask user for template-file | | C-3| 3 | edit-whole-buffer | insert and keep default template | | C-4| 4 | edit-whole-buffer | insert and keep template-file| #+end_quote As a little demonstration, I switch to outorg, and insert the following code-block. Doing C-c C-c in the block suffices to attach the ASCII version of the email. #+begin_src emacs-lisp :results value (org-export-as 'ascii) #+end_src #+results: ___ Thorsten Jolitz tjol...@gmail.com ___ 1 --text follows this line-- Sharon Kimble boudic...@talktalk.net writes: Rainer M Krug rai...@krugs.de writes: Hi I have two questions concerning sending subtrees as emails.1) Which properties are supported by org-mime - I could not find a list or an example of an email from org.2) I am using gnus and have the following hooks to add automatic signing of emails: , | #+begin_src emacs-lisp | (add-hook 'gnus-message-setup-hook 'mml-secure-message-sign-pgpmime) | (add-hook 'message-s'etup-hook 'mml-secure-message-sign-pgpmime) | #+end_src ` These hooks are not called when composing emails in org. Is this on purpose, or to gnus specific? I've found that I have to have some commands both in '.emacs' and in .gnus', and I use the same code to sign my emails in gnus. I've never tried writing an email in org-mode, but if I was I'd tend to use a snippet from YASnippet', or write my own for it. I've always believed in writing emails in gnus, and using org-mode for TODOs, documents, etc. You probably could have the best of both worlds using outorg.el, which works out of the box with message-mode (although I never tried these signing functions). 1. get outshine.el and outorg.el (github or melpa) 2. before loading outline-mode: define outline-minor-mode prefix in .emacs: , | ;; must be set before outline is loaded | (defvar outline-minor-mode-prefix \M-#) ` or maybe \C-c. 1. put this in your .emacs: , |
Re: [O] sending emails from org
Thorsten Jolitz tjol...@gmail.com writes: Sharon Kimble boudic...@talktalk.net writes: Rainer M Krug rai...@krugs.de writes: Hi I have two questions concerning sending subtrees as emails. 1) Which properties are supported by org-mime - I could not find a list or an example of an email from org. 2) I am using gnus and have the following hooks to add automatic signing of emails: , | #+begin_src emacs-lisp | (add-hook 'gnus-message-setup-hook 'mml-secure-message-sign-pgpmime) | (add-hook 'message-s'etup-hook 'mml-secure-message-sign-pgpmime) | #+end_src ` These hooks are not called when composing emails in org. Is this on purpose, or to gnus specific? I've found that I have to have some commands both in '.emacs' and in .gnus', and I use the same code to sign my emails in gnus. I've never tried writing an email in org-mode, but if I was I'd tend to use a snippet from YASnippet', or write my own for it. I've always believed in writing emails in gnus, and using org-mode for TODOs, documents, etc. You probably could have the best of both worlds using outorg.el, which works out of the box with message-mode (although I never tried these signing functions). 1. get outshine.el and outorg.el (github or melpa) 2. before loading outline-mode: define outline-minor-mode prefix in .emacs: #+begin_src emacs-lisp ;; must be set before outline is loaded (defvar outline-minor-mode-prefix \M-#) #+end_src or maybe \C-c. 3. put this in your .emacs: #+begin_src emacs-lisp (require 'outshine) ; has soft dependency to 'outorg (add-hook 'outline-minor-mode-hook 'outshine-hook-function) (add-hook 'message-mode-hook 'outline-minor-mode) #+end_src 4. write your emails/posts in message-mode, and switch to full Org-mode with e.g. M-# M-# (M-x outorg-edit-as-org). When there are already Org-mode headlines in the message mode buffer, use C-u M-# M-# to edit the whole buffer in Org-mode, and M-# M-# to edit the subtree at point. Use M-# (outorg-copy-edits-and-exit) when you are done in the \*outorg-edit-buffer\*. There are several prefix args that allow you to (temporarilly or persistently) insert a template for export options: #+begin_quote outorg-edit-as-org is an interactive Lisp function in `outorg.el'. (outorg-edit-as-org optional ARG) Convert and copy to temporary Org buffer With ARG, act conditional on the raw value of ARG: | prefix | raw | action 1 | action 2 | |+-+---+--| | C-u| (4) | edit-whole-buffer | --- | | C-1| 1 | edit-whole-buffer | insert default export-template | | C-2| 2 | edit-whole-buffer | ask user for template-file | | C-3| 3 | edit-whole-buffer | insert and keep default template | | C-4| 4 | edit-whole-buffer | insert and keep template-file| #+end_quote As a little demonstration, I switch to outorg, and insert the following code-block. Doing C-c C-c in the block suffices to attach the ASCII version of the email. #+begin_src emacs-lisp :results value (org-export-as 'ascii) #+end_src #+results: ___ Thorsten Jolitz tjol...@gmail.com ___ 1 --text follows this line-- Sharon Kimble boudic...@talktalk.net writes: Rainer M Krug rai...@krugs.de writes: Hi I have two questions concerning sending subtrees as emails.1) Which properties are supported by org-mime - I could not find a list or an example of an email from org.2) I am using gnus and have the following hooks to add automatic signing of emails: , | #+begin_src emacs-lisp | (add-hook 'gnus-message-setup-hook 'mml-secure-message-sign-pgpmime) | (add-hook 'message-s'etup-hook 'mml-secure-message-sign-pgpmime) | #+end_src ` These hooks are not called when composing emails in org. Is this on purpose, or to gnus specific? I've found that I have to have some commands both in '.emacs' and in .gnus', and I use the same code to sign my emails in gnus. I've never tried writing an email in org-mode, but if I was I'd tend to use a snippet from YASnippet', or write my own for it. I've always believed in writing emails in gnus, and using org-mode for TODOs, documents, etc. You probably could have the best of both worlds using outorg.el, which works out of the box with message-mode (although I never tried these signing functions). 1. get outshine.el and outorg.el (github or melpa) 2. before loading outline-mode: define outline-minor-mode prefix in .emacs: , | ;; must be set before outline is loaded | (defvar outline-minor-mode-prefix \M-#) ` or maybe \C-c. 1. put this in your .emacs: , |
Re: [O] Maintainer change on May 1st
Rainer M Krug rai...@krugs.de writes: Carsten Dominik carsten.domi...@gmail.com writes: per May 1st, I would like to swing the official maintainership back to Bastien, who has agreed to this change. To make this overwhelming majority not to silent, I have no objections at all. Thanks for all the hard work you and Bastien have put into org. 1+ -- cheers, Thorsten
Re: [O] Maintainer change on May 1st
Rainer M Krug rai...@krugs.de writes: Carsten Dominik carsten.domi...@gmail.com writes: Hi everyone, per May 1st, I would like to swing the official maintainership back to Bastien, who has agreed to this change. This really only means putting facts onto websites, because Bastien has in effect been doing this job all the time - I have unfortunately been unable to make time free to contribute here in any meaningful way, for which I apologise. I trust that an overwhelming majority of you will have not objections to this step To make this overwhelming majority not to silent, I have no objections at all. Thanks for all the hard work you and Bastien have put into org. Another big thank you from a not-so-silent user! atb Glyn
[O] [BUG] 'Args out of range' when exporting with reboxes
Hi List, I like to use rebox2 and put boxes in emails and source-file comment-sections, but when I use outorg on such an message-mode or elisp buffer and try to export it, I always get 'Args out of range' errors: ,, ,| org-element--parse-objects: Args out of range: 315, 316 ,` I have to add commas in front to make export work, but this does not look that nice anymore in the original buffer. E.g. evaluating the following block in outorg works only after adding the commas to the rebox above, and the output does not look that great either. #+begin_src emacs-lisp :results value replace (org-export-as 'ascii) #+end_src #+results: _ 697 Thorsten Jolitz _ Table of Contents _ 1 --text follows this line-- 1 --text follows this line-- Hi List, I like to use rebox2 and put boxes like this in emails or source-file comment-sections, but when I use outorg on such an message-mode or elisp buffer and try to export it, I always get 'Args out of range' errors: ,, ,| org-element--parse-objects: Args out of range: 315, 316 ,` I have to add commas in front to make export work, but this does not look nice anymore in the original buffer. E.g. evaluating this block in outorg works only after adding the commas to the rebox above, and the output does not look that great either. , | (org-export-as 'ascii) ` -- cheers, Thorsten -- cheers, Thorsten
Re: [O] Add-on: Github Flavored Markdown exporter
Thorsten Jolitz tjol...@gmail.com writes: Lars Tveito larst...@student.matnat.uio.no writes: Hi! I have written an exporter for Github Flavored Markdown, which is a derived back-end from the Markdown (vanilla) exporter. It adds Github-style src-blocks, strike-through and table of contents. Your library works really good, thanks. I would recommend adding it to /contrib. I used it to create new README.md files for all three libraries navi-mode.el, outorg.el and outshine.el, you can find the repos on github.com/tj64 if you want to take a look. I like the idea very much to write this documentation stuff once in one place and then reuse it in all other places. Therefore when I write a source file, I use outorg to write a more or less sophisticated comment header for that file. This is then automatically converted back to a programming language comment section, but I can always convert it back to Org-mode. From the outorg-edit-buffer, I can then export it to html, latex, ascii and now to markdown-github-flavor too, whats nice. I use a little trick to do this: I narrow the buffer to the first 1st level headline, and then use ,-- | C-1 M-# M-# | C-u 1 M-# M-# `-- to temporarily insert the default export template, or ,-- | C-3 M-# M-# | C-u 3 M-# M-# `-- to temporarily insert a custom export template from a file. A few questions and remarks: - I get the best results with just using example blocks - is it supposed to work with source-blocks and other blocks too? - Just like the Org exporter in general, it does not know how to deal with boxes made with rebox2.el, so I replaced them with example blocks. - What about numbered lists with longer text/blocks as item content - is the item numbering supposed to work? -- cheers, Thorsten
[O] Altering effect of deadline on priority calculation
Hi, I would like to make deadlines have a larger impact on priority calculation than scheduled date, but I can't figure out how to extract how many days before or past deadline from an agenda entry. I would also like to extract how many days overdue a task is from its scheduled date. Is there a function that gives me this information easily? Alternatively, can anybody point me to where priority is increased by 1 for each day late? Thanks - I've looked and looked. Inanna
Re: [O] Agenda items refer to the wrong headline
Dear all, This (in my opinion) serious bug still appears when using the last ELPA version of Org (8.2.5h-98-g0820d0-elpa @ ~/.emacs.d/elpa/org-20140407/) on Windows with GNU Emacs 24.3.1. I also tried that on my Debian system, with GNU Emacs 24.3.1. No problem with Org 7.9.3, but the same bug appears as soon as I upgrade Org to the last ELPA version. Again, nothing loaded except vanilla Emacs. FC On Sun, Apr 6, 2014 at 6:23 AM, Fletcher Charest fletcher.char...@gmail.com wrote: Dear all, I am confronted to a weird issue with the agenda. I would like to know if you can reproduce this bug. First of all, my emacs-version is: GNU Emacs 24.3.1 (i386-mingw-nt5.1.2600) of 2013-03-17 on MARVIN I installed Org using ELPA (org repository), my org-version is: Org-mode version 8.2.5h (8.2.5h-94-g91175a-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20140331/) For this test, Org was the only package installed outside vanilla Emacs packages. I have no problem with the version of Org bundled with my Emacs (which is Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ c:/Program Files/Emacs 24.3/lisp/org/). I do not load my init.el file. For the test I used a simple Org file: * TODO task 1:pro: SCHEDULED: 2014-04-01 mar. * TODO task 2:perso: SCHEDULED: 2014-04-02 mer. Then, I displayed the agenda for this file, and filtered it for the 'perso' tag using '/'. I attached the output for reference. The problem is that some tasks in the agenda refers to the wrong headlines in the main file. This is more obvious when activating follow mode: for example, if I put the cursor on the line marked '1' in the attached file, it refers to line '2' in the main file, which is the wrong line. This is obviously a bug, and of course very problematic. Can you reproduce this?! I hope I provided every possible piece of information. Thank you for your feedback, FC
Re: [O] Agenda items refer to the wrong headline
Fletcher Charest fletcher.char...@gmail.com writes: Dear all, I am confronted to a weird issue with the agenda. I would like to know if you can reproduce this bug. First of all, my emacs-version is: GNU Emacs 24.3.1 (i386-mingw-nt5.1.2600) of 2013-03-17 on MARVIN I installed Org using ELPA (org repository), my org-version is: Org-mode version 8.2.5h (8.2.5h-94-g91175a-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20140331/) For this test, Org was the only package installed outside vanilla Emacs packages. I have no problem with the version of Org bundled with my Emacs (which is Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ c:/Program Files/Emacs 24.3/lisp/org/). I do not load my init.el file. For the test I used a simple Org file: * TODO task 1 :pro: SCHEDULED: 2014-04-01 mar. * TODO task 2 :perso: SCHEDULED: 2014-04-02 mer. Then, I displayed the agenda for this file, and filtered it for the 'perso' tag using '/'. I attached the output for reference. The problem is that some tasks in the agenda refers to the wrong headlines in the main file. This is more obvious when activating follow mode: for example, if I put the cursor on the line marked '1' in the attached file, it refers to line '2' in the main file, which is the wrong line. This is obviously a bug, and of course very problematic. Can you reproduce this?! I hope I provided every possible piece of information. I tried a bit and I couldn't reproduce it. The agenda lines are properly linked to the file lines afaict in this version: Org-mode version 8.2.5h (release_8.2.5h-667-g971dc4 @ /home/nick/elisp/org-mode/lisp/) GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of 2013-07-14 But I *did* reproduce it with latest: Org-mode version 8.2.5h (release_8.2.5h-888-g798bb8 @ /home/nick/src/emacs/org/org-mode/lisp/) I did 'emacs -q -l /path/to/minimal.el' and then got an agenda, put it in follow mode, searched for the perso tag and went to that entry: C-c a a F / TAB perso RET n and got the wrong line in the main file. The minimal.el is as follows: --8---cut here---start-8--- ;;; -*- mode: emacs-lisp -*- (add-to-list 'load-path (expand-file-name ~/src/emacs/org/org-mode/lisp)) (add-to-list 'auto-mode-alist '(\\.\\(org\\|org_archive\\|txt\\)$ . org-mode)) (require 'org-loaddefs) (setq debug-on-error t) (setq debug-on-quit t) (setq eval-expression-print-length nil) (setq eval-expression-print-level nil) (global-set-key \C-cl 'org-store-link) (global-set-key \C-ca 'org-agenda) (setq org-agenda-files '(~/src/org/fletcher-charest-agenda.org)) --8---cut here---end---8--- and the agenda file ~/src/org/fletcher-charest-agenda.org is --8---cut here---start-8--- * TODO task 1 :pro: SCHEDULED: 2014-04-01 mar. * TODO task 2 :perso: SCHEDULED: 2014-04-02 mer. Org-mode version 8.2.5h (release_8.2.5h-888-g798bb8 @ /home/nick/src/emacs/org/org-mode/lisp/) --8---cut here---end---8--- -- Nick
Re: [O] Maintainer change on May 1st
On 8 April 2014 04:03, Glyn Millington glyn.milling...@gmail.com wrote: Rainer M Krug rai...@krugs.de writes: Carsten Dominik carsten.domi...@gmail.com writes: Hi everyone, per May 1st, I would like to swing the official maintainership back to Bastien, who has agreed to this change. This really only means putting facts onto websites, because Bastien has in effect been doing this job all the time - I have unfortunately been unable to make time free to contribute here in any meaningful way, for which I apologise. I trust that an overwhelming majority of you will have not objections to this step To make this overwhelming majority not to silent, I have no objections at all. Thanks for all the hard work you and Bastien have put into org. Another big thank you from a not-so-silent user! atb Glyn Another thank you to both of you for your hard work. And absolutely no objections to the change. Jon
Re: [O] [PATCH] ob-scheme.el: Fix scheme code blocks execution error in batch mode
Hi, folks Has anyone reviewed this patch? Or is there a better way to fix the bug? Thanks. On Wed, Apr 2, 2014 at 11:48 AM, KDr2 killy.d...@gmail.com wrote: The bug: write file ~/scheme-test.org with the content below: ---8-- #+BEGIN_SRC scheme :exports results :results output raw (display Hello Scheme in OrgMode) #+END_SRC ---8-- and run: emacs --batch --eval='(load ~/.emacs.d/init.el)' ~/scheme-test.org -f org-html-export-to-html you will find the bug: `org-babel-scheme-execute-with-geiser' uses `current-message' to get the results of scheme code blocks, but `current-message' always returns nil in batch mode, and this patch fixes this. -- -- KDr2, http://kdr2.com -- -- KDr2, http://kdr2.com
Re: [O] Tangling Bernt Hansen's Org-Mode.Org file..?
David Masterson dsmaster...@gmail.com writes: ...I then pulled down Bernt Hansen's Org-Mode.org file (amazing piece of work!!) and ran C-c C-v C-t on it to tangle it (is that the right verb?). The first time I did this, I get an error about org-with-silent-modifications being an invalid function (from org-refresh-category-properties). However, immediately doing the C-c C-v C-t again correctly tangles the file and produces the expected Org-Mode.el file Where did you download this file, please? I had it a while back, and can't find where I got it, or where I lost it! Thanks, Dave in New Port Richey, FL
Re: [O] Tangling Bernt Hansen's Org-Mode.Org file..?
jdavidb...@adboyd.com (J. David Boyd) writes: David Masterson dsmaster...@gmail.com writes: ...I then pulled down Bernt Hansen's Org-Mode.org file (amazing piece of work!!) and ran C-c C-v C-t on it to tangle it (is that the right verb?). The first time I did this, I get an error about org-with-silent-modifications being an invalid function (from org-refresh-category-properties). However, immediately doing the C-c C-v C-t again correctly tangles the file and produces the expected Org-Mode.el file Where did you download this file, please? I had it a while back, and can't find where I got it, or where I lost it! http://doc.norang.ca/org-mode.org -- cheers, Thorsten
Re: [O] Tangling Bernt Hansen's Org-Mode.Org file..?
Thorsten Jolitz tjol...@gmail.com writes: jdavidb...@adboyd.com (J. David Boyd) writes: David Masterson dsmaster...@gmail.com writes: ...I then pulled down Bernt Hansen's Org-Mode.org file (amazing piece of work!!) and ran C-c C-v C-t on it to tangle it (is that the right verb?). The first time I did this, I get an error about org-with-silent-modifications being an invalid function (from org-refresh-category-properties). However, immediately doing the C-c C-v C-t again correctly tangles the file and produces the expected Org-Mode.el file Where did you download this file, please? I had it a while back, and can't find where I got it, or where I lost it! http://doc.norang.ca/org-mode.org Thanks!
[O] Example text and source code in agenda - orgmanual.org typo
I was searching for the Org Mode Manual as org-mode file, but it was not easy to find. Then I discovered orgmanual.org by TS Dye https://github.com/tsdye/orgmanual. I remembered a thread about it in this mailing list. It seems to be not completely finished, but I like it. My expertise in org-mode is very small and I wanted to play around with that file. So I added it to the agenda. Building the agenda was slow and after a while I found out that it was because of typos in orgmanual.org (org-float instead of diary-float, see below), but also I did not expect dates or code from example text or source code snippets to appear on the agenda, but it does. Can I prevent that dates in example text like #+begin_example 2014-04-08 Di 15:54 #+end_example appear in the agenda? In orgmanual.org I discovered two examples that seem to contain typos. Probably it was intended to write diary-float but it is written org-float. (In 8.1 Timestamps, deadlines, and scheduling, and in 8.3 Deadlines and scheduling) And in the second it is written (diary-float t 42) instead of (diary-float t 4 2), I guess. Which is also in the original manual (info document) a typo, I guess. After correcting these issues in orgmanual.org, the agenda builds fast and no error messages like Bad sexp at line 5464 in /home/gsqual/git/orgmanual/orgmanual.org: (org-float t 4 2) appear any more. Gerhard
Re: [O] [BUG] 'Args out of range' when exporting with reboxes
Hello, Thorsten Jolitz tjol...@gmail.com writes: I like to use rebox2 and put boxes in emails and source-file comment-sections, but when I use outorg on such an message-mode or elisp buffer and try to export it, I always get 'Args out of range' errors: The following line | org-element--parse-objects: Args out of range: 315, 316 is a table row in Org syntax, so it will not be exported as you expect it to. However, it shouldn't return an error. I fixed it. Thank you for your report. Regards, -- Nicolas Goaziou
[O] bug#16832: 24.3.50; Emacs hangs in Org mode file
Glenn Morris wrote: Perhaps this is fixed now, according to comments at: http://lists.gnu.org/archive/html/emacs-orgmode/2014-03/msg01176.html (It would be great if someone would keep an eye on these Org bugs that get reported to Emacs and update them when appropriate. Although it seems better to report Org bugs to the Org-mode list rather than to Emacs.) No comments in two weeks so closed, presumed fixed.
Re: [O] [BUG] 'Args out of range' when exporting with reboxes
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Thorsten Jolitz tjol...@gmail.com writes: I like to use rebox2 and put boxes in emails and source-file comment-sections, but when I use outorg on such an message-mode or elisp buffer and try to export it, I always get 'Args out of range' errors: The following line | org-element--parse-objects: Args out of range: 315, 316 is a table row in Org syntax, so it will not be exported as you expect it to. However, it shouldn't return an error. I fixed it. Thank you for your report. #+begin_src emacs-lisp (call-interactively 'org-version) #+end_src #+results: : Org-mode version 8.2.5h (release_8.2.5h-890-gdfcfca @ /usr/share/emacs/24.3/lisp/org/lisp/) ,-- | lets see what happens `-- ,-- | several | important | lines | here `-- #+begin_src emacs-lisp :results value replace (org-export-as 'ascii) #+end_src #+results: _ Thorsten Jolitz _ 1 --text follows this line-- Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Thorsten Jolitz tjol...@gmail.com writes: I like to use rebox2 and put boxes in emails and source-file comment-sections, but when I use outorg on such an message-mode or elisp buffer and try to export it, I always get 'Args out of range' errors: The following line | org-element--parse-objects: Args out of range: 315, 316 is a table row in Org syntax, so it will not be exported as you expect it to. However, it shouldn't return an error. I fixed it. Thank you for your report. , | (call-interactively 'org-version) ` ,-- lets see what happens `-- ,-- several important lines here `-- , | (org-export-as 'ascii) ` [...] -- cheers, Thorsten Almost perfect. I think the missing | of the reboxes in the export spoil the looks a bit, but at least they signal a difference to the exported code or example blocks, otherwise everything would look the same. Thanks for fixing. -- cheers, Thorsten
[O] [Exporter] Keep formatting or non-org comment-section when exporting?
Hi Nicolas, is there any way to make the exporter recognize non-org comment-syntax in an org-buffer? When writing emails with outorg, I often have these message-mode quotes in the outorg-edit-buffer which have outcommented multiple times and therefore remain as message-mode comments). They do not cause any problems for editing, since outorg/org-mode treats them like normal text, but formatting is lost when exporting: , | Thorsten Jolitz tjol...@gmail.com writes: | | I like to use rebox2 and put boxes in emails and source-file | comment-sections, but when I use outorg on such an message-mode or elisp | buffer and try to export it, I always get 'Args out of range' errors: | | The following line | | | org-element--parse-objects: Args out of range: 315, 316 | | is a table row in Org syntax, so it will not be exported as you expect | it to. However, it shouldn't return an error. I fixed it. | | Thank you for your report. ` becomes: #+begin_src emacs-lisp :results value replace (org-export-as 'ascii) #+end_src #+results: , |_ | | Thorsten Jolitz |_ | | | 1 --text follows this line-- | | | Nicolas Goaziou n.goaz...@gmail.com writes: | |Hello, Thorsten Jolitz tjol...@gmail.com writes: I like to use | rebox2 and put boxes in emails and source-file comment-sections, | but when I use outorg on such an message-mode or elisp buffer and | try to export it, I always get 'Args out of range' errors: The | following line | org-element--parse-objects: Args out of range: 315, | 316 is a table row in Org syntax, so it will not be exported as you | expect it to. However, it shouldn't return an error. I fixed it. | Thank you for your report. ` This is a pity, would be nice if these quoted section could be wrapped in a verbatim-type block so that exporting them gives a nice result. The same thing happens when I use outorg with e.g. emacs-lisp or picolisp. Section that are outcommented twice or more like ,--- | ;; ;; Comment | ;; ;; part `--- are seen in the outorg-edit-buffer like ,--- | ;; Comment | ;; part `--- and lose their formatting when exported. -- cheers, Thorsten
Re: [O] [Exporter] Keep formatting or non-org comment-section when exporting?
Hello, Thorsten Jolitz tjol...@gmail.com writes: is there any way to make the exporter recognize non-org comment-syntax in an org-buffer? You could write a filter to wrap these lines within verbatim blocks. Regards, -- Nicolas Goaziou
Re: [O] Example text and source code in agenda - orgmanual.org typo
Aloha Gerhard, Gerhard gsq...@gmail.com writes: It seems to be not completely finished, but I like it. Jonathan Leech-Pepin's texinfo exporter is really nice to work with. At the time I was working on orgmanual.org I thought the texinfo and pdf output were superior to org.texi, but that was a personal preference and is not meant to be a criticism of org.texi. I ran out of steam on the project when Org mode moved to version 8. There were very many changes to the manual at that time and it proved difficult to keep up with the changes. It might be possible to automate the update process, but this is beyond the ability of someone with my limited skills. The manual process is a lot of error-prone work. When I was working on the project I hoped the Org mode developers would choose to eat their own dog food (as Carsten put it to me) and prepare the texinfo and other documentation with Org mode source. Of course, that hope was based on considerable naivete and an imperfect understanding of how Org mode is connected with the rest of the Emacs world. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Example text and source code in agenda - orgmanual.org typo
Hello, n...@tsdye.com (Thomas S. Dye) writes: When I was working on the project I hoped the Org mode developers would choose to eat their own dog food (as Carsten put it to me) and prepare the texinfo and other documentation with Org mode source. Of course, that hope was based on considerable naivete and an imperfect understanding of how Org mode is connected with the rest of the Emacs world. FWIW, I still think it would be good to have our documentation in our home-made format. Of course, there's the problem of backporting documentation fixes coming from Emacs developers, but we might find volunteers to take care of it. Also, it doesn't happen very frequently. There may be other road blocks that I'm not aware of, but if there is none, I suggest to think about the feasibility of this project again. Regards, -- Nicolas Goaziou
Re: [O] Tangling Bernt Hansen's Org-Mode.Org file..?
Thorsten Jolitz tjol...@gmail.com writes: jdavidb...@adboyd.com (J. David Boyd) writes: David Masterson dsmaster...@gmail.com writes: ...I then pulled down Bernt Hansen's Org-Mode.org file (amazing piece of work!!) and ran C-c C-v C-t on it to tangle it (is that the right verb?). The first time I did this, I get an error about org-with-silent-modifications being an invalid function (from org-refresh-category-properties). However, immediately doing the C-c C-v C-t again correctly tangles the file and produces the expected Org-Mode.el file Where did you download this file, please? I had it a while back, and can't find where I got it, or where I lost it! http://doc.norang.ca/org-mode.org Works for me Org-mode version 8.2.5h (release_8.2.5h-898-g8d7dbc @ /Users/rainerkrug/.emacs.d/org-mode/lisp/) Cheers, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 pgpbBcnO0mQvs.pgp Description: PGP signature
Re: [O] :no-expand not working on variables?
Eric Schulte schulte.e...@gmail.com writes:
Rainer M Krug rai...@krugs.de writes:
Eric Schulte schulte.e...@gmail.com writes:
According to the manual :no-expand is only supposed to have an effect
during tangling, not execution.
Thanks Eric - re-reading the manual, it became clear. Maybe to clarify
this in the manual, one could say:
,
| The `:no-expand' header argument can be used to turn off this behavior
| for tangling and has no effect on the expansion during code execution.
`
instead of:
,
| The `:no-expand' header argument can be used to turn off this behavior.
`
Could you supply a patch?
Sorry - sure. Attached.
From 924fc6e3f54d4a193387e010906bcb4bdda3f324 Mon Sep 17 00:00:00 2001
From: Rainer M. Krug r.m.k...@gmail.com
Date: Tue, 8 Apr 2014 21:51:48 +0200
Subject: [PATCH 7/7] Add clarification to `:no-expand' header argument
* doc/org.texi (no-expand): Added statement to clarify that this
header argument has no impact on the execution of a code block.
TINYCHANGE
---
doc/org.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/org.texi b/doc/org.texi
index 05b1888..cc51cae 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15002,6 +15002,9 @@ during tangling. This has the effect of assigning values to variables
specified with @code{:var} (see @ref{var}), and of replacing ``noweb''
references (see @ref{Noweb reference syntax}) with their targets. The
@code{:no-expand} header argument can be used to turn off this behavior.
+Note: The @code{:no-expand} header argument has no impact on export,
+i.e. code blocks will irrespective of this header argument expanded for
+execution.
@node session
@subsubsection @code{:session}
--
1.8.5.2 (Apple Git-48)
Sorry to ask for such a trivial thing, but I'm *very* short on time
these days, and applying a patch is *much* easier.
Sure - should have done it instead of asking.
Cheers,
Rainer
Thanks,
Rainer
Best,
Rainer M Krug rai...@krugs.de writes:
Hi
shouldn't the following not give an error from R as it should not be
expanding the variables?
--8---cut here---start-8---
#+PROPERTY: no-expand TRUE
#+PROPERTY: var YEAR=2014
* a noexpand code
#+begin_src R :results output :no-expand
cat(YEAR)
#+end_src
#+RESULTS:
: 2014
--8---cut here---end---8---
The manual states:
,
| 14.8.2.11 `:no-expand'
| ..
|
| By default, code blocks are expanded with `org-babel-expand-src-block'
| during tangling. This has the effect of assigning values to variables
| specified with `:var' (see *Note var::), and of replacing noweb
| references (see *Note Noweb reference syntax::) with their targets. The
| `:no-expand' header argument can be used to turn off this behavior.
`
Org-mode version 8.2.5h (release_8.2.5h-869-gdcfe09 @
/Users/rainerkrug/.emacs.d/org-mode/lisp/)
Cheers,
Rainer
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
pgpM7IOc6HDex.pgp
Description: PGP signature
Re: [O] Tangling Bernt Hansen's Org-Mode.Org file..?
David Masterson dsmaster...@gmail.com writes: Hello, David! I've installed a full version of Cygwin on a Windows 8.1 system. I'm, therefore, using Emacs 24.3 but I've added the org-mode 8.2.5h package. ... org-with-silent-modifications being an invalid function (from org-refresh-category-properties). However, immediately doing the C-c C-v C-t again correctly tangles the file and produces the expected Org-Mode.el file. Did I mis-setup org-mode?? The org-with-silent-modifications error tends to happen when Org 7 files are loaded and mixed up with Org 8 ones. If you've installed Org 8 from ELPA without taking any special precautions, chances are that you installed it when the previous version of Org was already loaded. You may want to start with emacs -q, then set up your package-archives (if you've added any sources), and then reinstall Org (so that it recompiles in a clean environment). Make sure that you do this before loading any Org files or org-related code. It might be partially addressed by org-reload, but I'm not sure. http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01128.html Hope that helps! Sacha
Re: [O] Agenda items refer to the wrong headline
Hello, Thank you Nick for trying, and for confirming this behaviour. Do I need to take further action at this point, or just wait? In any case I'm available to investigate the bug further. FC On Tue, Apr 8, 2014 at 3:07 PM, Nick Dokos ndo...@gmail.com wrote: Fletcher Charest fletcher.char...@gmail.com writes: Dear all, I am confronted to a weird issue with the agenda. I would like to know if you can reproduce this bug. First of all, my emacs-version is: GNU Emacs 24.3.1 (i386-mingw-nt5.1.2600) of 2013-03-17 on MARVIN I installed Org using ELPA (org repository), my org-version is: Org-mode version 8.2.5h (8.2.5h-94-g91175a-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20140331/) For this test, Org was the only package installed outside vanilla Emacs packages. I have no problem with the version of Org bundled with my Emacs (which is Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ c:/Program Files/Emacs 24.3/lisp/org/). I do not load my init.el file. For the test I used a simple Org file: * TODO task 1:pro: SCHEDULED: 2014-04-01 mar. * TODO task 2:perso: SCHEDULED: 2014-04-02 mer. Then, I displayed the agenda for this file, and filtered it for the 'perso' tag using '/'. I attached the output for reference. The problem is that some tasks in the agenda refers to the wrong headlines in the main file. This is more obvious when activating follow mode: for example, if I put the cursor on the line marked '1' in the attached file, it refers to line '2' in the main file, which is the wrong line. This is obviously a bug, and of course very problematic. Can you reproduce this?! I hope I provided every possible piece of information. I tried a bit and I couldn't reproduce it. The agenda lines are properly linked to the file lines afaict in this version: Org-mode version 8.2.5h (release_8.2.5h-667-g971dc4 @ /home/nick/elisp/org-mode/lisp/) GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of 2013-07-14 But I *did* reproduce it with latest: Org-mode version 8.2.5h (release_8.2.5h-888-g798bb8 @ /home/nick/src/emacs/org/org-mode/lisp/) I did 'emacs -q -l /path/to/minimal.el' and then got an agenda, put it in follow mode, searched for the perso tag and went to that entry: C-c a a F / TAB perso RET n and got the wrong line in the main file. The minimal.el is as follows: --8---cut here---start-8--- ;;; -*- mode: emacs-lisp -*- (add-to-list 'load-path (expand-file-name ~/src/emacs/org/org-mode/lisp)) (add-to-list 'auto-mode-alist '(\\.\\(org\\|org_archive\\|txt\\)$ . org-mode)) (require 'org-loaddefs) (setq debug-on-error t) (setq debug-on-quit t) (setq eval-expression-print-length nil) (setq eval-expression-print-level nil) (global-set-key \C-cl 'org-store-link) (global-set-key \C-ca 'org-agenda) (setq org-agenda-files '(~/src/org/fletcher-charest-agenda.org)) --8---cut here---end---8--- and the agenda file ~/src/org/fletcher-charest-agenda.org is --8---cut here---start-8--- * TODO task 1 :pro: SCHEDULED: 2014-04-01 mar. * TODO task 2 :perso: SCHEDULED: 2014-04-02 mer. Org-mode version 8.2.5h (release_8.2.5h-888-g798bb8 @ /home/nick/src/emacs/org/org-mode/lisp/) --8---cut here---end---8--- -- Nick
Re: [O] Add-on: Github Flavored Markdown exporter
Hi, thanks for checking it out! Thorsten Jolitz writes: Thorsten Jolitz tjol...@gmail.com writes: Lars Tveito larst...@student.matnat.uio.no writes: Hi! I have written an exporter for Github Flavored Markdown, which is a derived back-end from the Markdown (vanilla) exporter. It adds Github-style src-blocks, strike-through and table of contents. Your library works really good, thanks. I would recommend adding it to /contrib. I used it to create new README.md files for all three libraries navi-mode.el, outorg.el and outshine.el, you can find the repos on github.com/tj64 if you want to take a look. I try adding it soon. Checked out your README'S, looks good! I like the idea very much to write this documentation stuff once in one place and then reuse it in all other places. Therefore when I write a source file, I use outorg to write a more or less sophisticated comment header for that file. This is then automatically converted back to a programming language comment section, but I can always convert it back to Org-mode. From the outorg-edit-buffer, I can then export it to html, latex, ascii and now to markdown-github-flavor too, whats nice. I use a little trick to do this: I narrow the buffer to the first 1st level headline, and then use ,-- | C-1 M-# M-# | C-u 1 M-# M-# `-- to temporarily insert the default export template, or ,-- | C-3 M-# M-# | C-u 3 M-# M-# `-- to temporarily insert a custom export template from a file. A few questions and remarks: - I get the best results with just using example blocks - is it supposed to work with source-blocks and other blocks too? Getting it to work with source-blocks was the feature I missed the most from the vanilla markdown exporter. If you specify a language in the source-block it will be added to the exported version as well; a problem occurs if you specify a language not supported by Github. Emacs lisp is an example of this, so there is a alist `org-gfm-lang' which by default has the value: ((emacs-lisp . lisp) (elisp . lisp)) So a source block like this: #+begin_src emacs-lisp (defun foo () 'foo) #+end_src exports to this: ```lisp (defun foo () 'foo) ``` Which provides syntax highlighting in Github Flavored Markdown. - Just like the Org exporter in general, it does not know how to deal with boxes made with rebox2.el, so I replaced them with example blocks. I am not familiar with rebox2.el. This back-end inherits most functionality from the markdown (vanilla) exporter, which again inherits from the html exporter. Since rebox2.el doesn't play nice with any of those it will cause problems with the github flavored as well. If you'd like the boxes created with rebox2.el to appear in the exported version you could possibly wrap it inside an example-block. - What about numbered lists with longer text/blocks as item content - is the item numbering supposed to work? I hadn't tested this, but found an old org-file with notes packed with different lists. I generated it, and most of it looks good: https://gist.github.com/anonymous/694b7b5f53dd21850bcd (by the way, the content is rubbish, and in Norwegian). The only problems are with latex-code mixed in the document and sloppy work from the original org file. - Lars
Re: [O] Add-on: Github Flavored Markdown exporter
Dumb question, from where should we pull down your excellent exporter Lars? Grant Rettke | AAAS, ACM, AMA, COG, FSF, IEEE, Sigma Xi gret...@acm.org | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Tue, Apr 8, 2014 at 4:39 PM, Lars Tveito larst...@student.matnat.uio.no wrote: Hi, thanks for checking it out! Thorsten Jolitz writes: Thorsten Jolitz tjol...@gmail.com writes: Lars Tveito larst...@student.matnat.uio.no writes: Hi! I have written an exporter for Github Flavored Markdown, which is a derived back-end from the Markdown (vanilla) exporter. It adds Github-style src-blocks, strike-through and table of contents. Your library works really good, thanks. I would recommend adding it to /contrib. I used it to create new README.md files for all three libraries navi-mode.el, outorg.el and outshine.el, you can find the repos on github.com/tj64 if you want to take a look. I try adding it soon. Checked out your README'S, looks good! I like the idea very much to write this documentation stuff once in one place and then reuse it in all other places. Therefore when I write a source file, I use outorg to write a more or less sophisticated comment header for that file. This is then automatically converted back to a programming language comment section, but I can always convert it back to Org-mode. From the outorg-edit-buffer, I can then export it to html, latex, ascii and now to markdown-github-flavor too, whats nice. I use a little trick to do this: I narrow the buffer to the first 1st level headline, and then use ,-- | C-1 M-# M-# | C-u 1 M-# M-# `-- to temporarily insert the default export template, or ,-- | C-3 M-# M-# | C-u 3 M-# M-# `-- to temporarily insert a custom export template from a file. A few questions and remarks: - I get the best results with just using example blocks - is it supposed to work with source-blocks and other blocks too? Getting it to work with source-blocks was the feature I missed the most from the vanilla markdown exporter. If you specify a language in the source-block it will be added to the exported version as well; a problem occurs if you specify a language not supported by Github. Emacs lisp is an example of this, so there is a alist `org-gfm-lang' which by default has the value: ((emacs-lisp . lisp) (elisp . lisp)) So a source block like this: #+begin_src emacs-lisp (defun foo () 'foo) #+end_src exports to this: ```lisp (defun foo () 'foo) ``` Which provides syntax highlighting in Github Flavored Markdown. - Just like the Org exporter in general, it does not know how to deal with boxes made with rebox2.el, so I replaced them with example blocks. I am not familiar with rebox2.el. This back-end inherits most functionality from the markdown (vanilla) exporter, which again inherits from the html exporter. Since rebox2.el doesn't play nice with any of those it will cause problems with the github flavored as well. If you'd like the boxes created with rebox2.el to appear in the exported version you could possibly wrap it inside an example-block. - What about numbered lists with longer text/blocks as item content - is the item numbering supposed to work? I hadn't tested this, but found an old org-file with notes packed with different lists. I generated it, and most of it looks good: https://gist.github.com/anonymous/694b7b5f53dd21850bcd (by the way, the content is rubbish, and in Norwegian). The only problems are with latex-code mixed in the document and sloppy work from the original org file. - Lars
Re: [O] Agenda items refer to the wrong headline
Fletcher Charest fletcher.char...@gmail.com writes: Hello, Thank you Nick for trying, and for confirming this behaviour. Do I need to take further action at this point, or just wait? In any case I'm available to investigate the bug further. I did a git bisect and came up with this: , | 3559ff84b244dae2109131507804b21126e0b07c is the first bad commit | commit 3559ff84b244dae2109131507804b21126e0b07c | Author: Bastien Guerry b...@altern.org | Date: Thu Mar 20 17:07:03 2014 +0100 | | org-agenda.el: Fix bug when using `org-agenda-do-date-later' in filtered agendas | | * org-agenda.el (org-agenda-filter-hide-line): Hide from the | beginning of the line to the beginning of the next line. | (org-agenda-show-new-time): Use `move-beginning-of-line' and | `move-end-of-line'. | (org-agenda-drag-line-forward): Adapt to the new definition of | hidden filtered lines. | | Thanks to Igor Sosa Mayor for reporting this bug and to Nick Dokos | and Matt Lundin for providing further information. | | :04 04 dd6879dbb07b53a05b4b9f179f5969824cd7aab5 38ee4da60a939adbf0c69cc46470c5d9b9e99b19 Mlisp ` Starting from release_8.2.5h-888-g798bb8d (this was latest as of this morning) and reverting the above commit fixes Fletcher's problem. Bastien, can you please take another look? Thanks. FC On Tue, Apr 8, 2014 at 3:07 PM, Nick Dokos ndo...@gmail.com wrote: Fletcher Charest fletcher.char...@gmail.com writes: Dear all, I am confronted to a weird issue with the agenda. I would like to know if you can reproduce this bug. First of all, my emacs-version is: GNU Emacs 24.3.1 (i386-mingw-nt5.1.2600) of 2013-03-17 on MARVIN I installed Org using ELPA (org repository), my org-version is: Org-mode version 8.2.5h (8.2.5h-94-g91175a-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20140331/) For this test, Org was the only package installed outside vanilla Emacs packages. I have no problem with the version of Org bundled with my Emacs (which is Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @ c:/Program Files/Emacs 24.3/lisp/org/). I do not load my init.el file. For the test I used a simple Org file: * TODO task 1 :pro: SCHEDULED: 2014-04-01 mar. * TODO task 2 :perso: SCHEDULED: 2014-04-02 mer. Then, I displayed the agenda for this file, and filtered it for the 'perso' tag using '/'. I attached the output for reference. The problem is that some tasks in the agenda refers to the wrong headlines in the main file. This is more obvious when activating follow mode: for example, if I put the cursor on the line marked '1' in the attached file, it refers to line '2' in the main file, which is the wrong line. This is obviously a bug, and of course very problematic. Can you reproduce this?! I hope I provided every possible piece of information. I tried a bit and I couldn't reproduce it. The agenda lines are properly linked to the file lines afaict in this version: Org-mode version 8.2.5h (release_8.2.5h-667-g971dc4 @ /home/nick/elisp/org-mode/lisp/) GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of 2013-07-14 But I *did* reproduce it with latest: Org-mode version 8.2.5h (release_8.2.5h-888-g798bb8 @ /home/nick/src/emacs/org/org-mode/lisp/) I did 'emacs -q -l /path/to/minimal.el' and then got an agenda, put it in follow mode, searched for the perso tag and went to that entry: C-c a a F / TAB perso RET n and got the wrong line in the main file. The minimal.el is as follows: --8---cut here---start-8--- ;;; -*- mode: emacs-lisp -*- (add-to-list 'load-path (expand-file-name ~/src/emacs/org/org-mode/lisp)) (add-to-list 'auto-mode-alist '(\\.\\(org\\|org_archive\\|txt\\)$ . org-mode)) (require 'org-loaddefs) (setq debug-on-error t) (setq debug-on-quit t) (setq eval-expression-print-length nil) (setq eval-expression-print-level nil) (global-set-key \C-cl 'org-store-link) (global-set-key \C-ca 'org-agenda) (setq org-agenda-files '(~/src/org/fletcher-charest-agenda.org)) --8---cut here---end---8--- and the agenda file ~/src/org/fletcher-charest-agenda.org is --8---cut here---start-8--- * TODO task 1 :pro: SCHEDULED: 2014-04-01 mar. * TODO task 2 :perso: SCHEDULED: 2014-04-02 mer. Org-mode
Re: [O] Add-on: Github Flavored Markdown exporter
Lars Tveito larstvei at student.matnat.uio.no writes: Hi, thanks for checking it out! Thorsten Jolitz writes: Thorsten Jolitz tjolitz at gmail.com writes: Lars Tveito larstvei at student.matnat.uio.no writes: Hi! I have written an exporter for Github Flavored Markdown, which is a derived back-end from the Markdown (vanilla) exporter. It adds Github-style src-blocks, strike-through and table of contents. [snip] Nice! Getting it to work with source-blocks was the feature I missed the most from the vanilla markdown exporter. If you specify a language in the source-block it will be added to the exported version as well; a problem occurs if you specify a language not supported by Github. Emacs lisp is an example of this, so there is a alist `org-gfm-lang' which by default has the value: ((emacs-lisp . lisp) (elisp . lisp)) So a source block like this: #+begin_src emacs-lisp (defun foo () 'foo) #+end_src exports to this: ```lisp (defun foo () 'foo) ``` In https://github.com/github/linguist/blob/master/lib/linguist/languages.yml I see this: , | Emacs Lisp: | type: programming | lexer: Scheme | color: #c065db | aliases: | - elisp | - emacs | primary_extension: .el | filenames: | - .emacs | extensions: | - .emacs ` so doesn't '#+BEGIN_SRC elisp' just work? And shouldn't '((emacs-lisp . elisp)) be the value of `org-gfm-lang'? HTH, Chuck
Re: [O] Add-on: Github Flavored Markdown exporter
Grant Rettke g...@wisdomandwonder.com writes: Dumb question, from where should we pull down your excellent exporter Lars? It was attached to the initial email that Lars sent to the list. If you don't have that, you should be able to get it from http://thread.gmane.org/gmane.emacs.orgmode/84702 Lars Tveito larst...@student.matnat.uio.no writes: Hi! I have written an exporter for Github Flavored Markdown, which is a derived back-end from the Markdown (vanilla) exporter. It adds Github-style src-blocks, strike-through and table of contents. -- Nick
