Re: [O] Change in appearance of org-todo-keywords

Dear Adam, > "Adam" == Adam Porter writes: Adam> Colin Baxter writes: >> Considering how fundamental keywords and tags are to org-mode, >> I'm a little surprised that only two other users have reported >> the issue. Adam> It's

Re: [O] Change in appearance of org-todo-keywords

Colin Baxter writes: > Considering how fundamental keywords and tags are to org-mode, I'm a > little surprised that only two other users have reported the issue. It's because of the bravery of users like you that I don't run master. ;)

Re: [O] Change in appearance of org-todo-keywords

> Colin Baxter writes: > Hello, > 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

Re: [O] Change in appearance of org-todo-keywords

Dear Josh, > "Josh" == Josh Moller-Mara writes: Josh> Nicolas Goaziou writes: >> Hello, >> >> Colin Baxter writes: >> >>> Yes, you are correct. I can confirm that switching off >>>

Re: [O] Change in appearance of org-todo-keywords

Dear Nicolas, > "Nicolas" == Nicolas Goaziou writes: Nicolas> Hello, Colin Baxter writes: >> Yes, you are correct. I can confirm that switching off >> org-todo-state-tags-triggers removes the insertion of colons for >> me too.

Re: [O] Change in appearance of org-todo-keywords

Nicolas Goaziou writes: > Hello, > > Colin Baxter writes: > >> Yes, you are correct. I can confirm that switching off >> org-todo-state-tags-triggers removes the insertion of colons for me >> too. > > Fixed. Thank you. > Hello, ~org-toggle-tag~ now

Re: [O] Change in appearance of org-todo-keywords

Hello, Colin Baxter writes: > Yes, you are correct. I can confirm that switching off > org-todo-state-tags-triggers removes the insertion of colons for me > too. Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Change in appearance of org-todo-keywords

> "Josh" == Josh Moller-Mara writes: Josh> From what I can tell, doing something like (org-toggle-tag Josh> "sometag" 'off) produces these double colons. It seems to have to Josh> do with the way that org-split-string no longer returns nil, but Josh> returns (""). I'm also

Re: [O] Change in appearance of org-todo-keywords

Dear Josh, > "Josh" == Josh Moller-Mara writes: Josh> 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

Re: [O] Change in appearance of org-todo-keywords

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

Re: [O] Change in appearance of org-todo-keywords

Colin Baxter writes: > Thanks for the suggestion, but I think I may be missing something. My > emacs init has not changed. My org keyword settings have worked for a > few years satisfactorily - until that is today. I think I need to bisect > org-mode to find the case? I've

Re: [O] Change in appearance of org-todo-keywords

Dear Adam, > Adam Porter writes: > I don't mean this in a snide way, but do you keep your config in > version control? e.g. if you have it stored in git, you can > bisect it and find the change that caused the problem. > Other than that, you can probably

[O] Change in appearance of org-todo-keywords

Hello, 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

Re: [O] Change in appearance of org-todo-keywords

I don't mean this in a snide way, but do you keep your config in version control? e.g. if you have it stored in git, you can bisect it and find the change that caused the problem. Other than that, you can probably find the problem using the bug-hunter package. It can bisect your init file and