[O] Bug in org-log-into-drawer
Hi, Current the org-log-into-drawer function does not honor the value of the LOG_INTO_DRAWER property if the property has the value nil. For example, if the org-log-into-drawer variable is set to t, but we have the file: * Foo :PROPERTIES: :LOG_INTO_DRAWER: nil :END: ** TODO Bar org-mode will log changes to the TODO entry into a drawer. The attached patch fixes the issue, allowing a nil value of the LOG_INTO_DRAWER property to override a t value of the org-log-into-drawer variable. best, Erik diff --git a/lisp/org.el b/lisp/org.el index 4e79125..2aa70bd 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -2519,9 +2519,10 @@ a subtree. Return the value of `org-log-into-drawer', but let properties overrule. If the current entry has or inherits a LOG_INTO_DRAWER property, it will be used instead of the default value. - (let ((p (org-entry-get nil LOG_INTO_DRAWER 'inherit))) + (let ((p (org-entry-get nil LOG_INTO_DRAWER 'inherit t))) (cond - ((or (not p) (equal p nil)) org-log-into-drawer) + ((not p) org-log-into-drawer) + ((equal p nil) nil) ((equal p t) LOGBOOK) (t p Sent from my free software system http://fsf.org/.
[O] 7.9.2: no testing directory
Following the installation instructions in the manual I failed at 'make test' with this message: Cannot open load file: testing/org-test.el make: *** [test] Error 255 Indeed, the testing directory is not present in the org-7.9.2.tar.gzand therefore not in the org-mode top directory, whereas it ispresent in the daily snapshot. Is this a bug or is testing assumed to only be necessary for non-stable versions? Uvius
Re: [O] 7.9.2: no testing directory
Uvius uv...@gmx.de writes: Following the installation instructions in the manual I failed at 'make test' with this message: Cannot open load file: testing/org-test.el make: *** [test] Error 255 Indeed, the testing directory is not present in the org-7.9.2.tar.gz and therefore not in the org-mode top directory, whereas it is present in the daily snapshot. Is this a bug or is testing assumed to only be necessary for non-stable versions? This was a bug in the documentation, I just fix it. make test is available when cloning Org from git, not in the main distribution. Thanks for reporting this, -- Bastien
Re: [O] Web site bug
Hi Simon, Simon Thum simon.t...@gmx.de writes: Sorry but to me this just worsens the (or my) confusion around org-install. In git we find this org-install.el: ;;; org-install.el --- autogenerated file, do not edit ;; ;;; Code: (warn The file org-install is obsolete. Please change your configuration to (require 'org) instead.) Yes, this was confusing. I updated this file like this ;;; org-install.el --- backward compatibility file for obsolete configuration ;; ;;; Code: (warn The file org-install is obsolete. It is provided here so that (require 'org-install) does not trigger an error for users with obsolete Emacs configuration. You can safely remove (require 'org-install) from your config.) (provide 'org-install) ;; Local Variables: ;; no-byte-compile: t ;; coding: utf-8 ;; End: ;;; org-install.el ends here I hope it is clearer. Apart from it not being autogenerated, it's confusing that I should use org instead. Indeed. The main message is: you don't need (require 'org-install) anymore. It used to be needed to get the correct autoloads but it is not anymore, as autoloads are taken from org-autoloads.el, which is either provided (in the distrib tar.gz/zip archives) or dynamically generated (from make). Which is the recommended thing in what setup? If ELPA needs not even 'org, which AFAIK is not the case, then what? And what about git installs? If you use Org from Emacs, you don't need anything. If you use Org from the distribution archives, you need to add the directory with the extracted directory in your load-path and to add (require 'org) after adding the Org directory to the load-path. If you use Org from git, you need the above plus runing make or make autoloads so that the correct autoloads are loaded. If you use Org from ELPA, you just need to add (package-initialize) before any Org configuration of the type (setq org-* ...). I guess I'm wholly confused now. I hope I helped to clarify things. I also remove any reference to org-install in http://orgmode.org/elpa.html since the ELPA archive is produced from maint, which is 7.9.2 anyway. Thanks for the heads up, -- Bastien
Re: [O] Bug in org-log-into-drawer
Hi Erik, thanks for the patch, I just applied it. Best, -- Bastien
Re: [O] C-c ^ for plain lists? Why not?
Carsten Dominik carsten.domi...@gmail.com writes: I would think that checked - transitionary - unchecked - no box is a pretty decent default. +1 (defun org-sort-list-by-checkbox-type () Sort list items according to Checkbox state. (interactive) (org-sort-list nil ?f (lambda () (if (looking-at org-list-full-item-re) (cdr (assoc (match-string 3) '(([X] . 1) ([-] . 2) ([ ] . 3) (nil . 4 4 Thanks -- I added this on Worg's hacks: http://orgmode.org/worg/org-hacks.html#sec-1-2-9 -- Bastien
Re: [O] Suggestion: Replace #+SETUP_FILE with #+INCLUDE
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Therefore, I don't see any reason to keep maintaining the #+SETUP_FILE keyword. I'd rather remove it and suggest to use #+INCLUDE: keyword instead. Any objection? FWIW, none on my side. Thanks, -- Bastien
Re: [O] Web site bug
Simon Thum writes: Which is the recommended thing in what setup? If ELPA needs not even org, which AFAIK is not the case, then what? And what about git installs? I guess I'm wholly confused now. You never needed to do anything extra for using Org as it comes with Emacs, the autoloads are automatically loaded from loaddefs.el. The distribution contained an empty org-install for ease of transition. The package manager generates and loads its own autoload file (org-autoloads.el, it also re-generates org-loaddefs.el in 7.9.2 and later), so again you don't need to do anything extra there. If you were using a seperate Org install (from tarball or Git), org-install needed to be loaded for getting the correct autoload definitions. With the introduction of org-loaddefs, things have become muddled: in Emacs and with package manager, org-loaddefs only contains those autoload definitions that become available _after_ Org has been loaded, and the generally visible autoloads come from either loaddefs.el or org-autoloads.el respectively. The standalone Org does not have a second autoload file for these first level autoloads, so they are rolled into org-loaddefs as well. As a result, you must now load org (which in turn loads org-loaddefs). I still think it would be better if Org had a separate first-level autoloads file that must be explicitly required by the user (and it would probably be easiest if it was still called org-install). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Web site bug
Achim Gratz strom...@nexgo.de writes: As a result, you must now load org (which in turn loads org-loaddefs). I don't think so. With a fresh git clone in e.g. ~/org-mode/ and make autoloads, or with the tar/zip archive unpacked in this directory, I get the correct autoloads without (require 'org). Here is how to reproduce: 1. emacs -Q 2. M-: (add-to-list 'load-path ~/org-mode/lisp/) RET 3. C-h f org-agenda RET This will refer to the definition of org-agenda from the ~/org-mode/lisp/org-agenda.el. This is with a fresh Emacs (24.2.50.1) but should be the same with older version. -- Bastien
Re: [O] From latest maint/master, no need to (require 'org-install)
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: Would it be possible/reasonable to have org-version available before (require 'org)? I would like to put the Org version into the Message Buffer at Emacs startup without the need of loading the entire Org yet. Yes, you can call (org-version) before any (require 'org). This will call the org-version that is autoloaded in Emacs. -- Bastien
Re: [O] From latest maint/master, no need to (require 'org-install)
Achim Gratz strom...@nexgo.de writes: Starting Emacs now requires ~18 seconds vs 2 seconds before. That is one of the consequences of how org.el is currently structured. The move to using org-loaddefs.el was to optimize things within Emacs. Before org-loaddefs.el, all Org's autoloads were added to loaddefs.el. This had the effect of preloading too many Org's functions in a bare emacs -Q. After org-loaddefs.el, only the core Org functions are added to Emacs' loaddefs.el. The time you spare by not preloading all autoloads in loaddefs.el is lost when you require org for the first time -- either in your config or by simply finding a new .org file. But on the overall, I think it's cleaner that way. The next step to optimize things a bit is to have less autoloads in org-autoloads.el... any suggestion is welcome in this area! -- Bastien
Re: [O] org-special-block
Hi Sanjib, Sanjib Sikder sanjibju2...@gmail.com writes: I have checked special-blocks in customize-apropos org-modules. But still i cannot load org-special-blocks. When org-special-blocks is checked from org-modules, you need to restart Org. -- Bastien
Re: [O] [wish] also provide documentation for contrib
Hi Sébastien and Thomas, Sébastien Delafond sdelaf...@gmail.com writes: As the Debian maintainer for org-mode, I cannot agree more with Thomas: since contrib is *distributed* in the regular org-mode tarball, its documentation should be found in there as well. I agree. Let's start by patching README_contribute with a new section containing short documentation for contributions. Can you help about this? Thanks, -- Bastien
Re: [O] Web site bug
Hi Bastien, Bastien wrote: ;;; Code: (warn The file org-install is obsolete. Please change your configuration to (require 'org) instead.) Yes, this was confusing. I updated this file like this ;;; org-install.el --- backward compatibility file for obsolete configuration ;; ;;; Code: (warn The file org-install is obsolete. It is provided here so that (require 'org-install) does not trigger an error for users with obsolete Emacs configuration. You can safely remove (require 'org-install) from your config.) Wouldn't it be better to tell users to require 'org-loaddefs instead, so that they don't have a performance penalty when loading their .emacs file, until they really access Org -- if they do, in that session? Best regards, Seb -- Sebastien Vauban
Re: [O] Bug in org-log-into-drawer
Hello Erik, Erik Hetzner wrote: Current the org-log-into-drawer function does not honor the value of the LOG_INTO_DRAWER property if the property has the value nil. For example, if the org-log-into-drawer variable is set to t, but we have the file: * Foo :PROPERTIES: :LOG_INTO_DRAWER: nil :END: ** TODO Bar org-mode will log changes to the TODO entry into a drawer. I would have said that this does make sense, as the property LOG_INTO_DRAWER is not inherited by the TODO entry, does it? See http://orgmode.org/manual/Property-inheritance.html for the few Org properties for which inheritance is hard-coded. The attached patch fixes the issue, allowing a nil value of the LOG_INTO_DRAWER property to override a t value of the org-log-into-drawer variable. Best regards, Seb -- Sebastien Vauban
Re: [O] agenda view of repeated time-ranges
William Léchelle william.leche...@ens-lyon.fr writes: Hi, On Fri, 26 Oct 2012 15:05:07 +0200, Philipp Kroos spake thus: I want some events to show up every week with start and end-time in the agenda. Is it possible to combine a time-range with a repeater? I think I tried every combination of range and repeater, but I can only get one of both to work. Hi :) Did you try 2012-10-31 Mi 15:00-17:00 +1w ? No, I didn't :) Thank you! #+begin_src org ** Weekly meeting 2012-10-31 Mi 15:00--2012-10-31 Mi 17:00 this doesn't repeat #+end_src org
Re: [O] Perhaps BUG: Proper quotes around math in new exporter
Hello, Rasmus ras...@gmx.us writes: I can't seem to get the new exporter to export proper quotes around single element math symbols. Here's a test-string: 'x' '\(x\)' '$x$' `$x$' `\(x\)' \(x\) x (first and last are always correct) There is now a better smart quotes export module in org-export.el. This issue should be fixed. Thanks for the report. Regards, -- Nicolas Goaziou
[O] Problem with some src blocks
Hi, I have these lines : Bla bla bla #+INCLUDE: ../java/Power2/Power2.java src java Bla bla bla that get exported this way : p Bla bla bla /p p #+BEGIN_SRC java public class Power2 ... How is it possible that the src block be exported literally ? I tried a couple of other java files but it happends only with this one. (I will look into it but if in the mean time someone has an explanation and better: a fix !) Best regards, -- Fabrice
[O] [ANN] Smart quotes in org-export.el
Hello, I've installed a smart quotes module in org-export.el (new exporter). It is off by default. You can turn it on globally with `org-export-with-smart-quotes' variable, or locally with: #+OPTIONS: ':t For now it includes quotes for de, en, es and fr languages only. If you want to help completing it, you can improve `org-export-smart-quotes-alist' defconst. Also, it isn't perfect (which smart quote module is?) so, in the long run, it may be required to tweak `org-export-smart-quotes-regexps' defconst. Regards, -- Nicolas Goaziou
Re: [O] Problem with some src blocks
Well ... this bothered me for a couple of days, and the reason is easy: the lf encoding of the file does not match the one of the buffer where it gets included. I switched the lf encoding of the java file and it gets included correctly. So: is it possible to add something to make sure that the file is included with the right lf encoding? Fabrice 2012/10/27 Fabrice Popineau fabrice.popin...@supelec.fr: Hi, I have these lines : Bla bla bla #+INCLUDE: ../java/Power2/Power2.java src java Bla bla bla that get exported this way : p Bla bla bla /p p #+BEGIN_SRC java public class Power2 ... How is it possible that the src block be exported literally ? I tried a couple of other java files but it happends only with this one. (I will look into it but if in the mean time someone has an explanation and better: a fix !) Best regards, -- Fabrice -- Fabrice Popineau - SUPELEC Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 --
Re: [O] Problem with some src blocks
Hello, Fabrice Popineau fabrice.popin...@supelec.fr writes: I have these lines : Bla bla bla #+INCLUDE: ../java/Power2/Power2.java src java Bla bla bla that get exported this way : p Bla bla bla /p p #+BEGIN_SRC java public class Power2 ... How is it possible that the src block be exported literally ? I tried a couple of other java files but it happends only with this one. (I will look into it but if in the mean time someone has an explanation and better: a fix !) Does it happen with the new exporter? Also, could you provide Power2.java so I can try to reproduce it? Thanks. Regards, -- Nicolas Goaziou
Re: [O] [ANN] Smart quotes in org-export.el
Nicolas Goaziou n.goaz...@gmail.com writes: #+OPTIONS: ':t I like this option, the choice of ' is quite smart indeed! Thanks for implementing this, -- Bastien
Re: [O] How to automatic list org files via Elisp and then, import them for an HTML export
Hi Flammable (!), flammable project flammable.proj...@gmail.com writes: If someone can help me to do this I will really appreciate! I think we will be able to help with a more limited example. Keep it minimal, if possible... Thanks in advance, -- Bastien
Re: [O] Web site bug
Bastien writes: Achim Gratz strom...@nexgo.de writes: As a result, you must now load org (which in turn loads org-loaddefs). I don't think so. Fake an autoload refering to some non-existing file or function in org-loaddefs.el in the Git worktree and try if you see that without doing a (require 'org). That some of the autoloads that come with Emacs happen to fall back onto the correct file via load-path is not something you want to rely on. That aside, there have been quite a few changes from at least Emacs 23 that moved functions to different files and/or changed their signature. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] [PATCH] Separate clocksum format for durations = 1 day
Personally, I find the time duration 123:15 much harder to parse mentally than 5d 3:15. The attached patch adds a new customization option `org-time-clocksum-days-format'. When non-nil, this is used instead of `org-time-clocksum-format' for clocksum durations longer than 1 day. It gets passed three values: # days, # hours, # mins. (Note that you don't have to use all three in the format if, say, you don't feel the need to display the minutes for such long durations.) In the patch, I've set the default value for this new customization option to a non-nil value. If you prefer to keep the current behaviour as the default, just make the default value nil. Toby PS: I guess the logical extrapolation of this is to add even more `org-time-clocksum-[months|years|decades]-format' options. (Or, probably better, abandon printf formats for long durations and just add an `org-time-clocksum-format-function' option, leaving it up users to define a function to format the time as they wish.) I haven't done this in the patch, because I think 64d 3:15 is no harder to parse than 2m 4d 3:15 (plus there's the thorny issue of how many days should be in a month). And by the time you get to 535d 3:15 vs. 2y 5d 3:15, the duration is so long that you probably don't care much about the exact value, except that it's a very long-running task indeed! -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org From 2891e0500265df24461d85493e70c1d31c095408 Mon Sep 17 00:00:00 2001 From: Toby S. Cubitt ts...@cantab.net Date: Wed, 17 Oct 2012 20:48:41 +0200 Subject: [PATCH] Allow separate format for clocksum lines longer than 1 day. Configured by new org-time-clocksum-days-format customization option. --- lisp/org-colview.el |7 +-- lisp/org.el |6 ++ 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/lisp/org-colview.el b/lisp/org-colview.el index 9d58b5f..244458f 100644 --- a/lisp/org-colview.el +++ b/lisp/org-colview.el @@ -1058,8 +1058,11 @@ Don't set this, this is meant for dynamic scoping.) ((memq fmt '(estimate)) (org-estimate-print n printf)) ((not (numberp n)) ) ((memq fmt '(add_times max_times min_times mean_times)) -(let* ((h (floor n)) (m (floor (+ 0.5 (* 60 (- n h)) - (format org-time-clocksum-format h m))) +(let* ((h (floor n)) (m (floor (+ 0.5 (* 60 (- n h) (d (/ h 24))) + (if (or (= d 0) (null org-time-clocksum-days-format)) + (format org-time-clocksum-format h m) + (setq h (- h (* 24 d))) + (format org-time-clocksum-days-format d h m ((eq fmt 'checkbox) (cond ((= n (floor n)) [X]) (( n 1.) [-]) diff --git a/lisp/org.el b/lisp/org.el index 2aa70bd..2eb65d6 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -2720,6 +2720,12 @@ This is also used when org-mode generates a time duration. :group 'org-time :type 'string) +(defcustom org-time-clocksum-days-format %dd %d:%02d + The format string used for CLOCKSUM lines longer than 1 day. +If null, fall back to `org-time-clocksum-format'. + :group 'org-time + :type '(choice (string :tag format) (const :tag disabled nil))) + (defcustom org-time-clocksum-use-fractional nil If non-nil, \\[org-clock-display] uses fractional times. org-mode generates a time duration. -- 1.7.8.6
Re: [O] Web site bug
Hi Bastien, thanks a lot for clarifying this. One nit left, see below. I'm having a look at putting a summary in worg. Thanks, Simon On 10/27/2012 09:33 AM, Bastien wrote: Hi Simon, Simon Thumsimon.t...@gmx.de writes: Sorry but to me this just worsens the (or my) confusion around org-install. In git we find this org-install.el: ;;; org-install.el --- autogenerated file, do not edit ;; ;;; Code: (warn The file org-install is obsolete. Please change your configuration to (require 'org) instead.) Yes, this was confusing. I updated this file like this ;;; org-install.el --- backward compatibility file for obsolete configuration ;; ;;; Code: (warn The file org-install is obsolete. It is provided here so that (require 'org-install) does not trigger an error for users with obsolete Emacs configuration. You can safely remove (require 'org-install) from your config.) Judging from what you say further down there are use-cases left where this is bad advice, namely the distribution archives and git. (provide 'org-install) ;; Local Variables: ;; no-byte-compile: t ;; coding: utf-8 ;; End: ;;; org-install.el ends here I hope it is clearer. Apart from it not being autogenerated, it's confusing that I should use org instead. Indeed. The main message is: you don't need (require 'org-install) anymore. It used to be needed to get the correct autoloads but it is not anymore, as autoloads are taken from org-autoloads.el, which is either provided (in the distrib tar.gz/zip archives) or dynamically generated (from make). Which is the recommended thing in what setup? If ELPA needs not even 'org, which AFAIK is not the case, then what? And what about git installs? If you use Org from Emacs, you don't need anything. If you use Org from the distribution archives, you need to add the directory with the extracted directory in your load-path and to add (require 'org) after adding the Org directory to the load-path. If you use Org from git, you need the above plus runing make or make autoloads so that the correct autoloads are loaded. If you use Org from ELPA, you just need to add (package-initialize) before any Org configuration of the type (setq org-* ...). I guess I'm wholly confused now. I hope I helped to clarify things. I also remove any reference to org-install in http://orgmode.org/elpa.html since the ELPA archive is produced from maint, which is7.9.2 anyway. Thanks for the heads up,
[O] Bug or not? vCard export problem
Hi all, I'm currently setting up org for more automatic syncing. One of the tings I'm testing is auto-regenerating a vCard list of my org-contacts content on update: emacs -f org-contacts-export-as-vcard This does not work. However if I load some org file: emacs whatnot.org -f org-contacts-export-as-vcard things get rolling. I'm not sure it's a bug, and the workaround seems easy enough if superfluous. Just wanted to let you know in case this is intended to actually work. If someone knows a better solution please speak up. Cheers, Simon
Re: [O] Web site bug
Hi Sébastien, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Wouldn't it be better to tell users to require 'org-loaddefs instead No, (require 'org-loaddefs) is never needed IMHO. , so that they don't have a performance penalty when loading their .emacs file, until they really access Org -- if they do, in that session? The penalty comes from requiring org explicitely but I don't see why you would need to require org explicitely anyway. Do you have a use case example? -- Bastien
[O] Running babel blocks in :noexport: sections
For papers and beamer presentations, I sometimes hide more universal babel blocks inside a sort of setup headline. I thought I'd done this before, but perhaps not... The idea would be like so: * Data setup :noexport: #+begin_src R :session r load libraries read data files do universal operations #+end_src * Slide #+begin_src R :session r :exports results :results output graphics subset(larger_data_set_from_above) processing plot something #+end_src I noticed today that my :noexport: setup sections (I had a couple) were not updating. I re-defined a variable name further down in my file and it was re-using the definition from an above setup section (tagged with :noexport:). Just because I don't want it export doesn't mean I don't want to have useful stuff in the headline... Is this a bug/inappropriate setting, desirable based on how others use :noexport: headlines, or would others see value in executing babel blocks in :noexport: headlines? If I /didn't/ want it executed, I'd use :execute no. Thanks for any input, John
[O] Contradiction between code and doc as regards commented lines
Before Git commit e8046d2, lines like this were treated as comments in
org-mode:
### This used to be a comment
At present, lines as the above are not highlighted as comments and will
be exported verbatim. Only lines like the following are considered to be
comments, currently:
# Only this is now a comment
This behavior is clearly in contradiction with the documentation,
according to this relevant part of doc/org.texi:
@node Comment lines, , Horizontal rules, Structural markup elements
[snip]
Lines starting with zero or more whitespace characters followed by @samp{#}
are treated as comments and will never be exported.
Please, fix the documentation (or restore the previous behavior, if the
documentation is meant to be correct).
Cheers,
Rafael
Re: [O] Web site bug
Hi Simon, Simon Thum simon.t...@gmx.de writes: ;;; org-install.el --- backward compatibility file for obsolete configuration ;; ;;; Code: (warn The file org-install is obsolete. It is provided here so that (require 'org-install) does not trigger an error for users with obsolete Emacs configuration. You can safely remove (require 'org-install) from your config.) Judging from what you say further down there are use-cases left where this is bad advice, namely the distribution archives and git. People using Org from the distribution archives don't get this warning because the distribution archive still use the old way, org-install.el containing autoloads when make autoloads is run. People using from Git don't need (require 'org-install), and the org-install.el provided in a Git clone is empty (not auto-generated), with just this warning. I hope this clarifies further :) -- Bastien
Re: [O] Contradiction between code and doc as regards commented lines
Rafael Laboissiere raf...@laboissiere.net writes: Please, fix the documentation (or restore the previous behavior, if the documentation is meant to be correct). Done, thanks. -- Bastien
[O] [PATCH 0/2] Orgpan: resize correct window
Teach orgpan-panel to resize the correct window; that is the newly created panel window instead of the document window. I only tested this with Emacs-24.2.1. There are a few other outstanding issues: - search prompts in the minibuffer but selects the document window - orgpan-panel-buttons:=t causes an error - indentation is strange I must say I am not really interested in fixing these myself. I marked both changes as TINYCHANGE because that's what I think they are. Doesn't matter whether you disagree, I signed the fsf papers for Emacs this spring anyway. @Bastien: Of course I used git-format-patch to create the patch (git-refilter-branch was a typo)... Thanks for the tip about git-send-email - I did not know about that command, and it appears most blog posts on the subject neglect mentioning it in addition to format-patch. I should not have assumed that message-mode would either know how to correctly handle the patches/messages created by format-patch or otherwise fail completely (instead of sending a corrupted message). Jonas Bernoulli (2): Orgpan: resize the correct window Orgpan: quiet byte-compiler contrib/lisp/org-panel.el | 17 - 1 file changed, 8 insertions(+), 9 deletions(-) -- 1.8.0.rc3.331.g5b9a629
[O] [PATCH 1/2] Orgpan: resize the correct window
* contrib/lisp/org-panel.el (orgpan-panel): Make sure the panel buffer is resized to four lines not the document buffer. TINYCHANGE --- contrib/lisp/org-panel.el | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/contrib/lisp/org-panel.el b/contrib/lisp/org-panel.el index 3ffdfaf..95876b4 100644 --- a/contrib/lisp/org-panel.el +++ b/contrib/lisp/org-panel.el @@ -598,12 +598,11 @@ button changes the binding of the arrow keys. org-mode-map)) ;;(org-back-to-heading) ;;(remove-hook 'window-configuration-change-hook 'orgpan-window-config-change) - (split-window) + (setq orgpan-org-window (selected-window)) + (setq orgpan-panel-window (split-window nil -4 'below)) + (select-window orgpan-panel-window) (set-window-buffer (selected-window) (orgpan-make-panel-buffer)) - (setq orgpan-panel-window (selected-window)) ;;(set-window-dedicated-p (selected-window) t) - (fit-window-to-buffer nil nil 3) - (setq orgpan-org-window (next-window)) ;; The minor mode version starts here: (when orgpan-minor-mode-version (select-window orgpan-org-window) -- 1.8.0.rc3.331.g5b9a629
[O] [PATCH 2/2] Orgpan: quiet byte-compiler
* contrib/lisp/org-panel.el: don't setq undefined and otherwise unused variable orgpan-this-panel-window * contrib/lisp/org-panel.el (orgpan-check-panel-mode): fix format string of (error) * contrib/lisp/org-panel.el: declare variables viper-emacs-state-mode-list and viper-new-major-mode-buffer-list which are defined in viper.el TINYCHANGE --- contrib/lisp/org-panel.el | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/contrib/lisp/org-panel.el b/contrib/lisp/org-panel.el index 95876b4..a732027 100644 --- a/contrib/lisp/org-panel.el +++ b/contrib/lisp/org-panel.el @@ -133,8 +133,6 @@ active.) ;;; ;;; Hook functions etc -;;(defvar orgpan-this-panel-window nil) - (defun orgpan-delete-panel () Remove the panel. (interactive) @@ -203,8 +201,7 @@ active.) (unless (and orgpan-point (= (point) orgpan-point)) ;; Go backward so it is possible to click on a button: - (orgpan-backward-field) - (setq orgpan-this-panel-window nil)) + (orgpan-backward-field)) (error (lwarn 't :warning orgpan-post: %S err ;; (defun orgpan-window-config-change () @@ -294,7 +291,7 @@ active.) (defun orgpan-check-panel-mode () (unless (derived-mode-p 'orgpan-mode) - (error Not orgpan-mode in buffer: major-mode))) + (error Not orgpan-mode in buffer: %s major-mode))) (defun orgpan-display-bindings-help () (orgpan-check-panel-mode) @@ -401,6 +398,9 @@ There can be only one such buffer at any time.) (defvar orgpan-point nil) ;;(make-variable-buffer-local 'orgpan-point) +(defvar viper-emacs-state-mode-list) +(defvar viper-new-major-mode-buffer-list) + (defun orgpan-avoid-viper-in-buffer () ;; Fix-me: This is ugly. However see `this-major-mode-requires-vi-state': (set (make-local-variable 'viper-emacs-state-mode-list) '(orgpan-mode)) -- 1.8.0.rc3.331.g5b9a629
[O] Base64 embedded images?
Has anyone ever tried embedding images directly in the HTML when exporting an org-mode file, similar to what the SingleFile Chrome extension does (https://github.com/gildas-lormeau/SingleFile)? This would be extremely handy, allowing me to periodically archive the page in Git, including changes to images. It also makes sharing a document dead-simple. I've seen a few similar things, e.g.: http://thread.gmane.org/gmane.emacs.orgmode/55155 http://thread.gmane.org/gmane.emacs.orgmode/11180 But what I'm hoping for is to create the image in the usual way, with a [[file:foo.png]] tag (usually this is the result of plotting something in R), and the Base64 encoding happens to all images during *export*. The above approaches create the Base64-encoded img tag right in the org-mode buffer, which limits the other types of exports one can do (e.g. normal HTML, LaTeX, etc.). -- Ken Williams, Senior Research Scientist WindLogics http://windlogics.com CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.
Re: [O] Running babel blocks in :noexport: sections
Hello, John Hendy jw.he...@gmail.com writes: Is this a bug/inappropriate setting, desirable based on how others use :noexport: headlines, or would others see value in executing babel blocks in :noexport: headlines? If I /didn't/ want it executed, I'd use :execute no. This is the behaviour of the new export engine. The current exporter removes :noexport: sections before executing src blocks within (it always did). Regards, -- Nicolas Goaziou
Re: [O] Contradiction between code and doc as regards commented lines
* Bastien b...@altern.org [2012-10-27 21:44]: Rafael Laboissiere raf...@laboissiere.net writes: Please, fix the documentation (or restore the previous behavior, if the documentation is meant to be correct). Done, thanks. Thanks. You might be interested in applying the patch attached below, which fixes the comments in the *Remember* buffer, allowing them to get correctly fontified. Rafael From b1ae1021338a156dc7f65256cc6f085b6b2bf103 Mon Sep 17 00:00:00 2001 From: Rafael Laboissiere raf...@laboissiere.net Date: Sat, 27 Oct 2012 23:40:39 +0200 Subject: [PATCH] org-remember.el: Start the commented lines with the appropriate characters * org-remember.el (org-remember-apply-template): Start the commented lines in the Remember temporary buffer with the appropriate characters. TINYCHANGE --- lisp/org-remember.el | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lisp/org-remember.el b/lisp/org-remember.el index d555ca6..bfbca73 100644 --- a/lisp/org-remember.el +++ b/lisp/org-remember.el @@ -472,12 +472,12 @@ to be run from that hook to function properly. (erase-buffer) (insert (substitute-command-keys (format - ## %s \%s\ - \* %s\ -## C-u C-c C-c like C-c C-c, and immediately visit note at target location -## C-0 C-c C-c \%s\ - \* %s\ -## %s to select file and header location interactively. -## C-2 C-c C-c as child (C-3: as sibling) of the currently clocked item -## To switch templates, use `\\[org-remember]'. To abort use `C-c C-k'.\n\n + # %s \%s\ - \* %s\ +# C-u C-c C-c like C-c C-c, and immediately visit note at target location +# C-0 C-c C-c \%s\ - \* %s\ +# %s to select file and header location interactively. +# C-2 C-c C-c as child (C-3: as sibling) of the currently clocked item +# To switch templates, use `\\[org-remember]'. To abort use `C-c C-k'.\n\n (if org-remember-store-without-prompt C-c C-c C-1 C-c C-c) (abbreviate-file-name (or file org-default-notes-file)) (or headline ) -- 1.7.10.4
[O] Bug: stored link description craziness [7.9.2 (release_7.9.2-609-g853125 @ /Users/dave/.emacs.d/el-get/org-mode/lisp/)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Go to the headline in the following org-snippet and do `M-x
org-store-link RET'. Then, anywhere, do `M-x org-insert-link RET RET'.
The result is a link whose visible description is
{{org-mode.org}{org-mode}}. IMO, it should be simply org-mode.
--8---cut here---start-8---
* [[org-mode.org][org-mode]]
:PROPERTIES:
:ID: 35D50B60-F339-4B08-B8C3-FA0CA0D861A3
:END:
--8---cut here---end---8---
Emacs : GNU Emacs 24.2.1 (x86_64-apple-darwin11.4.2, Carbon Version 1.6.0
AppKit 1138.51)
of 2012-10-26 on pluto.luannocracy.com
Package: Org-mode version 7.9.2 (release_7.9.2-609-g853125 @
/Users/dave/.emacs.d/el-get/org-mode/lisp/)
current state:
==
(setq
org-hide-leading-stars t
org-export-babel-evaluate nil
org-export-preprocess-before-selecting-backend-code-hook
'(org-beamer-select-beamer-code)
org-tab-first-hook '(yas/org-very-safe-expand org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-adapt-indentation nil
org-footnote-section nil
org-time-clocksum-use-fractional t
org-log-buffer-setup-hook '((lambda nil (setq fill-column (- fill-column 5
org-habit-preceding-days 42
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-fontify-priorities t
org-reverse-note-order t
org-agenda-auto-exclude-function 'org-my-auto-exclude-function
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-agenda-scheduled-leaders '( S%d: )
org-agenda-start-on-weekday nil
org-clock-into-drawer LOGBOOK
org-export-preprocess-before-normalizing-links-hook
'(org-remove-file-link-modifiers)
org-clock-mode-line-total 'current
org-confirm-shell-link-function nil
org-id-link-to-org-use-id 'create-if-interactive-and-no-custom-id
org-x-backends '(ox-org ox-redmine)
org-finalize-agenda-hook '(org-agenda-add-overlays)
org-speed-commands-user '((+ . org-priority-up) (- . org-priority-down)
(: . org-set-tags))
org-clock-idle-time 10
org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-habit-completed-glyph 10004
org-agenda-restore-windows-after-quit t
org-file-apps '((\\.pptx?\\' . open %s) (auto-mode . emacs) (\\.mm\\' .
default) (\\.x?html?\\' . default)
(\\.pdf\\' . default))
org-agenda-deadline-leaders '(D: D%d: )
org-pretty-entities t
org-special-ctrl-a/e 'reversed
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-x-redmine-title-prefix-function 'org-x-redmine-title-prefix
org-agenda-prefix-format '((agenda . %-11:c%?-12t% s) (timeline . % s)
(todo . %-11:c)
(tags . %-11:c))
org-agenda-skip-scheduled-if-done t
org-agenda-custom-commands '((E Errands (next 3 days) tags
ErrandTODO\DONE\TODO\CANCELED\STYLE\habit\SCHEDULED\+3d\
((org-agenda-overriding-header Errands (next 3
days
(A Priority #A tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header Today's priority #A tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
notregexp) \\=.*\\[#A\\])))
)
)
(b Priority #A and #B tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header Today's priority
#A and #B tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
regexp) \\=.*\\[#C\\])))
)
)
(w Waiting/delegated tasks tags
TODO=\WAITING\|TODO=\DELEGATED\
((org-agenda-overriding-header
Waiting/delegated tasks:)
(org-agenda-sorting-strategy (quote
(todo-state-up priority-down category-up
)
(p Unprioritized tasks tags
AREA\Work\TODO\\TODO{DONE\\|CANCELED\\|NOTE\\|PROJECT\\|DEFERRED\\|SOMEDAY}
((org-agenda-files
Re: [O] Running babel blocks in :noexport: sections
John Hendy jw.he...@gmail.com writes: For papers and beamer presentations, I sometimes hide more universal babel blocks inside a sort of setup headline. I thought I'd done this before, but perhaps not... The idea would be like so: * Data setup :noexport: #+begin_src R :session r load libraries read data files do universal operations #+end_src * Slide #+begin_src R :session r :exports results :results output graphics subset(larger_data_set_from_above) processing plot something #+end_src I noticed today that my :noexport: setup sections (I had a couple) were not updating. I re-defined a variable name further down in my file and it was re-using the definition from an above setup section (tagged with :noexport:). Just because I don't want it export doesn't mean I don't want to have useful stuff in the headline... Is this a bug/inappropriate setting, desirable based on how others use :noexport: headlines, or would others see value in executing babel blocks in :noexport: headlines? If I /didn't/ want it executed, I'd use :execute no. Thanks for any input, John Instead of tagging the headline as :noexport: you can add the COMMENT flag to it. This should result in your desired behavior. See the attached example. #+Title: example * COMMENT not exported but run #+name: the-date #+begin_src sh date #+end_src * exported and able to call into un-exported subtrees The date today is, #+call: the-date() -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Bug in org-log-into-drawer
At Sat, 27 Oct 2012 11:00:40 +0200, Sebastien Vauban wrote: Hello Erik, I would have said that this does make sense, as the property LOG_INTO_DRAWER is not inherited by the TODO entry, does it? See http://orgmode.org/manual/Property-inheritance.html for the few Org properties for which inheritance is hard-coded. The attached patch fixes the issue, allowing a nil value of the LOG_INTO_DRAWER property to override a t value of the org-log-into-drawer variable. Hi Seb, The function org-log-into-drawer called the function org-entry-get with the inherit argument before I got there. (Maybe it needs to be added to that list?) This issue had to do with the difference between the string nil (as supplied in the property) and the value nil (meaning no property was found). best, Erik Sent from my free software system http://fsf.org/.
