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 because of the bravery of users like you tha
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.
;)
> 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 what's wrong with my
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
>>> org-todo-state-tags-triggers removes the insertion of colons for
>>> me too.
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.
Nicolas> Fixed. Thank you.
Nicolas> R
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 seems to delete currently set tags for a hea
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
> "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 seeing this proble
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 -q, so the cause is
>> presumably i
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:
>
> (
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 tried reverting a coupl
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 find the problem usi
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 (quot
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 fi
14 matches
Mail list logo
