Samuel Wales writes:
> ok, better testcase below. please ignore last 2 messages.
>
> complete with code, data, explanation, and steps to reproduce.
Reproduced, and fixed. Thank you.
> comment: 4 d. ago: TODO COMMENT this one is possibly bad syntax
> comment: 4 d. ago: COMMENT TOD
ok, better testcase below. please ignore last 2 messages.
complete with code, data, explanation, and steps to reproduce.
* commented subtrees show in agenda even if org-agenda-skip-comment-trees is t
to reproduce, load the code below, find this file, put
restriction lock on this subtree (< at bo
oops, the previous test case file was wrong, but the code for -Q
reproduction was correct. here is a correct test case file:
* x
*** y
* TODO yes
DEADLINE: <2015-08-05 Wed>
* TODO COMMENT no
DEADLINE: <2015-08-05 Wed>
* asasasas
DEADLINE: <2015-08-05 Wed>
*** asdfasdfasdf
***
can anybody else reproduce?
* x
*** TODO yes
DEADLINE: <2015-08-05 Wed>
TODO COMMENT no
DEADLINE: <2015-08-05 Wed>
On 8/5/15, Samuel Wales wrote:
> 24.4.1
>
> can repro with -Q and this old testcase code and restriction lock and
> org-agenda-list.
>
> ===
>
> ;;;
> ;;;alpha-org-testcase.el
0 in outline
nil in agenda
On 8/8/15, Nicolas Goaziou wrote:
> What is the return value of (org-in-commented-heading-p) on your
> pseudo-commented headlines?
Samuel Wales writes:
> ok, then i don't understand the code. (i thought that was how it
> determined whether it was a commented headline to skip.) (it's nil
> but commented headers show.)
My bad. I misread your question. It should be non-nil, indeed.
What is the return value of (org-in-commen
On 8/7/15, Nicolas Goaziou wrote:
> Samuel Wales writes:
>> should (get-text-property (point-at-bol) :org-comment) be nil on a
>> commented headline?
>
> Yes, once `org-agenda-prepare-buffers' has been called.
ok, then i don't understand the code. (i thought that was how it
determined whether i
On 8/7/15, Nicolas Goaziou wrote:
> Samuel Wales writes:
>> should (get-text-property (point-at-bol) :org-comment) be nil on a
>> commented headline?
>
> Yes, once `org-agenda-prepare-buffers' has been called.
then i didn't understand the code. (i thought that was how it
determined whether it w
Samuel Wales writes:
> should (get-text-property (point-at-bol) :org-comment) be nil on a
> commented headline?
Yes, once `org-agenda-prepare-buffers' has been called.
Regards,
should (get-text-property (point-at-bol) :org-comment) be nil on a
commented headline?
On 8/6/15, Nicolas Goaziou wrote:
> I cannot reproduce it either. Did you try minimal example provided by
> Kyle in this thread? Does it show the "no" headline?
yes, i put the example into an entry, with odd levels only, in my
version of emacs as above, with my testcase as above, with -Q, and
res
Hello,
Samuel Wales writes:
> can repro with -Q and this old testcase code and restriction lock and
> org-agenda-list.
I cannot reproduce it either. Did you try minimal example provided by
Kyle in this thread? Does it show the "no" headline?
Regards,
--
Nicolas Goaziou
24.4.1
can repro with -Q and this old testcase code and restriction lock and
org-agenda-list.
===
;;;
;;;alpha-org-testcase.el
;;;
;;;minimal testcase for org
;;;
;;; dorg=your-org-dir delorgsrc=your-org-src-dir emacs -Q -l
alpha-org-testcase.el
;;;
;;;
;;;for my use i do this:
;;;
"
mep=t em
Samuel Wales wrote:
> git maint -> new git maint caused this.
>
> On 8/5/15, Samuel Wales wrote:
>> agenda shows them.
>>
>> org-agenda-skip-comment-trees is non-nil.
I can't reproduce this running emacs -Q with the current master
(b5f5d66) and Emacs 24.5.1 using the following test file as the
git maint -> new git maint caused this.
On 8/5/15, Samuel Wales wrote:
> agenda shows them.
>
> org-agenda-skip-comment-trees is non-nil.
15 matches
Mail list logo
