Re: [Orgmode] BUG? starting org-agenda-list from .emacs
Carsten Dominik [EMAIL PROTECTED] writes: this happens because the command needs a variable that is set by the post-command-hook in the agenda buffer. Normally you are issuing a command to get to the buffer, so the hook is run. However, in your case no command has been called yet. As a work-around, just press d twice, or execute any command, like a cursor motion first. I will have this fixed in the next version, thanks for the report. Thanks. I've been using 'd' twice for a long time - I was just wondering if this (potentially missing setup) is possibly the cause of some of the other weird problems I've been seeing (like the font faces issue that still hasn't been resolved -- I still can't reliably reproduce this but it happens about once/day for me). Regards, Bernt ___ 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
Re: [Orgmode] BUG: column view in agenda -- marker does not point anywhere
Carsten Dominik [EMAIL PROTECTED] writes: So far I cannot reproduce this problem. One helpful thing would be to post a full backtrace, made with uncompiled org.el that will tell me exactly which function tries to use an undefined marker. How do I generate a debug backtrace again? I tried finding this on the list but failed :( BTW, I guess your file starts with an empty line, to get column view for the entire file? Or do you call it in one of those headlines? If yes why do yoou need down to get to the task? No there is no blank line at the top of the file. I used boxquote-insert-file without touching the result. I can't use a blank line in my regular (huge) org files because column view seems to go into an infinite loop sometimes (or I never waited long enough for it to finish) ___ 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
Re: [Orgmode] BUG: column view in agenda -- marker does not point anywhere
Bernt Hansen said unto the world upon 21/01/08 08:32 AM: Carsten Dominik [EMAIL PROTECTED] writes: So far I cannot reproduce this problem. One helpful thing would be to post a full backtrace, made with uncompiled org.el that will tell me exactly which function tries to use an undefined marker. How do I generate a debug backtrace again? I tried finding this on the list but failed :( http://orgmode.org/manual/Feedback.html#Feedback Best, Brian vdB ___ 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
Re: [Orgmode] BUG: column view in agenda -- marker does not point anywhere
Bernt Hansen [EMAIL PROTECTED] writes: Carsten Dominik [EMAIL PROTECTED] writes: So far I cannot reproduce this problem. One helpful thing would be to post a full backtrace, made with uncompiled org.el that will tell me exactly which function tries to use an undefined marker. How do I generate a debug backtrace again? I tried finding this on the list but failed :( (setq debug-on-error t) In case you've lost the backtrace buffer, its name is *Backtrace*. -- Bastien ___ 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
Re: [Orgmode] TODO dependencies
Hi I am curious why I never got any feedback on this implementation of task dependencies. Did people overlook this? Or is the need for dependencies not as pressing as some of you thought? - Carsten On Oct 19, 2007, at 8:27 AM, Carsten Dominik wrote: On Oct 11, 2007, at 16:46, Carsten Dominik wrote: - concerning the TRIGGER proposal by John, and the TRIGGER/BLOCKER functionality discussed later: In Emacs terms, this seems to translate into a *hook* that is called at the right moment. I'd say that a single hook is enough. The right moment to call it would be when Org-mode has figured out everything about a change that is about to occur, but before actually doing it. We can be general what kind of change this could be, a TODO state change, adding a tag, setting a property, changing the priority, anything really. So we would have a property that contains a Lisp form, and that lisp form would be evaluated at that moment. TRIGGER would then mean to perform actions in other entries. BLOCKER would mean to query other entries for information, and, if necessary, abort the current action, for example by throwing to a specified catch form. Obviously, if you nee both triggers and blockers, the blockers need to run first, but we don't need separate properties/functions for this. The detailed implementation would then be a number of Lisp functions that take as arguments a *single* structure that contains all the info of the change, for example a property list like (list :type 'TODOSTATE :from nil %to INPROGRESS Due to the controversial nature of the discussion on this subject, it seems to be better, for the time being, to keep this functionality outside the core of org-mode. Other reasons for this are that the free-form nature of Org-mode files do make it non-trivial to implement dependencies in a bullet-proof way. I will actually take still another step back from the proposals we discussed: I'd like to not even fix the properties that should be used for dependencies. Instead, I am proposing and starting up the following route: Org-mode version 5.13 contains two new hooks, `org-blocker-hook' and `org-trigger-hook'. These hooks are called before and after a state change, respectively. Currently only TODO state changes will do this, but more could be added in the future. The blocker hook is able to block a state change, the trigger hook just happens after the change. This is all that will go into the core for now. While this may seem little, it actually opens the dore wide for a number of dependency extensions to be written, with free choice of properties to be used and the language applied in these properties to describe dependencies. In this way we can have different implementations working alongside without conflicts. As a proof of concept, I am providing a small file org-depend.el. This is not meant as a definition of how things should be, but as an inspiration to people who want to try their teeth at this. Nevertheless, this small set of functions already does most of what at least some of you have been asking for: It introduces the concept of chaining a sequence of TODO entries together by insinuating only the first entry in the chain. It also allows for entries to be identified by an :ID: property, and this property to be used to trigger or be blocked by entries in arbitrary places in the current file. So I hope it will be a good starting point, I have tried to comment it well enough so that hacking should be easy. Here is a copy of the documentation from that file. The file itself is available at http://orgmode.el/org-depend.el. - Carsten ---8 8-- WARNING: This file is just a PROOF OF CONCEPT, not a supported part of Org-mode. This is an example implementation of TODO dependencies in Org-mode. It uses the new hooks in version 5.13 of Org-mode, `org-trigger-hook' and `org-blocker-hook'. It implements the following: Triggering -- 1) If an entry contains a TRIGGER property that contains the word chain-siblings, then switching that entry to DONE does the following: - The sibling following this entry is marked DONE. - The sibling also get the chain-sibling property, to make sure that, when *it* is DONE, the chain will continue. 2) If the TRIGGER property contains any other words, these are treated as entry id's. That means, Org-mode will search for an entry with the ID property exactly equal to this word, and switch that entry to TODO as well. Blocking 1) If an entry contains a BLOCKER property that contains the word previous-sibling, the sibling above the current entry is checked. If it is still in a TODO state, the current state change is blocked. 2) If the BLOCKER property contains any other words, these are treated as entry id's. That means, Org-mode will search for an entry with the ID property exactly
Re: [Orgmode] one TODO for multiple projects
On Jan 18, 2008, at 5:45 PM, Erik Colson wrote: Hi, I'm thinking about moving from planner to org-mode. Particularly for the outline and better file formatting. I've been reading through the doc and I'm missing a feature of planner. In planner we can create a todo which can be bound to multiple projects. So if it is marked completed in one project it is also in the other projects. Can this be done in org-mode ? Not in a similar way like in Planner. However, you could set up an outline subtree with such general tasks ad then, in the projects, have links to those tasks. - Carsten ___ 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
Re: [Orgmode] Documentation request
Hi Adam and all others From time to time my emails don't reach the list. Maybe I made a mistake and sent my answer to Adam personally this afternoon. Adam Spiers [EMAIL PROTECTED] writes: Your request is right on the money; in fact Bastien's already ahead of you - http://search.gmane.org/search.php?group=gmane.emacs.orgmodequery=worg In fact, I didn't realize that worg is exactly for that purpose. A good idea, although the Name reminds me on the MAD Magazine ;-) Thank you very much, Bastien. I will send you my request for registration soon. Greetings Sven pgpiSXWzx7f96.pgp Description: PGP signature ___ 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
Re: [Orgmode] TODO dependencies
On Mon, Jan 21, 2008 at 03:43:18PM +0100, Carsten Dominik wrote: Hi I am curious why I never got any feedback on this implementation of task dependencies. Did people overlook this? Or is the need for dependencies not as pressing as some of you thought? I guess maybe not. Or maybe we all have an entry in our TODO lists ** BLOCKED implement automatic unblocking upon dependency completion *** DONE read Carsten's reply ;-) ___ 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
Re: [Orgmode] TODO dependencies
On Jan 21, 2008, at 6:43 PM, Adam Spiers wrote: On Mon, Jan 21, 2008 at 03:43:18PM +0100, Carsten Dominik wrote: Hi I am curious why I never got any feedback on this implementation of task dependencies. Did people overlook this? Or is the need for dependencies not as pressing as some of you thought? I guess maybe not. Or maybe we all have an entry in our TODO lists ** BLOCKED implement automatic unblocking upon dependency completion *** DONE read Carsten's reply LoL! - Carsten ___ 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
[Orgmode] FR: multiple or repeating active timestamps in agenda
Hello! I'm getting to the point of actually using org for organization (as opposed to using it for note taking and publishing and procrastination). Currently, when a repeated task is marked as done, it shows up again in the agenda on the date of the next occurrence of the task as long as the task is scheduled or has a deadline. I'd like to request two additions to this behavior. First, would it be possible to add this same feature for active timestamps that don't occur in a SCHEDULED or DEADLINE line? I follow the advice in the manual and don't use SCHEDULED for meetings, but I do have some recurring meetings. So, for the following entry: --8---cut here---start-8--- * Standing Appointments ** TODO Meeting with Mike 2008-01-23 Wed 10:00-11:30 +1w --8---cut here---end---8--- I'd like to be able to mark it as done every week, without needing it to be SCHEDULED or have a DEADLINE. Currently, the first time I mark it as done, all past and future repetitions are also marked as done. Second, for some events with only a few repetitions I create multiple active timestamps within one entry instead of using a repeating timestamp. So, for example, I have an entry like: --8---cut here---start-8--- * Standing Appointments ** TODO Swing III 2008-01-21 Mon 19:30-21:30 2008-01-28 Mon 19:30-21:30 2008-02-04 Mon 19:30-21:30 --8---cut here---end---8--- Given that we can't combine repetition intervals with date ranges (or can we?), would it be possible to add a new behavior to deal with this case? When a TODO entry contains multiple time stamps, all of them would show up in the agenda as TODO items. Marking the item as done would use the same logic used for dealing with repeaters, and would continue to include the next active timestamp in the agenda as a TODO. In the past I have dealt with this second case by adding more structure to the task: --8---cut here---start-8--- * Standing Appointments ** Swing III *** TODO Week 1 2008-01-21 Mon 19:30-21:30 *** TODO Week 2 2008-01-28 Mon 19:30-21:30 *** TODO Week 3 2008-02-04 Mon 19:30-21:30 --8---cut here---end---8--- This gets the job done, but seems unnecessarily cluttered and redundant to me. Thanks for considering it, /au -- Austin Frank http://aufrank.net GPG Public Key (D7398C2F): http://aufrank.net/personal.asc pgpdcwEkCYgxQ.pgp Description: PGP signature ___ 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
Re: [Orgmode] Re: patch: link to the log of an ERC session
Phil Jackson [EMAIL PROTECTED] writes: [...] How about writing a little extension org-irc.el that extends the link mechanism for both cases? I'd love to see more such extensions, and I would be happy to distribute them with Org-mode, and to put them into Emacs if the papers are in order. Sure, I'll get a patch to you when I can. Please find attached a 'beta' of the plugin. If anyone could give it a quick test that would be great. It needs a little bit of re-factoring I think so I'll do that post critique. org-link-irc.el Description: application/emacs-lisp Phil -- Phil Jackson http://www.shellarchive.co.uk ___ 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
