From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: Is there a way to get all agenda TODOs programmatically? Date: Wed, 03 Jan 2018 09:48:19 -0600 Message-ID: <87bmibt03g.fsf@alphapapa.net> References: <87376v36up.fsf@mbork.pl> <87a813rqdx.fsf@fastmail.fm> <87r2ue29j8.fsf@mbork.pl> <874lrasxu2.fsf@fastmail.fm> <877et5joln.fsf@mbork.pl> <87shbqv58k.fsf@alphapapa.net> <87vagjffuq.fsf@mbork.pl> <87vagjtgom.fsf@alphapapa.net> <87po6rt76o.fsf@alphapapa.net> <874lo3f2p6.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWlHW-0000Gp-Qz for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 10:48:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWlHT-0001oS-MJ for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 10:48:42 -0500 Received: from [195.159.176.226] (port=55906 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWlHT-0001nN-Ew for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 10:48:39 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eWlFJ-0006oW-Bl for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 16:46:25 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Nicolas Goaziou writes: >> I have some more code you might find useful. I had an idea to take a >> different approach with my org-agenda-ng code (not using org-element to >> parse the whole buffer first), and it seems to be working well so far. > > Clearly, `org-element-parse-buffer' is not adequate for the task. When > buildings the agenda view, you're most probably interested in very > specific parts of the document, whereas Element tries to be as thorough > as possible. Right, so now I'm using outline-next-heading to go directly to headings. > I suggest even to not use any org-element-* function there. That may be the best option, however at the moment I'm using just org-element-headline-parser, which seems to work well. It avoids a lot of manual gathering of data in later functions, because they can just use the plist it creates, and it seems fast with a hacky search bound that prevents it from going too far past the headline. >> The code is here: >> >> https://github.com/alphapapa/org-agenda-ng/tree/non-element-parsing >> >> The code doesn't generate an identical result to the org-agenda code >> (not yet, anyway), but it's very similar. It lacks the agenda prefix >> feature and full application of agenda faces (it does do a few faces >> already). Most, if not all, text properties are applied. And of >> course, more work could be done to make it look more like an official >> agenda buffer. > > I don't want to sound offending, but your 400 locs library cannot > possibly be "very similar" to 10k locs org-agenda.el. Also, after > a cursory look, it is not clear how you solve the multi-days issue. > I.e., AFAIU, you still run multiple checks on the same entry. What I meant is, for my own very basic, one-day agenda view, it produces a similar-looking result--superficially, at least. Of course it does not support more than probably 5% of the features and settings org-agenda.el does, as it's barely more than a proof-of-concept. But maybe it would be helpful to Marcin for his idea. > Nevertheless, I think your approach is right. I think that, at some > point, we'll need to rewrite "org-agenda.el" from scratch, like we did > for "org-export.el" a few years back, so it becomes manageable again. In > the process, we definitely need to find a better replacement for > `org-agenda-skip', as done in your library. > > So, in a nutshell, I think you're doing a step in the right direction. > I hope Org can ultimately benefit from a better "org-agenda.el". Me too. I'm just exploring some ideas, not proposing this as a replacement. org-agenda.el has had hundreds, if not thousands, of hours put into it, and a full replacement would take as long to make.