Re: [O] Sticky agenda branch merged
Max Mikhanosha m...@openchat.com writes: Hi Max, I had pushed a fix, which should fix `org-agenda-to-appt' Yes, it seems to work again. Thanks a lot, Tassilo
Re: [O] Yearly repeats on the agenda
SW sabrewolfy at gmail.com writes: I have entries such as the following: *** 2011-01-01 +1y New Year's Day :holiday: which appear on the agenda on the correct day each year, but they appear as: File: 2011-01-01 +1y Public Holiday: Freedom Day :holiday: with the date showing. Other deadline/schedule/plain timestamp entries do not show the full date. Which variable controls this? Apologies -- the above was a copy and paste nightmare between Emacs and Firemacs. What I meant was the following in an org file: *** 2011-01-01 +1y New Year's Day :holiday: and the following appearing on the agenda: File: 2011-01-01 +1y New Year's Day :holiday: What I'm asking about is the fact that the full timestamp itself appears in in the agenda for this entry, but not for other deadline/schedule/plain timestamp entries.
Re: [O] Yearly repeats on the agenda
SW sabrewolfy at gmail.com writes: Apologies -- the above was a copy and paste nightmare between Emacs and Firemacs. What I meant was the following in an org file: *** 2011-01-01 +1y New Year's Day :holiday: and the following appearing on the agenda: File: 2011-01-01 +1y New Year's Day :holiday: What I'm asking about is the fact that the full timestamp itself appears in in the agenda for this entry, but not for other deadline/schedule/plain timestamp entries. And I'd like to disable the timestamp in for these entries. They appear ON the correct day in the agenda, so there is no need to include the full timestamp. Also, this makes the entry very long in the Agenda. Other entries (timestamps/deadlines/schedules) appear in the agenda without the timestamp text in .
Re: [O] Yearly repeats on the agenda
On 17 Apr 2012 09:25, SW sabrewo...@gmail.com wrote: SW sabrewolfy at gmail.com writes: snip *** 2011-01-01 +1y New Year's Day :holiday: and the following appearing on the agenda: File: 2011-01-01 +1y New Year's Day :holiday: What I'm asking about is the fact that the full timestamp itself appears in in the agenda for this entry, but not for other deadline/schedule/plain timestamp entries. snip Hi there, 1) I believe org works much more happily if you don't include timestamps in headlines. 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Best, Brian vdB
Re: [O] Yearly repeats on the agenda
On 17 Apr 2012 09:39, Brian van den Broek brian.van.den.br...@gmail.com wrote: 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Emailing before first coffee is a bad idea. I left out some syntax. See http://orgmode.org/manual/Weekly_002fdaily-agenda.html. Best, Brian vdB
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
Hello, Shaun Johnson sh...@slugfest.demon.co.uk writes: The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. This is a limitation from HTML exporter: it requires `org-footnote-section' being non-nil. Regards, -- Nicolas Goaziou
[O] org-protocol-capture and chrome
Could someone please post a working setup (browser bookmark url and template) for org-protocol-capture to correctly get triggered from a Google Chrome bookmark link in order to store the current url. Googling shows some conflicting views : some with removing calls to encodeURI and others hacking xdg-open. thanks!
[O] defining a clocktable in a capture template with absolute timespan computed relative to today
Hi all, I've been experimenting with a new means of using org to plan my day at the outset and, at the end of it, to easily review how close I have come to accomplishing what I planned. For that second component, I want a clocktable covering the day to allow for an easy review of what I have accomplished. Since I am an extreme night-owl, I want the table to cover 8:00 of the day to 8:00 of the next one. (Things I do at 0:300 I think of as having been part of the previous day.) This is easy enough to accomplish manually. Today's, for instance, is defined as #+BEGIN: clocktable :maxlevel 4 :scope agenda :tstart 2012-04-17 08:00 :tend 2012-04-18 Wed 08:00 :fileskip0 #+END: I've defined a capture template to produce, in a datetree, the boiler-plate for my daily planning and for the end of day review. As yet, the best I have managed for the clocktable is to include (some aspects omitted): #+BEGIN: clocktable :tstart \%(format-time-string \%Y-%m-%d\ (current-time)) 08:00\ :tend \%(format-time-string \%Y-%m-%d\ (current-time)) 08:00\ :fileskip0 #+END: This still needs some fiddling to get the :tend parameter right as it defines it as exactly the same as the :tstart. What I need is something that fulfils the intent of :tend \%(format-time-string \%Y-%m-%d\ (+ oneday (current-time))) 08:00\. However, the docstring of (current-time) reads: Return the current time, as the number of seconds since 1970-01-01 00:00:00. The time is returned as a list of three integers. The first has the most significant 16 bits of the seconds, while the second has the least significant 16 bits. The third integer gives the microsecond count. My meagre elisp means that I will have to spend quite some time figuring out how to add 1 day to the return value of (current-time). So: 1) Is there an org-native way that I have overlooked to define a clock-table in a capture template that has the relative time-span that I desire? 2) If not, would someone please take pity on my poor elisp and give me the push to bring home my definition? Thanks and best, Brian vdB PS I suspect that this will wrap badly. Apologies if so; I hope the intent is nonetheless clear.
[O] Folding again in the way of autocomplete for headers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I just discovered another autocomplete / folding interaction: when #+begin_src R :r[*] #+end_src pressing tab at [*], the block folds, where as when after the : it works nicely. Is this expected? 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+NO3AACgkQoYgNqgF2egryHwCfS13Rx2JljH1b+UmGFLrFsao0 H2QAnijr650JVWtsEYKZ/CxQF4OpJ3fk =M2R5 -END PGP SIGNATURE-
Re: [O] org-protocol-capture and chrome
Richard Riley rile...@gmail.com writes: Could someone please post a working setup (browser bookmark url and template) for org-protocol-capture to correctly get triggered from a Google Chrome bookmark link in order to store the current url. Googling shows some conflicting views : some with removing calls to encodeURI and others hacking xdg-open. thanks! As an aside, the documentation in worg is wrong with regard to the default template key for capture: The doc says :- , | You don't need to setup a capture template to use org-protocol-capture, | since Org-mode provides a default template for those cases. Newer | versions provide an interactive interface for choosing a template. You | may provide a template to be used by customizing the variable | org-capture-default-template. ` I believe the correct variable is , | org-protocol-default-template-key ` regards r.
Re: [O] Sticky agenda branch merged
Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer
Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode
There was another crash this morning, here is the report (as from Console.app): Process: Emacs [6378] Path:/Applications/Emacs.app/Contents/MacOS/Emacs Identifier: org.gnu.Emacs Version: Version 24.0.95 (9.0) Code Type: X86-64 (Native) Parent Process: launchd [117] Date/Time: 2012-04-17 11:57:41.796 +0200 OS Version: Mac OS X 10.7.3 (11D50) Report Version: 9 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGABRT) Exception Codes: KERN_INVALID_ADDRESS at 0x0018 VM Regions Near 0x18: -- __TEXT 0001-000100203000 [ 2060K] r-x/rwx SM=COW /Applications/Emacs.app/Contents/MacOS/Emacs Application Specific Information: objc[6378]: garbage collection is OFF abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x7fff9801a82a __kill + 10 1 org.gnu.Emacs 0x0001000a824b fatal_error_signal + 347 2 libsystem_c.dylib 0x7fff981cecfa _sigtramp + 26 3 libsystem_kernel.dylib 0x7fff9801ace2 __pthread_kill + 10 4 libsystem_c.dylib 0x7fff9817c7d2 pthread_kill + 95 5 libsystem_c.dylib 0x7fff9816da7a abort + 143 6 org.gnu.Emacs 0x000100191f41 ns_term_shutdown + 81 7 org.gnu.Emacs 0x0001000a8217 fatal_error_signal + 295 8 libsystem_c.dylib 0x7fff981cecfa _sigtramp + 26 9 libobjc.A.dylib 0x7fff9a22d3af objc_msgSend_vtable14 + 47 10 org.gnu.Emacs 0x000100196268 x_free_frame_resources + 216 11 org.gnu.Emacs 0x0001001963e9 x_destroy_window + 25 12 org.gnu.Emacs 0x0001000115bc delete_frame + 828 13 org.gnu.Emacs 0x000100123c55 Ffuncall + 1125 14 org.gnu.Emacs 0x00010011fff6 Fcall_interactively + 6374 15 org.gnu.Emacs 0x000100123c42 Ffuncall + 1106 16 org.gnu.Emacs 0x000100123e26 call3 + 38 17 org.gnu.Emacs 0x0001000bc16e command_loop_1 + 1134 18 org.gnu.Emacs 0x000100122285 internal_condition_case + 293 19 org.gnu.Emacs 0x0001000b1787 command_loop_2 + 55 20 org.gnu.Emacs 0x000100122389 internal_catch + 217 21 org.gnu.Emacs 0x0001000b1f0c recursive_edit_1 + 364 22 org.gnu.Emacs 0x0001000b2082 Frecursive_edit + 290 23 org.gnu.Emacs 0x0001000a8f4e main + 3262 24 org.gnu.Emacs 0x000122f4 start + 52 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x7fff9801b7e6 kevent + 10 1 libdispatch.dylib 0x7fff931885be _dispatch_mgr_invoke + 923 2 libdispatch.dylib 0x7fff9318714e _dispatch_mgr_thread + 54 Thread 2: 0 libsystem_kernel.dylib 0x7fff9801b192 __workq_kernreturn + 10 1 libsystem_c.dylib 0x7fff9817c594 _pthread_wqthread + 758 2 libsystem_c.dylib 0x7fff9817db85 start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib 0x7fff9801b192 __workq_kernreturn + 10 1 libsystem_c.dylib 0x7fff9817c594 _pthread_wqthread + 758 2 libsystem_c.dylib 0x7fff9817db85 start_wqthread + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x rbx: 0x0006 rcx: 0x7fff5fbfe628 rdx: 0x rdi: 0x18ea rsi: 0x0006 rbp: 0x7fff5fbfe660 rsp: 0x7fff5fbfe628 r8: 0x0001 r9: 0x0010 r10: 0x7fff9801ad0a r11: 0xff80002d8220 r12: 0x0006 r13: 0x00010058a688 r14: 0x7fff7f356960 r15: 0x00010058a79c rip: 0x7fff9801a82a rfl: 0x0202 cr2: 0x7fff7f34da28 Logical CPU: 0 Binary Images: 0x1 -0x100202fef +org.gnu.Emacs (Version 24.0.95 - 9.0) 7C48528A-6CE3-F9D3-AECA-8F5120471764 /Applications/Emacs.app/Contents/MacOS/Emacs 0x100b29000 -0x100b2dff7 libFontRegistryUI.dylib (??? - ???) 46FDC6A3-EF17-3E57-AACD-8B36AB1F00E9 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Resources/libFontRegistryUI.dylib 0x100e69000 -0x100e6ffef libcldcpuengine.dylib (1.50.69 - compatibility 1.0.0) C0C4CC37-F2FD-301C-A830-EC54D86612D5 /System/Library/Frameworks/OpenCL.framework/Libraries/libcldcpuengine.dylib 0x100e76000 -0x100e79ff7 libCoreFSCache.dylib (??? - ???) 0E2C3D54-7D05-35E8-BA10-2142B7C03946
Re: [O] Yearly repeats on the agenda
Brian van den Broek brian.van.den.broek at gmail.com writes: 1) I believe org works much more happily if you don't include timestamps in headlines. This *** New Year's Day 2011-01-01 +1y does *not* include the timestamp in the agenda, yes. However, timestamps are *not* included in the agenda from other entries which *do* have timestamps in the headline. I've tested with repeating timestamps, timestamps with times, timestamps repeating with last year as the start date, and I cannot replicate this. I'll post if I find anything further.
Re: [O] Yearly repeats on the agenda
SW sabrewolfy at gmail.com writes: This *** New Year's Day 2011-01-01 +1y does *not* include the timestamp in the agenda, yes. However, timestamps are *not* included in the agenda from other entries which *do* have timestamps in the headline. I've tested with repeating timestamps, timestamps with times, timestamps repeating with last year as the start date, and I cannot replicate this. I'll post if I find anything further. I've tracked down what causes this behaviour -- it's actually a repeating timestamp which is from a year ore more ago (contrary to what I posted above). This: ** 2011-04-17 +1y Test :holiday: or this: ** 2010-04-17 +1y Test :holiday: appears in the agenda *with* the timestamp included. This: ** 2012-04-17 +1y Test :holiday: does *not* appear with the timestamp included. The difference is the *starting* year. (I have not included the *day* in the timestamp. I excluded it initially with the thought that the day would not be correct for subsequent years. Including it does not affect the problematic behaviour.)
Re: [O] Yearly repeats on the agenda
SW sabrewo...@gmail.com wrote: SW sabrewolfy at gmail.com writes: This *** New Year's Day 2011-01-01 +1y does *not* include the timestamp in the agenda, yes. However, timestamps are *not* included in the agenda from other entries which *do* have timestamps in the headline. I've tested with repeating timestamps, timestamps with times, timestamps repeating with last year as the start date, and I cannot replicate this. I'll post if I find anything further. I've tracked down what causes this behaviour -- it's actually a repeating timestamp which is from a year ore more ago (contrary to what I posted above). This: ** 2011-04-17 +1y Test :holiday: or this: ** 2010-04-17 +1y Test :holiday: appears in the agenda *with* the timestamp included. This: ** 2012-04-17 +1y Test :holiday: does *not* appear with the timestamp included. The difference is the *starting* year. Indeed - I can reproduce that. It happens in org-agenda-get-timestamps, in the call to org-agenda-format-item: this function takes a regexp argument, remove-re, and removes any matches from the string it produces. The regexp is constructed from the *current* date though: (concat (regexp-quote (format-time-string %Y-%m-%d (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date .*?) so it becomes 2012-04-17.*?. Hence it removes the date in the third example above, but not in the other two. The question is whether this is intended or not: personally, I don't see any reason for the difference in behavior, so it might be a good idea to generalize the regexp to match *any* year. Nick
Re: [O] Sticky agenda branch merged
At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? 2. I don't understand the TODO state changes as expected part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? 3. Are sticky agendas enabled? 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with g or r key? 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Regards, Max
Re: [O] Yearly repeats on the agenda
Nick Dokos nicholas.dokos at hp.com writes: Indeed - I can reproduce that. It happens in org-agenda-get-timestamps, in the call to org-agenda-format-item: this function takes a regexp argument, remove-re, and removes any matches from the string it produces. The regexp is constructed from the *current* date though: (concat (regexp-quote (format-time-string %Y-%m-%d (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date .*?) so it becomes 2012-04-17.*?. Hence it removes the date in the third example above, but not in the other two. The question is whether this is intended or not: personally, I don't see any reason for the difference in behavior, so it might be a good idea to generalize the regexp to match *any* year. Nick Thanks for the reply. Do I need to file this as a bug, or does this thread constitute a bug report? I'm behind a firewall/proxy and haven't setup email in Emacs, so I would just copy and paste the message from org-submit-bug-report and email it? I'm not (yet) an elisp-er, so I can't fix this myself.
Re: [O] Yearly repeats on the agenda
Brian van den Broek brian.van.den.broek at gmail.com writes: On 17 Apr 2012 09:39, Brian van den Broek brian.van.den.broek at gmail.com wrote: 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Emailing before first coffee is a bad idea. I left out some syntax. See http://orgmode.org/manual/Weekly_002fdaily-agenda.html. Best, Brian vdB Thanks, didn't know about those, but that's exactly what I need. There is *so* much to org-mode and always another section to the manual ... :)
Re: [O] Yearly repeats on the agenda
SW sabrewo...@gmail.com wrote: Nick Dokos nicholas.dokos at hp.com writes: Indeed - I can reproduce that. It happens in org-agenda-get-timestamps, in the call to org-agenda-format-item: this function takes a regexp argument, remove-re, and removes any matches from the string it produces. The regexp is constructed from the *current* date though: (concat (regexp-quote (format-time-string %Y-%m-%d (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date .*?) so it becomes 2012-04-17.*?. Hence it removes the date in the third example above, but not in the other two. The question is whether this is intended or not: personally, I don't see any reason for the difference in behavior, so it might be a good idea to generalize the regexp to match *any* year. BTW, this should be *any* date: monthly, daily, weekly repeaters would exhibit the same behavior. Nick Thanks for the reply. Do I need to file this as a bug, or does this thread constitute a bug report? I'll let the maintainers decide a) whether it's a bug and b) whether a formal bug report is needed. I'm behind a firewall/proxy and haven't setup email in Emacs, so I would just copy and paste the message from org-submit-bug-report and email it? I'm not (yet) an elisp-er, so I can't fix this myself. Yes, that would be the procedure. Nick
Re: [O] Yearly repeats on the agenda
SW sabrewolfy at gmail.com writes: 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Emailing before first coffee is a bad idea. I left out some syntax. See http://orgmode.org/manual/Weekly_002fdaily-agenda.html. Thanks, didn't know about those, but that's exactly what I need. There is *so* much to org-mode and always another section to the manual ... :) FWIF 1: Anniversaries in the agenda don't have tags now. The tag I provided appears in the headline only and does not appear in the agenda. Adding :TAG: didn't solve this. FWIW 2: The CATEGORY example included in the link above resulted in the category appearing next to some other entries in the agenda as well. Replacing it with :CATEGORY: instead of #+CATEGORY: solved this.
[O] Some settings are missing while exporting included org files to the tex file
Dear Org-mode users:
Recently I am considering using org-mode to write my thesis and would
like to separate each chapter into a single file. In order to do so, I
created a file gathering all the rest files like this:
#+OPTIONS: Tex:t |:t toc:nil
#+OPTIONS: LaTeX:t
#+LaTeX_CLASS: koma-book
#+LATEX_HEADER: \usepackage[english,ngerman]{babel}
#+LATEX_HEADER: \usepackage{fancyhdr}
...
#+BEGIN_LATEX
\pagestyle{fancy}
\newenvironment{abstract}%
{\cleardoublepage \null \vfill \begin{center}%
\bfseries \abstractname \end{center}}%
{\vfill \null }
#+END_LATEX
#+TITLE:
#+AUTHOR:
#+DATE: \today
#+INCLUDE: Ch00_Abs_Eng.org
#+INCLUDE: Ch00_Abs_Deu.org
#+LATEX: \selectlanguage{english}
#+LATEX: \tableofcontents
#+LATEX: \listoftables
#+LATEX: \listoffigures
#+INCLUDE: Ch01_Introduction.org :minlevel 0
...
#+INCLUDE: Ch07_Conclusion.org :minlevel 0
\bibliographystyle{plain}
\bibliography{References}
I noticed the tex output misses some settings and those are before the
first chapter, like included abstract, table of contents, etc. and after
the last chapter, like bibliography. To work around, I have to add
something like this:
...
* Introduction
#+INCLUDE: Ch01_Introduction.org :minlevel 0
...
and also move the bibliography settings to the end of the file of last
chapter.
I am wondering if there is any way to keep the structure I had earlier
or at least to know where the problem is. Any suggestion or idea?
In addition, I also tried to export a single org file without any
preamble to be able to use input/include in latex but with no luck. And
it seems org mode does not support this function yet. I would recommend
the development team to re-consider this feature. Now the tex output of
org mode draws all the separate files into single tex file and the user
has to compile the entire tex file every time. By doing so, it also
misses the feature of LaTex as mentioned here:
http://web.science.mq.edu.au/~rdale/resources/writingnotes/latexstruct.html
emacs version: 23.4
orgmode version: 7.8
R.
Keith
Re: [O] Sticky agenda branch merged
Hi Max, see below Am 17.04.2012 14:29, schrieb Max Mikhanosha: At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file 2. I don't understand the TODO state changes as expected part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? I have set org-clock-in-switch-to-state to INARBEIT state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state INARBEIT and doing a clockin, the CLOCK: line appears. 3. Are sticky agendas enabled? YES! 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with g or r key? it is not from agenda 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Let me see: no, problem occurs with or without sticky agendas Regards, Max Thanks for checking! Regards, Rainer
[O] org-list-demote-modify-bullet and alphabetic/numerical bullets
Hi all, I have (setq org-alphabetical-lists t) in my .emacs. I am trying to set org-list-demote-modify-bullet to cycle on demoting between bullets of the form -/+ and 1./A. (setq org-list-demote-modify-bullet '((+ . -) (- . +) )) accomplishes the -/+ cycling just fine. (setq org-list-demote-modify-bullet '((+ . -) (- . +) (1. . A.) (A. . 1.))) has, however, no effect on numerical nor alphabetic bullets, nor do either of (setq org-list-demote-modify-bullet '((+ . -) (- . +) (1. . -) )) and (setq org-list-demote-modify-bullet '((+ . -) (- . +) (1 . -) )) affect numerical bullets, so I doubt that it is that alphabetical bullets are the problem. Is there a way to do what I am trying to effect? Thanks and best, Brian vdB
Re: [O] Yearly repeats on the agenda
On 17 April 2012 15:11, SW sabrewo...@gmail.com wrote: SW sabrewolfy at gmail.com writes: 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Emailing before first coffee is a bad idea. I left out some syntax. See http://orgmode.org/manual/Weekly_002fdaily-agenda.html. Thanks, didn't know about those, but that's exactly what I need. There is *so* much to org-mode and always another section to the manual ... :) FWIF 1: Anniversaries in the agenda don't have tags now. The tag I provided appears in the headline only and does not appear in the agenda. Adding :TAG: didn't solve this. FWIW 2: The CATEGORY example included in the link above resulted in the category appearing next to some other entries in the agenda as well. Replacing it with :CATEGORY: instead of #+CATEGORY: solved this. I've not tagged any of my holidays and days of observance. The #+CATEGORY issue will arise in other regards as well. It was a first pass at changing categories within an org file before the general category property mechanism was included. I don't recall if #+CATEGORY has been deprecated, but I've treated it as such and been much happier than when I was struggling with it. Best, Brian vdB
Re: [O] Yearly repeats on the agenda
Brian van den Broek brian.van.den.br...@gmail.com wrote: On 17 April 2012 15:11, SW sabrewo...@gmail.com wrote: SW sabrewolfy at gmail.com writes: 2) I just added a bunch of holidays / days of observation to my system. Your use case is better accomplished via org-anniversary: (org-anniversary 2011 01 01) New Year's Day Emailing before first coffee is a bad idea. I left out some syntax. See http://orgmode.org/manual/Weekly_002fdaily-agenda.html. Thanks, didn't know about those, but that's exactly what I need. There is *so* much to org-mode and always another section to the manual ... :) FWIF 1: Anniversaries in the agenda don't have tags now. The tag I provided appears in the headline only and does not appear in the agenda. Adding :TAG: didn't solve this. FWIW 2: The CATEGORY example included in the link above resulted in the category appearing next to some other entries in the agenda as well. Replacing it with :CATEGORY: instead of #+CATEGORY: solved this. I've not tagged any of my holidays and days of observance. The #+CATEGORY issue will arise in other regards as well. It was a first pass at changing categories within an org file before the general category property mechanism was included. I don't recall if #+CATEGORY has been deprecated, but I've treated it as such and been much happier than when I was struggling with it. I'm still stuck in the past, using #+CATEGORY: instead of properties, but fwiw I haven't had any problem. Like Brian, I'm not tagging these things. Nick
[O] [babel] [bug?] create graph in R
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I am irritated - shouldn't the following create a pdf? #+begin_src R :results file :file sustEconOnlyNonRec.pdf :session R plot(runif(100)) #+end_src I am getting no error messages in the R console, nothing in the messages? Org-mode version 7.8.09 (release_7.8.09.230.gec7b.dirty) What does the dirty mean, by the way? Cheers, 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+NfskACgkQoYgNqgF2egoOmACfSyJ0CeN1e4/XsAQsJ0ZIEvLT tp8AnRbosinDi7o4rJ0tCTK2rOt331oq =ezvQ -END PGP SIGNATURE-
[O] [bug?] Computations on efforts expressed in days
Hello,
I want to compute efforts given in days. As explained by the doc of
`org-effort-durations', we must add a =d= modifier to tell Org that given
numbers
must be multiplied by 480 (in the case of hours) to get the correct number of
corresponding minutes.
I did that, but (as shown in the following inlined ECM):
- the computed total for task A is interpreted as hours (4.5 days becomes
4 hours 30 minutes).
- the grand computed total for all tasks becomes completely wrong (4:38
instead of 4.5 + 0.125 = 4.625 days).
Am I doing something wrong, or forgetting something?
Best regards,
Seb
--8---cut here---start-8---
#+COLUMNS: %66ITEM(Task) %6Effort(Estim.){:}
#+TITLE: ECM Proposal
#+AUTHOR:Seb Vauban
* Tasks
:PROPERTIES:
:ID: 75dd37bf-a15a-4910-89f8-25d481f3e523
:END:
** TODO A
*** TODO A1
:PROPERTIES:
:Effort: 1.5d
:END:
Time required: 1.5 days.
*** TODO A2
:PROPERTIES:
:Effort: 3d
:END:
Time required: 3 days.
** TODO B
:PROPERTIES:
:Effort: 0.125d
:END:
Time: around 1 hour.
* Budget estimate
We have estimated the budget as follows:
#+tblname: dblock-tasks
#+BEGIN: columnview :hlines 1 :id 75dd37bf-a15a-4910-89f8-25d481f3e523
:maxlevel 3
| Task| Estim. |
|-+|
| * Tasks | 4:38 |
| ** TODO A | 4:30 |
| *** TODO A1 | 1.5d |
| *** TODO A2 | 3d |
| ** TODO B | 0.125d |
#+END:
--8---cut here---end---8---
--
Sebastien Vauban
Re: [O] [babel] [bug?] create graph in R
Hi Rainer, Rainer M Krug wrote: I am irritated - shouldn't the following create a pdf? #+begin_src R :results file :file sustEconOnlyNonRec.pdf :session R plot(runif(100)) #+end_src I am getting no error messages in the R console, nothing in the messages? I'm not using R -- yet! --, so I'm not sure about the following, but please check whether you must write: #+begin_src R :results file :file sustEconOnlyNonRec.pdf or #+begin_src R :results graphics :file sustEconOnlyNonRec.pdf Best regards, Seb -- Sebastien Vauban
Re: [O] [babel] [bug?] create graph in R
Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: Hi Rainer, Rainer M Krug wrote: I am irritated - shouldn't the following create a pdf? #+begin_src R :results file :file sustEconOnlyNonRec.pdf :session R plot(runif(100)) #+end_src I am getting no error messages in the R console, nothing in the messages? I'm not using R -- yet! --, so I'm not sure about the following, but please check whether you must write: #+begin_src R :results file :file sustEconOnlyNonRec.pdf or #+begin_src R :results graphics :file sustEconOnlyNonRec.pdf I've lost track of all these header arguments and their possible values: are they documented somewhere (other than the mailing list)? AFAICT, they are not in the manual. Nick
[O] More than one column view in a file
Hello,
I'd like to have a couple of different (column) views in my Org file, for
example:
- one (public) view with the estimated time only
- another one (private, I mean not exported) with the real clocked time
I thought about setting the columns I wish to display in the corresponding
sections... but it appears that the column specification that's taken into
account must be defined where the tasks are (file-wide, or in the Tasks
subtree) -- not where the table will be generated.
This, by no way, is a bug: nobody said it should be working the way I'd like
it to be working right now.
Though, I have the impression the current way is quite limiting.
But my question is simply: do you have any idea for a way to work around this?
In the following ECM, you see (on purpose) that PRIOR is displayed in both
columns, while only set in the PROPERTY of the Tasks subtree.
Best regards,
Seb
--8---cut here---start-8---
#+TITLE: Effort vs Estimate
#+AUTHOR:Seb Vauban
* Tasks
:PROPERTIES:
:ID: 49380c04-9b6e-4298-aff8-d936d9679d8e
:COLUMNS: %6TODO %66ITEM(Task) %6Effort(Estim.){:}
:END:
** TODO A
*** TODO A1
:PROPERTIES:
:Effort: 12:00
:END:
:LOGBOOK:
CLOCK: [2012-03-01 Thu 09:00]--[2012-03-01 Thu 17:00] = 8:00
CLOCK: [2012-03-02 Fri 09:00]--[2012-03-02 Fri 17:00] = 8:00
CLOCK: [2012-04-05 Thu 09:00]--[2012-04-05 Thu 12:45] = 3:45
CLOCK: [2012-04-16 Mon 09:00]--[2012-04-16 Mon 14:45] = 5:45
:END:
*** TODO A2
:PROPERTIES:
:Effort: 24:00
:END:
** TODO B
:PROPERTIES:
:Effort: 1:00
:END:
:LOGBOOK:
CLOCK: [2012-03-01 Thu 09:00]--[2012-03-01 Thu 09:30] = 0:30
:END:
* Budget estimate
:PROPERTIES:
:COLUMNS: %66ITEM(Task) %6Effort(Estim.){:}
:END:
We have estimated the budget as follows:
#+tblname: dblock-tasks
#+BEGIN: columnview :hlines 1 :id 49380c04-9b6e-4298-aff8-d936d9679d8e
:maxlevel 3
| TODO | Task| Estim. |
|--+-+|
| | * Tasks | 37:00 |
| TODO | ** A| 36:00 |
| TODO | *** A1 | 12:00 |
| TODO | *** A2 | 24:00 |
| TODO | ** B| 1:00 |
#+END:
* Worked hours :noexport:
:PROPERTIES:
:COLUMNS: %66ITEM(Task) %6CLOCKSUM(Time) %6Effort(Estim.){:}
:END:
We have worked that much, and can compare with what had been estimated:
#+tblname: dblock-tasks
#+BEGIN: columnview :hlines 1 :id 49380c04-9b6e-4298-aff8-d936d9679d8e
:maxlevel 3
| TODO | Task| Estim. |
|--+-+|
| | * Tasks | 37:00 |
| TODO | ** A| 36:00 |
| TODO | *** A1 | 12:00 |
| TODO | *** A2 | 24:00 |
| TODO | ** B| 1:00 |
#+END:
--8---cut here---end---8---
--
Sebastien Vauban
Re: [O] [babel] [bug?] create graph in R
Nick Dokos nicholas.do...@hp.com wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: Hi Rainer, Rainer M Krug wrote: I am irritated - shouldn't the following create a pdf? #+begin_src R :results file :file sustEconOnlyNonRec.pdf :session R plot(runif(100)) #+end_src I am getting no error messages in the R console, nothing in the messages? I'm not using R -- yet! --, so I'm not sure about the following, but please check whether you must write: #+begin_src R :results file :file sustEconOnlyNonRec.pdf or #+begin_src R :results graphics :file sustEconOnlyNonRec.pdf I've lost track of all these header arguments and their possible values: are they documented somewhere (other than the mailing list)? AFAICT, they are not in the manual. To answer the question: on Worg http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html and other such language pages. Sorry for the noise. Nick
Re: [O] Sticky agenda branch merged
Hi Rainer, At Tue, 17 Apr 2012 15:23:00 +0200, Rainer Stengele wrote: Am 17.04.2012 14:29, schrieb Max Mikhanosha: At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file 2. I don't understand the TODO state changes as expected part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? I have set org-clock-in-switch-to-state to INARBEIT state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state INARBEIT and doing a clockin, the CLOCK: line appears. 3. Are sticky agendas enabled? YES! 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with g or r key? it is not from agenda 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Let me see: no, problem occurs with or without sticky agendas So far this looks to me as its unrelated to sticky changes, could you by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 which is 1 before sticky merge , and see if same scenario is broken there? The git commands to do it (ignore if your git-fu is strong) git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 .. test .. git checkout master .. back to normal .. Regards, Max
Re: [O] Sticky agenda branch merged
Hi Max, I'll try later. What I just found: being in a sticky agenda and trying v r I get this error which was not there before the merge: org-agenda-check-type: Not allowed in nil-type agenda buffers. Actually v c directly before entering v r gave results! Thanks, Rainer Am 17.04.2012 17:32, schrieb Max Mikhanosha: Hi Rainer, At Tue, 17 Apr 2012 15:23:00 +0200, Rainer Stengele wrote: Am 17.04.2012 14:29, schrieb Max Mikhanosha: At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file 2. I don't understand the TODO state changes as expected part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? I have set org-clock-in-switch-to-state to INARBEIT state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state INARBEIT and doing a clockin, the CLOCK: line appears. 3. Are sticky agendas enabled? YES! 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with g or r key? it is not from agenda 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Let me see: no, problem occurs with or without sticky agendas So far this looks to me as its unrelated to sticky changes, could you by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 which is 1 before sticky merge , and see if same scenario is broken there? The git commands to do it (ignore if your git-fu is strong) git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 ... test .. git checkout master ... back to normal .. Regards, Max
[O] BUG: Agenda clock related v for multi-block agendas
At Tue, 17 Apr 2012 17:58:27 +0200, Rainer Stengele wrote: What I just found: being in a sticky agenda and trying v r I get this error which was not there before the merge: org-agenda-check-type: Not allowed in nil-type agenda buffers. Actually v c directly before entering v r gave results! Investigating this showed it's not related to sticky agendas, but uncovered the following bug. Clock related sub-functions of the v key, have a check that they could only be done in the time related agenda buffers, as opposite to the ones generated by C-c a t For multi-block agendas, that include a an agenda block followed by several todo blocks, you can only invoke v c or v r when point is in the daily agenda block area, instead of tags or todo block area. Interestingly enough the block separator line (the ) has agenda type text property of nil, so you only get the type nil message when you do v r or v c with point on the separator line. Regards, Max
Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode
Ho Marius Marius Hofert marius.hof...@math.ethz.ch writes: There was another crash this morning, here is the report (as from Console.app): Process: Emacs [6378] Path:/Applications/Emacs.app/Contents/MacOS/Emacs Identifier: org.gnu.Emacs Version: Version 24.0.95 (9.0) Code Type: X86-64 (Native) Parent Process: launchd [117] Date/Time: 2012-04-17 11:57:41.796 +0200 OS Version: Mac OS X 10.7.3 (11D50) Report Version: 9 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGABRT) Exception Codes: KERN_INVALID_ADDRESS at 0x0018 VM Regions Near 0x18: -- __TEXT 0001-000100203000 [ 2060K] r-x/rwx SM=COW /Applications/Emacs.app/Contents/MacOS/Emacs Application Specific Information: objc[6378]: garbage collection is OFF abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib0x7fff9801a82a __kill + 10 1 org.gnu.Emacs 0x0001000a824b fatal_error_signal + 347 2 libsystem_c.dylib 0x7fff981cecfa _sigtramp + 26 3 libsystem_kernel.dylib0x7fff9801ace2 __pthread_kill + 10 4 libsystem_c.dylib 0x7fff9817c7d2 pthread_kill + 95 5 libsystem_c.dylib 0x7fff9816da7a abort + 143 6 org.gnu.Emacs 0x000100191f41 ns_term_shutdown + 81 7 org.gnu.Emacs 0x0001000a8217 fatal_error_signal + 295 8 libsystem_c.dylib 0x7fff981cecfa _sigtramp + 26 9 libobjc.A.dylib 0x7fff9a22d3af objc_msgSend_vtable14 + 47 10 org.gnu.Emacs 0x000100196268 x_free_frame_resources + 216 11 org.gnu.Emacs 0x0001001963e9 x_destroy_window + 25 12 org.gnu.Emacs 0x0001000115bc delete_frame + 828 13 org.gnu.Emacs 0x000100123c55 Ffuncall + 1125 14 org.gnu.Emacs 0x00010011fff6 Fcall_interactively + 6374 15 org.gnu.Emacs 0x000100123c42 Ffuncall + 1106 16 org.gnu.Emacs 0x000100123e26 call3 + 38 17 org.gnu.Emacs 0x0001000bc16e command_loop_1 + 1134 18 org.gnu.Emacs 0x000100122285 internal_condition_case + 293 19 org.gnu.Emacs 0x0001000b1787 command_loop_2 + 55 20 org.gnu.Emacs 0x000100122389 internal_catch + 217 21 org.gnu.Emacs 0x0001000b1f0c recursive_edit_1 + 364 22 org.gnu.Emacs 0x0001000b2082 Frecursive_edit + 290 23 org.gnu.Emacs 0x0001000a8f4e main + 3262 24 org.gnu.Emacs 0x000122f4 start + 52 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib0x7fff9801b7e6 kevent + 10 1 libdispatch.dylib 0x7fff931885be _dispatch_mgr_invoke + 923 2 libdispatch.dylib 0x7fff9318714e _dispatch_mgr_thread + 54 Thread 2: 0 libsystem_kernel.dylib0x7fff9801b192 __workq_kernreturn + 10 1 libsystem_c.dylib 0x7fff9817c594 _pthread_wqthread + 758 2 libsystem_c.dylib 0x7fff9817db85 start_wqthread + 13 Thread 3: 0 libsystem_kernel.dylib0x7fff9801b192 __workq_kernreturn + 10 1 libsystem_c.dylib 0x7fff9817c594 _pthread_wqthread + 758 2 libsystem_c.dylib 0x7fff9817db85 start_wqthread + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x rbx: 0x0006 rcx: 0x7fff5fbfe628 rdx: 0x rdi: 0x18ea rsi: 0x0006 rbp: 0x7fff5fbfe660 rsp: 0x7fff5fbfe628 r8: 0x0001 r9: 0x0010 r10: 0x7fff9801ad0a r11: 0xff80002d8220 r12: 0x0006 r13: 0x00010058a688 r14: 0x7fff7f356960 r15: 0x00010058a79c rip: 0x7fff9801a82a rfl: 0x0202 cr2: 0x7fff7f34da28 Logical CPU: 0 Binary Images: 0x1 -0x100202fef +org.gnu.Emacs (Version 24.0.95 - 9.0) 7C48528A-6CE3-F9D3-AECA-8F5120471764 /Applications/Emacs.app/Contents/MacOS/Emacs 0x100b29000 -0x100b2dff7 libFontRegistryUI.dylib (??? - ???) 46FDC6A3-EF17-3E57-AACD-8B36AB1F00E9 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Resources/libFontRegistryUI.dylib 0x100e69000 -0x100e6ffef libcldcpuengine.dylib (1.50.69 - compatibility 1.0.0) C0C4CC37-F2FD-301C-A830-EC54D86612D5 /System/Library/Frameworks/OpenCL.framework/Libraries/libcldcpuengine.dylib 0x100e76000 -0x100e79ff7 libCoreFSCache.dylib (???
Re: [O] Sticky agenda branch merged
Am 17.04.2012 17:32, schrieb Max Mikhanosha: Hi Rainer, At Tue, 17 Apr 2012 15:23:00 +0200, Rainer Stengele wrote: Am 17.04.2012 14:29, schrieb Max Mikhanosha: At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file 2. I don't understand the TODO state changes as expected part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? I have set org-clock-in-switch-to-state to INARBEIT state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state INARBEIT and doing a clockin, the CLOCK: line appears. 3. Are sticky agendas enabled? YES! 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with g or r key? it is not from agenda 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Let me see: no, problem occurs with or without sticky agendas So far this looks to me as its unrelated to sticky changes, could you by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 which is 1 before sticky merge , and see if same scenario is broken there? The git commands to do it (ignore if your git-fu is strong) git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 .. test .. git checkout master .. back to normal .. Regards, Max Hi Max, I just tested. The missing CLOCK: entry is unrelated to your merge. It also appears in 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 So this must be related to another change. Can anyone confirm? Sorry and thanks you for the work on the sticky agendas! Regards, Rainer
Re: [O] [babel] eval code only once :eval once
Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Hi Thomas, Thomas S. Dye wrote: Torsten Wagner torsten.wagner-re5jqeeqqe8avxtiumw...@public.gmane.org writes: I started to use lisp (as well as other) code blocks more and more to modify my work environment (emacs) for a particular (buffer-based) task. That is I change some variables, add some stuff etc. A real world example is for example the section below * Set-up :nonexport: #+source: setup-minted #+begin_src emacs-lisp :exports none :results silent (setq org-export-latex-listings 'minted) (setq org-export-latex-custom-lang-environments '( (emacs-lisp common-lispcode) )) (setq org-export-latex-minted-options '((frame lines) (fontsize \\scriptsize) (linenos ))) (setq org-latex-to-pdf-process '(pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f)) #+end_src This are settings from worg, which I use only during my work on that particular file/buffer e.g. to modify the export of the following beamer presentation. Whenever I load the buffer I jump to set-up and hit C-c C-C to execute it once. After that exports will do what I want. If I would change the above to :exports results and :results silent I would be asked to execute the code block on every export. Thanks to the new auto completion feature, I came across :eval and wonder if it makes sense to add :eval once and :eval once-query Which would allow to execute it only once (with query) if not called before and otherwise keeps quite. That would make *Set-up blocks much more efficient. Was thinking why there is no 'no-query' resp. 'always' flag which would execute code blocks without query even if asked for it in general but that would be somehow against safety measures ;) Aloha Totti, Will :cache yes do what you want? I'd answer no, as this wouldn't be re-eval'ed the next time he opens that buffer. But...? Best regards, Seb Aloha Seb, Yes, you're right. Perhaps #+BIND: then, instead of a babel code block? Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Sticky agenda branch merged
Am 17.04.2012 12:09, schrieb Rainer Stengele: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer Hi Max, I found the culprit: (defun bh/mark-parent-tasks-started () Visit each parent task and change TODO states to STARTED (unless bh/mark-parent-tasks-started (when (equal state INARBEIT) (let ((bh/mark-parent-tasks-started t)) (save-excursion (while (org-up-heading-safe) (when (member (nth 2 (org-heading-components)) (list TODO INARBEIT WARTEN)) (org-todo INARBEIT (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started 'append) something seems to have changed conecerning the state variable. The function fails and stops the clockin process. Deactivating the hook brings back the right behaviour. Sorry for that. Bernt, that function of yours does seem to have stopped working? Thanks and regards, Rainer
Re: [O] [babel] [bug?] create graph in R
On Tuesday, April 17, 2012 at 7:46 AM Sebastien Vauban wrote: Hi Rainer, Rainer M Krug wrote: I am irritated - shouldn't the following create a pdf? #+begin_src R :results file :file sustEconOnlyNonRec.pdf :session R plot(runif(100)) #+end_src I am getting no error messages in the R console, nothing in the messages? I'm not using R -- yet! --, so I'm not sure about the following, but please check whether you must write: #+begin_src R :results file :file sustEconOnlyNonRec.pdf or #+begin_src R :results graphics :file sustEconOnlyNonRec.pdf Hi, Seb. Your suggestion produces what I take to be the desired output on my system: $ uname -a Linux mikehppc.gh.lan 3.3.1-5.fc16.x86_64 #1 SMP Tue Apr 10 19:56:52 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ emacs --version GNU Emacs 23.3.1 Copyright (C) 2011 Free Software Foundation, Inc. Org-mode version 7.8.03 (release_7.8.03.324.gc4b233) $ R --version R version 2.15.0 (2012-03-30) -- Mike
Re: [O] Sticky agenda branch merged
Rainer Stengele rainer.steng...@online.de wrote: Am 17.04.2012 12:09, schrieb Rainer Stengele: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer Hi Max, I found the culprit: (defun bh/mark-parent-tasks-started () Visit each parent task and change TODO states to STARTED (unless bh/mark-parent-tasks-started (when (equal state INARBEIT) (let ((bh/mark-parent-tasks-started t)) (save-excursion (while (org-up-heading-safe) (when (member (nth 2 (org-heading-components)) (list TODO INARBEIT WARTEN)) (org-todo INARBEIT (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started 'append) something seems to have changed conecerning the state variable. Presumably another victim of the variable renaming patches. Try renaming state to org-state and see if that works (untested, no promises). Nick The function fails and stops the clockin process. Deactivating the hook brings back the right behaviour. Sorry for that. Bernt, that function of yours does seem to have stopped working? Thanks and regards, Rainer
Re: [O] [babel] using babel for regression testing
Ilya Shlyakhter ilya_...@alum.mit.edu writes: Is there a babel command to do the following: evaluate all code blocks; for those for which the result is not yet recorded in the org file, record the result; for those for which the result was already recorded, compare the new result with the old result; flag blocks where there is a difference. thanks, ilya Hi ilya, No, the above workflow is not wrapped up in any existing single Babel function. If you wanted to implement this yourself you could do so with a custom emacs lisp function or perhaps more easily, you could either; 1. add one code block to the file which calls all other code blocks and performs the result comparison, or 2. you could do what we did when initially testing the Babel functionality, and include all of your tests in a single table along with the expected results, you can then use the `sbe' function from table formulas, to run all code blocks by evaluating the table. -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug: Footnotes badly positioned in HTML export [7.8.09 (release_7.8.09.234.g4a35)]
On 17/04/2012 09:48, Nicolas Goaziou wrote: Hello, Shaun Johnsonsh...@slugfest.demon.co.uk writes: The attached example org file (t.org) with two footnotes generates the attached HTML file (t.html). As you can see in the attached screenshot (t.png) the footnote placement is odd to say the least. This is a limitation from HTML exporter: it requires `org-footnote-section' being non-nil. Ah, ok, thanks. Is this documented? Shaun.
Re: [O] Sticky agenda branch merged
Am 17.04.2012 21:35, schrieb Nick Dokos: Rainer Stengele rainer.steng...@online.de wrote: Am 17.04.2012 12:09, schrieb Rainer Stengele: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer Hi Max, I found the culprit: (defun bh/mark-parent-tasks-started () Visit each parent task and change TODO states to STARTED (unless bh/mark-parent-tasks-started (when (equal state INARBEIT) (let ((bh/mark-parent-tasks-started t)) (save-excursion (while (org-up-heading-safe) (when (member (nth 2 (org-heading-components)) (list TODO INARBEIT WARTEN)) (org-todo INARBEIT (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started 'append) something seems to have changed conecerning the state variable. Presumably another victim of the variable renaming patches. Try renaming state to org-state and see if that works (untested, no promises). Nick The function fails and stops the clockin process. Deactivating the hook brings back the right behaviour. Sorry for that. Bernt, that function of yours does seem to have stopped working? Thanks and regards, Rainer Yep, org-state works. Sorry, I missed the renaming tale. Thanks a lot, Nick! Rainer
Re: [O] Sticky agenda branch merged
Rainer Stengele rainer.steng...@online.de writes: Am 17.04.2012 12:09, schrieb Rainer Stengele: Hi Max, I found the culprit: (defun bh/mark-parent-tasks-started () Visit each parent task and change TODO states to STARTED (unless bh/mark-parent-tasks-started (when (equal state INARBEIT) (let ((bh/mark-parent-tasks-started t)) (save-excursion (while (org-up-heading-safe) (when (member (nth 2 (org-heading-components)) (list TODO INARBEIT WARTEN)) (org-todo INARBEIT (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started 'append) something seems to have changed conecerning the state variable. The function fails and stops the clockin process. Deactivating the hook brings back the right behaviour. Sorry for that. Bernt, that function of yours does seem to have stopped working? Hi Rainer, I no longer use a STARTED state so I've dropped this function from my setup. I'll update the doc - thanks for the notification. Regards, Bernt
[O] broken link in online docs
Hi all, http://orgmode.org/manual/Tables.html#Tables has a link (see a href=../calc/index.html#TopCalc/a) that yields a 404. I know patches are preferred, but I don't know to what the link ought to point, so cannot fix the issue myself. Best, Brian vdB
Re: [O] [PATCH] Allow more control over inserted whitespace in capture templates
This patch is sitting on the patchwork server. It's not lost. http://patchwork.newartisans.com/project/org-mode/list/ -Bernt Toby Cubitt ts...@cantab.net writes: Was there any feedback on this patch, or did it get lost in the noise? At least for me, org-capture breaks the document heading layout by inserting incorrect amounts of whitespace. And there's no way to configure capture templates to make it work correctly. The patch I posted fixes this behaviour. (Or am I missing some already-existing way of doing this? See below for a detailed description of the problem.) Toby On Mon, Feb 13, 2012 at 01:26:09PM +0100, Toby Cubitt wrote: When capturing an item as a subheading, the capture template :empty-lines property is not sufficient to ensure the correct document layout is maintained after capturing. This patch fixes the capture behaviour to insert new subheadings immediately after the previous heading (rather than immediately before the next one). And it adds new :empty-lines-before and :empty-lines-after capture template properties. (I can split these two changes into separated patches, if desired.) When set, the new :empty-lines-before and :empty-lines-after properties take precedence over :empty-lines in determining the amount of whitespace to add before or after the captured item, respectively. Together, these changes allow the correct document layout to be achieved after capturing, without any manual editing. (Since the whole idea of org-capture is to rapidly capture new ideas or todos, having to manually edit whitespace after capturing to fix the document layout is far from ideal.) To give a more detailed example of why I think these changes are needed, consider for example an org-mode document in which headings are separated by two empty lines, and subheadings are separated by a single empty line. (This is a natural layout if one wants headings to be separated by whitespace when folded, but subheadings not to be separated when folded): * heading 1 ** subheading 1.1 ** subheading 1.2 * heading 2 ** subheading 2.1 Let's say I want add a captured item as a new subheading 1.3 under heading 1, preserving this layout structure. Then we need to add the new item immediately after subheading 1.2, inserting one empty line before and two empty lines after. There appears to be no way to do this using :empty-lines. In fact, the existing implementation adds the new capture item immediately *before* the *following* heading (heading 2 in this case), which seems to be altogether wrong, as it effectively forces two empty lines before the new item, regardless of the :empty-lines setting. Currently, setting :empty-lines to 0 leaves the document looking like this: * heading 1 ** subheading 1.1 ** subheading 1.2 ** subheading 1.3 * heading 2 ** subheading 2.1 whilst setting :empty-lines to 1 leaves the document looking like this: * heading 1 ** subheading 1.1 ** subheading 1.2 ** subheading 1.3 * heading 2 ** subheading 2.1 neither of which are likely to ever be what we want. With this patch, setting the new :empty-lines-before to 1 and :empty-lines-after to 2 results in the correct structure after capturing: * heading 1 ** subheading 1.1 ** subheading 1.2 ** subheading 1.3 * heading 2 ** subheading 2.1 I think this patch is largely orthogonal to the recent removing whitespace from new captures patch (currently in patchwork). That patch causes `whitespace-cleanup' to be called in the CAPTURE buffer before finalizing, which doesn't affect the additional whitespace inserted later on by the :empty-lines property. This patch allows more control over the latter, by providing a fairly simple extension of the existing :empty-lines property. Toby
[O] [beamer] What is the easiest way to inject latex code between block environments?
Hello!
I would like to explicitly define heights for columns that contain blocks to be
able to use \vfill [1] in-between blocks. And here comes the problem. I kind of
need to inject
#+latex: \vfill
before new block
** block2
but after \end{block} was emitted, not before. Is there an easy way to approach
that?
[1]
http://tex.stackexchange.com/questions/15244/why-does-vfill-not-work-inside-a-beamer-column
Mikhail
Re: [O] [beamer] What is the easiest way to inject latex code between block environments?
On Tue, Apr 17, 2012 at 8:08 PM, Mikhail Titov m...@gmx.us wrote:
Hello!
I would like to explicitly define heights for columns that contain blocks to
be able to use \vfill [1] in-between blocks. And here comes the problem. I
kind of need to inject
#+latex: \vfill
before new block
** block2
but after \end{block} was emitted, not before. Is there an easy way to
approach that?
Everything in org-mode gets treated as belonging to the parent
headline. I don't think there's an easy way to do this except by
tweaking the .tex file after export and re-compiling via LaTeX
directly.
I could be wrong, but I believe it's the same principle as why the
answer to these questions is No:
-- http://orgmode.org/worg/org-faq.html#closing-outline-sections
In other words... everything is always in some headline and what
you're trying to do is escape a headline to enter text in kind of a
no man's land. Sorry to say, I don't think it's possible.
Best regards,
John
[1]
http://tex.stackexchange.com/questions/15244/why-does-vfill-not-work-inside-a-beamer-column
Mikhail
Re: [O] [beamer] What is the easiest way to inject latex code between block environments?
On Tue, Apr 17, 2012 at 8:19 PM, John Hendy jw.he...@gmail.com wrote:
On Tue, Apr 17, 2012 at 8:08 PM, Mikhail Titov m...@gmx.us wrote:
Hello!
I would like to explicitly define heights for columns that contain blocks to
be able to use \vfill [1] in-between blocks. And here comes the problem. I
kind of need to inject
#+latex: \vfill
before new block
** block2
but after \end{block} was emitted, not before. Is there an easy way to
approach that?
Everything in org-mode gets treated as belonging to the parent
headline. I don't think there's an easy way to do this except by
tweaking the .tex file after export and re-compiling via LaTeX
directly.
I could be wrong, but I believe it's the same principle as why the
answer to these questions is No:
-- http://orgmode.org/worg/org-faq.html#closing-outline-sections
In other words... everything is always in some headline and what
you're trying to do is escape a headline to enter text in kind of a
no man's land. Sorry to say, I don't think it's possible.
Actually, I was picturing doing this in between /frames/, not blocks.
Since you're in a frame, you can just write the LaTeX syntax directly
inside of your frame headline?
---
* Frame 1
\begin{block}{Block 1}
stuff
\end{block}
\vfill
\begin{block}{Block 2}
more stuff
\end{block}
** Frame 2
--
What about that?
John
Best regards,
John
[1]
http://tex.stackexchange.com/questions/15244/why-does-vfill-not-work-inside-a-beamer-column
Mikhail
Re: [O] Bug in org-diary (Bad sexp)?
Rafael Villarroel rvf0...@gmail.com writes: I think there might be a bug related to the recent changes in the agenda code, since it has just appeared in the last days. The following are minimal steps: (Ubuntu 11.10, GNU Emacs 23.3.1 (i686-pc-linux-gnu, GTK+ Version 2.24.5) of 2011-08-14 on rothera, modified by Debian, Org version just pulled: Org-mode version 7.8.09 (release_7.8.09.230.gec7b)) With the following file, say simpleorg.el (setq debug-on-error t debug-on-signal nil debug-on-quit nil) (add-to-list 'load-path ~/Downloads/org-mode/lisp) (require 'org-install) and a ~/diary file containing only: %%(org-diary) - and starting with 'emacs -Q -l simpleorg.el' Then M-x diary gives: Bad sexp at line 1 in ~/diary: (org-diary) FWIW, using the tip from http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00702.html to go back to a previous state, I can confirm that commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 is good and that commit 973efcd9c9f5a29ffc9db2c317fab44112a97b07 introduced the error described above.
Re: [O] [beamer] What is the easiest way to inject latex code between block environments?
On Apr 17, 2012, at 8:23 PM, John Hendy jw.he...@gmail.com wrote:
On Tue, Apr 17, 2012 at 8:19 PM, John Hendy jw.he...@gmail.com wrote:
On Tue, Apr 17, 2012 at 8:08 PM, Mikhail Titov m...@gmx.us wrote:
Hello!
I would like to explicitly define heights for columns that contain blocks
to be able to use \vfill [1] in-between blocks. And here comes the problem.
I kind of need to inject
#+latex: \vfill
before new block
** block2
but after \end{block} was emitted, not before. Is there an easy way to
approach that?
Everything in org-mode gets treated as belonging to the parent
headline. I don't think there's an easy way to do this except by
tweaking the .tex file after export and re-compiling via LaTeX
directly.
That is how I'm proceeding now as I don't have time to hack now:(
I could be wrong, but I believe it's the same principle as why the
answer to these questions is No:
-- http://orgmode.org/worg/org-faq.html#closing-outline-sections
I wonder if a special case can be made via some extra property and some changes
to orgmode code (or with hooks?). It should be possible as I need just quite
specific command and not arbitrary text embedded.
In other words... everything is always in some headline and what
you're trying to do is escape a headline to enter text in kind of a
no man's land. Sorry to say, I don't think it's possible.
Actually, I was picturing doing this in between /frames/, not blocks.
That is how beamerposter is organized.
Since you're in a frame, you can just write the LaTeX syntax directly
inside of your frame headline?
I was trying to escape to orgmode from plain latex not to return that far back
;)
M
