[Orgmode] Bug in org-colview/org-beamer?
Hi, I'm making my first real Org mode Beamer presentation, using org-mode 7.01g, and trying to set the ignore_heading for a multi-column slide. In column mode, when I hit 'e' in the Env column, Emacs says: Wrong type argument: commandp, org-beamer-set-environment-tag (and org-beamer-set-environment-tag does not appear to be defined anywhere). It's triggered from this code in org-colview.el ((equal key "BEAMER_env") (setq eval '(org-with-point-at pom (call-interactively 'org-beamer-set-environment-tag Any idea what's wrong? Please tell me if I should use the bug tracker for this, rather than ask on the list. cheers, Simon ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] Bug in org-colview/org-beamer?
On Sat, Jul 31, 2010 at 12:54 PM, Simon Guest wrote: > Hi, > > I'm making my first real Org mode Beamer presentation, using org-mode > 7.01g, and trying to set the ignore_heading for a multi-column slide. > > In column mode, when I hit 'e' in the Env column, Emacs says: > Wrong type argument: commandp, org-beamer-set-environment-tag > (and org-beamer-set-environment-tag does not appear to be defined > anywhere). > > It's triggered from this code in org-colview.el > ((equal key "BEAMER_env") > (setq eval '(org-with-point-at pom >(call-interactively 'org-beamer-set-environment-tag > > Any idea what's wrong? > > This function was renamed to org-beamer-select-environment and I think it was not changed here. The attached patch should solve the problem. * lisp/org-colview.el Use org-beamer-select-environment instead of org-beamer-set-environment-tag Thanks and Regards Noorul diff --git a/lisp/org-colview.el b/lisp/org-colview.el index 8c0ade2..dc0ab04 100644 --- a/lisp/org-colview.el +++ b/lisp/org-colview.el @@ -468,7 +468,7 @@ Where possible, use the standard interface for changing this line." (call-interactively 'org-schedule ((equal key "BEAMER_env") (setq eval '(org-with-point-at pom - (call-interactively 'org-beamer-set-environment-tag + (call-interactively 'org-beamer-select-environment (t (setq allowed (org-property-get-allowed-values pom key 'table)) (if allowed ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] org-capture: Make messages consistent.
A very small patch that makes the message displayed consistent. * lisp/org-capture.el (org-capture-finalize): Make messages consistent. diff --git a/lisp/org-capture.el b/lisp/org-capture.el index 0ecea6a..111f7f7 100644 --- a/lisp/org-capture.el +++ b/lisp/org-capture.el @@ -527,7 +527,7 @@ bypassed." (when abort-note (cond ((equal abort-note 'clean) - (message "Capture process aborted and target file cleaned up")) + (message "Capture process aborted and target buffer cleaned up")) ((equal abort-note 'dirty) (error "Capture process aborted, but target buffer could not be cleaned up correctly")) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] org-gnus.el: Suppress compiler warning.
The attached patch suppresses a compiler warning in org-gnus.el * lisp/org-gnus.el: Suppress compiler warning by declaring outside function nnimap-retrieve-headers-from-file. diff --git a/lisp/org-gnus.el b/lisp/org-gnus.el index 7a339cd..16aa476 100644 --- a/lisp/org-gnus.el +++ b/lisp/org-gnus.el @@ -41,7 +41,8 @@ (declare-function message-narrow-to-head-1 "message" nil) ;; The following line suppresses a compiler warning stemming from gnus-sum.el (declare-function gnus-summary-last-subject "gnus-sum" nil) - +;; Suppress compiler warning +(declare-function nnimap-retrieve-headers-from-file "nnimap" nil) ;; Customization variables (when (fboundp 'defvaralias) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Footnote export
On 07/31/2010 08:32 AM, Typhoon wrote: > > Yes, thanks. I was using f:nil but what I would really like is to > disable [1] type footnotes while retaining the [fn:1] style. > > Nice trick on the zero-space - That would be OK, I suppose, but like > you say, a bit tedious after a while. > Alright, so we know a way to do what we want (although it is possibly not the most elegant method), but it is a tedious, repetitive task. No worries, that's what computers are for! Add the following to your .emacs: (defun jb/disable-plain-footnotes-hack () (if (plist-get opt-plist :no-plain-footnotes) (save-excursion (goto-char 1) (replace-regexp "\\[\\([0-9]+\\)\\]" "[\u200B\\1]" (add-to-list 'org-export-inbuffer-options-extra '("DISABLE_PLAIN_FOOTNOTES" :no-plain-footnotes)) (add-hook 'org-export-preprocess-hook 'jb/disable-plain-footnotes-hack) To disable plain footnotes, you can now add a line like this to your Org file: #+DISABLE_PLAIN_FOOTNOTES: some arbitrary text Hope this works and solves your problem for now. Jan ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: keys and command name info
Am 31.07.2010 10:53, schrieb Bastien: Hi Andreas, Andreas Röhler writes: Please not I signed the FSF-disclaimer but not the paper transferring copyright under US-law. Are you willing to sign those paper? That would help, because the patch is more than 10 lines... Hi Bastien, please permit pointing at the silliness of such approaches, which state a creative work starts upward from 10 lines. No single haiku will ever have a change to be protected by that famous US-copyright law. I'm against spreading stupidity over the world and see with sorrow people abiding to it. It's quite the opposite of freedoms GPL promises BTW. Beside: Writing a programs name at the side of it's key will remain a trivial change even if this triviality is repeated. So don't be afraid, if I refuse to sign which I think it's wrong from bottom up. It remains a trivial change, sure. Andreas Thanks for your help, ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Patchwork: Patch 176 Accepted
On Saturday 31 July 2010 10:34:56 Bastien Guerry wrote: Hi Bastien, > Patch 176 (http://patchwork.newartisans.com/patch/176/) is now Accepted. > > This relates to the following submission: > > http://mid.gmane.org/%3C87fwz4159y.fsf%40thinkpad.tsdh.de%3E Oh, I didn't notice that this patch was grabbed by patchwork. It should definitively NOT be applied. It's only half-finished and it seems the workaround I was trying to implement won't work anyway. Bye, Tassilo ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: keys and command name info
Aloha Andreas, I agree with you about the stupidity of the 10 line rule, and I begrudge every bit of attention I have to squander on US copyright law. However, if that law keeps like-minded individuals from working together on a free project that requires a corporate entity to complete long-term goals, then I think it will have achieved one of its core goals. I'd hate to see that happen. All the best, Tom On Jul 31, 2010, at 7:53 AM, Andreas Röhler wrote: Am 31.07.2010 10:53, schrieb Bastien: Hi Andreas, Andreas Röhler writes: Please not I signed the FSF-disclaimer but not the paper transferring copyright under US-law. Are you willing to sign those paper? That would help, because the patch is more than 10 lines... Hi Bastien, please permit pointing at the silliness of such approaches, which state a creative work starts upward from 10 lines. No single haiku will ever have a change to be protected by that famous US-copyright law. I'm against spreading stupidity over the world and see with sorrow people abiding to it. It's quite the opposite of freedoms GPL promises BTW. Beside: Writing a programs name at the side of it's key will remain a trivial change even if this triviality is repeated. So don't be afraid, if I refuse to sign which I think it's wrong from bottom up. It remains a trivial change, sure. Andreas Thanks for your help, ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Org-indent-mode (lack of) support for plain list
I was happy to finally find a way to do soft line wrapping with org-indent-mode and visual-line-mode, unfortunately it seems that it doesn't support plain lists. Are there any plans to expand org-indent-mode to support the full markup of org-mode? ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] user control of source block header line exporting formats
I've attached a diff of my apparently-working changes to allow better control of the way ob-exp.el formats the name and arguments of source code blocks. What do you think? diff --git a/lisp/ob-exp.el b/lisp/ob-exp.el index 796812c..0c34431 100644 --- a/lisp/ob-exp.el +++ b/lisp/ob-exp.el @@ -206,42 +206,66 @@ The function respects the value of the :exports header argument." (org-babel-exp-results info type)) (defvar backend) + +(defvar org-babel-format-code-functions + '(inline org-babel-format-code-inline +block org-babel-format-code-block +lob org-babel-format-code-lob)) + +(defun org-babel-format-code-inline (lang body args switches name) + (format "=%s=" body)) + +(defvar org-babel-format-code-block-control-string "%s(%s)") + +(defun org-babel-format-code-block-default-style (info) + (destructuring-bind (lang body args0 switches name &rest ignore) info +(format org-babel-format-code-block-control-string + name + (mapconcat #'identity args ", " + +(defun org-babel-format-code-block-alternate-style (info) + (destructuring-bind (lang body args0 switches name &rest ignore) info +(format "SOURCE: %s ARGUMENTS: %s LANGUAGE: %s" + name (if (null args) "None." + (mapconcat #'identity args ", ")) + lang))) + +(defvar org-babel-format-code-block-caption-function + 'org-babel-format-code-block-default-style) + +(defun org-babel-format-code-block (lang body args switches name) + (let ((str + (format "#+BEGIN_SRC %s %s\n%s%s#+END_SRC\n" lang switches body + (if (and body (string-match "\n$" body)) + "" "\n" +(when name + (add-text-properties + 0 (length str) + (list 'org-caption + (funcall org-babel-format-code-block-caption-function + (list lang body args switches name))) + str)) +str)) + +(defun org-babel-format-code-lob (lang body args switches name) + (let ((call-line (and (string-match "results=" (car args)) + (substring (car args) (match-end 0) +(cond + ((eq backend 'html) + (format "\n#+HTML: %s\n" + call-line)) + ((format ": %s\n" call-line) + (defun org-babel-exp-code (info type) "Prepare and return code in the current code block for export. -Code is prepared in a manner suitable for exportat by +Code is prepared in a manner suitable for export by org-mode. This function is called by `org-babel-exp-do-export'. The code block is not evaluated." - (let ((lang (nth 0 info)) -(body (nth 1 info)) -(switches (nth 3 info)) -(name (nth 4 info)) -(args (mapcar - #'cdr - (org-remove-if-not (lambda (el) (eq :var (car el))) (nth 2 info) -(case type - ('inline (format "=%s=" body)) - ('block - (let ((str - (format "#+BEGIN_SRC %s %s\n%s%s#+END_SRC\n" lang switches body - (if (and body (string-match "\n$" body)) - "" "\n" - (when name - (add-text-properties - 0 (length str) - (list 'org-caption - (format "%s(%s)" - name - (mapconcat #'identity args ", "))) - str)) - str)) - ('lob - (let ((call-line (and (string-match "results=" (car args)) - (substring (car args) (match-end 0) - (cond - ((eq backend 'html) - (format "\n#+HTML: %s\n" - call-line)) - ((format ": %s\n" call-line + (destructuring-bind (lang body args0 switches name &rest ignore) info +(let ((args (mapcar #'cdr + (org-remove-if-not (lambda (el) (eq :var (car el))) args0 + (let ((formatter (getf org-babel-format-code-functions type))) + (funcall formatter lang body args switches name) (defun org-babel-exp-results (info type &optional silent) "Evaluate and return the results of the current code block for export. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Patchwork: Patch 176 Accepted
Hi Tassilo, Tassilo Horn writes: >> Patch 176 (http://patchwork.newartisans.com/patch/176/) is now Accepted. >> >> This relates to the following submission: >> >> http://mid.gmane.org/%3C87fwz4159y.fsf%40thinkpad.tsdh.de%3E > > Oh, I didn't notice that this patch was grabbed by patchwork. Yes, every (correctly) attached patch is grabbed by patchwork. I misread your email and thought the correctED patch was the correct one... sorry for that. I reverted the patch. Thanks, -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Footnote export
On Sat, 31 Jul 2010 19:33:14 +0200 Jan Böcker wrote: > On 07/31/2010 08:32 AM, Typhoon wrote: > > > > Yes, thanks. I was using f:nil but what I would really like is to > > disable [1] type footnotes while retaining the [fn:1] style. > > > > Nice trick on the zero-space - That would be OK, I suppose, but like > > you say, a bit tedious after a while. > > > > Alright, so we know a way to do what we want (although it is possibly > not the most elegant method), but it is a tedious, repetitive task. No > worries, that's what computers are for! > > Add the following to your .emacs: > > (defun jb/disable-plain-footnotes-hack () > (if (plist-get opt-plist :no-plain-footnotes) > (save-excursion > (goto-char 1) > (replace-regexp "\\[\\([0-9]+\\)\\]" "[\u200B\\1]" > > (add-to-list 'org-export-inbuffer-options-extra > '("DISABLE_PLAIN_FOOTNOTES" :no-plain-footnotes)) > > (add-hook 'org-export-preprocess-hook > 'jb/disable-plain-footnotes-hack) > > > To disable plain footnotes, you can now add a line like this to your > Org file: > #+DISABLE_PLAIN_FOOTNOTES: some arbitrary text > > Hope this works and solves your problem for now. Hi Jan, That does it with one minor modification: I needed (load "org-exp.el") before the (add-to-list xxx). Thanks for your help! Cheers, Alan in .emacs in order to make it work. > > Jan > -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [ANN] Org-Drill: Interactive revision a la Anki/Mnemosyne
Announcing the first release of "org-drill", a module which uses "org-learn" to present interactive "drill sessions" of marked material in org buffers and files. Org-learn, which is found in org's "contrib" directory, is an implementation of the spaced repetition algorithm from SuperMemo. Repository: http://bitbucket.org/eeeickythump/org-drill See the preamble in org-drill.el, and the accompanying file "spanish.org", for documentation and examples. I have tried to make it quite customisable. You can set variables to control number of items per session, and max session duration. You can also create custom "card types" and write elisp functions to control how the information in those topics is displayed. Note that org-learn currently considers items rated 4 or 5 (ie perfect or excellent recall) as NEVER needing to be revised. I think this is a misfeature of org-learn, and I hope it will eventually be fixed. For now, if you use org-drill and rate items as 4 or 5, org-drill will consider them as "new" each time you rpeat the drill session, so they will always come up. Paul ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode