emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Change in appearance of org-todo-keywords
Date: Thu, 03 Aug 2017 20:54:40 +0100	[thread overview]
Message-ID: <87mv7g4ebj.fsf@yandex.com> (raw)
In-Reply-To: <87o9rwsdr1.fsf@alphapapa.net> (Adam Porter's message of "Thu, 03 Aug 2017 13:33:06 -0500")

Dear Adam,
>>>>> Adam Porter <adam@alphapapa.net> 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 using the
    > bug-hunter package.  It can bisect your init file and find the
    > lisp form that's causing it.

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 couple of recent
org-mode commits but to no avail.

Best wishes,

Colin.

-- 
--
Colin Baxter
m43cap@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

  reply	other threads:[~2017-08-03 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 16:42 Change in appearance of org-todo-keywords Colin Baxter
2017-08-03 18:33 ` Adam Porter
2017-08-03 19:54   ` Colin Baxter [this message]
2017-08-03 22:11     ` Adam Porter
2017-08-07  4:16 ` Josh Moller-Mara
2017-08-07  6:31   ` Colin Baxter
2017-08-07  9:39     ` Nicolas Goaziou
2017-08-07 10:18       ` Colin Baxter
2017-08-07 11:01       ` Josh Moller-Mara
2017-08-07 11:49         ` Colin Baxter
2017-08-07  9:31   ` Malcolm Purvis
2017-08-09 14:03 ` Colin Baxter
2017-08-09 17:00   ` Adam Porter
2017-08-10  9:04     ` Colin Baxter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mv7g4ebj.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).