From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josh Moller-Mara Subject: Re: Change in appearance of org-todo-keywords Date: Mon, 07 Aug 2017 12:16:08 +0800 Message-ID: <87mv7cxbav.fsf@cns.nyu.edu> References: <87y3r0zjpx.fsf@yandex.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39902) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1deZSi-0001CM-Bl for emacs-orgmode@gnu.org; Mon, 07 Aug 2017 00:16:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1deZSf-0008T0-70 for emacs-orgmode@gnu.org; Mon, 07 Aug 2017 00:16:16 -0400 Received: from mail-pf0-x244.google.com ([2607:f8b0:400e:c00::244]:33563) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1deZSe-0008Sn-Vq for emacs-orgmode@gnu.org; Mon, 07 Aug 2017 00:16:13 -0400 Received: by mail-pf0-x244.google.com with SMTP id c65so7871166pfl.0 for ; Sun, 06 Aug 2017 21:16:12 -0700 (PDT) In-Reply-To: <87y3r0zjpx.fsf@yandex.com> 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: Colin Baxter , emacs-orgmode@gnu.org Colin Baxter writes: > As of today, TODO now appears with three sets of un-requested double > colons after it, as in TODO :: :: :: > > The behaviour doesn't occur with emacs -q, so the cause is presumably in > my ~/.emacs. I can't work out what's wrong with my org-todo-sequence, > which is: > > (setq org-todo-keywords (quote((sequence "TODO(t)" "STARTED(s)" > "NEXT(n@/!)" "WAITING(w@/!)" > "HOLD(h@/!)" "CANCELLED(c@/!)" > "PHONE(p)" "BREAK(b)" "MEETING(m)" "DONE(d@/!)" > )))) This is happening with me too. But I suspect it has more to do with org-todo-state-tags-triggers being set. I don't get the double colons if I don't set org-todo-state-tags-triggers. >From what I can tell, doing something like (org-toggle-tag "sometag" 'off) produces these double colons. It seems to have to do with the way that org-split-string no longer returns nil, but returns (""). Best, Josh