emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] TODO [/] cookie not updating if list has inline task
Date: Sun, 17 May 2015 23:56:38 +0200	[thread overview]
Message-ID: <87pp5y7trd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87lhgnxc1r.fsf@gmx.us> (rasmus@gmx.us's message of "Sun, 17 May 2015 21:02:24 +0200")

Rasmus <rasmus@gmx.us> writes:

>> You shouldn't use `org-next-visible-heading' as statistics cookie
>> updates shouldn't depend on current visibility.
>
> That's why I used org-with-wide-buffer.

This is orthogonal. `o-w-w-b' is about narrowing. `o-n-v-h' ignores
inlinetasks.

> But perhaps a better solution would be an org-next-heading or
> whatever, that considered inlinetasks.

I'm not sure what you mean. `outline-next-heading'?

>> Also, the problem is more subtle: you have to check if you're within an
>> inlinetask, in which case you don't want to use
>> `org-with-limited-levels' or not.
>
> Is that saying that org-with-wide-buffer is no good here?

I'm saying `org-next-visible-heading', or, more precisely,
`org-with-limited-levels' is no good here. See `org-get-property-block'
for an example.


Regards,

next prev parent reply	other threads:[~2015-05-17 21:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17 11:22 [bug] TODO [/] cookie not updating if list has inline task Eric S Fraga
2015-05-17 13:08 ` Eric S Fraga
2015-05-17 13:23   ` Eric S Fraga
2015-05-17 13:32     ` Rasmus
2015-05-17 13:51 ` Rasmus
2015-05-17 18:26   ` Eric S Fraga
2015-05-17 18:27   ` Eric S Fraga
2015-05-17 18:51   ` Nicolas Goaziou
2015-05-17 19:02     ` Rasmus
2015-05-17 21:56       ` Nicolas Goaziou [this message]
2015-05-20  8:26         ` e.fraga
2015-06-09 15:09           ` Nicolas Goaziou
2015-06-11 14:40             ` e.fraga
2015-05-17 19:28     ` Eric S Fraga
2015-05-17 19:44       ` Rasmus
2015-05-17 22:05         ` Nicolas Goaziou
2015-05-18  8:16         ` Eric S Fraga

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=87pp5y7trd.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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

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).