From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] org-agenda: Add 'none setting for org-agenda-overriding-header Date: Sun, 10 Sep 2017 14:32:41 +0200 Message-ID: <87k216zqc6.fsf@nicolasgoaziou.fr> References: <87k22416un.fsf@alphapapa.net> <87bmnep8yz.fsf@nicolasgoaziou.fr> <8760dmynkk.fsf@alphapapa.net> <871so9nt04.fsf@nicolasgoaziou.fr> <87pobrc5vp.fsf@alphapapa.net> <87wp5yir25.fsf@nicolasgoaziou.fr> <87a82rkqmf.fsf@alphapapa.net> <8760dfko9f.fsf@alphapapa.net> <87lgma1xgj.fsf@nicolasgoaziou.fr> <87efrphle7.fsf@alphapapa.net> <87wp5h1qxc.fsf@nicolasgoaziou.fr> <87mv6ceets.fsf@alphapapa.net> <87shg0axf6.fsf@nicolasgoaziou.fr> <87tw0fcu0j.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dr1Pp-0004TP-27 for emacs-orgmode@gnu.org; Sun, 10 Sep 2017 08:32:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dr1Po-0003qA-0s for emacs-orgmode@gnu.org; Sun, 10 Sep 2017 08:32:45 -0400 Received: from relay2-d.mail.gandi.net ([2001:4b98:c:538::194]:47365) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dr1Pn-0003pS-RO for emacs-orgmode@gnu.org; Sun, 10 Sep 2017 08:32:43 -0400 In-Reply-To: <87tw0fcu0j.fsf@alphapapa.net> (Adam Porter's message of "Wed, 06 Sep 2017 18:00:28 -0500") 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: Adam Porter Cc: emacs-orgmode@gnu.org Hello, Adam Porter writes: > I looked at that file and I see that it's pretty basic. There's a first step in everything. > I recently put together a sort of testing framework for > org-super-agenda that makes it pretty easy to develop and run > consistent tests on agendas: > > https://github.com/alphapapa/org-super-agenda/blob/master/test/test.el > > Would you be interested in a patch that adds something like that to Org? > It would make it easy to test specific agenda features, and I guess it > might help with your agenda rewrite. :) Thank you. I didn't try it, but AFAIU, it requires to learn some DSL to write tests. There are two possible issues: - the DSL does not cover all use cases, and therefore gets in the way; - the DSL implies overhead in writing tests, which is counterproductive. I didn't test your library, so I cannot tell if your system suffers from one of the items above. I'm merely pointing out my concerns. OTOH, I think we need proper tooling to write tests for Org agenda. Since you put some thought in it, do you think it is feasible to have something like this, albeit more lightweight (e.g., macros around regular Org code instead of a DSL)? If so, would you to give it a try? Regards, -- Nicolas Goaziou