From: Ihor Radchenko <yantar92@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-back-to-heading with inline tasks above point [9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/)]
Date: Tue, 06 Nov 2018 11:05:54 +0800 [thread overview]
Message-ID: <87va5a9a7h.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87a7mn8crw.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
Thanks!
Did not know about `org-with-limited-levels'.
After reading the function docstring again, I see that it behaved
correctly.
However, it seems that `org-back-to-heading' is not really used
according to the docstring in the org source code:
- `org-agenda' with subtree restriction: the results are different if
you call it below or above an inline task.
- `org-attach', `org-attach-dir', `org-attach-tag', with point
below/above an inline task behave differently
- the following functions from org.el behave depending on the point
position (below or above an inline task):
`org-entry-beginning-position', `org-entry-end-position',
`org-get-heading', `org-get-entry',
`org-insert-heading-after-current', `org-promote', `org-demote',
`org-move-subtree-down', etc.
Some of the functions above give very unexpected results if the point
is below an inline task.
Would it make sense to add org specific macros to Hacking section of org
manual?
It is sometimes difficult to guess that some of these macros even exist.
Best,
Ihor
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hllo,
>
> yantar92@gmail.com writes:
>
>> Consider calling =org-back-to-heading= for the following org entry:
>>
>> #+begin_src org
>> * Sample entry
>>
>> Some text.
>>
>> *************** TODO Inline task
>> *************** END
>>
>> Some more text.
>>
>> ->(point)<-
>>
>> Yet another piece of text.
>> #+end_src
>>
>> The expected behaviour is that the point moves to the first line of the
>> entry.
>> However, the point moves to the end of the inline task.
>>
>> Indeed, the wrong behaviour is because =outline-regexp= variable is set
>> to ="\\*+ "=, which includes inline tasks.
>
> This is the desired effect. Use the macro `org-with-limited-levels' to
> ignore headlines.
>
> Regards,
>
> --
> Nicolas Goaziou
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-11-06 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 8:10 Bug: org-back-to-heading with inline tasks above point [9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/)] yantar92
2018-11-05 20:55 ` Nicolas Goaziou
2018-11-06 3:05 ` Ihor Radchenko [this message]
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=87va5a9a7h.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).