From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Org-mode Habit with Varying Description Date: Tue, 28 Oct 2014 06:41:31 -0700 Message-ID: <87sii8wbuc.fsf@ericabrahamsen.net> References: <87ppdmfxre.fsf@enterprise.sectorq.net> <87zjcqz2f2.fsf@ericabrahamsen.net> <87egu1zk8k.fsf@konixwork.incubateur.ens-lyon.fr> <87zjcpfksm.fsf@ericabrahamsen.net> <878uk6nng6.fsf@enterprise.sectorq.net> <87tx2q7rt7.fsf@ericabrahamsen.net> <8738a8coih.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47041) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xj6wy-0004LN-0B for emacs-orgmode@gnu.org; Tue, 28 Oct 2014 09:36:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xj6ws-00018o-JZ for emacs-orgmode@gnu.org; Tue, 28 Oct 2014 09:36:39 -0400 Received: from plane.gmane.org ([80.91.229.3]:40026) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xj6ws-00018j-Cw for emacs-orgmode@gnu.org; Tue, 28 Oct 2014 09:36:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xj6wr-0000Nr-F9 for emacs-orgmode@gnu.org; Tue, 28 Oct 2014 14:36:33 +0100 Received: from c-76-28-195-250.hsd1.wa.comcast.net ([76.28.195.250]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Oct 2014 14:36:33 +0100 Received: from eric by c-76-28-195-250.hsd1.wa.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 28 Oct 2014 14:36:33 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Hello, > > Eric Abrahamsen writes: > >> Right now it looks like the central "cond" statement in >> `org-add-log-setup' is as close as we've got to a canonical definition >> of where a heading's log list is to be found. Should I just write my own >> version of this, or would you be open to refactoring `org-add-log-setup' >> so the "finding" part is a separate function that can be reused >> elsewhere? > > Done, as `org-log-beginning'. Note that it will return a non-nil value > even if there is no log list in the entry. Very cool, thanks a lot! Eric