[O] Option to override date on org-add-note?

Frequently I find myself logging a note for something that occurred in the past either because I wasn't at my computer or just not paying attention at the time. C-u C-c C-z doesn't change anything. I tried looking at the source code for the logging functions but nothing jumped out. Does this

Re: [O] Export of property key:value

Nicolas Goaziou n.goaz...@gmail.com writes: You can use a hook (e.g., `org-export-before-processing-hook) to insert amount : {{{property(amount)}}} (or with `org-entry-get', you don't need the macro in that case) after each property drawer with an amount property. (apologies if this is a

Re: [O] Export of property key:value

Thanks for the info. I took it up as a challenge to finally learn a little elisp. This is what I have so far, which appears to work as long as I expand the entire subtree to be exported. I'd appreciate any criticism since I really don't know if I'm handling things the best possible way. (defun

[O] Export subtree options not working

It appears that I'm using the properties syntax correctly, however I cannot seem to get export to use the options I set in the properties drawer. If I move the LaTeX_CLASS and OPTIONS over to their #+ equivalents at the top of the file they work just fine. Is there something (hopefully not *too*

[O] Export of property key:value

I've been trying to get a handle on this the past couple of days since I wanted to use column mode for revising properties and then export (print) the subtree out showing those properties under the heading. I understand that the exporter changed and now doesn't export the properties drawer in

Re: [O] TODO list sorted across categories

Thank you. That was far simpler than I expected.

[O] TODO list sorted across categories

I'd like to be able to produce a TODO list that is sorted by timestamp independently of category. I'm still new to elisp and so don't yet understand all the code involved. What I've been able to do so far is create a separate version of org-todo-list by changing a single line:

Re: [O] Minibuffer jumping to two lines when agenda displays 3rd(4th) level heading

In order to better describe the problem I see, I set up a simple example file: * H 1 SCHEDULED: 2013-03-31 Sun ** H 1a SCHEDULED: 2013-03-31 Sun ** H 1b *** H 1b1 SCHEDULED: 2013-03-31 Sun H 1b1a SCHEDULED: 2013-03-31 Sun ** H 1b1a1 SCHEDULED: 2013-03-31 Sun * H 2

Re: [O] Minibuffer jumping to two lines when agenda displays 3rd(4th) level heading

Found the problem. Some color themes boldface the 3rd and 4th heading levels and that causes the minibuffer to jump to 2 lines. No more themes, no more jumping. -ED-

Re: [O] Minibuffer jumping to two lines when agenda displays 4th level heading

Thanks for the response. Again, I'm afraid I wasn't clear enough. It's not that the minibuffer is automatically growing to fit the information display - that would make sense to me. The problem I'm having is that the minibuffer is growing to two lines for no apparent reason. There is plenty of

Re: [O] Minibuffer jumping to two lines when agenda displays 4th level heading

Edward DeMeulle e...@demeulle.org writes: Just realized that I was incorrect about the level. It is actually when moving the cursor in the agenda to a 4th level heading that the minibuffer expands in size to two lines and then back to one line when moving to another entry that isn't 4th level

[O] Minibuffer jumping to two lines when agenda displays 3rd level heading

I don't if this is a bug or a feature however to me it's just annoying. I've recently noticed that when moving up and down the agenda some entries will cause the minibuffer to expand to two lines while others make it shrink back to one. From bouncing around a bit, the one thing in common I

Re: [O] auto-fill non-op, fill-paragraph error

org-element-parse-buffer is a Lisp function in `org-element.el'. (org-element-parse-buffer optional GRANULARITY VISIBLE-ONLY) Recursively parse the buffer and return structure. If narrowing is in effect, only parse the visible part of the buffer. Optional argument GRANULARITY determines the

Re: [O] auto-fill non-op, fill-paragraph error

locate shows org-element.el here: /home/ewd/.emacs.d/org-mode/contrib/lisp/org-element.el /home/ewd/.emacs.d/org-mode/lisp/org-element.el /home/ewd/.emacs.d/org-mode/lisp/org-element.elc /usr/share/emacs/site-lisp/org/org-element.el /usr/share/emacs/site-lisp/org/org-element.elc org.el:

Re: [O] auto-fill non-op, fill-paragraph error

I thought that might be the case as I was posting it. Will do. Thanks.

Re: [O] auto-fill non-op, fill-paragraph error

Whacking the org-mode directory and re-cloning the repository did it. Thanks again.

Re: [O] auto-fill non-op, fill-paragraph error

Achim Gratz strom...@nexgo.de writes: It also tells you that it is not a good idea to keep …/org/contrib in load-path before …/org. Maybe the manual and Worg should be checked for bad advice in that direction? My init is set as follows: (add-to-list 'load-path ~/.emacs.d/org-mode/lisp)

Re: [O] auto-fill non-op, fill-paragraph error

Nick Dokos nicholas.do...@hp.com writes: So you can either reverse the order, or you can say (add-to-list 'load-path ~/.emacs.d/org-mode/contrib/lisp t) which will add it to the end of the list. The two methods are not equivalent, mind you, but in either case the org lisp directory will

Re: [O] auto-fill non-op, fill-paragraph error

Org-mode version 7.9.1 (release_7.9.1-382-g1a1d06-git @/home/ewd/.emacs.d/org-mode/lisp/) I'd been simply running it from sources but will try compiling it.

Re: [O] auto-fill non-op, fill-paragraph error

I ran 'make up2' and received the following (I'm still on emacs23) ... Compiling /home/ewd/.emacs.d/org-mode/lisp/org.el... In org-store-link: org.el:8999:23:Warning: `org-link-to-org-use-id' is an obsolete variable (as of Emacs 24.3); use `org-id-link-to-org-use-id' instead.

Re: [O] auto-fill non-op, fill-paragraph error

Ok. Ran 'make update2', which completed w/o errors. Still running into error: org-fill-paragraph: Symbol's function definition is void: org-element--parse-objects Org-mode version 7.9.1 (release_7.9.1-396-g5ba6bd @ /home/ewd/.emacs.d/org-mode/lisp/)

Re: [O] auto-fill non-op, fill-paragraph error

Unfortunately, I am still experiencing the problem with release_7.9.1-382-g1a1d06-git. Is there any information I can provide to help?

Re: [O] auto-fill non-op, fill-paragraph error

I'm on 7.9.1. I've been pulling from the repository every once in a while.

[O] auto-fill non-op, fill-paragraph error

The last several weeks or so I've noticed that auto-fill isn't working and when I try to invoke fill-paragraph I receive the following error: org-element-map: Symbol's function definition is void: org-element--parse-objects I've been tied up in the middle of a system migration at work, so I'd

[O] Option to keep drawers closed on org-agenda-show-and-scroll-up?

Is there an option that prevents all the drawers from opening when using org-agenda-show-and-scroll-up (spacebar on Agenda view)? With all the logged items I think I might prefer to have at least the option to keep the drawers closed when using this option for a quick preview. -ED-

[O] 'exit' required on gnuplot code block for svg output

Has anyone else noticed that an 'exit' line is needed on a code block for gnuplot to generate the needed /svg closing tag? -ED-

[Orgmode] set show

-- Edward DeMeulle e...@demeulle.org ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode