emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Adding user-defined task state for agenda
Date: Thu, 29 Oct 2015 16:17:23 -0400	[thread overview]
Message-ID: <6sw6c7a8r1a0q4.fsf@pfdstudio.com> (raw)

Kyle Meyer <kyle@kyleam.com> writes:

> Peter Davis <pfd@pfdstudio.com> writes:
>
> [...]
>
>> Hmmm. It worked in the minimal case, but still doesn't work in my
>> normal environment.
>
> Well that gives you something to go on.  I'd recommend looking for parts
> of your normal Org configuration that seem like they could affect this
> and dumping small bits into the minimal config from above to see if any
> result in NOTE not being listed.
>
>   $ emacs -Q -l <minconfig> --visit /tmp/test.org -f org-todo-list   
>
> Or, if nothing stands out to you as suspicious, you could use a binary
> search approach, similar to what git bisect does.  But the details of
> doing that would depend on how your config files are organized.

Thanks, Kyle. I just tried saving one of my "real" org files as test.org, and repeated the experiment with the minimal config, and
it FAILED ... the NOTE headings did not show up.

I also tried saving the simple test.org file in my regular org files folder, and it FAILED again.

So I can't isolate either the emacs setup file or the org file itself.

-pd

             reply	other threads:[~2015-10-29 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 20:17 Peter Davis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-29 19:19 Adding user-defined task state for agenda Peter Davis
2015-10-29 19:49 ` Kyle Meyer
2015-10-29 17:18 Peter Davis
2015-10-29 18:53 ` Kyle Meyer
2015-10-29 16:04 Peter Davis
2015-10-29 16:28 ` Kyle Meyer
2015-10-29 15:37 Peter Davis
2015-10-29 15:50 ` Kyle Meyer

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=6sw6c7a8r1a0q4.fsf@pfdstudio.com \
    --to=pfd@pfdstudio.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    /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).