Re: [O] Maintainer change on May 1st
Thanks Eric! - Carsten On Fri, Apr 7, 2000 at 8:09 PM, Eric S Fraga wrote: > On Monday, 7 Apr 2014 at 16:24, Carsten Dominik wrote: > > 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 > > Just to help ensure that we are not a silent majority, I have no > objection to this at all! > > thanks to both of you for all the effort you have and continue to put > into this project. > > -- > : Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.5h-660-gef207f >
Re: [O] Embedding an image in base64; exporting to ascii, html, and latex?
On Mon, Apr 7, 2014 at 4:01 PM, Grant Rettke wrote: > Goal is to keep the document all-in-one Maybe have a look at this proposal for a zipped up org format, sort of like docx for MS Word: http://comments.gmane.org/gmane.emacs.orgmode/75454 It looks like there was some an attempt to implement the proposal. Using a zip file with a more-or-less standardized structure might help make org files, images, and configurations more portable.
Re: [O] Add-on: Github Flavored Markdown exporter
Lars Tveito 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. > > I think this could be useful because Org is a great tool for writing > README's. Org is supported by Github, but it currently does not support > syntax highlighting and table of contents (and has some other minor > quirks). > > Should I contribute this to the /lisp/contrib/? > > Best regards, > - Lars This is nice, because I like to reuse the comment-sections of my elisp libraries as README files on github, but neither the raw org nor the markdown export looked so nice when I tried, so I used the ascii exporter. When I structure my .el files with outshine headers, with the whole comment section as one tree, I can simply use M-x outorg-edit-as-outorg on that entry and then export from the outorg-edit-buffer. I tried your library with outorg.el itself. Here is the comment section after converting it to outorg (the org-exporter does not like the reboxes, so I had to put manually , in front of them - is that a bug? Same problem with ascii-export): ### * outorg.el --- Org-style comment editing Author: Thorsten Jolitz Version: 1.0 URL: https://github.com/tj64/outorg ** MetaData :PROPERTIES: :copyright: Thorsten Jolitz :copyright-years: 2013 :version: 1.0 :licence: GPL 2 or later (free software) :licence-url: http://www.gnu.org/licenses/ :part-of-emacs: no :author: Thorsten Jolitz :author_email: tjolitz AT gmail DOT com :inspiration: org-src :keywords: emacs org-mode comment-editing :END: ** Commentary *** About outorg [NOTE: For the sake of adding this library to MELPA, headlines had to be converted back from 'Org-mode style' to 'oldschool', and a few extra lines of required information had to be added on top of the MetaData section - just to comply with the required file formatting. All outshine, outorg and navi-mode functionality still works with this file. See my [[https://github.com/tj64/iorg][iOrg]] repository for examples of Emacs-Lisp and PicoLisp files structured 'the outshine way'.] `outorg' is like "reverse Org-Babel": editing of comment-sections from source code files in temporary Org-mode buffers instead of editing of Org-mode source-blocks in temporary source-code buffers. It should be used together with `outline-minor-mode' and `outshine.el'. Keep in mind, that `outorg' only works with outshine-style headlines like those produced by calling `comment-region' on Org-mode style headlines in a source-code buffer. Take this file as an example for suitable outline headlines in an Emacs Lisp buffer. In other major-modes, the `comment-start' character ';' of Emacs Lisp would be replaced by that of the respective major-mode, e.g. '#' in PicoLisp mode or '%' in LaTeX mode. `outorgs' main command is accessible via two different keybindings 1. with outline-minor-mode-prefix 'C-c' , ,--- , | C-c ' (outorg-edit-as-org) , `--- 2. with outline-minor-mode-prefix 'M-#' , ,--- , | M-# M-# (outorg-edit-as-org) , `--- used in source-code buffers where `outline-minor-mode' is activated with `outshine' extensions. The Org-mode edit-buffer popped up by this command has `outorg-edit-minor-mode' activated, a minor-mode with only 2 commands: ,, ,| M-# (outorg-copy-edits-and-exit) ,| C-x C-s (outorg-save-edits-to-tmp-file) ,` If you want to insert Org-mode source-code or example blocks in comment-sections, simply outcomment them in the outorg-edit buffer before calling `outorg-copy-edits-and-exit'. *** Installation Insert ;; #+begin_src emacs-lisp ;; (require 'outorg) ;; #+end_src in your .emacs. *** Bugs and Shortcomings `outorg' is line-based, it only works with 'one-line' comments, i.e. with comment-sections like those produced by `comment-region' (a command that comments or uncomments each line in the region). Those special multi-line comments found in many programming languages are not recognized and lead to undefined behaviour. *** Emacs Version `outorg.el' works with [GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of 2013-01-20 on eric]. No attempts of testing with older versions or other types of Emacs have been made (yet). ** ChangeLog | date| author(s) | version | |-+-+-| | <2013-05-03 Fr> | Thorsten Jolitz | 1.0 | | <2013-02-11 Mo> | Thorsten Jolitz | 0.9 | ## And here is the "*Org GFM Export*" buffer after exporting with your library: ### - [outorg.el
Re: [O] Maintainer change on May 1st
hi guys, are we going to get the "just when i thought i was out they pull me back in" video? :) -cesar On Mon, Apr 7, 2014 at 11:24 AM, Carsten Dominik wrote: > 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 > > Regards > > - Carsten >
[O] Add-on: Github Flavored Markdown exporter
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. I think this could be useful because Org is a great tool for writing README's. Org is supported by Github, but it currently does not support syntax highlighting and table of contents (and has some other minor quirks). Should I contribute this to the /lisp/contrib/? Best regards, - Lars ox-gfm.el Description: application/emacs-lisp
Re: [O] [PATCH] Re: Bug: `org-agenda-prepare-buffers' fails at (org-refresh-properties "APPT_WARNTIME" 'org-appt-warntime) [8.2.5h (8.2.5h-82-gd91d4b-elpaplus @ /home/wgg/.emacs.d/elpa/org-plus-contri
Org Mode community (and WGG), Looks like my last email to this list was a duplicate. When I checked on my post I saw that my GMANE search had hidden the recent post by Sacha Chua, sorting by relevance rather than by newest-first. Feel free to disregard/discard my duplicate. Regards, Jonathan -- Jonathan Johnson
[O] Bug: Passing nil argument in org-refresh-properties [8.2.5h (8.2.5h-98-g0820d0-elpa @ /home/jjohnson/.emacs.d/elpa/org-20140407/)]
Org Mode community, I updated to the latest ELPA release today and got an error loading an agenda with 'C-c a a'. The problem can be reproduced by including a properly-formatted Org file in the agenda list. To present that formatting, that Org file should end with an outline heading that has an effort property set in its properties. The problem stems from the last line of org-refresh-properties (line 9298), in which (point-at-eol) was replaced with (outline-next-heading). This is not an emacs versioning issue; in the 24.3 emacs release, as in my version (a recent Cygwin version of Emacs), the outline-next-heading function returns nil when there is no next heading after the point. I worked around the problem by adding a dummy heading at the end of the offending Org file, but a fix would be to add some conditional construct that validates the return value from outline-next-heading to avoid passing nil to put-text-property, or revert the code to using (point-at-eol). Not knowing more about the history of the code, and as an amateur lisp hacker, I probably shouldn't make recommendations...but...how would the following work: ... (put-text-property (point-at-bol) (or (outline-next-heading) (point-max)) tprop p)... It works for me, anyway. My info: Emacs : GNU Emacs 24.3.1 (i686-pc-cygwin, GTK+ Version 3.8.2) of 2013-08-14 on moufang Package: Org-mode version 8.2.5h (8.2.5h-98-g0820d0-elpa @ /home/jjohnson/.emacs.d/elpa/org-20140407/) current state: == (setq org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-agenda-todo-ignore-scheduled 'future org-clock-persist 'history org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-hide-inline-tasks org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent) org-babel-pre-tangle-hook '(save-buffer) org-occur-hook '(org-first-headline-recenter) org-clock-history-length 10 org-log-done 'time org-metaup-hook '(org-babel-load-in-session-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-agenda-todo-ignore-deadlines 14 org-agenda-dim-blocked-tasks 'invisible org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-agenda-include-diary t org-enforce-todo-dependencies t org-mode-hook '(org-clock-load #[nil "\300\301\302\303\304 $\207" [org-add-hook change-major-mode-hook org-show-block-all append local] 5] #[nil "\300\301\302\303\304$\207" [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-clock-idle-time 6 org-metadown-hook '(org-babel-pop-to-session-maybe) org-agenda-files "/cygdrive/i/org/.agenda_files" org-clock-report-include-clocking-task t org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-after-todo-state-change-hook '(org-clock-out-if-current) org-after-todo-statistics-hook '(org-summary-todo) org-confirm-shell-link-function 'yes-or-no-p ) Regards, -- Jonathan Johnson
[O] is it possible to customise what headline level which-function displays?
Hello all, I have started using which-function (now that I have a monitor big enough for my emacs mode-line... ;-). I was pleasantly surprised to see that org supports which-function out of the box, although I shouldn't by now be surprised at anything that org does. Anyway, a quick question: which-function for org files seems to only keep track of second level headings (or first level in some cases). My documents often have three levels and I would like to have the third level, or even a hierarchical representation (e.g. "first -> second -> third") shown. I have not been able to figure out how which-function picks up the information it displays. Is there any way to customise org to display different information? Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.2, Org release_8.2.5h-888-g798bb8
Re: [O] sending emails from org
Sharon Kimble writes: > Rainer M Krug 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 writes: > Rainer M Krug 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: , | (require 'outshine) ; has soft dependency to 'outorg | (add-hook 'outline-minor-mode-hook 'outshine-ho
[O] Embedding an image in base64; exporting to ascii, html, and latex?
Hi, Got curious about how one might embed an image in base64 encoding inside an org mode document and allow export to asciii, html, and latex. Goal is to keep the document all-in-one; so that users may work with the document and "worry about nothing else beyond that one document". Perhaps this isn't a new or good idea? Has it been done before? Searching yielded no results. Regards, 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
[O] Possible to always show items in clocktable?
Hello, I would like to my clocktable include a line for every node, regardless of whether there is any time clocked, or whether the time clocked is 0:00. I found :stepskip0 in the manual, but this does the opposite of what I want to do. Which implies that what I want to do is the default. But it doesn't seem that way. My intention here is to highlight notes that have received no attention. I want them to show up on my report so that I can see that I need to work on them. Thanks, Noah
[O] [PATCH] Fix: allow org-refile in goto mode from everywhere
It seems like org-refile with the goto argument is no longer allowed
From non org-mode buffers. In commit 49da67d the condition was changed
from:
(unless goto ...)
to:
(unless (and goto (listp goto)) ...)
where the condition of unless is only true for non-empty lists. IMO the
condition has to be:
(unless (or goto (listp goto)) ...)
(replace and with or) due to the `unless`, so that either t or '(.)
is checked.
This patch allows org-refile with the goto flag from outside org-buffers
(again).
Patch is attached.
Best,
Markus
From 5a2fcef327ff463ed660dd594a6237df8d18d1a8 Mon Sep 17 00:00:00 2001
From: Markus Hauck
Date: Mon, 7 Apr 2014 19:21:43 +0200
Subject: [PATCH] org.el (org-refile): Allow org-refile goto from everywhere
* lisp/org-agenda.el (org-refile): Flip logic to allow instead of
prohibit the use of `org-refile' with the goto flat from non
org-mode buffers.
In commit 49da67d the condition was changed from only
`(unless goto ...)` to `(unless (and goto (listp arg)) ...)`
where the `and` condition is only true for non-empty lists, so that
calling `(org-refile t)` complains about not being inside an org-mode
buffer.
With this patch org-refile can be used (again) from anywhere when
passed the goto flag to jump to the chosen task.
TINYCHANGE
---
lisp/org.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/org.el b/lisp/org.el
index f8615a2..1705c5e 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -11675,7 +11675,7 @@ prefix argument (`C-u C-u C-u C-c C-w')."
(setq it (or rfloc
(let (heading-text)
(save-excursion
-(unless (and arg (listp arg))
+(unless (or arg (listp arg))
(org-back-to-heading t)
(setq heading-text
(replace-regexp-in-string
@@ -11683,7 +11683,7 @@ prefix argument (`C-u C-u C-u C-c C-w')."
"\\3"
(nth 4 (org-heading-components)
(org-refile-get-location
- (cond ((and arg (listp arg)) "Goto")
+ (cond ((or arg (listp arg)) "Goto")
(regionp (concat actionmsg " region to"))
(t (concat actionmsg " subtree \""
heading-text "\" to")))
--
1.8.3
signature.asc
Description: PGP signature
[O] Org clock cookies
Hello,
I discovered you can use "[/]" and "[%]" as cookies and have them updated
as you complete subnodes. "[3/7]", or "[20%]" and so on.
Would it be possible to code a similar cookie ("[:]" to be expanded into
"01:10" for example) that you could update with C-c C-c, or better yet,
automatically!
Thanks,
Noah
[O] Sorting nodes by clocked time
Hello, Is there any way to sort a collection of siblings by the total clocked time? If not, approximately how hard would this be for me to write? Ideally, I could specify the scope of the clocked time, just like you can do in a clocktable. Perhaps "last30" (days) would be my preferred default. This feature would allow me to keep my node list sorted by how much time has been spent on each area. Which would be a great feedback mechanism. Thanks, Noah
[O] Problem with org-clock-display
I'm having some issues with org-clock-dosplay. Screenshot here: https://gist.github.com/nslater/10022848 Note: - Times are indented like the nodes, meaning they don't line up. (I presume this is intentional, but I find it annoying. Is there a way to turn it off?) - Everything is highlighted with yellow. Is this intentional? Can I turn it off? - Why are some of the times blue and some white. Can I turn this off? - Why are some of the "..." bits visible (in blue) and invisible (in white for the subnodes) and can I turn these off, or hide them consistently? - Would there be any way to move the black "..." bit meaning "this node can be expanded" to the very left, where it usually is, and then hide the rest? - Why can't I edit node names when this is active? Thanks! Noah
Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
Nicolas Goaziou writes: Correcting myself, > Sebastien Vauban > writes: > >> What I don't understand is: >> >> Why are Emacs Lisp minor modes loaded for exporting >> the Org document to HTML? > > As a final filter, `set-auto-mode' is called in order to indent the > buffer properly. See `org-html-final-function'. When the major mode > switch happens, all associated minor modes are installed. Err, I'm wide of the mark. Sacha is right. Regards, -- Nicolas Goaziou
Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
Hello, Sebastien Vauban writes: > What I don't understand is: > > Why are Emacs Lisp minor modes loaded for exporting > the Org document to HTML? As a final filter, `set-auto-mode' is called in order to indent the buffer properly. See `org-html-final-function'. When the major mode switch happens, all associated minor modes are installed. It also happens when exporting to a temporary buffer. Of course, this doesn't explain why Emacs lisp minor modes are attached to an HTML buffer. I guess there is something funny happening with `set-auto-mode'. > If not necessary, this seems suboptimal (performance-wise). > > Is it really necessary? Not really. We could be more careful when generating code, i.e., we could generate code already indented. Another option is to change major mode only when `org-html-indent' is non-nil. > So, is there a way to disactivate those minor modes during export? Not at the moment. Regards, -- Nicolas Goaziou
[O] Maintainer change on May 1st
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 Regards - Carsten
Re: [O] Insert UUID with org-insert-todo-heading
John Kitchin writes: > this kind of does what you want: Hehe, that's really great;). Thanks a bunch. -- Esben Stien is b0ef@e s a http://www. s tn m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@n n
Re: [O] Navigating description lists
Haha, that's a lot more clever than what I was trying to do. Thanks for pointing that out. - Will On Mon, Apr 7, 2014 at 11:20 AM, Nicolas Goaziou wrote: > Hello, > > William Kunkel writes: > > > I use description lists a lot in org documents, and I find myself > following > > a certain pattern to add new ones: > > > >1. Put the cursor on another item and hit M- to create a new item > >2. Enter the first part of the list item > >3. Hit , , , > >4. Enter the second part of the list item > > > > Frequently, I find myself hitting to try to do step 3, which > indents > > the line, which I then have to undo. Is there a key combination which > does > > step 3 without needing to hit four keys sequentially? > > C-e > > > Regards, > > -- > Nicolas Goaziou >
Re: [O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
Sebastien Vauban writes: Hello, Sebastien! > Why are Emacs Lisp minor modes loaded for exporting > the Org document to HTML? > If not necessary, this seems suboptimal (performance-wise). org-export-format-source-code-or-example loads the mode associated with the language in org-src-lang-modes in order to fontify the block. You could check if org-export-current-backend is nil before loading anything that you want to use only interactively. Maybe like so? (add-hook 'emacs-lisp-mode-hook (lambda () (unless org-export-current-backend (turn-on-redshank-mode Sacha
Re: [O] Navigating description lists
Hello, William Kunkel writes: > I use description lists a lot in org documents, and I find myself following > a certain pattern to add new ones: > >1. Put the cursor on another item and hit M- to create a new item >2. Enter the first part of the list item >3. Hit , , , >4. Enter the second part of the list item > > Frequently, I find myself hitting to try to do step 3, which indents > the line, which I then have to undo. Is there a key combination which does > step 3 without needing to hit four keys sequentially? C-e Regards, -- Nicolas Goaziou
Re: [O] Biblatex and Org
Hi Tom, t...@tsdye.com (Thomas S. Dye) writes: > I think you'll be fine with org-bibtex and biblatex. > > Richard Lawrence writes: > >> So it looks like switching to biblatex is just a matter of changing my >> compilation process and the bibliography commands in my documents. Does >> that sound right? > > Here is a description of using bibtex and biblatex with the old > exporter that should still be useful: > > http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17 > > It is easy to switch from one to the other. > ... This was very helpful. Many thanks! Best, Richard
[O] Navigating description lists
I use description lists a lot in org documents, and I find myself following a certain pattern to add new ones: 1. Put the cursor on another item and hit M- to create a new item 2. Enter the first part of the list item 3. Hit , , , 4. Enter the second part of the list item Frequently, I find myself hitting to try to do step 3, which indents the line, which I then have to undo. Is there a key combination which does step 3 without needing to hit four keys sequentially? Thanks, Will
[O] Redshank gets loaded when exporting ELisp code blocks to HTML!?
Hello, Incidentally, because I had removed `paredit.el' from my load-path, I could not export any Org file anymore which contained just one simple `emacs-lisp' code block, such as: --8<---cut here---start->8--- * ECM Type: #+begin_src emacs-lisp M-x load-library RET ox-beamer RET #+end_src --8<---cut here---end--->8--- I found the culprit lines being: --8<---cut here---start->8--- ;; Common Lisp editing extensions (autoload 'redshank-mode "redshank" "Minor mode for restructuring Lisp code (i.e., refactoring)." t) (add-hook 'emacs-lisp-mode-hook 'turn-on-redshank-mode) --8<---cut here---end--->8--- because: - Redshank requires ParEdit, and - ParEdit was not found anymore. What I don't understand is: Why are Emacs Lisp minor modes loaded for exporting the Org document to HTML? If not necessary, this seems suboptimal (performance-wise). Is it really necessary? I don't think so, because if I comment the Redshank activation, then I can still export to HTML as before. I just loose the editing features in my real Emacs Lisp buffers. So, is there a way to disactivate those minor modes during export? Best regards, Seb -- Sebastien Vauban
Re: [O] sending emails from org
Rainer M Krug 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. Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, Fluxbox 1.3.5, emacs 24.3.1 signature.asc Description: PGP signature
Re: [O] [PATCH] Re: Bug: `org-agenda-prepare-buffers' fails at (org-refresh-properties "APPT_WARNTIME" 'org-appt-warntime) [8.2.5h (8.2.5h-82-gd91d4b-elpaplus @ /home/wgg/.emacs.d/elpa/org-plus-contri
Sacha Chua writes: > > I ran into a similar problem with org-agenda-prepare-buffers and the > EFFORT property. This change to org-refresh-properties seems to fix it: Awesome, thanks. :) This patch is still needed (and works) as of the ELPA build from org 8.2.5h, commit g0820d0. -- Best, WGG
Re: [O] Exporting to multiple files
Hello Sacha and other Emacs people, thanks for pointing this out, org-publish-meta is my "child". It is now in early beta. I hope to start test-driving it soon. Iannis On Sun, Apr 6, 2014 at 11:45 PM, Sacha Chua wrote: > Marcin Borkowski writes: > > Hello, Marcin, all! > > >> > I'd like to export an Org-mode file to /multiple/ HTML files. For > >> > instance, I might want to convert all first and second level > ... > > Thanks a lot! Your code seems inspiring - I've only skimmed through it > > now, but e.g. the org-map-entries is something very useful I had no > > idea existed... > > This might also be useful: https://github.com/iani/org-publish-meta > It seems to allow you to export subtrees to different projects. Hope > that helps! > > Sacha > > >
[O] sending emails from org
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? Thanks, 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 pgpShNYZRU8j1.pgp Description: PGP signature
Re: [O] emphasis borders, double quotes, and export
Nicolas Goaziou writes: > Alan Schmitt writes: > >> Thanks, I'm aware this works. I was trying not to manually set some >> default values so that, if default changes, I would benefit from the >> change. But from what I understand there is not really a choice here >> without changing org. > > I guess the next stop for this variable will be, hopefully, the dustbin. > So, if I were you, I wouldn't worry much about future changes. I won't then. And thank you for putting up with me ;-) Alan
Re: [O] Prepare release 8.2.6
Hello,
"R. Michael Weylandt" writes:
> I'm not as familiar with org-element-context, but I think the attached
> is what you had in mind.
Thanks. Comments follow.
>> Another option for the problem at hand is to simply remove newline
>> characters in inline source blocks before executing them.
>
> That might be better but would require a bit more work:
It would require more work, but adding functions to
`fill-nobreak-predicate' has a cost, too.
It needs to be discussed, but I tend to think that it would be better to
allow newlines characters in macros and inline babel calls, even if it
means replacing them with a space when needed.
> at present,
> inline source blocks can't extend over multiple lines so org wouldn't
> recognize a construct like
>
> src_python[:exports results]{1 + 2 +
> 3 + 4}
>
> as an inline source block in the first place. Looking at
> org-inline-src-block-regexp I'm not sure why though.
Because there is everywhere [^...\n...], which means "no newline
characters, please". The same goes for ".*?", as "." cannot match
a newline character.
> +(defun org-fill-element-nobreak-p ()
Technically, it is about "objects", not elements. So the function could
be named `org-fill-objects-nobreak-p'.
> + "Non-nil when a new line at point would break an element which
> + cannot be split over multiple lines."
Ditto. Also the first sentence in the docstring cannot be split into two
lines.
> + (member (car (org-element-context))
> + '(inline-src-block macro)))
(memq (org-element-type (org-element-context))
...)
Regards,
--
Nicolas Goaziou
Re: [O] Biblatex and Org [was: [OT] Don't use BibTeX!]
Aloha Richard, I think you'll be fine with org-bibtex and biblatex. Richard Lawrence writes: > So it looks like switching to biblatex is just a matter of changing my > compilation process and the bibliography commands in my documents. Does > that sound right? Here is a description of using bibtex and biblatex with the old exporter that should still be useful: http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17 It is easy to switch from one to the other. We use the Chicago Manual of Style at work and the BibTeX chicago style. We find that it approximates the Chicago Manual fairly well, but not completely. A couple of years ago we contemplated moving to biblatex, which has an extremely competent chicago style, but gave up on the idea because it would have meant adding information to thousands of entries in our BibTeX database. It seemed like a lot of work to meet a standard that most of our readers don't know or care about. Where biblatex has helped me the most is writing for history journals. Biblatex is much better at humanities styles than BibTeX, which was designed with science publications fairly firmly in mind. Also, because the biblatex styles are based on LaTeX, rather than BibTeX's weird style language, it is in my experience relatively easy to tweak a biblatex style to meet a journal's specification. In the sciences you'll undoubtedly find journals that accept LaTeX manuscripts and require that a BibTeX style be used, so I would recommend against putting all your eggs in the biblatex basket. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Prepare release 8.2.6
Bastien writes: > Hi all, > > I'll spend a few hours this afternoon chasing the last > bugs in maint for Org 8.2.6. This release will then be > merged into the emacs-24 branch, which first pretest is > to be released very soon now. > > If you have outstanding bugs, please point at them. > > As usual, thanks in advance for your help, > > PS: gmane.org seems to be down since April, 1st, so I > could not follow the discussions since that time. Sorry if this has ben already received the list, but I must have missed it. I don't know if this effects the release of 8.2.6, but I have a bug which I would consider as serious. Using the following as the org file, results in the error in R during export to latex / pdf: --8<---cut here---start->8--- #+TITLE: single_to_multi #+DATE: <2013-10-15 Tue> #+AUTHOR: Rainer M. Krug #+EMAIL: rai...@krugs.de #+PROPERTY: session *R_MOBILIS* * R functions :PROPERTIES: :eval: never :END: Some function definitions and setting up of the compouting environment. The functions are in the ~./R/~ folder, while the data has been stored in the ~./data/~ folder as an ~.rda~ file. These can be put into a package later. ** Data IO Functions Some functions to for interaction with SQLite database. *** IFN data Load spatial forest inventory data * Data Assessment Results ** IFN *** Load spatial forest inventory data #+begin_src R :results output IFN.raw <- "Here it is" #+end_src *** Maps Raw point data The data from the raw points is plotted as maps. #+begin_src R :results output cat(IFN.raw) #+end_src * Versions: - org :: Org-mode version 8.2.5h (release_8.2.5h-879-g23e62f @ /Users/rainerkrug/.emacs.d/org-mode/lisp/) - emacs :: GNU Emacs 24.3.1 (x86_64-apple-darwin13.0.0, Carbon Version 1.6.0 AppKit 1265) of 2014-02-13 on Rainers-MacBook-Pro-2.local --8<---cut here---end--->8--- The error is: , | > cat(IFN.raw) | 'org_babel_R_eoe' | Error in cat(IFN.raw) : object 'IFN.raw' not found | > [1] "org_babel_R_eoe" | > ` In other words, the second code block is evaluated, but the second one not. If I remove the :evel: property *in the previous* tree, it works as expected. But in the main document, I have code in there which I do not want to have evaluated. This has been introduced within the previous week, if I am not mistaken. Cheers, Rainer -- Rainer M. Krug PGP: 0x0F52F982 smime.p7s Description: S/MIME cryptographic signature smime.p7s Description: S/MIME cryptographic signature
Re: [O] [BABEL] BUG Re: Omitting try/catch blocks from tangled R code?
Eric Schulte writes:
> Rainer M Krug writes:
>
>> Eric Schulte writes:
>>
Apologies - I am still struggling with encryption..
So here is my example:
--8<---cut here---start->8---
#+TITLE: single_to_multi
#+DATE: <2013-10-15 Tue>
#+AUTHOR: Rainer M. Krug
#+EMAIL: rai...@krugs.de
≈* Load R packages and data
#+BEGIN_SRC R
cat("Loading Data\n")
#+END_SRC
--8<---cut here---end--->8---
I am using only org loaded and R enabled.
C-c C-c on the block produces the error
emacs version:
GNU Emacs 24.3.1 (x86_64-apple-darwin13.0.0, Carbon Version 1.6.0
AppKit 1265) of 2014-02-13 on Rainers-MacBook-Pro-2.local
org version:
Org-mode version 8.2.5h (release_8.2.5h-837-gb296cc @
/Users/rainerkrug/.emacs.d/org-mode/lisp/)
>>>
>>> Thanks, a fixed version of the patch is attached. If this works please
>>> let me know and I'll apply.
>>
>> Still the same error:
>>
>
> Your previous example works as expected for me with the latest patch.
>
> * Load R packages and data
>
> #+BEGIN_SRC R :results output
> cat("Loading Data\n")
> #+END_SRC
>
> #+RESULTS:
> : Loading Data
>
> Please double check that you applied the patch and reloaded Org-mode,
> and if the bug persists provide another minimal example.
Sorry - no idea what went wrong, but I assumed I applied the old
patch.
I applied the patch and it is working.
Cheers,
Rainer
>
> Thanks,
>
>>
>> ,
>> | Debugger entered--Lisp error: (wrong-type-argument sequencep 99)
>> | Mapconcat(identity "cat(\"YEAR\")" "\n")
>> | Org-babel-execute:R("cat(\"YEAR\")" ((:comments . "") (:shebang
>> | . "") (:cache . "no") (:padline . "") (:noweb . "no") (:tangle
>> | . "no") (:exports . "code") (:results . "replace output") (:session
>> | . "none") (:hlines . "no") (:result-type . output) (:result-params
>> | "output" "replace") (:rowname-names) (:colname-names)))
>> | org-babel-execute-src-block(nil)
>> | org-babel-execute-src-block-maybe()
>> | org-babel-execute-maybe()
>> | org-babel-execute-safely-maybe()
>> | run-hook-with-args-until-success(org-babel-execute-safely-maybe)
>> | org-ctrl-c-ctrl-c(nil)
>> | call-interactively(org-ctrl-c-ctrl-c nil nil)
>> `
>>
>> Cheers,
>>
>> Rainer
>>
>>
>>>
>>> Best,
>>>
>>>
>>> From d67248db79faf19e1bdcac0230c37670b6115bdd Mon Sep 17 00:00:00 2001
>>> From: Eric Schulte
>>> Date: Sun, 23 Mar 2014 20:01:37 -0600
>>> Subject: [PATCH] only wrap R code graphics-file on execution
>>>
>>> Move this out of the expand-body function so that it is *never*
>>> applied to tangled code.
>>> ---
>>> lisp/ob-R.el | 40 +---
>>> 1 file changed, 21 insertions(+), 19 deletions(-)
>>>
>>> diff --git a/lisp/ob-R.el b/lisp/ob-R.el
>>> index 62aa7f2..780d99f 100644
>>> --- a/lisp/ob-R.el
>>> +++ b/lisp/ob-R.el
>>> @@ -97,24 +97,15 @@ this variable.")
>>>"Expand BODY according to PARAMS, return the expanded body."
>>>(let ((graphics-file
>>> (or graphics-file (org-babel-R-graphical-output-file params
>>> -(mapconcat
>>> - #'identity
>>> - (let ((inside
>>> -(append
>>> - (when (cdr (assoc :prologue params))
>>> - (list (cdr (assoc :prologue params
>>> - (org-babel-variable-assignments:R params)
>>> - (list body)
>>> - (when (cdr (assoc :epilogue params))
>>> - (list (cdr (assoc :epilogue params)))
>>> - (if graphics-file
>>> - (append
>>> -(list (org-babel-R-construct-graphics-device-call
>>> - graphics-file params))
>>> -inside
>>> -(list "},error=function(e){plot(x=-1:1, y=-1:1, type='n',
>>> xlab='', ylab='', axes=FALSE); text(x=0, y=0, labels=e$message, col='red');
>>> paste('ERROR', e$message, sep=' : ')}); dev.off()"))
>>> - inside))
>>> - "\n")))
>>> +(mapconcat #'identity
>>> + (append
>>> + (when (cdr (assoc :prologue params))
>>> + (list (cdr (assoc :prologue params
>>> + (org-babel-variable-assignments:R params)
>>> + (list body)
>>> + (when (cdr (assoc :epilogue params))
>>> + (list (cdr (assoc :epilogue params)
>>> + "\n")))
>>>
>>> (defun org-babel-execute:R (body params)
>>>"Execute a block of R code.
>>> @@ -127,7 +118,18 @@ This function is called by
>>> `org-babel-execute-src-block'."
>>>(colnames-p (cdr (assoc :colnames params)))
>>>(rownames-p (cdr (assoc :rownames params)))
>>>(graphics-file (org-babel-R-graphical-output-file params))
>>> - (full-body (org-babel-expand-body:R body params graphics-file))
>>> + (full-body
>>> + (let ((inside
>>> + (list (org-babel-expand-body:R body para
[O] ox-bibtex: Customization of HTML heading
Hi, Would it be reasonable to have an additional option for customizing the HTML heading of the reference section for ox-bibtex? By default, a 'References' gets inserted in the HTML file. I would suggest to include an option for omitting the heading complete (and letting the user define the context in which it occurs). Optionally, one could also think about an option for changing the heading text, instead of hardcoding it. Any thoughts regarding this? Best wishes Julian
