[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 option already exist somewhere I've missed? _ED_
Re: [O] Export of property key:value
Nicolas Goaziou 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 double-post, the first didn't seem to have been sent)
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 ewd/export-properties (backend)
"Export all properties whose names listed in EXPORT_PROPERTIES in the format:
- : after each heading of specified level
NOTE: 1st value in EXPORT_PROPERTIES is heading level"
(if (org-entry-get (point) "EXPORT_PROPERTIES")
(let* (
(export_properties (split-string
(org-entry-get (point) "EXPORT_PROPERTIES") "
"))
(export-level (string-to-number (car export_properties)))
(export-list (cdr export_properties))
)
(org-map-entries
(lambda ()
(next-line)
(open-line 1)
(dolist (prop export-list)
(if (= export-level (car (org-heading-components)))
(progn (insert "- " prop ": "
(if (org-entry-get (point) prop)
(org-entry-get (point) prop) "N/A"))
(newline)
(add-hook 'org-export-before-processing-hook 'ewd/export-properties)
[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* obvious) that I'm doing wrong? :PROPERTIES: :EXPORT_LaTeX_CLASS: report :EXPORT_OPTIONS: toc:nil num:nil H:4 :COLUMNS: %25ITEM %TODO %15Business %16Start-Date %16Last-Update :EXPORT_PROPERTIES: 2 Business Start-Date Last-Update :END:
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 ewd/export-properties (backend) "Export all property names listed in EXPORT_PROPERTIES in the format: - : after each heading of specified level NOTE: 1st value in EXPORT_PROPERTIES is heading level" (if (org-entry-get (point) "EXPORT_PROPERTIES") (let* ( (export_properties (split-string (org-entry-get (point) "EXPORT_PROPERTIES") " ")) (export-level (string-to-number (car export_properties))) (export-list (cdr export_properties)) ) (org-map-entries (lambda () (next-line) (open-line 1) (dolist (prop export-list) (if (= export-level (car (org-heading-components))) (progn (insert "- " prop ": " (if (org-entry-get (point) prop) (org-entry-get (point) prop) "N/A")) (newline) (add-hook 'org-export-before-processing-hook 'ewd/export-properties)
[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 total (and I think I understand why). It appears,
though, that I have to duplicate the syntax "key: {{{property(key)}}}
for every subheading. It would seem to me that the simplest solution, at
least from the users perspective, would be to have a way to specify
certain property keys to be exported for a particular subtree but I
haven't found that option yet.
This is my simple example. Is there a simpler way to export the amount
property without duplicating "amount: {{{property(amount)}}}" in every
subheading?
#+OPTIONS: toc:nil d:t
* Buy stuff
:PROPERTIES:
:COLUMNS: %25ITEM %TODO %15amount(Amount){$}
:END:
** DONE Buy something
:PROPERTIES:
:amount: 1234.56
:END:
amount: {{{property(amount)}}}
** TODO Buy something else
:PROPERTIES:
:ID: db34ed38-7658-48b4-9770-9a572efcdb11
:amount: 5445.43
:END:
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: (org-set-sorting-strategy 'timestamp-up) ; was 'todo however that appears to sort by timestamp within categories, not across. Is there a relatively simply way to have org-todo-list ignore categories?
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 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 SCHEDULED: <2013-03-31 Sun> In the agenda, when I move my cursor from 'H 1b1' to 'H 1b1a' the minibuffer expands to two lines even though the path display is only using a small portion of the line (ie not wrapping). It seems to have more to do with the heading depth since the same 2-line minibuffer continues when the cursor is in 'H 1b1a1' but drops back to 1-line when moved to 'H 2'. Does anyone have any ideas why this is happening? -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 room left on the line. The only thing I've noticed is that the lines in the agenda that do cause the minibuffer to grow each are 4th level headings (i.e. the minibuffer is showing up to the 3rd level heading). So far, that's the only thing I've seen that they have in common. The minibuffer grows to two lines on those particular items and shrinks back to one line when the cursor is moved to the next or previous line. It's the growing, shrinking, growing thing that is annoying. -ED-
Re: [O] Minibuffer jumping to two lines when agenda displays 4th level heading
Edward DeMeulle 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. This happens under Linux but not Windows. Am I the only one experiencing this? -ED-
[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 noticed is that each of the entries that cause the jump to two lines are on a third level heading (***). Is this intentional and is there a way to make it stop? GNU Emacs 24.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12) of 2012-09-22 on batsu, modified by Debian Org-mode version 8.0-pre (release_8.0-pre-116-g65cde8 @ /home/ewd/.emacs.pkg/org-mode/lisp/) -ED-
Re: [O] auto-fill non-op, fill-paragraph error
Nick Dokos 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 be found before the org contrib lisp directory. I understand. I didn't realize that add-to-list is stacking entries but it does make sense that you'd want new entries to override previous ones and I do see the distinction between the two options (reversing the stacking order vs putting one at the other end of the list). Thank you for the explanation.
Re: [O] auto-fill non-op, fill-paragraph error
Achim Gratz 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") (add-to-list 'load-path "~/.emacs.d/org-mode/contrib/lisp") isn't that the way it should be? -ED-
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
I thought that might be the case as I was posting it. Will do. Thanks.
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: /home/ewd/.emacs.d/org-mode/lisp/org.el /home/ewd/.emacs.d/org-mode/lisp/org.elc /usr/share/emacs/23.3/lisp/org/org.elc /usr/share/emacs/site-lisp/org/org.el /usr/share/emacs/site-lisp/org/org.elc
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 depth of the recursion. It can be set to the following symbols: `headline' Only parse headlines. `greater-element' Don't recurse into greater elements excepted headlines and sections. Thus, elements parsed are the top-level ones. `element' Parse everything but objects and plain text. `object'Parse the complete buffer (default). When VISIBLE-ONLY is non-nil, don't parse contents of hidden elements. Assume buffer is in Org mode. --- org-fill-paragraph is an interactive compiled Lisp function in `org.el'. (org-fill-paragraph &optional JUSTIFY) Fill element at point, when applicable. This function only applies to comment blocks, comments, example blocks and paragraphs. Also, as a special case, re-align table when point is at one. If JUSTIFY is non-nil (interactively, with prefix argument), justify as well. If `sentence-end-double-space' is non-nil, then period followed by one space does not end a sentence, so don't break a line there. The variable `fill-column' controls the width for filling. For convenience, when point is at a plain list, an item or a footnote definition, try to fill the first paragraph within. [back]
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
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. org.el:9001:32: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. org.el:9002:37: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. org.el:9005:24: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. In org-deadline-close: org.el:16039:12:Warning: `org-days-to-time' is an obsolete function (as of Emacs 24.3); use `org-time-stamp-to-now' instead. Wrote /home/ewd/.emacs.d/org-mode/lisp/org.elc Done (Total of 110 files compiled, 2 skipped) make[2]: Leaving directory `/home/ewd/.emacs.d/org-mode/lisp' make[1]: Leaving directory `/home/ewd/.emacs.d/org-mode/lisp' install -m 755 -d /tmp/tmp-orgtest TMPDIR=/tmp/tmp-orgtest emacs -batch -Q --eval '(add-to-list '"'"'load-path "./lisp")' --eval '(add-to-list '"'"'load-path "./testing")' -l org-install.el -l testing/org-test.el --eval '(require '"'"'ob-awk)' --eval '(require '"'"'ob-C)' --eval '(require '"'"'ob-fortran)' --eval '(require '"'"'ob-maxima)' --eval '(require '"'"'ob-lilypond)' --eval '(require '"'"'ob-octave)' --eval '(require '"'"'ob-python)' --eval '(require '"'"'ob-sh)' --eval '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests Cannot open load file: ert make: *** [test] Error 255
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
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 figured that the problem would surface elsewhere and eventually go away but now maybe it's something I'm doing? Also, fill-paragraph works fine in gnus. That's about all I know.
[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 closing tag? -ED-
[Orgmode] set show
-- Edward DeMeulle ___ 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
