Re: [O] Custom todo-like thing in agenda?
On Sat, Aug 16, 2014 at 3:15 AM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote: Hi all, I was wondering whether something like this is possible. (Well, I'm pretty sure it is, what I don't know whether I'm competent enough to pull it off...) I'd like to be able to create a special agenda view (or block in a normal agenda, this shouldn't make much difference, since I may use block agenda instead of the usual C-c a a), in which the lines would behave much like TODOs, with the exception that their source would not be an Org file, but something else. One possible idea would be to check out org-weather-metno from https://github.com/ruediger/weather-metno-el -- RMS: I am not on vacation, but I am at the end of a long time delay. I am located somewhere on Earth, but as far as responding to email is concerned, I appear to be well outside the solar system.
Re: [O] Custom todo-like thing in agenda?
Hello Marcin, Marcin Borkowski wrote: I was wondering whether something like this is possible. (Well, I'm pretty sure it is, what I don't know whether I'm competent enough to pull it off...) I'd like to be able to create a special agenda view (or block in a normal agenda, this shouldn't make much difference, since I may use block agenda instead of the usual C-c a a), in which the lines would behave much like TODOs, with the exception that their source would not be an Org file, but something else. In my case, it would be a web todo-like service, with the possibility of extracting info (like the deadline and such) using some command-line curl invocation. Then, I could (rather easily, I guess) write some Elisp to parse this info, and (here the hard part - at least for me - begins) somehow insert it in the agenda buffer. Of course, I could also just generate an intermediate, temporary org file, using curl - parsing - buffer - save and include it in the agenda. This would most probably speed up the process of generating the agenda (which is a plus). However, I'd like another functionality: I'd like to have the `t' command to send some information to the web service I'm using. Where should I start? Is there anything even remotely similar to what I'm trying to achieve so that I could analyze its source, for instance? This seems interesting for sure. I don't have more knowledge than you on such a topic; however, if I had to really look into that, I'd start by taking a look at the following: - `org-debbugs.el' package from Michael Albinus - Bugzilla integration from John Wiegley (see https://gist.github.com/jwiegley/472120) HTH -- and please publish any step you make! Best regards, Seb -- Sebastien Vauban
Re: [O] Custom todo-like thing in agenda?
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Hello Marcin, Hi, - `org-debbugs.el' package from Michael Albinus ... which is meanwhile debbugs-org.el, part of the debbugs package on GNU ELPA. Best regards, Seb Best regards, Michael.
[O] Custom todo-like thing in agenda?
Hi all, I was wondering whether something like this is possible. (Well, I'm pretty sure it is, what I don't know whether I'm competent enough to pull it off...) I'd like to be able to create a special agenda view (or block in a normal agenda, this shouldn't make much difference, since I may use block agenda instead of the usual C-c a a), in which the lines would behave much like TODOs, with the exception that their source would not be an Org file, but something else. In my case, it would be a web todo-like service, with the possibility of extracting info (like the deadline and such) using some command-line curl invocation. Then, I could (rather easily, I guess) write some Elisp to parse this info, and (here the hard part - at least for me - begins) somehow insert it in the agenda buffer. Of course, I could also just generate an intermediate, temporary org file, using curl - parsing - buffer - save and include it in the agenda. This would most probably speed up the process of generating the agenda (which is a plus). However, I'd like another functionality: I'd like to have the `t' command to send some information to the web service I'm using. Where should I start? Is there anything even remotely similar to what I'm trying to achieve so that I could analyze its source, for instance? Is the intermediate org file idea a reasonable one (the more I think about it, the more I like it)? If I decide to go the intermediate-file way, where could I hook into the agenda generation, so that it is e.g. created only once each day (to save time) or on explicit demand (this part is easy, I guess - just some command to create it and a key in org-agenda-mode-map...)? Should I advise org-agenda or is there some hook run *before* agenda generation? Should I advise org-todo? (Just looking at its source made my head spin...) Should I use some hooks for the todo behavior I described? (I found org-trigger-hook and org-after-todo-state-change-hook; frankly, I don't really get why both are there... Sorry for being a bit vague - this is still a concept in a preliminary stage, and it's 4:07 am here;)... Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University
